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

Stephane:

You're welcome.

Hi Mark,

I have a laptop that doesn't boot at all, it keep entering repair mode. here's my bcd output anything wrong with it?

(It's french windows)

Gestionnaire de d?marrage Windows
---------------------------------
identificateur {bootmgr}
device partition=E:
description Windows Boot Manager
locale fr-FR
inherit {globalsettings}
default {default}
resumeobject {aa71ffe2-be44-11e0-b411-60eb69a3eb77}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Chargeur de d?marrage Windows
-----------------------------
identificateur {default}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale fr-FR
inherit {bootloadersettings}
recoverysequence {aa71ffe4-be44-11e0-b411-60eb69a3eb77}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {aa71ffe2-be44-11e0-b411-60eb69a3eb77}
nx OptIn

Chargeur de d?marrage Windows
-----------------------------
identificateur {aa71ffe4-be44-11e0-b411-60eb69a3eb77}
device ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{aa71ffe5-be44-11e0-b411-60eb69a3eb77}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{aa71ffe5-be44-11e0-b411-60eb69a3eb77}
systemroot \windows
nx OptIn
winpe Yes

Reprendre ? partir de la mise en veille prolong?e
-------------------------------------------------
identificateur {aa71ffe2-be44-11e0-b411-60eb69a3eb77}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale fr-FR
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Testeur de m?moire Windows
--------------------------
identificateur {memdiag}
device partition=E:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale fr-FR
inherit {globalsettings}
badmemoryaccess Yes

Param?tres EMS
--------------
identificateur {emssettings}
bootems Yes

Param?tres du d?bogueur
-----------------------
identificateur {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

Erreurs de m?moire RAM
----------------------
identificateur {badmemory}

Param?tres globaux
------------------
identificateur {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Param?tres du chargeur de d?marrage
-----------------------------------
identificateur {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}

Param?tres de l'hyperviseur
-------------------
identificateur {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200

Param?tres du chargeur de reprise
---------------------------------
identificateur {resumeloadersettings}
inherit {globalsettings}

Options de p?riph?rique
-----------------------
identificateur {aa71ffe5-be44-11e0-b411-60eb69a3eb77}
description Ramdisk Options
ramdisksdidevice partition=E:
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Robert:

There doesn't appear to be anything wrong with the BCD, so there must be a problem that's preventing Windows from starting, so it fails over to the recovery environment.

I would start by troubleshooting the two most-common causes of failure - memory and hard disk. From the recovery menu, try running the memory test to rule out RAM failures. If the RAM is OK, next try running chkdsk /R from a command prompt on each partition, especially the one that the operating system is on.

Hello again Mark, I see you are keeping up the good work. You are a saint for doing this for the masses...

I have a request as well, HP desktop running Windows 7. Computer boots fine into safe mode and normal mode. F8 Repair your computer option is broken though, when "Repair your computer" is pressed it returns a Windows Boot Manager error code 0xc000000e message, when pressing enter it boots to windows normally.

Disk Structure is 102MB NTFS System partition, Healthy (System, Active, Primary Partition), HP C: 1386.25GB NTFS Healthy (Boot, Page File, Crash Dump, Primary Partition), FACTORY IMAGE D: 10.91GB NTFS Healthy (Primary Partition)

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

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
extendedinput Yes
default {current}
resumeobject {bfdd8840-01f8-11df-a57d-e0cb4e04fa1a}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
customactions 0x1000085000001
0x5400000f
custom:5400000f {bfdd8842-01f8-11df-a57d-e0cb4e04fa1a}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {bfdd8842-01f8-11df-a57d-e0cb4e04fa1a}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {bfdd8840-01f8-11df-a57d-e0cb4e04fa1a}
nx OptIn

Windows Boot Loader
-------------------
identifier {bfdd8842-01f8-11df-a57d-e0cb4e04fa1a}

Windows Boot Loader
-------------------
identifier {bfdd8844-01f8-11df-a57d-e0cb4e04fa1a}
device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{bfdd8845-01f8
-11df-a57d-e0cb4e04fa1a}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{bfdd8845-01f8
-11df-a57d-e0cb4e04fa1a}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {bfdd8840-01f8-11df-a57d-e0cb4e04fa1a}
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\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 {bfdd8843-01f8-11df-a57d-e0cb4e04fa1a}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {bfdd8845-01f8-11df-a57d-e0cb4e04fa1a}
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Thanks again mate, hope it's an easy fix. Cheers!

Sai:

Should be an easy fix. Links to the recovery environment in your BCD are incorrect. You need to change two entries to fix them. Enter the following commands into an elevated command prompt window:

bcdedit /set {bootmgr} custom:5400000f {bfdd8844-01f8-11df-a57d-e0cb4e04fa1a}
bcdedit /set {current} recoverysequence {bfdd8844-01f8-11df-a57d-e0cb4e04fa1a}

Test to see if the recovery environment is now working. If so, the following commands remove orphaned BCD entries and fix some appearance issues:

bcdedit /set {bfdd8844-01f8-11df-a57d-e0cb4e04fa1a} description "Windows Recovery Environment"
bcdedit /set {bfdd8844-01f8-11df-a57d-e0cb4e04fa1a} locale en-US
bcdedit /delete {bfdd8842-01f8-11df-a57d-e0cb4e04fa1a}
bcdedit /delete {bfdd8843-01f8-11df-a57d-e0cb4e04fa1a}

Hello Mark, your fix did indeed work as intended, the only error I received was at the end with the last two commands, if this is a problem let me know. Otherwise thanks again for your quality help and as always it is greatly appreciated. Cheers!

C:\Windows\system32>bcdedit /delete {bfdd8842-01f8-11df-a57d-e0cb4e04fa1a}
An error occurred while attempting to delete the specified entry.
The system cannot find the file specified.

C:\Windows\system32>bcdedit /delete {bfdd8843-01f8-11df-a57d-e0cb4e04fa1a}
An error occurred while attempting to delete the specified entry.
The system cannot find the file specified.

Current BCDEdit /enum all:

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

C:\Windows\system32>bcd /enum all
'bcd' is not recognized as an internal or external command,
operable program or batch file.

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
extendedinput Yes
default {current}
resumeobject {bfdd8840-01f8-11df-a57d-e0cb4e04fa1a}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
customactions 0x1000085000001
0x5400000f
custom:5400000f {bfdd8846-01f8-11df-a57d-e0cb4e04fa1a}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {bfdd8846-01f8-11df-a57d-e0cb4e04fa1a}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {bfdd8840-01f8-11df-a57d-e0cb4e04fa1a}
nx OptIn

Windows Boot Loader
-------------------
identifier {bfdd8844-01f8-11df-a57d-e0cb4e04fa1a}
device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{bfdd8845-01f8
-11df-a57d-e0cb4e04fa1a}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{bfdd8845-01f8
-11df-a57d-e0cb4e04fa1a}
systemroot \windows
winpe Yes

Windows Boot Loader
-------------------
identifier {bfdd8846-01f8-11df-a57d-e0cb4e04fa1a}
device ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{bfdd8847-01f8
-11df-a57d-e0cb4e04fa1a}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[D:]\Recovery\WindowsRE\Winre.wim,{bfdd8847-01f8
-11df-a57d-e0cb4e04fa1a}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {bfdd8840-01f8-11df-a57d-e0cb4e04fa1a}
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\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 {bfdd8845-01f8-11df-a57d-e0cb4e04fa1a}
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {bfdd8847-01f8-11df-a57d-e0cb4e04fa1a}
description Ramdisk Options
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\Windows\system32>

Sai:

That's curious - the two identifiers that I wanted you to delete are not present in the BCD anymore, so that's why you got an error message. You seem to have somehow added two more identifiers to the BCD; {bfdd8846-01f8-11df-a57d-e0cb4e04fa1a} and {bfdd8847-01f8-11df-a57d-e0cb4e04fa1a}, and they are linked correctly leaving the IDs {bfdd8844-01f8-11df-a57d-e0cb4e04fa1a} and {bfdd8845-01f8-11df-a57d-e0cb4e04fa1a} orphaned.

Did you run Windows automatic repair or something? Otherwise, I don't understand how the new IDs were created. But they're now present and working correctly, so that's what is important.

Huh, I dunno. All I did is enter the first two in an elevated cmd, rebooted and tested the WinPE recovery environment. rebooted again and then entered the final commands. Anyway, it works so that's all I care about at this time. Thanks dude !

Hi Mark

I'm now having a problem with the Advanced Boot Option ... well it like this I opened my laptop (windows7 ) then I got a black screen with a blinking "_" on it so I press Enter then a Windows Boot Manager show up . It let choose 1 program its Windows 7 down it there a hint telling me that I can go to advance option using F8 Keys . Down another there's some tool called Windows Memory Diagnostics Tool , Then I press the F8 keys to go to advance option suddenly it go back to the blinking thing and then I repeat the same thing Pressing The Enter again ....

Please Help I Don't Want To Go The Shop To Fix This And Pay It ... I'm not that expert of this computer stuff and I'm a new member :)

Domain Kid54:

The recommended course of action is to boot your laptop from a Windows 7 installation DVD or a Windows 7 System Repair Disk that you can create on any Windows 7 PC. Then use the Automatic Repair tool to see if it can fix the boot issue easily. If not, run disk diagnostics to see if there are any bad sectors on your disk that prevent Windows from starting. Laptop hard disk failure is a common problem due to the shock/vibration experienced by the disk in normal use, so I would suspect some kind of disk problem. At least the disk can read the partition containing the boot manager, so your disk isn't completely dead. But apparently it isn't able to continue and load Windows, perhaps because you have bad sectors on the Windows partition.

If you don't have experience troubleshooting problems like this then you should find a friend who does or find a good repair shop.

Dear Mark,

How can I create a Windows 7 System Repair Disk and how do i boot my laptop from Windows 7 Installation DVD ? :-)

Sorry If I Make You Troubled , I'm New To This System

If you're that new to fixing computers you best find a friend who can help you.

Dear Mark,

I don't have any friend that expert on this system too ... so please teach me
Well I'm not that new to the system ... sometimes I know what to do ... but this kind of problem no idea so please mark teach me .

I'm 13 years old boy . No expert friend on this computer system

Domain Kid54

To make a system repair disk - open up Windows Control Panel, select Backup and Restore and from there you will see an option to ' Create a system repair disc' .

Do you have either a Windows install DVD or (assuming your laptop came with Windows 7) the laptop manufacturers restore DVD? There should be (if installed by the manufacturer) a recovery option somewhere on your laptop.

Dear Colin B,

How can I create a system repair disc when I can't even log in to the computer when the F8 Keys is not let me go to the Advance Option ?

Domain Kid54 wrote:

How can I create a system repair disc when I can't even log in to the computer when the F8 Keys is not let me go to the Advance Option ?

Ah, I thought you could log on normally, just the advanced options didn't work.

This is getting tricky as it is one of those things where you really need someone who can see your laptop. Are you able to find a Windows 7 install DVD or possibly download a repair or recovery environment from the laptop manufacturer?

What brand and model is your laptop?

I assume you do not have a complete disk image of your laptop made by True Image or any other imaging software.

I'll reread your complete thread.

Dear Colin B,

My laptop brand is Samsung and its model is RV413 ... Find a Windows 7 install DVD ? what's that ? :-) And how to download a repair or recovery environment from the laptop manufacturer? In other words , what is a laptop manufacturer

sorry if i let you to explain much because i didn't know much about this
please explain me what's the thing is and please teach me step to step to repair my laptop ;-}

Domain Kid54,

I'm not sure which country you live in or if English is your native language, but I find it a little difficult to believe that someone who can negotiate the Acronis forum and owns a laptop wouldn't know who or what a laptop/computer manufacturer is, or in this day and age for someone who purports to be 13 years old not know what an install DVD is.

Dear Colin B,

If you wanna know where i live ... its Malaysia . Don't worry about the manufacturer i search it on the internet but what's an Install DVD ?

Don't you have a friend with a windows 7 laptop or parents who own a windows 7 desktop/laptop? If that is the case then you can make a repair DVD from their computer using Colin B's instructions. My other question would be have you tried tapping the F8 key rapidly when booting the computer to get other boot options like Safe Mode, Repair your computer rather than just trying when it hints at the advanced options?

Sounds like your hard drive is having issues from my experience. Could be something else but until you get a professional diagnosis from someone who can look at it in person it is near impossible to diagnose over a forum given the circumstances.

Well I have a computer Windows Xp

Domain Kid54 wrote:

Well I have a computer Windows Xp

Are you saying the PC you are having a problem with is running XP and not Windows 7, or the PC you are now using is running XP and the laptop with the problem is using Windows 7?

ok, what version of windows 7 was running on your laptop then? Check the C.O.A. sticker on the bottom (example: https://public.dm2301.livefilestore.com/y2poHW2WI8ufe0l17pm9Yum00f2mp7J… ) and see if it states "Windows 7 (home premium, pro, etc.) 64bit or 32bit. If not I'm going to just guess it is a 64bit OS as they are the most common and you can download a legal copy from mydigitalriver site. http://msft.digitalrivercontent.net/win/X17-59465.iso (this is the 64bit version) the 32bit version can be provided if this one doesn't work. (This ISO is 3.1GB!) If you have limitations on the amount you can download or if you have a slow internet connection then you should install a download manager that allows pausing and resuming or recovery of a stalled download such as "Downthemall" which is an addon for a web browser, here is the link for the Firefox Down Them All addon: https://addons.mozilla.org/en-US/firefox/addon/downthemall/

Here are clear instructions on how to use the windows 7 install disk to get to the "Repair your Computer" option instead of mistakenly installing a fresh copy over the top of your existing files http://www.techsupportalert.com/content/how-repair-windows-7-system-ins…
Once there you would first use "startup repair" and if that does not resolve your issue there is a command prompt that can be used to check the integrity of your hard drive, repair issues with the drive, and lastly if it is indeed a problem with your boot manager then once we get you to the command prompt we can get you to to a bcdedit /enum all command and let the Magician Mark Wharton take over... :)

Question, does your XP machine have a DVD burner? If not then you may have to get more advanced and create a Windows 7 Bootable USB Memory Stick from the ISO you download. If it does have a DVD burner then you will need to use some software like IMGBurn http://www.imgburn.com/ which is 100% free and has no junkware/spyware/malware and is tailored to burn downloaded ISO's.

Lastly if this is all over your head and it makes no sense, get a buddy who understands what I'm talking about to follow these instructions, if your hard drive is failing then none of these instructions will likely help you, at that point you may need to just pull the drive and hook it up with an external hard drive reader and backup data if it is readable. Good Luck!

Sai.

Colin he is replying to my inquiry of another computer besides the dying W7 laptop so he can download a technet or mydigitalriver ISO to get the "repair your computer" option from a legitimate install disk.

Dear Colin B ,

I have a laptop Windows 7 64bit and a computer Windows Xp

Domain Kid, are you able to follow my post at all ?

Hello Mark, have another conundrum for you. :D if you can find the time it would be great, getting a 0xc000000f error on the Windows Setup EMS enabled selection on an HP All in One Windows 7 machine.

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

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {aa913f02-98e0-11e1-9c3e-d7896f5bd782}
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 {aa913f04-98e0-11e1-9c3e-d7896f5bd782}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {aa913f02-98e0-11e1-9c3e-d7896f5bd782}
nx OptIn

Windows Boot Loader
-------------------
identifier {aa913f04-98e0-11e1-9c3e-d7896f5bd782}
device ramdisk=[C:]\Recovery\aa913f04-98e0-11e1-9c3e-d7896f5bd7
82\Winre.wim,{aa913f05-98e0-11e1-9c3e-d7896f5bd782}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\aa913f04-98e0-11e1-9c3e-d7896f5bd7
82\Winre.wim,{aa913f05-98e0-11e1-9c3e-d7896f5bd782}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {aa913f02-98e0-11e1-9c3e-d7896f5bd782}
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\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 {aa913f05-98e0-11e1-9c3e-d7896f5bd782}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\aa913f04-98e0-11e1-9c3e-d7896f5bd782\boot.sdi

Sai:

Are you just wanting to get rid of the boot menu entry labeled "Windows Setup EMS Enabled"? If so,

bcdedit /set {emssettings} bootems no

In looking at your disk structure you seem to have an OEM recovery partition yet your BCD links to recovery files on the main Windows partition. Usually the OEM provides a means of restoring the factory image and the links to that function point to the recovery partition. Is this what you want to get working? If so, browse the factory image partition and find the path to WinRE.wim and boot.sdi and I'll show you how to change the recovery function to use the recovery files on the OEM partition.

there is a boot.sdi in the recovery partition at D:\boot and at D:\NST but no winre.wim, just the default HP recovery .wim's
and a WinRE.wim and boot.sdi in the C:\recovery\aa913f04-98e0-11e1-9c3e-d7896f5bd782 folder...

What are the paths and names of the HP recovery .wims?

D:\preload

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

C:\Users\OWNER>D:

D:\>cd preload

D:\preload>dir
Volume in drive D is FACTORY_IMAGE
Volume Serial Number is 2A8D-8431

Directory of D:\preload

03/04/2010 02:46 AM 91,684,342 A1NAv6PrA3.wim
03/04/2010 02:45 AM 92,036,447 A1NAv6PrA310.wim
03/04/2010 02:45 AM 104,824,151 A1NAv6PrA311.wim
03/04/2010 02:45 AM 104,679,935 A1NAv6PrA312.wim
03/04/2010 02:45 AM 101,017,726 A1NAv6PrA313.wim
03/04/2010 02:45 AM 41,321,388 A1NAv6PrA314.wim
03/04/2010 02:45 AM 141,404,806 A1NAv6PrA315.wim
03/04/2010 02:45 AM 104,854,419 A1NAv6PrA316.wim
03/04/2010 02:45 AM 104,369,222 A1NAv6PrA317.wim
03/04/2010 02:45 AM 104,272,908 A1NAv6PrA318.wim
03/04/2010 02:45 AM 104,854,234 A1NAv6PrA319.wim
03/04/2010 02:46 AM 140,886,498 A1NAv6PrA32.wim
03/04/2010 02:45 AM 104,295,857 A1NAv6PrA320.wim
03/04/2010 02:45 AM 104,793,994 A1NAv6PrA321.wim
03/04/2010 02:45 AM 104,723,780 A1NAv6PrA322.wim
03/04/2010 02:45 AM 99,973,107 A1NAv6PrA323.wim
03/04/2010 02:45 AM 104,854,163 A1NAv6PrA324.wim
03/04/2010 02:45 AM 98,018,472 A1NAv6PrA325.wim
03/04/2010 02:45 AM 103,632,670 A1NAv6PrA326.wim
03/04/2010 02:45 AM 104,836,441 A1NAv6PrA327.wim
03/04/2010 02:45 AM 64,934,681 A1NAv6PrA328.wim
03/04/2010 02:45 AM 108,681,693 A1NAv6PrA329.wim
03/04/2010 02:46 AM 101,858,471 A1NAv6PrA33.wim
03/04/2010 02:45 AM 59,676,867 A1NAv6PrA330.wim
03/04/2010 02:45 AM 101,200,809 A1NAv6PrA331.wim
03/04/2010 02:45 AM 100,913,427 A1NAv6PrA332.wim
03/04/2010 02:45 AM 88,701,981 A1NAv6PrA333.wim
03/04/2010 02:45 AM 61,783,192 A1NAv6PrA334.wim
03/04/2010 02:45 AM 103,621,746 A1NAv6PrA335.wim
03/04/2010 02:45 AM 96,169,428 A1NAv6PrA336.wim
03/04/2010 02:45 AM 104,159,360 A1NAv6PrA337.wim
03/04/2010 02:45 AM 97,349,272 A1NAv6PrA338.wim
03/04/2010 02:45 AM 104,835,326 A1NAv6PrA339.wim
03/04/2010 02:46 AM 100,941,972 A1NAv6PrA34.wim
03/04/2010 02:45 AM 12,049,503 A1NAv6PrA340.wim
03/04/2010 02:45 AM 216,585,674 A1NAv6PrA341.wim
03/04/2010 02:45 AM 77,483,301 A1NAv6PrA342.wim
03/04/2010 02:45 AM 85,287,278 A1NAv6PrA343.wim
03/04/2010 02:45 AM 99,159,453 A1NAv6PrA344.wim
03/04/2010 02:44 AM 95,908,283 A1NAv6PrA345.wim
03/04/2010 02:44 AM 182,179,109 A1NAv6PrA346.wim
03/04/2010 02:44 AM 88,706,306 A1NAv6PrA347.wim
03/04/2010 02:44 AM 84,663,399 A1NAv6PrA348.wim
03/04/2010 02:44 AM 95,485,618 A1NAv6PrA349.wim
03/04/2010 02:46 AM 84,993,488 A1NAv6PrA35.wim
03/04/2010 02:44 AM 102,222,877 A1NAv6PrA350.wim
03/04/2010 02:44 AM 83,913,416 A1NAv6PrA351.wim
03/04/2010 02:44 AM 90,606,963 A1NAv6PrA352.wim
03/04/2010 02:44 AM 104,689,531 A1NAv6PrA353.wim
03/04/2010 02:44 AM 101,818,004 A1NAv6PrA354.wim
03/04/2010 02:44 AM 0 A1NAv6PrA355.wim
03/04/2010 02:44 AM 104,418,270 A1NAv6PrA356.wim
03/04/2010 02:44 AM 101,211,004 A1NAv6PrA357.wim
03/04/2010 02:44 AM 97,089,627 A1NAv6PrA358.wim
03/04/2010 02:44 AM 98,999,623 A1NAv6PrA359.wim
03/04/2010 02:46 AM 101,133,394 A1NAv6PrA36.wim
03/04/2010 02:44 AM 100,907,918 A1NAv6PrA360.wim
03/04/2010 02:44 AM 102,258,842 A1NAv6PrA361.wim
03/04/2010 02:44 AM 104,853,347 A1NAv6PrA362.wim
03/04/2010 02:44 AM 104,726,725 A1NAv6PrA363.wim
03/04/2010 02:44 AM 102,989,257 A1NAv6PrA364.wim
03/04/2010 02:44 AM 104,852,276 A1NAv6PrA365.wim
03/04/2010 02:44 AM 104,660,174 A1NAv6PrA366.wim
03/04/2010 02:44 AM 97,594,941 A1NAv6PrA367.wim
03/04/2010 02:44 AM 104,725,897 A1NAv6PrA368.wim
03/04/2010 02:44 AM 104,635,975 A1NAv6PrA369.wim
03/04/2010 02:46 AM 97,975,631 A1NAv6PrA37.wim
03/04/2010 02:44 AM 102,883,734 A1NAv6PrA370.wim
03/04/2010 02:44 AM 103,958,103 A1NAv6PrA371.wim
03/04/2010 02:44 AM 104,456,110 A1NAv6PrA372.wim
03/04/2010 02:44 AM 102,725,021 A1NAv6PrA373.wim
03/04/2010 02:44 AM 104,690,865 A1NAv6PrA374.wim
03/04/2010 02:44 AM 104,837,885 A1NAv6PrA375.wim
03/04/2010 02:44 AM 59,948,111 A1NAv6PrA376.wim
03/04/2010 02:44 AM 168,393,267 A1NAv6PrA377.wim
03/04/2010 02:44 AM 104,841,069 A1NAv6PrA378.wim
03/04/2010 02:44 AM 104,790,586 A1NAv6PrA379.wim
03/04/2010 02:46 AM 103,264,936 A1NAv6PrA38.wim
03/04/2010 02:44 AM 102,933,464 A1NAv6PrA380.wim
03/04/2010 02:44 AM 104,213,489 A1NAv6PrA381.wim
03/04/2010 02:44 AM 103,965,794 A1NAv6PrA382.wim
03/04/2010 02:44 AM 101,400,642 A1NAv6PrA383.wim
03/04/2010 02:44 AM 102,892,958 A1NAv6PrA384.wim
03/04/2010 02:44 AM 59,910,966 A1NAv6PrA385.wim
03/04/2010 02:46 AM 104,726,841 A1NAv6PrA39.wim
85 File(s) 8,439,781,730 bytes
0 Dir(s) 2,248,056,832 bytes free

D:\preload>

Sai:

That's certainly an interesting and complex recovery image scheme. Usually there is a version of Windows PE as well as a factory image on most OEM laptops. The Windows PE file is usually in ...\Recovery\WindowsRE\winre.wim and the ramdisk file is in ...\Recovery\WindowsRE\boot.sdi, like in your earlier post, reply #656. If you don't have those files then HP must be using the standard Windows recovery scheme on the Windows partition, and I don't have any idea how they start the "restore to factory image" process on the preload partition.

Back to the original question - do you just want to get rid of the boot menu entry "Windows Setup EMS Enabled"? After restoring to the factory image, this menu item should have been deleted by the installer. If this still appears in the boot menu then it's from a botched restore operation and can be removed by the command in reply #678.

No, next step is to just get some recovery disks for this machine. I was just hoping the recovery scheme was broken via the BCD as I can't even boot to the recovery partition as is usually the case with HP's, pressing F11 gets me the same 0xc000000f boot error, setting the partition as active does the same... the recovery partition has its own BCD as well... would it help to get an enum of that?

Don't Worry Guys My Laptop Is At The Shop Now And I Have To Pay 50$ Dollars for them to Format My Laptop Then They Say The Problem Still There ... So They Going To Check The Hard disk

Thanks For All The Tip And Help Guys

Wouldn't hurt to take a look at the BCD on the recovery partition.

Hello Mark, wondering how to direct the /enum all command to a specific BCD file as it just defaults to the system BCD,
the output I get from the BCD by using Visual BCD Editor is:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {7619dcc9-fafe-11d9-b411-000476eba25f}
displayorder {7619dcc9-fafe-11d9-b411-000476eba25f}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {7619dcc9-fafe-11d9-b411-000476eba25f}
device ramdisk=[boot]\Recovery\WindowsRE\winre.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path \windows\system32\boot\winload.exe
description Windows Setup
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice ramdisk=[boot]\Recovery\WindowsRE\winre.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot \windows
detecthal Yes
winpe Yes
ems Yes

Sai:

bcdedit /store D:\boot\bcd /enum all > %userprofile%\Desktop\BCD.txt

This will create a text file on your desktop, assuming that the path to the BCD on the factory image partition is D:\Boot\BCD

Windows Boot Manager
--------------------
identifier {bootmgr}
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {default}
device ramdisk=[boot]\Recovery\WindowsRE\winre.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path \windows\system32\boot\winload.exe
description Windows Setup
locale en-US
inherit {bootloadersettings}
osdevice ramdisk=[boot]\Recovery\WindowsRE\winre.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot \windows
detecthal Yes
winpe Yes
ems Yes

Windows Memory Tester
---------------------
identifier {memdiag}
device boot
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}

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

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

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

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

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

Device options
--------------
identifier {7619dcc8-fafe-11d9-b411-000476eba25f}
ramdisksdidevice boot
ramdisksdipath \boot\boot.sdi

Funny, based on what I see in the BCD for the Recovery Partition I surmised that there was supposed to be a \Recovery\WindowsRE\WinRE.wim directory and there wasn't (of which you surmised there was supposed to be in an earlier reply), I created a hidden directory/subdirectory and copied the C:\Recovery version of the WinRE.wim to the newly created WindowsRE folder and was then allowed to start creating Recovery disks as the CDCreator.exe file isn't whining about the computer lacking a Recovery Partition anymore.... We will see if the Recovery Disks work and if so then I will enjoy yet another unorthodox method of repairing a computer problem of which I stumble on frequently.....

:-)

Unfortunately the Winre.wim file I used worked for making restore disks and will now boot the recovery partition but it is just a bland WinRE default Win7 with no link to the HP restore..... oh well, on the right track but not sure if the HP WinRE is different or if there is something in the BCD that instructs the HP program to be listed in the WinRE advanced options or what..... it's a real head scratcher.....

Sai:

Replying to your last 3 messages - sorry for the delay. From the contents of the BCD on the factory image partition, the partition must be set as active because some of the BCD pointers use the terminology "boot" instead of a referring to a particular partition. "Boot" means the partition with the active flag set. Also, like you discovered, the image loaded by the recovery operation is (or should be) WinRE.wim located at D:\Recovery\WindowsRE\. In most OEM laptops this is a windows image file that is customized by the OEM and contains code to either enter the standard recovery environment or start a restore to factory operation. In reply #681 you listed a lot of smaller image files that must comprise the custom OEM image but I have no idea how they piece them back together.

Well, they are .wim files so most likely they use imagex behind the scenes, I'm thinking of just deploying their image since it is a named hierarchy of files but not sure if imagex is enough as they likely have some other tools behind the scenes, at any rate this is all dabbling at this point (as I am waiting on purchased recovery media anyhow) to better understand HP's method of deployment as it is proprietary and very few people expend much effort into reverse engineering their crappy UI-based restore methods. This is why I was so intrigued that you were able to understand the BCD of these RTM versions of Windows, they are not only proprietary but there is little to no information out there on the structure of a brand name BCD. Thanks for all your help as usual Mark.

hi all,

I have backup my dell laptop which contains DELL recovery partition, OS partition and MBR sector. I able to restore all the partition into vmware but somehow it is not able to boot up which give me below error:

A problem has been detected and Windows has been shut down to prevent damage to your computer.

If this is the first time you've seen.......

Techical information:
*** STOP: 0x0000007B (0X8078BA50, 0xC0000034, 0x00000000, 0x00000000)

Partition drive is automatically assigned from C(dell recovery)--> D and D(OS partition)-->E during acronis restoring process.

But after restored, C drive become Dell Recovery partition and D drive become OS partition.

Need some expert to give me some clues what is going on, i have stuck few days :( ... Thank you

Below is my bcdedit /enum all
===========================================================================

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {34e73374-9958-11e0-a3af-fec9a6843150}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {default}
device partition=D:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {34e73376-9958-11e0-a3af-fec9a6843150}
recoveryenabled Yes
osdevice partition=D:
systemroot \Windows
resumeobject {34e73374-9958-11e0-a3af-fec9a6843150}
nx OptIn

Windows Boot Loader
-------------------
identifier {34e73376-9958-11e0-a3af-fec9a6843150}

Windows Boot Loader
-------------------
identifier {822a0174-4ff8-11e4-b35b-be59fc5d55db}
device ramdisk=[C:]\Recovery\windowsre\Winre.wim,{822a0175-4ff8-11e4-b35b-be59fc5d55db}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\windowsre\Winre.wim,{822a0175-4ff8-11e4-b35b-be59fc5d55db}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {34e73374-9958-11e0-a3af-fec9a6843150}
device ramdisk=[C:]\recovery\windowsre\Winre.wim,{34e73374-9958-11e0-a3af-fec9a6843150}
path \Windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
filedevice partition=D:
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

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 {34e73377-9958-11e0-a3af-fec9a6843150}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {822a0175-4ff8-11e4-b35b-be59fc5d55db}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\windowsre\boot.sdi

=================================================================

I think stop code 0x7B is a driver error rather than a BCD error. It might relate to the boot files not being in the correct place as far as the BCD is concerned, but I think the problem is more likely that registry contains the wrong disk information and possibly the wrong chipset driver install.

If you can either get into Windows safe mode (in the VM) or boot from an install DVD to get to a command prompt you might be able to run fixboot or boot rec.

Mark will probably be able to help you if it is a BCD problem though.

In reply to tien choon ng.

Does Acronis have anything like the Paragon P2P adjust? If so that would be the optimal way to go about resolving this issue, it changes the drivers to what they need to be or to system default generic drivers so windows can boot on new hardware...

thanks colin.

I have tried fixboot, fixmbr and rebuildbcd but still no luck to boot up the OS. Between I found out there is no "recovery" and "boot" hidden folder in my D drive(OS partition). These 2 folders only exist in C drive which is DELL Recovery partition.

hi sai,

thanks for the recommendation, will try it if not able to solve this. Because it is quite large disk space required to restore back and it's took very long time to restore. :(

tien choon ng:

The issue here is not related to the BCD. Stop errors are produced by Windows, so by that point in the boot process, the boot manager has done its job and handed off control to Windows. The stop error that you see is due to having the wrong disk driver for the VM's virtual disk drive.

Two thoughts come to mind. One is to go back to your source and enter BIOS setup. Change the disk access method to IDE and make a new image. Try restoring this to the VM. If you're lucky, Windows can sort out the driver incompatibilities and find the right drivers on first boot.

The other is to download VMWare's vCenter Converter here: http://www.vmware.com/products/converter/ It can read some of the older TI file formats and convert the image file directly to a virtual disk file. It only works with some of the older versions of TI but from your screenshot, it looks like you have an older version.

I get error when i use f8 and try to repair windows. attached error Screen

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {a8ea09f3-02d2-11e0-9d03-ece59d85daeb}
displayorder {current}
toolsdisplayorder {bdbdbd00-6057-11e0-a7f3-ce9adfd72001}
{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 {a8ea09f5-02d2-11e0-9d03-ece59d85daeb}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {a8ea09f3-02d2-11e0-9d03-ece59d85daeb}
nx OptIn
bootstatuspolicy IgnoreShutdownFailures

Windows Boot Loader
-------------------
identifier {a8ea09f5-02d2-11e0-9d03-ece59d85daeb}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {a8ea09f3-02d2-11e0-9d03-ece59d85daeb}
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 unknown
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

Real-mode Boot Sector
---------------------
identifier {bdbdbd00-6057-11e0-a7f3-ce9adfd72001}
device partition=\Device\HarddiskVolume2
path \bdr-ld01.mbr
description Bitdefender Rescue Mode - Windows 7 Profess

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 {a8ea09f6-02d2-11e0-9d03-ece59d85daeb}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\Windows\system32>

Please help, solution to this will be highly appreciated.

Regards,

Gagan Parbhat Jain

Hi Mark,

I have been following your posts in this thread and I am thankful for all your work and efforts in helping others. I have been having the same issue as others when I try to click on repair computer to restore my xps 1647 computer to the factory state I keep going back to windows 7 logon. I was able to successfully restore my computer twice in the past but I no longer get that option.

Can you please check my bcdedit /enum data and guide me. Thanks!!