Skip to main content

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

Thread needs solution
Forum Star
Posts: 19
Comments: 2110

#351

For the recovery image WinRE.wim on your recovery partition and on your USB flash drive, is the file winload.exe located at \Windows\System32\boot\winload.exe or is it located at \Windows\System32\winload.exe? The one on the flash drive uses the first path and the one on the recovery partition uses the second path. The orphaned BCD entry on your hard disk also references the first path.

Let's try this. Change the path on the recovery partition to see if it will complete the boot process into the Windows installer correctly:

bcdedit /set {6abef737-3411-11de-8ea8-ac010edf8f1e} path \Windows\System32\boot\winload.exe

Then try booting into the recovery environment on the hard disk again.

I don't see a problem with the BCD on your flash drive unless that's the one that has the incorrect path to Winload.exe.

Beginner
Posts: 0
Comments: 1

#352

I have a Sony Vaio computer which just started giving startup error. I don't have recovery CD. I am able to get to command prompts. I don't see anything under C:. D: does show windows and other files.
Any help to fix this is greatly appriciated.

Forum Star
Posts: 19
Comments: 2110

#353

Viral:

Please consult a Sony user forum for help.

Beginner
Posts: 0
Comments: 6

#354

Hi Mark,

I was wondering if you could help me with my Repair My Computer 0xc000000e error. The files listed under [\Device\HarddiskVolume2] exist. Here is my bcdedit /enum all output:
++++++++++++++++++++++++++++++++

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {f6b8802b-a758-11df-8e2f-d2556076c230}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {072cc690-502f-11df-a91e-c37c39b119af}

Windows Boot Loader
-------------------
identifier {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{93fb8a38-79ef-11e2-90cb-cc6704a6e5bf}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{93fb8a38-79ef-11e2-90cb-cc6704a6e5bf}
systemroot \windows
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {072cc690-502f-11df-a91e-c37c39b119af}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {f6b8802b-a758-11df-8e2f-d2556076c230}
nx OptIn

Windows Boot Loader
-------------------
identifier {f6b8802d-a758-11df-8e2f-d2556076c230}

Resume from Hibernate
---------------------
identifier {f6b8802b-a758-11df-8e2f-d2556076c230}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

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

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 {072cc691-502f-11df-a91e-c37c39b119af}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {93fb8a38-79ef-11e2-90cb-cc6704a6e5bf}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\windowsre\boot.sdi

Device options
--------------
identifier {f6b8802e-a758-11df-8e2f-d2556076c230}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\f6b8802d-a758-11df-8e2f-d2556076c230\boot.sdi
+++++++++++++++++++++++++++

I've been reading through this thread but it seems that my case is a little bit different and I'm not sure which GUID and command that I should execute. I really appreciate if you could look into this when you got a chance.

Thanks!

Forum Star
Posts: 19
Comments: 2110

#355

wiki mee:

The recoverysequence value is pointing to the wrong entry in the BCD. Try the following command from an elevated command prompt window:

bcdedit /set recoverysequence {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf}
bcdedit /set {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf} description "Windows Recovery Environment"
bcdedit /set {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf} locale en-US

If this fixes the problem then you can delete the orphaned BCD entries:

bcdedit /delete {f6b8802d-a758-11df-8e2f-d2556076c230}
bcdedit /delete {f6b8802e-a758-11df-8e2f-d2556076c230}

bcdedit /delete {072cc690-502f-11df-a91e-c37c39b119af}
bcdedit /delete {072cc691-502f-11df-a91e-c37c39b119af}


Beginner
Posts: 0
Comments: 6

#356

Hi Mark,

I didn't expect a response this fast and the best of all, it fixed the F8 Repair My Computer 0xc000000e right away. You are amazing. I wish I can give a point/star to a user in this forum.

Thanks again!

Beginner
Posts: 0
Comments: 6

#357

Hi Mark,

Sorry to bother you again. So, I ran the bcdedit /delete {072cc691-502f-11df-a91e-c37c39b119af} as per your recommendation to clean up the orphanced BCD entries. As soon as the command was executed, I could not find 'Repair Your Computer' in the F8 menu anymore. Is there any way I can undo or recreate this entry?

Thanks in advance.

Beginner
Posts: 0
Comments: 6

#358

Upon further investiagion, I found that this is related to the reagentc. Here is the output from reagentc /info:
++++++++++++++++++++
WIndows RE enabled: 1
WIndows RE staged: 0
Setup enabled: 0
Custom recovery tool: 0
BCD ID: {072cc690-502f-11df-a91e-c37c39b119af}
++++++++++++++++++++

I think now I need to find a way to restore this line in bcdedit /enum all:
++++++++++++++++++++
Windows Boot Loader
-------------------
identifier {072cc690-502f-11df-a91e-c37c39b119af}
++++++++++++++++++++

Or perhaps changed the reagentc's BCD ID to {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf}. I might be wrong though :) , any feedback are welcome.

Beginner
Posts: 0
Comments: 6

#359

Hi Mark, found the solution - by referring to your earlier posts :)

I tried to regenerated the reagentc's BCD ID by running this command:
reagentc /disable
reagentc /enable

After enabling reagentc, the BCD ID is automatically regenerated with the correct GUID: {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf}

Repair Your Computer is now showing up in F8 menu and I'm able to restore successfully.

What a learning curve and thanks!

Beginner
Posts: 0
Comments: 6

#360

One thing to note though, I am not sure why - after factory image restore image process (I successfully tried 3 times today), I always have to:
1. Set the recoverysequence to the correct GUID. Was: {072cc690-502f-11df-a91e-c37c39b119af}, should be: {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf}. If this is not set, the Repair Your Computer will not show up in F8 Advanced Boot Options.

2. Disable and enable reagentc again. Was: {072cc690-502f-11df-a91e-c37c39b119af}, should be: {93fb8a37-79ef-11e2-90cb-cc6704a6e5bf}. If this is not set, the Repair Your Computer will point to your normal OS boot.

My system is Dell Vostro 3400 with Windows 7 OEM Pro where the BCD and recovery disk is in the hidden partition.

The original hard drive is a spindle but I upgraded it to SSD like 2 years ago using some free cloning tools, never bothered to restore to factory image until today.

Just FYI.

Forum Star
Posts: 19
Comments: 2110

#361

wiki mee:

Your PC originally had the Windows Recovery Environment BCD entry with the ID {072cc690-502f-11df-a91e-c37c39b119af}, apparently. When you ran automated recovery, a new entry was generated with a new ID. If you then do a restore to factory settings, the file used by reagentc (with the new ID), and located at C:\Windows\System32\Recovery\Reagent.xml is replaced with the version in the factory image, which references the old ID.

Based on what you observed, running the Dell factory restore must only replace the main Windows partition and not affect anything on the recovery partition. Since your BCD is located on the recovery partition, it apparently isn't affected by a factory restore, or at least the settings for Windows Recovery Environment aren't affected.

If the behavior following a factory restore bothers you then you could, in theory, do this:
1. Print out a copy of the BCD contents
2. Delete the BCD entry for the Windows Recovery Environment and the one at the end for Device Options (bcdedit /delete ...)
3. Create new entries for each but use the old ID (bcdedit /create ...)
4. Replace all of the lines currently present in each of these entries (bcdedit /set ...)
5. Change any references to the new ID in any other entries so that they refer to the old ID instead (bcdedit /set ...)

Beginner
Posts: 0
Comments: 2

#362

hi,first let me start by saying that this is an awesome thread..now i have the exact same problem with OPs the repair computer from f8 menu is missing..i tried to apply your directions to my case but as i didn't exactly know what i was doing(some really advanced stuff right there) it didn't work..so i am wondering if you can help..
the C:/Recovery exists C:\Recovery\f268fb25-02e2-11e2-9e9f-8e0645807138
i run bcd and here is the results:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {current}
resumeobject {f268fb25-02e2-11e2-9e9f-8e0645807138}
displayorder {f268fb26-02e2-11e2-9e9f-8e0645807138}
{current}
{1d49a2dd-65c6-11e2-be7f-001d60d7f2bb}
toolsdisplayorder {memdiag}
timeout 10

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \Windows
resumeobject {f268fb23-02e2-11e2-9e9f-8e0645807138}
nx OptIn
numproc 2
usefirmwarepcisettings No

Windows Boot Loader
-------------------
identifier {f268fb26-02e2-11e2-9e9f-8e0645807138}
device partition=D:
path \Windows\system32\winload.exe
description Windows 8
locale en-US
inherit {bootloadersettings}
recoverysequence {f268fb27-02e2-11e2-9e9f-8e0645807138}
integrityservices Enable
recoveryenabled Yes
custom:17000077 352321653
osdevice partition=D:
systemroot \Windows
resumeobject {f268fb25-02e2-11e2-9e9f-8e0645807138}
nx OptIn
numproc 2
custom:250000c2 1
usefirmwarepcisettings No

Windows Boot Loader
-------------------
identifier {f268fb27-02e2-11e2-9e9f-8e0645807138}
device ramdisk=[D:]\Recovery\f268fb27-02e2-11e2-9e9f-8e06458071
38\Winre.wim,{f268fb28-02e2-11e2-9e9f-8e0645807138}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
custom:15000065 3
custom:15000066 3
osdevice ramdisk=[D:]\Recovery\f268fb27-02e2-11e2-9e9f-8e06458071
38\Winre.wim,{f268fb28-02e2-11e2-9e9f-8e0645807138}
systemroot \windows
nx OptIn
custom:250000c2 1
winpe Yes

Windows Boot Loader
-------------------
identifier {f268fb29-02e2-11e2-9e9f-8e0645807138}
device ramdisk=[C:]\Recovery\f268fb25-02e2-11e2-9e9f-8e06458071
38\Winre.wim,{f268fb2a-02e2-11e2-9e9f-8e0645807138}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\f268fb25-02e2-11e2-9e9f-8e06458071
38\Winre.wim,{f268fb2a-02e2-11e2-9e9f-8e0645807138}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {f268fb23-02e2-11e2-9e9f-8e0645807138}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {f268fb25-02e2-11e2-9e9f-8e0645807138}
device partition=D:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
recoverysequence {f268fb27-02e2-11e2-9e9f-8e0645807138}
recoveryenabled Yes
custom:17000077 352321653
filedevice partition=D:
filepath \hiberfil.sys
custom:25000008 1
debugoptionenabled No

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

Real-mode Boot Sector
---------------------
identifier {1d49a2dd-65c6-11e2-be7f-001d60d7f2bb}
device partition=D:
path \ubuntu\winboot\wubildr.exe
description Ubuntu

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 {f268fb28-02e2-11e2-9e9f-8e0645807138}
description Windows Recovery
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\f268fb27-02e2-11e2-9e9f-8e0645807138\boot.sdi

Device options
--------------
identifier {f268fb2a-02e2-11e2-9e9f-8e0645807138}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\f268fb25-02e2-11e2-9e9f-8e0645807138\boot.sdi

Thanks in advance

Forum Star
Posts: 19
Comments: 2110

#363

Spyros:

You have a complex setup with Windows 7, Windows 8, and WUBI installed as bootable operating systems. It looks to me like Windows 8 recovery entries are correct, so I'm assuming that this works correctly, and that you are aware that you cannot access W8 recovery from the F8 key; Microsoft removed this feature from Windows 8. To reach the recovery environment for W8 you need to access the settings menu from within W8 or from the control panel.

Since the recovery entries for Windows 7 don't look correct, I am going to assume that Windows 7 recovery is broken, correct? The pointer to the recovery loader is missing and recovery is not enabled. To fix, add these two BCD entries from an elevated command prompt window:

bcdedit /set {current} recoverysequence {f268fb29-02e2-11e2-9e9f-8e0645807138}
bcdedit /set {current} recoveryenabled yes

You can also make two cosmetic tweaks to the recovery loader for W7 to fix a blank locale entry and to remove the word "Recovered" from the description (added by Windows automatic repair):

bcdedit /set {f268fb29-02e2-11e2-9e9f-8e0645807138} locale en-US
bcdedit /set {f268fb29-02e2-11e2-9e9f-8e0645807138} description "Windows 7 Recovery Environment"

Hopefully this will fix your problem.

Beginner
Posts: 0
Comments: 2

#364

wow this is amazing!!..yes i was talking about windows 7 and the bcd entries fixed my problem at last..i didn't know that about windows 8 thanks for pointing out..do you know what may have caused the problem so i be careful in the future won't happen again?

Thanks Mark i am really grateful..Keep up the good work!!

Forum Star
Posts: 19
Comments: 2110

#365

Spyros:

One reason may be if you move or resize the W7 partition, the BCD entries that refer to partitions (partition = C:, etc.) do so by absolute sector location. So the BCD needs to be repaired afterwards. W7 automatic repair will do some of this repair but it seems that it cannot fix the boot loader for the recovery environment automatically; this must be done manually.

I also wonder whether the W8 installer will disable W7 recovery environment in an attempt to prevent a user from using W7 recovery to fix W8 accidentally. This is only a guess on my part - I haven't tested this.

I'm glad that you were able to fix your problem.

Beginner
Posts: 0
Comments: 2

#366

Hi Mark,

Would you mind looking at my info? I am having same problem, and I want to restore the factory image. My computer is a DELL XPS L501X, I did replaced the hardrive with a new one after cloned everything with ATI.

I have a Partition called Recovery without any drive letter specified for it, I also have an hidden folder called "System Recovery" in the C drive but I can't access it (Access denied). I finally find out that winre.wim file is located in the Recovery partition (for the purpose I named it E) in the folder \Recovery\windowsre

Here is the output from bcdedit /enum all:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {4bfaa7ef-f5bf-11df-ae77-f04da259e42e}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
recoverysequence {4bfaa7f1-f5bf-11df-ae77-f04da259e42e}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {4bfaa7ef-f5bf-11df-ae77-f04da259e42e}
nx OptIn

Windows Boot Loader
-------------------
identifier {4bfaa7f1-f5bf-11df-ae77-f04da259e42e}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{4bfaa7f2-f5bf-11df-ae77-f04da259e42e}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{4bfaa7f2-f5bf-11df-ae77-f04da259e42e}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {4bfaa7ef-f5bf-11df-ae77-f04da259e42e}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

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

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 {4bfaa7f2-f5bf-11df-ae77-f04da259e42e}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

----- end of the file -----

Any help will be welcome!

Francois

Forum Star
Posts: 19
Comments: 2110

#367

Francois:

The "Device Options" entry at the end of the BCD lists "unknown" for its device location.

Use Windows Disk Management to assign drive letter E to the recovery partition again. Then fix the entry using the following command, entered into an elevated command prompt window:

bcdedit /set {4bfaa7f2-f5bf-11df-ae77-f04da259e42e} ramdisksdidevice partition=E:

Then you can remove drive letter E: from the recovery partition.

Beginner
Posts: 0
Comments: 2

#368

WoW Mark!!! Worked right and very well!!! I'm impressed!! Do you have any idea why this entry was incorrect? Is it related to the fact I did cloned the drive?

Thanks a lot!

Francois

Forum Star
Posts: 19
Comments: 2110

#369

Francois:

Usually a device location shows as "unknown" if the starting sector of the partition ends up in a different location on the clone compared to the source. If your clone process changed the size of any of the partitions then that might have happened.

Beginner
Posts: 0
Comments: 1

#370

What does Ren C:\boot.ini to boot ini.bak do if malware removed registry items & i am stuck in a loop trying to get out of safe mode after manually entering safe mode why do i have to rename the boot.ini file then change it back once i am out of safe mode through msconfig?

Forum Star
Posts: 19
Comments: 2110

#371

Mark:

If you are talking about Windows Vista, Windows 7, or Windows 8 then boot.ini doesn't do anything; it isn't used any more.

If you are talking about Windows XP then you are in the wrong forum area. This thread is about the Windows Recovery Environment for the newer operating systems.

Beginner
Posts: 0
Comments: 1

#372

Hi Mark, Please can you help me. i wanted to restore my laptop into factory setting but f8 boot option is not working.. PLEASE HELP.. THANK YOU IN ADVANCE..;)

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {e1272e24-f52c-11de-8369-dddcb41e0d4e}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 3

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {e1272e26-f52c-11de-8369-dddcb41e0d4e}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {e1272e24-f52c-11de-8369-dddcb41e0d4e}
nx OptIn

Windows Boot Loader
-------------------
identifier {e1272e26-f52c-11de-8369-dddcb41e0d4e}
device ramdisk=[C:]\Recovery\e1272e26-f52c-11de-8369-dddcb41e0d4e\Winre.wim,{e1272e27-f52c-11de-8369-dddcb41e0d4e}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\e1272e26-f52c-11de-8369-dddcb41e0d4e\Winre.wim,{e1272e27-f52c-11de-8369-dddcb41e0d4e}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {e1272e24-f52c-11de-8369-dddcb41e0d4e}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

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

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 {e1272e27-f52c-11de-8369-dddcb41e0d4e}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\e1272e26-f52c-11de-8369-dddcb41e0d4e\boot.sdi

Forum Star
Posts: 19
Comments: 2110

#373

Edith:

I don't see anything wrong with your BCD, although it looks like a plain-vanilla Windows 7 installation; not like a recovery tool set up by a laptop manufacturer. A likely reason that you cannot access the advanced boot options via the F8 key is one of timing - timing of when you hit the F8 key is very critical and must be done right before Windows starts to boot. A method that I sometimes use is to wait for the BIOS power-on self-test to complete, then rapidly keep hitting the F8 key until you see the menu. If you see the Windows logo then you weren't fast enough.

Some laptop manufacturers offer a set of recovery disks, so if you do get the PC to boot into the advanced boot options menu and you can't find any menus from your laptop manufacturer that will let you restore the PC to factory state, then check with the manufacturer to see if you can get recovery disks.

Beginner
Posts: 0
Comments: 11

#374

NEXT

Beginner
Posts: 0
Comments: 11

#375
elton simon wrote:

Hi.. i have the boot.sdi and Winre.wim C:\Recovery\8a75ade4-a059-11e2-b2f8-92df666e1921

My hp_recovery don't start, anybody can help me?

bcdoutput attach

Thanks

Attachment Size
129278-107314.txt 4.6 KB
129278-107317.jpg 77.55 KB
Forum Star
Posts: 19
Comments: 2110

#376

Elton:

Look on your HP_Recovery partition (D:) for these two files:

D:\Recovery\WindowsRE\Winre.wim
D:\Recovery\WindowsRE\boot.sdi

Are these files present? You may need to enable display of both Hidden and "Protected Operating System" files in order to see them.

Beginner
Posts: 0
Comments: 11

#377

Hi Mark,

I have the two files:

D:\Recovery\WindowsRE\Winre.wim
D:\Recovery\WindowsRE\boot.sdi

Forum Star
Posts: 19
Comments: 2110

#378

Elton:

I don't see any problems with the BCD. The recoverysequence value in the main Windows 7 boot manager entry is {f5784620...}, which points to the correct boot manager entry {f5784620...}. This entry links to the files on the D: partition that you listed above. Also, the links to the Boot Options (last entry in the BCD) are correct. So this should work. I don't see why it doesn't.

Could you describe what happens when you try to enter the recovery environment? Do you see the screens shown in reply #153 of this thread?

Beginner
Posts: 0
Comments: 11

#379

Mark: First I have notebook Hp Probook 4530s.

I used the F11 one time and my notebook back to original fact funct.

Later, i try use the F11 and not functioned, when i get he WIN7DVD and formatted.

Now I can back to original factory functions through HP RECOVERY (press F11)

When restart or start my computer i can't open the recovery hp (press F11). When i press f11 start windows normaly.

When press space bar see the same screen of #153, but i can't open HP RECOVERY. Go to screen of repair windows (and i can't repair)

I have other HP Probook 4530s, and the F11 is OK. But i can't create DVD to back to original factory functions in another (notebook).

Thanks

Forum Star
Posts: 19
Comments: 2110

#380

Elton:

There may have been a custom entry in the BCD to access HP Recovery that got wiped out when you reinstalled Windows 7.

Can you post the BCD of the other HP 4530; the one where F11 is working?

Beginner
Posts: 0
Comments: 11

#381

Attach

Attachment Size
129482-107362.txt 3.79 KB
Forum Star
Posts: 19
Comments: 2110

#382

Elton:
Thank you for posting that. I think that I see the issue. The first entry in the BCD on the working PC is:

Gerenciador de Inicializa??o do Windows
--------------------
identificador {bootmgr}
device partition=G:
description Windows Boot Manager
locale pt-BR
inherit {globalsettings}
extendedinput Yes
default {current}
resumeobject {a7af4856-9c34-11e2-b2cf-e6ea224d12c3}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
customactions 0x1000085000001
                       0x5400000f
custom:5400000f {a7af4858-9c34-11e2-b2cf-e6ea224d12c3}

Note the lines at the end that are custom actions; they map the F11 key to the entries for HP Recovery. These are missing in your other PC's BCD.
The document reference for setting up a custom OEM action is here:

http://download.microsoft.com/download/9/c/5/9c5b2167-8017-4bae-9fde-d599bac8184a/OEMBoot_Vista.doc

Let's see if I can get this right - the syntax is very tricky. From an elevated command prompt, enter the following:

bcdedit /set {bootmgr} custom:0x000000005400000f {f5784620-a07d-11e2-9816-f66f3bf22382}
bcdedit /set {bootmgr} customactions 0x0001000085000001 0x000000005400000f

I've never tried this before, so there are no guarantees that it will work. If you get any error messages, let me know what they are (exact text, please).

Beginner
Posts: 0
Comments: 11

#383

Mark:

In command prompt:

bcdedit /set {bootmgr} custom: 0x000000005400000f {f5784620-a07d-11e2-9816-f66f3bf22382}
the data type of the specified element is not recognized or does not apply to specified input
run "BCEdit /?" for assistance from the command line.
Parameter incorrect.

bcdedit /set {bootmgr} customactions 0x0001000085000001 0x000000005400000f
the operation was completed with success

F11 not work.

I can copy the files of Notebook to another? (F11 work to F11 don't work)? solve it?

I think: somehow copy the entire hd f11ok for f11 that does not work, just changing the cdkey windows after

Attachment Size
129540-107383.txt 4.68 KB
Forum Star
Posts: 19
Comments: 2110

#384

Elton:

I had a space between custom: element and the hex number that follows the :, so this is most likely the problem. In reply #382, I've edited the command to remove the extra space. Try re-entering this (first) command. The other (second) command was entered into the BCD properly - you can see it in the file bcd.txt that you posted.

You should not copy the BCD from your other notebook - each has different {ID} values.

Beginner
Posts: 0
Comments: 11

#385

bcdedit /set {bootmgr} custom: 0x000000005400000f {f5784620-a07d-11e2-9816-f66f3bf22382}
the operation was completed with success

But F11 not work. (simply enter in windows)

I edit my comment #383 about format all files of hd F11 not work and copy all files hd F11 work.

Forum Star
Posts: 19
Comments: 2110

#386

Elton:

Please post the current BCD contents again (bcdedit /enum all).

Beginner
Posts: 0
Comments: 11

#387

here

Attachment Size
129551-107386.txt 4.74 KB
Forum Star
Posts: 19
Comments: 2110

#388

Elton:

I forgot to add the statement that enables extended function keys. Please add the following statement to the BCD:

bcdedit /set {bootmgr} extendedinput yes

Let me know if that works.

Forum Star
Posts: 46
Comments: 2760

#389

Mark,

You never cease to amaze me with your knowledge of this topic. I have learned a great deal reading these posts.

Thanks for the time you spend in this (SOLVED) post.

James

Forum Star
Posts: 19
Comments: 2110

#390

Thanks, James. I didn't know anything about the BCD when this thread was started. It all started when I screwed up my own PC when Vista came out and had to figure out how to fix it. The rest has been OJT (on-the-job training).

Beginner
Posts: 0
Comments: 11

#391

Hi Mark.

Now I'm traveling without notebook, back after tomorrow.

Thankss

Beginner
Posts: 0
Comments: 11

#392

Mark Wharton:

It worked! Perfect! Thank you! I'm your fan

:D

Forum Star
Posts: 19
Comments: 2110

#393

Elton:

I am glad that worked. If it wasn't for you having a second working laptop I would not have figured that out.

I noticed in your BCD that most of the sections are set to Brazilian Portuguese but some are set to US English. Probably the Windows installer did that. If you want to change them back, here are the entries:

bcdedit /set {bootmgr} locale pt-BR

bcdedit /set {f5784620-a07d-11e2-9816-f66f3bf22382} locale pt-BR

bcdedit /set {memdiag} locale pt-BR

Beginner
Posts: 0
Comments: 11

#394

thanks again ;D

Sai
Forum Member
Posts: 0
Comments: 52

#395

Hello, looks like quite a few Dell users have been helped on this forum, here is my issue, hope you can help.

Dell hard drive was dying, having issues with bad sectors, etc...

Cloned the drive to a new one but it wouldn't boot, used Gimagex to apply the Factory.wim file and got windows booting, was able to get dell local backup/restore program to make factory restore disks, blanked out the hard drive and ran the restore disks, dell is back to factory defaults but when I press F8 and get the boot menu even though there is a "Repair your computer" option it just boots into regular windows mode instead of going into the WinRE dell repair utility....

Any help would be great..

Attached a readout of my bcdedit /enum all

Dell Studio 1555 Windows 7

Attachment Size
131332-107788.txt 3.64 KB
Forum Star
Posts: 19
Comments: 2110

#396

Sai:

The second entry in your BCD (the one that boots Windows 7) has an incorrect value for the recoverysequence. The correct value is the ID for the third entry in the BCD {110215ad-877e-11de-bb0f-adba867b8d4e}.

To fix, enter the following command in an elevated command prompt window:

bcdedit /set {current} recoverysequence {110215ad-877e-11de-bb0f-adba867b8d4e}

Sai
Forum Member
Posts: 0
Comments: 52

#397

Dude, you are the man !

How do you know so much about this stuff? I'd love to know how to get more knowledge on the inner workings of Windows... I consider myself to be fairly knowledgeable but this stuff is beyond me as I have no reference point on where to begin... Thanks again Mark, you are the best. :D

Beginner
Posts: 0
Comments: 4

#398

Hello Mark, so I have some trouble with my windows 7 not having a system protection to enable the system recovery. I've read some of the feedbacks you gave, but I tried checking if my computer has C://Recovery, and I didn't see anything. What am I supposed to do? Please help me, Thank You.

Forum Star
Posts: 19
Comments: 2110

#399

vi ta:

Could you post the contents of your BCD? Enter the following into an elevated command prompt window:
bcdedit /enum all > %userprofile%\desktop\bcd.txt

After running the command there should be a text file on your desktop named bcd.txt. Please attach it to your next post. A screenshot of the Disk Management window showing the layout of your disk would also be helpful.

Beginner
Posts: 0
Comments: 1

#400

Hey Mark,
I just recovered from a pretty nasty virus and was hoping to restore the factory settings when I encountered the issue with the "Repair your computer" F8 boot option not working. It brings up the starting windows screen after attempting to load the files. I have followed some of your advice in the forum, but keep getting myself turned around so I did a system restore to the day after I discovered I was unable to restore the factory settings (the virus seems to have deleted prior system restore points) in the hopes of receiving advice specific to my issue. The virus has been removed, chkdsk doesn't show any issues, sfc /scannow stops at 58%, using a restore disk created from the control panel causes a boot manager error associated with file:\windows\system32\boot\winload.exe, status:0xc00...00d, I am unable to find the C:\recovery folder. My BCDedit is attached. My knowledge of computers is limited, but I am good at following directions. Also, I'd like to note that my computer boots fine and seems to have no issues besides being unable to restore to factory settings, and I do not know anyone with the same model of computer or even windows 7. Any help is appreciated.

Thank You,
Jordan

Attachment Size
131522-107827.txt 3.63 KB