Boot menu at start up, 2 min of beeps before Win7 successfully starts

(Hello, people coming here with the same problem.
update/edit: the boot menu upon start up has been resolved with this

rvcjew said:

Just run an elevated command prompt in windows and put:
bcdedit /set optionsedit No
then hit enter and reboot the pc and see if it just starts up into windows normally.

Elevated Command Prompt

Malcolm.

Start up beep issue has not been resolved. Upon start up, it is still beeping and displaying "starting windows" for minutes before windows successfully starts--but not in safe mode.)

___________________________________________________________________________________
Original post
Thank you in advance for any help. I run Windows 7 Premium on a refurbished Acer that my mother gave me right after she let windows install updates,and only since then the computer has had this problem. It booted fine prior. Now when I power it on it goes straight to the boot menu, I select the operating system, then sit through 2 minutes of loud beeps while Win7 loads files then starts up. I have no recovery CD's or images (for this Acer but can burn from an Asus Win 7 64 bit) but barely know what I am doing and have tried:

*created system repair disk: successful--joy!

*System restore: successful once for 2/9/17 point but has failed for other points via safe mode, system recovery, and normal admin log in.

*windows memory diagnostic tool via system recovery: unsuccessful. Gets to end of scan, retarts, goes back to boot manager, does not display results (?) after loading windows successfully.

* Disk check via system recovery command prompt: unsuccessful? "chkdsk/r" did not work because the volume was right protected. "chkdsk c: /f /r/ /x" I tried three times and got a different message: failed to transfer logged messages, or in use by another process.

*Startup repair via boot disk and via boot manager, advanced boot options: unsuccessful with nothing attached to the computer! Grr. Both ways produced "start up repair could not detect a problem. If you have recently attached a device to this computer, ..., remove it and retart your computer."

Start up repair diagnostic and repair details
-------------------
last successful boot time: 3/19/2017
number of attempts: 2

session details
-----------------
system disk = /device/harddisk0
windows directory = d:/windows
autochk run = 0
number of root causes=1

test performed
--------------
name: check for updates
result: completed successfully. Error code = 0x0
time taken : 15ms

test performed
---------------
name system disk test
result: completed successfully. Error code = 0x0
time taken: 0ms

test performed
--------------
name: disk failure diagnosis
result: completed successfully. Error code = 0x0
time taken: 219 ms

test performed
--------------
disk metadata test
result: completed successfully. Error code = 0x0
time taken: 62 ms

test performed
--------------

name: target OS test
result: completed successfully. Error code = 0x0
time taken: 203ms

test performed
--------------

name: volume content check
result: completed successfully. Error code = 0x0
time taken: 234ms

test performed
---------------
name: boot manager diagnosis
result: completed successfully. Error code = 0x0
time taken: 0 ms

test performed
--------------

name: system boot log diagnosis
result: completed successfully. Error code = 0x0
time taken: 0ms


test performed
--------------

name: event log diagnosis
result: completed successfully. Error code = 0x0
time taken: 46ms

test performed
--------------
name: internal state check
result: completed successfully. Error code = 0x0
time taken: 246ms


test performed
--------------
name: boot status test
result: completed successfully. Error code = 0x0
time taken: 47ms

root cause found:
-----------------------------------
boot status indicates that the OS booted successfully

--------------------------

Chkdsk when in the recovery environment is not C: for your hard drive normally. It is normally another letter when you are in the recovery disc Command Prompt and if you see C:\ and you type dir then hit enter what do you see? As for the list you get at start up when in windows hit win+r and put msconfig then enter and on the boot tab is there more than one OS listed and are any of the boxes checked in that window? If you could also follow the guide below to fill in your full system specs that would also help determine the beeping.

System Info - See Your System Specs

Malcolm

Okay yeah your edit options are flagged possibly by your recovery work. Hit enter and does it boot into windows after that, if so try to get to look at the msconfig afterwards.

Malcolm

No, dont mess with any boot disk if you mean a recovery cd. Just run an elevated command prompt in windows and put:
bcdedit /set optionsedit No
then hit enter and reboot the pc and see if it just starts up into windows normally.

Elevated Command Prompt

Malcolm.

I now have my system info edited into my profile

bcdedit /set optionsedit No completed successfully

Upon restart it did not show the boot menu I was seeing so that problem seems to be resolved. :) Edit: nevermind. it is still doing it.

But it still beeped for a few minutes before successfully starting windows. I still only have the power cord connected to the computer and nothing in the disk drive.

That beeping is normally windows thinks you have a stuck key. Do you have any broken keys on the keyboard of the laptop?

Malcolm

It is making the beeping when it says starting windows right?
EDIT: It could be a modifier key that is stuck or broken like the shift, alt keys ect.

Malcolm