Skip to main content

Windows 7, "Repair your computer" F8 boot option not working (SOLVED)

Thread needs solution
Beginner
Posts: 0
Comments: 1

hello, i have a problem. when i turn on my pc, it just takes me to "boot menu". i have tried to get to the advanced boot menu by pressing the F8 button after i ran the diagnostics. that said everything was fine with the pc. I turned it off then back on to press F8, but it wouldnt get passed the boot menu over and over, so in doing that i tried to get to the advanced with no luck, just took me back to regular boot. can anyone please help me with this?

Forum Star
Posts: 19
Comments: 2110

Brad:

 Your BCD is missing all of the partition reference locations. Please make a copy of the current BCD and then try the following commands. Enter each, one at a time, into a command prompt window from your Windows 7 installation DVD:

bcdedit /set {bootmgr} device partition=c:
bcdedit /set {default} device partition=d:
bcdedit /set {default} osdevice partition=d:
bcdedit /set {facca3c6-03f1-11e1-8e63-180373c7cff2} device ramdisk=[c:]\Recovery\WindowsRE\Winre.wim,{facca3c7-03f1- 11e1-8e63-180373c7cff2}
bcdedit /set {facca3c6-03f1-11e1-8e63-180373c7cff2} osdevice ramdisk=[c:]\Recovery\WindowsRE\Winre.wim,{facca3c7-03f1- 11e1-8e63-180373c7cff2}
bcdedit /set {facca3c4-03f1-11e1-8e63-180373c7cff2} device partition=d:
bcdedit /set {facca3c4-03f1-11e1-8e63-180373c7cff2} filedevice partition=d:
bcdedit /set {memdiag} device partition=c:
bcdedit /set {facca3c7-03f1-11e1-8e63-180373c7cff2} ramdisksdidevice partition=c:

If you get any error messages while entering a command, please copy down the exact text of the message and post back. When done, post the output of:

bcdedit /enum all

Forum Star
Posts: 19
Comments: 2110

Kailee:

Which operating system are you using?
Do you have an installation disk or a recovery disk for the operating system?
Am I understanding you correctly that now your PC boots OK but you can't get to the advanced boot menu? Or is it still stuck at the boot menu screen?

Anonymous

Thank you but all this is already unchecked.

Beginner
Posts: 0
Comments: 3

Mark, check off another one as "Solved". I turned it into a batch like file and ran it (list of text strings copied and pasted). It ran with errors, but still, your instructions were good enough to revive the disk after an extra reboot. Thank you for all your assistance, Mark.

Forum Star
Posts: 19
Comments: 2110

Brad:

You're welcome! Glad to hear that you got things working again.

Beginner
Posts: 0
Comments: 5

hey mark, i have the same problem like these people have but the error is different sometimes, sometimes it says winload missing or corrupted sometimes it says something I/O. the problem is that i can't even boot my windows 7 dvd so i can enter windows repair or something,
i am completely lost and have no idea what to do, i changed the HDD to my old one which still has windows xp and i'm on this xp atm, and i have the problem causing hdd connected also as my drive F: atm and i can access all files and folders without problems
please help :S

Beginner
Posts: 0
Comments: 5

anyone? :/

Forum Star
Posts: 19
Comments: 2110

Denis:

What happened to cause your Windows 7 installation to fail to boot?

To repair this you are going to need to boot your PC from a Windows 7 installation DVD or repair CD, so let's work on that issue first. Why can't your PC boot from the DVD? Can it boot from any bootable DVD or CD?

Beginner
Posts: 0
Comments: 5

don't know, the last 2 or 3 reboots when it still booted my disk always had to go trough that disk check at boot, and now it just won't boot, uhmm when i try too boot from win7 cd i get the same winload.exe error while the "Windows is loading files" screen

Beginner
Posts: 0
Comments: 5

can i expect any help here or should i go look elsewhere? :/

Forum Star
Posts: 19
Comments: 2110

Denis:

 Sorry that I was unable to respond earlier. Yes, you may have better luck looking elsewhere for a solution. This forum is specific to the disk imaging program Acronis True Image.

Your symptoms before the failure seem to indicate that you have disk errors. If you're still booting XP with the Win 7 disk attached, try running disk checks on all of the partitions on the Win 7 hard disk. Go to a command prompt and type:

 chkdsk X: /R

but substitute the letter of each partition on your Windows 7 disk for X: in the above command. The partition most likely to be corrupted is the one that Win 7 is installed on (was C: when booted to Win 7 but will have a different drive letter when viewed from Win XP).

I did some online searching for the installation media failing to complete the boot process and found that certain hardware devices may not be supported by the installation DVD and may cause the installation media to fail to boot properly. One such forum thread is here: http://windowsforum.com/threads/windows-system32-winload-exe.1488/

Beginner
Posts: 0
Comments: 5

hey mark, i really appreciate your help, the disk check is running as we speak and later i'll try something i came across the forum u posted. i'll let u know the results

Beginner
Posts: 0
Comments: 6

Hi guys

This might be a bit of a long shot but I've been trying to sort this all day!

Im fixing a friends laptop and am running into problems.

1. I cant boot from a windows disc (either a full copy or a repair CD) - it loads the windows files and then displays the "bcd is missing or corrupt.."

it tries to locate the windload file at:... windows\system32\boot\winload.exe

Im not totally sure if this is correct

2. the recovery files are located on a hidden partition.

I have included the bcdedit file if anyone can provide any information..

I am able to make changes to the bcd by running cmd as administrator.

ps.. i made some edits to the bcdedit file so I may have broken it more than fixed it =/

Attachment Size
141548-110029.txt 3.58 KB
Forum Star
Posts: 19
Comments: 2110

Russell:

I don't see any problems with the BCD that you posted.

What are the laptop's symptoms when you try to boot normally? From the BCD that you posted, the laptop should be trying to boot from the second partition on the disk (the hidden recovery partition). The most likely problem is that the wrong partition is set as "Active". Can you boot the laptop from some tool that lets you run DISKPART or some other tool to determine which partition is active? If you can't get a Windows 7 DVD or repair CD to boot, try a live Linux CD or any other partition management tool.

Beginner
Posts: 0
Comments: 6

Hi Mark. Thanks for the quick reply.

I forgot to mention that the laptop was booting normally into Windows. But I have since occurred a BSOD everyone on startup now.

The BSOD image is attached.

I cannot pass this bsod even boring into safe mode.

when I try to boot form a Windows installation CD it loads the necessary files but then fails.

I have saved all media on the laptop so I'm not worried about losing anything. I just want a fresh copy of Windows installed. Even if that means reinstalling the os as opposed to the oem recovery.

Any further help would be appreciated

Attachment Size
141562-110035.jpg 2.36 MB
Forum Star
Posts: 19
Comments: 2110

Beginner
Posts: 0
Comments: 6

Hi Mark,

I cant get the laptop to boot from a windows CD so I'm currently trying to boot with Linux Live CD.. I'll try delete the offending file and hopefully I'll get it to boot back into windows.

Will post my results soon

Beginner
Posts: 0
Comments: 6

Im not sure if im doing this correctly..

i found the partitions on the HDD using fdisk -l

i mounted a partition to /mnt/windows

i then navigated to /mnt/windows/system32/codeintegrity and deleteed the file in question..

with no luck..

any pointers?

Will creating a bootable flash usb work to get it into windows? im running out of ideas

Forum Star
Posts: 19
Comments: 2110

Russell:

That looks like the correct path. I have no idea what's going on. Have you tried a user forum for your brand of laptop?

Beginner
Posts: 0
Comments: 6

I havent as yet..

when i fdisk the HDD using Linux Live CD i noticed the "Boot" seemed to contain the "Recovery folder" and NOT the windows folder..

does this sound right?

Surely the Boot partition should be the one holding the "Windows" folder?

Is there a way to change this?

Forum Star
Posts: 19
Comments: 2110

That sounds correct and is consistent with your BCD. The boot files for Windows 7 are usually located on a small primary partition called the "System Reserved Partition". In the case of an OEM PC, the boot files are located in the recovery partition.

Beginner
Posts: 0
Comments: 6

Update:

I created, and booted from a windows 7 flash disk.. (i dont understand why the same CD wouldn't boot before)

Im currently installing a fresh copy of windows on the main partition

Just going to forget about the recovery for now (as i had everything backed up before it b0rked)

Mark, thanks for your help today and yesterday

Hopefully this will resolve my issue :)

Attachment Size
141608-110041.jpg 3.73 MB
Beginner
Posts: 0
Comments: 2

hi Mark,
recently my battery level dropped to 0 and my laptop shut down. when i tried to turn it back on it gave me the message:

insert your windows installation disc and restart the computer
choose your language settings, and then click next
click repair your computer

file \EFI\microsoft\boot\bcd
status 0xc000000d
bcd file is missing required information

i made bootable device which eventually took me to the page asking to choose between install and repair, but in repair i keep getting this message:

"This version of System Recovery Options is not compatible with the version of Windows you are trying to repair. Try using a recovery disc that is compatible with this version of Windows."

i tried both 32bit and 64bit versions, and both are returning the same info.
i saw earlier in this thread that there could be problem with other system previously installed on the same computer, but that's not the case here, because this is the only system ever installed.

it seems that i have no other options but clean install.

if you could help me get into repair option i'll be gratefull

ps the system is windows 7 home premium, 64bit (i'm pretty sure), i downloaded .iso from the internet, not the same version number as mine (x17 #####), but that's not supposed to be a problem.

Forum Star
Posts: 19
Comments: 2110

jovan m:

Try reading this forum thread from Microsoft: http://answers.microsoft.com/en-us/windows/forum/windows_7-system/this-…

Read the entire thread because it contains several suggestions for solving the problem that you are seeing. One suggestion is to disable UEFI temporarily in the BIOS before trying to boot from the repair disk.

Beginner
Posts: 0
Comments: 2

thank you for reply, Mark

after few tries, the thing with deleting partitions seems to be working.
i did the bcdedit as others in this thread, it's attached, but it appears much shorter than those.
there's a great possibility that i messed something up.

Attachment Size
142542-110191.txt 910 bytes
Beginner
Posts: 0
Comments: 5

Hi Mark,

here's my bcdedit output and my disk management screen shot.

between I have a lenovo T410, I've capture the image and deployed after that. Then I can't restore to factory and Repair option disappear.

Thanks,
Robert.

Attachment Size
150826-110503.txt 5.09 KB
150826-110506.jpg 182.91 KB
Forum Star
Posts: 19
Comments: 2110

Robert:

Your BCD is missing entries that enable the recovery environment and link to it. Here are the needed entries. Use BCDEDIT in an elevated command prompt window to enter the following:

bcdedit /set {current} recoverysequence {40fe008a-52f2-11e3-b10f-a9bc8b7f0145}
bcdedit /set {current} recoveryenabled yes

You can also delete two old entries that are no longer valid:

bcdedit /delete {0703fbbb-80e0-11df-bc04-f1393b11ec23}
bcdedit /delete {0703fbba-80e0-11df-bc04-f1393b11ec23}

There is also an entry that allows booting into the ThinkVantage restore to factory function but I don't know how it works or how it's activated. Hopefully it will work after you make the above changes.

I've attached a text file that shows what your BCD should look like after changes.

Attachment Size
150891-110509.txt 4.25 KB
Beginner
Posts: 0
Comments: 2

Hi Mark,

Like so many others here having trouble with BCD. I have a dual boot system two hard drives (Not Raided), one is windows 7 my main drive that I usually boot into. Also my other drive ,windows XP I use for flight simming.

I have read through most of this thread and think I know what I should do but don't want to bugger it up. I believe it is to do with the device entries for the recovery or repair of windows. I get the error if I need to select repair my computer option, "The boot selection failed because a required device is inaccessible"

Here is my BCDedit enum output:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {791d7284-a06c-11e0-8f3e-d295cae145cb}
displayorder {current}
{ntldr}
toolsdisplayorder {memdiag}
timeout 10
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {791d7281-a06c-11e0-8f3e-d295cae145cb}

Windows Boot Loader
-------------------
identifier {current}
device partition=G:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {791d7286-a06c-11e0-8f3e-d295cae145cb}
recoveryenabled Yes
testsigning No
osdevice partition=G:
systemroot \Windows
resumeobject {791d7284-a06c-11e0-8f3e-d295cae145cb}
nx OptIn
pae Default
quietboot Yes
sos No
debug No

Windows Boot Loader
-------------------
identifier {791d7286-a06c-11e0-8f3e-d295cae145cb}

Windows Boot Loader
-------------------
identifier {791d7288-a06c-11e0-8f3e-d295cae145cb}
device ramdisk=[G:]\Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\Winre.wim,{791d7289-a06c-11e0-8f3e-d295cae145cb}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[G:]\Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\Winre.wim,{791d7289-a06c-11e0-8f3e-d295cae145cb}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {791d7284-a06c-11e0-8f3e-d295cae145cb}
device partition=G:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=G:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=C:
path \ntldr
description Windows XP

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {791d7282-a06c-11e0-8f3e-d295cae145cb}
ramdisksdidevice unknown
ramdisksdipath \Recovery\80aefb9c-750b-11e0-be81-a980c9e4b302\boot.sdi

Device options
--------------
identifier {791d7287-a06c-11e0-8f3e-d295cae145cb}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\boot.sdi

Device options
--------------
identifier {791d7289-a06c-11e0-8f3e-d295cae145cb}
ramdisksdidevice partition=G:
ramdisksdipath \Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\boot.sdi

Forum Star
Posts: 19
Comments: 2110

John:

The recoverysequence value is incorrect in the section of the BCD that boots Windows 7. It's currently entered as {791d7286-a06c-11e0-8f3e-d295cae145cb} but should be {791d7288-a06c-11e0-8f3e-d295cae145cb}. Enter the following command in an elevated command prompt window to fix:

bcdedit /set {current} recoverysequence {791d7288-a06c-11e0-8f3e-d295cae145cb}

Test this to see if it's working properly. If so, you can delete the following "orphaned" or incorrect entries, and remove the word "recovered" from the description of the Windows Recovery Environment entry by doing these:
bcdedit /delete {791d7281-a06c-11e0-8f3e-d295cae145cb}
bcdedit /delete {791d7282-a06c-11e0-8f3e-d295cae145cb}
bcdedit /delete {791d7286-a06c-11e0-8f3e-d295cae145cb}
bcdedit /delete {791d7287-a06c-11e0-8f3e-d295cae145cb}
bcdedit /set {791d7288-a06c-11e0-8f3e-d295cae145cb} description "Windows Recovery Environment"

Beginner
Posts: 0
Comments: 2

Mark,

Perfect. Copy of new output below. Good job I asked, I thought it was the "unknowns" that were the problem. They were tho in the sense that the GUIDs were unrecognizable. Am I on the right path?

Anyway sorted now and much appreciated.

John F

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {791d7284-a06c-11e0-8f3e-d295cae145cb}
displayorder {current}
{ntldr}
toolsdisplayorder {memdiag}
timeout 10
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=G:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {791d7288-a06c-11e0-8f3e-d295cae145cb}
recoveryenabled Yes
testsigning No
osdevice partition=G:
systemroot \Windows
resumeobject {791d7284-a06c-11e0-8f3e-d295cae145cb}
nx OptIn
pae Default
quietboot Yes
sos No
debug No

Windows Boot Loader
-------------------
identifier {791d7288-a06c-11e0-8f3e-d295cae145cb}
device ramdisk=[G:]\Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\Winre.wim,{791d7289-a06c-11e0-8f3e-d295cae145cb}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale
osdevice ramdisk=[G:]\Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\Winre.wim,{791d7289-a06c-11e0-8f3e-d295cae145cb}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {791d7284-a06c-11e0-8f3e-d295cae145cb}
device partition=G:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=G:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=C:
path \ntldr
description Windows XP

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {791d7289-a06c-11e0-8f3e-d295cae145cb}
ramdisksdidevice partition=G:
ramdisksdipath \Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\boot.sdi

Forum Star
Posts: 19
Comments: 2110

John:

Do you mean the paths marked "unknown" in these two former BCD entries?
=======================================================
Device options
--------------
identifier {791d7282-a06c-11e0-8f3e-d295cae145cb}
ramdisksdidevice unknown
ramdisksdipath \Recovery\80aefb9c-750b-11e0-be81-a980c9e4b302\boot.sdi

Device options
--------------
identifier {791d7287-a06c-11e0-8f3e-d295cae145cb}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\791d7286-a06c-11e0-8f3e-d295cae145cb\boot.sdi
=================================================
They weren't doing any damage because no other entry in the BCD referred to them, so they were just sitting there doing nothing. The problem was that the recoverysequence value was referencing an empty BCD entry instead of the one that starts the recovery environment. So just one byte was in error (86h instead of 88h in the GUID).

I'm glad you got things back to working again.

Beginner
Posts: 0
Comments: 2

Hi Mark, perhaps you could help me correct whatever I did wrong when cloning from HDD to my new SSD:

Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{e3922e37-3ba5-11e3-b9a8-806e6f6e6963}
{741a0f20-3b97-11e3-ab03-916269b0289c}
{741a0f21-3b97-11e3-ab03-916269b0289c}
timeout 0

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {769f00d1-5f84-11e3-8277-806e6f6e6963}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Firmware Application (101fffff)
-------------------------------
identifier {0e46f8eb-5c7c-11e3-826d-806e6f6e6963}
description Internal EFI Shell

Firmware Application (101fffff)
-------------------------------
identifier {0e46f8ec-5c7c-11e3-826d-806e6f6e6963}
description Internal EFI Shell

Firmware Application (101fffff)
-------------------------------
identifier {1cac5435-3b8f-11e3-8255-806e6f6e6963}
description Internal Hard Disk or Solid State Disk

Firmware Application (101fffff)
-------------------------------
identifier {3818387c-51c8-11e3-825c-806e6f6e6963}
description Internal Hard Disk or Solid State Disk

Firmware Application (101fffff)
-------------------------------
identifier {741a0f20-3b97-11e3-ab03-916269b0289c}
description USB Drive (UEFI)

Firmware Application (101fffff)
-------------------------------
identifier {741a0f21-3b97-11e3-ab03-916269b0289c}
description Internal CD/DVD ROM Drive (UEFI)

Firmware Application (101fffff)
-------------------------------
identifier {741a0f23-3b97-11e3-ab03-916269b0289c}
description Internal EFI Shell

Firmware Application (101fffff)
-------------------------------
identifier {741a0f24-3b97-11e3-ab03-916269b0289c}
description Internal Hard Disk or Solid State Disk

Firmware Application (101fffff)
-------------------------------
identifier {ac187f51-5bc8-11e3-827c-806e6f6e6963}
description Internal Hard Disk or Solid State Disk

Firmware Application (101fffff)
-------------------------------
identifier {ac187f53-5bc8-11e3-827c-806e6f6e6963}
description Internal EFI Shell

Firmware Application (101fffff)
-------------------------------
identifier {e3922e37-3ba5-11e3-b9a8-806e6f6e6963}
description Internal Hard Disk or Solid State Disk

Firmware Application (101fffff)
-------------------------------
identifier {e3eb1a46-5f94-11e3-bcb2-806e6f6e6963}
description USB Hard Drive (UEFI) - KingstonDataTraveler SE9

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 8.1
locale en-US
recoverysequence {215db7ed-5f95-11e3-bcb2-fb65e3bba413}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {769f00d1-5f84-11e3-8277-806e6f6e6963}
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {215db7ed-5f95-11e3-bcb2-fb65e3bba413}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{215db7ee-5f95-11e3-bcb2-fb65e3bba413}
path \windows\system32\winload.efi
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
displaymessage Recovery
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{215db7ee-5f95-11e3-bcb2-fb65e3bba413}
systemroot \windows
nx OptIn
bootmenupolicy Standard
winpe Yes

Resume from Hibernate
---------------------
identifier {769f00d1-5f84-11e3-8277-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.efi
description Windows 8.1
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

EMS Settings
------------
identifier {emssettings}
bootems No

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {215db7ee-5f95-11e3-bcb2-fb65e3bba413}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Thanks in advance for your help

Beginner
Posts: 0
Comments: 3

Hi mark,

I have the same problem as many others here, My laptop doesn't boot into windows and I can't even repair it. The problem started when windows downloaded some updates, then some of everyday programs like office wouldn't open, I tried restoring windows to a date before updates, but it didn't go well and windows won't boot up. I have tried repairing it by windows 7 Disk (both 32 & 64 bit) but I get this message:

"This version of System Recovery Options is not compatible with the version of Windows you are trying to repair. Try using a recovery disc that is compatible with this version of Windows."

I've attached bcdedit output file.

thank you for your help in advance.

Attachment Size
151721-110542.txt 3.43 KB
Forum Star
Posts: 19
Comments: 2110

Gabriel:

I don't see anything wrong with your BCD, but I have to qualify that by saying that I have little or no knowledge of UEFI systems. The parts of the BCD that I do recognize seem fine - there is a recovery environment entry and it's linked to properly in the main Windows 8.1 entry. So I don't think that I can be of any help.

Forum Star
Posts: 19
Comments: 2110

sima om:

Your BCD entry for Windows 7 does not have a recovery sequence identified, even though one exists in the BCD. To fix, enter the following two commands into an elevated command prompt window:

bcdedit /set {default} recoverysequence {92533631-6399-11e0-b2e8-cdeaf5827b00}
bcdedit /set {default} recoveryenabled yes

The recovery environment entry in the BCD was apparently modified by using the Windows automatic repair disk function. Apparently it failed to also fix the link to this entry.

The following two commands fix some cosmetic issues with the Windows Recovery Environment entry:

bcdedit /set {92533631-6399-11e0-b2e8-cdeaf5827b00} description "Windows Recovery Environment"
bcdedit /set {92533631-6399-11e0-b2e8-cdeaf5827b00} locale en-US

Beginner
Posts: 0
Comments: 2

Thank you anyway Mark, guess I'll continue looking for a solution to boot to the recovery partition

Beginner
Posts: 0
Comments: 3

wow! Problem solved. My laptop recovered and is working perfectly.
I really appreciate your help Mark.

Beginner
Posts: 0
Comments: 3

wow! Problem solved. My laptop recovered and is working perfectly.
I really appreciate your help Mark.

Beginner
Posts: 0
Comments: 5

Hi Mark,

What's the reason, my repair is missing. I don't see anything wrong with the bcd file.

Attachment Size
153725-110626.txt 4.36 KB
Beginner
Posts: 0
Comments: 2

Hi Mark,

My repair is not working . I am getting this error.

Windows failed to start. A Recent hardware or software change might be the cause. To fix the problem:

1. Insert your windows installation disc and restart your computer.
2. Choose your langugae settings, and then click next
3. Click "repair your computer."

Status: 0xc000000e
Info: The boot selection failed because a required device is inaccessible.

This started to happen after a factory restore.

Thanks.

Attachment Size
153765-110629.txt 3.89 KB
Forum Star
Posts: 19
Comments: 2110

Robert:

I agree - I don't see anything wrong with your BCD either. Sometimes this function is difficult to activate because it requires quick timing. Typically you need to begin tapping the F8 key right after the PC power-on self-test completes but before the "starting Windows" screen appears. You have to be quick on most newer, fast PCs.

Are you able to do this step? If so, does your screen look similar to the one in step 3 of this article: http://www.sevenforums.com/tutorials/666-advanced-boot-options.html?

Forum Star
Posts: 19
Comments: 2110

Aravindh:

The second entry in your BCD with identifier {50da91bd-4f6c-11e3-8680-f01faf567a00} is missing all of the other data needed to boot into the Windows Recovery Environment. Enter the following commands into an elevated command prompt window to add the missing data:

bcdedit /set {50da91bd-4f6c-11e3-8680-f01faf567a00} device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\winre.wim,{50da91be-4f6c-11e3-8680-f01faf567a00}

bcdedit /set {50da91bd-4f6c-11e3-8680-f01faf567a00} osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\winre.wim,{50da91be-4f6c-11e3-8680-f01faf567a00}

bcdedit /set {50da91bd-4f6c-11e3-8680-f01faf567a00} path \windows\system32\winload.exe

bcdedit /set {50da91bd-4f6c-11e3-8680-f01faf567a00} description "Windows Recovery Environment"

bcdedit /set inherit {bootloadersettings}

bcdedit /set {50da91bd-4f6c-11e3-8680-f01faf567a00} systemroot \windows

bcdedit /set {50da91bd-4f6c-11e3-8680-f01faf567a00} nx OptIn

bcdedit /set {50da91bd-4f6c-11e3-8680-f01faf567a00} winpe yes

Also, the second-to-last entry in the BCD with identifier {50da91be-4f6c-11e3-8680-f01faf567a00} has "unknown" as the path to a needed device. Use the following command to add the path:

bcdedit /set {50da91be-4f6c-11e3-8680-f01faf567a00} ramdisksdidevice partition=\Device\HarddiskVolume2

Test this to see if all is working. If it is, you can delete some unneeded or incorrect entries from the BCD:

bcdedit /delete {7937d523-6541-11e3-8d8c-e1ee991c3e05}

bcdedit /delete {50da91bb-4f6c-11e3-8680-f01faf567a00}

bcdedit /delete {7937d524-6541-11e3-8d8c-e1ee991c3e05}

Beginner
Posts: 0
Comments: 2

It worked . Thanks a lot :)

Sai
Forum Member
Posts: 0
Comments: 52

Hello again Mark, you sure rock for helping people so much, I have another question for you about a strange BCD issue... trying to do an in-place upgrade for a vista machine, bcd will not allow changes to it and mentions a few strange errors... all research on the issues lead to resolutions that do not apply to this machine. perhaps something in the BCD will alert you to the issue, and perhaps using bcdedit will allow me to modify boot settings where msconfig and windows setup have failed...

The message I am most concerned about occurs after the copying files stage of windows in-place upgrade,
"Windows could not update the computer's boot configuration. Installation cannot proceed."

when doing an msconfig and attempting to remove the Setup boot parameter I get
"System Configuration cannot save the original boot configuration for later restoration. Boot changes will be reverted.
The handle is Invalid."

The system is a Toshiba Satellite A305D
Windows Vista Home Premium 32Bit
Any light you could shed on this would be appreciated, if not thanks for trying... Happy Holidays.

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device unknown
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {32ffcaa8-d9f2-11dc-bec7-00a0d1df3d8b}
displayorder {default}
{current}
toolsdisplayorder {572bcd56-ffa7-11d9-aae0-0007e994107d}
{memdiag}
timeout 30
resume No
customactions 0x1000000720001
0x54000001
custom:54000001 {572bcd56-ffa7-11d9-aae0-0007e994107d}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows Vista (TM) Home Premium (recovered)
recoverysequence {572bcd56-ffa7-11d9-aae0-0007e994107d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {f666b853-596e-11e3-b79f-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {572bcd56-ffa7-11d9-aae0-0007e994107d}

Windows Setup
-------------
identifier {default}
device partition=C:
path \$WINDOWS.~BT\Windows\system32\winload.exe
description Windows Setup
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \$WINDOWS.~BT\Windows
nx OptOut
detecthal Yes
winpe Yes

Resume from Hibernate
---------------------
identifier {f666b853-596e-11e3-b79f-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Vista (TM) Home Premium (recovered)
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Forum Star
Posts: 19
Comments: 2110

Sai:

The first entry in your BCD with ID {bootmgr} describes the boot configuration for the PC, and it has the entry "unknown" for the device. This entry should contain a reference to the partition that the machine boots from. This entry can be added using bcdedit, once we figure out the correct partition reference.

If the machine will boot into Windows, can you post a screen shot showing the Disk Management window? Type "partition" in the Vista START/SEARCH box and choose "create and format hard disk partitions" from the search hits. Drag the window large enough to read the description of the contents of each partition. We're looking for the partition marked as "Active". See the attached example.

Attachment Size
154830-110752.png 77.26 KB
Sai
Forum Member
Posts: 0
Comments: 52

there are no other hard drives installed on the computer, there is a 1.47GB unallocated space at the beginning of the drive, the drive is device 0 and the C: drive is the second partition on the drive. there used to be a recovery partition and I am assuming a couple other partitions including the 100MB system part. The drive went RAW at one point and I had to do a Partition Recovery using EASUS or some other part recovery program.

Forum Star
Posts: 19
Comments: 2110

Sai:

If the C: drive is the second partition on the disk, what is in the first partition?

Or, did you mean that the unallocated space is at the beginning of the disk and the first partition is the C: partition? This is important; it would help if I could see the screenshot from Disk Management.

Sai
Forum Member
Posts: 0
Comments: 52

yeah it's just 1.47GB Unallocated on the first partition "far left"
and 184.84GB NTFS Healthy (System, Boot, Page File, Active, Primary Partition)
on the right side...

No other partitions exist on the computer, they may have before the disk structure was compromised and it turned "RAW" but this is what I was able to get back to and actually get it booting... everything seems to work fine except for windows updates and changing boot options.. etc..
So I decided to do an In-place upgrade to repair system files as an SFC /SCANNOW was unable to fix all problems it found.

Attachment Size
154875-110758.jpg 149.14 KB
Forum Star
Posts: 19
Comments: 2110

Sai:

Good. That means that the "unknown" device reference in the first BCD entry should refer to the C: partition. I suspect that since this reference is missing, Windows setup doesn't know where to look to find the boot configuration information. That can be fixed with bcdedit. While you're at it, the resume from hibernate entry is wrong, so you might as well fix that also. Enter the following in an elevated command prompt window:

bcdedit /set {bootmgr} device partition=c:
bcdedit /set {bootmgr} resumeobject {f666b853-596e-11e3-b79f-806e6f6e6963}

Then try your in-place update again to see if it will complete. There are some other things missing in the BCD; for example, the Windows Recovery Environment entry, but perhaps Windows setup will fix those. It's worth a try. If not, they can be fixed manually later.