Skip to main content

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

Thread needs solution
Beginner
Posts: 0
Comments: 5

#51

@Mark, I tried all the steps you explained me, nothing works, I always have same error when trying to add the lines:
http://forum.acronis.com/sites/default/files/forum/2009/12/6758/capture.jpg
I had tried to write it, copy it to notepad first and from notepad to cmd line, nothing helps.

Beginner
Posts: 0
Comments: 1

#52

I had the same problem --booting into wins 7 is fine but going into "repair your coputer" is not. it keeps giving me error message.
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.

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

C:\Users\Jansen Yong>BCDEDIT /ENUM ALL

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
default {current}
displayorder {current}
timeout 3

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
recoverysequence {77fbffa4-92e1-11df-ba64-cfd6b580c5d4}
truncatememory 0xfff00000
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {adb02e78-925b-11df-a9ec-806e6f6e6963}
nx AlwaysOff
numproc 4
usefirmwarepcisettings No

Windows Boot Loader
-------------------
identifier {77fbffa4-92e1-11df-ba64-cfd6b580c5d4}

Windows Boot Loader
-------------------
identifier {77fbffa6-92e1-11df-ba64-cfd6b580c5d4}
device ramdisk=[C:]\Recovery\59aba661-9135-11df-b8c6-dc94307c07
ff\Winre.wim,{77fbffa7-92e1-11df-ba64-cfd6b580c5d4}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\59aba661-9135-11df-b8c6-dc94307c07
ff\Winre.wim,{77fbffa7-92e1-11df-ba64-cfd6b580c5d4}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {adb02e78-925b-11df-a9ec-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Premium (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae No
debugoptionenabled No

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

Debugger Settings
-----------------
identifier {dbgsettings}

Device options
--------------
identifier {77fbffa5-92e1-11df-ba64-cfd6b580c5d4}
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {77fbffa7-92e1-11df-ba64-cfd6b580c5d4}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\59aba661-9135-11df-b8c6-dc94307c07ff\boot.sdi

C:\Users\Jansen Yong>

all these happens when i reinstall the os.
Thanks!

Beginner
Posts: 0
Comments: 1

#53

Dear Mark, Guess you're probably weary of sorting out all the windows 7 boot manager problems, but can I ask you a favor and look at mine?
I have exactly the same symptoms as the initial poster d.chatten the same error code and the device not accessible message. I don't understand why the error message had to be so cryptic why couldn't it say what device it cant access? Anyway here's my BCD help it helps, By the way I don't have on my c drive a recovery folder? Can I create one? Windows boots fine.

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {bca1474e-2e6b-11df-89e6-89964aef05b7}
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 {bca14750-2e6b-11df-89e6-89964aef05b7}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {bca1474e-2e6b-11df-89e6-89964aef05b7}
nx OptIn

Windows Boot Loader
-------------------
identifier {bca14750-2e6b-11df-89e6-89964aef05b7}
device ramdisk=[C:]\Recovery\bca14750-2e6b-11df-89e6-89964aef05b7\Winre.wim,{bca14751-2e6b-11df-89e6-89964aef05b7}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\bca14750-2e6b-11df-89e6-89964aef05b7\Winre.wim,{bca14751-2e6b-11df-89e6-89964aef05b7}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {bca1474e-2e6b-11df-89e6-89964aef05b7}
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 {bca14751-2e6b-11df-89e6-89964aef05b7}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\bca14750-2e6b-11df-89e6-89964aef05b7\boot.sdi

Beginner
Posts: 3
Comments: 4

#54

I hope some can help me here

Thanks Joe N7QPP

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {92f86b6a-5c65-11dd-8c93-d0fc8cd23e7f}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {92f86b69-5c65-11dd-8c93-d0fc8cd23e7f}
device unknown
path \Windows\system32\winload.exe
description Microsoft Windows Vista
locale en-US
inherit {bootloadersettings}
osdevice unknown
systemroot \Windows
resumeobject {92f86b6a-5c65-11dd-8c93-d0fc8cd23e7f}
nx OptIn

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Ultimate (recovered)
locale en-US
recoverysequence {current}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows

Windows Boot Loader
-------------------
identifier {current}
device ramdisk=[C:]\Recovery\101def7b-c0c7-11de-89c2-91c1d3245a80\Winre.wim,{e6e74358-f00c-11df-9dbf-81b77f161c89}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\101def7b-c0c7-11de-89c2-91c1d3245a80\Winre.wim,{e6e74358-f00c-11df-9dbf-81b77f161c89}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {92f86b6a-5c65-11dd-8c93-d0fc8cd23e7f}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
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 Earlier Version of Windows

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}

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

Device options
--------------
identifier {e6e74358-f00c-11df-9dbf-81b77f161c89}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\101def7b-c0c7-11de-89c2-91c1d3245a80\boot.sdi

Beginner
Posts: 0
Comments: 1

#55

I noticed a (SOLVED) notation in the header for this issue. Has the new 2011 Acronis Products corrected the issue with cloning a drive with the Windows 7 Recovery Environment on a hidden partition yet?

Beginner
Posts: 0
Comments: 18

#56

      "HELP" cry to Mark Wharton from Germany!!!

Since this case is closed I could only hope that you, Mark, are stil listening!

Months ago I encountered the mentioned trouble and was unsuccessfully trying to find a solution in the internet. Following your advice my "bcdoutput" looks like a heep of junk with lots of old (?) sections, which I am not coming along with.

Mark, could you give me a note via this forum, if you are still online and willing to help a bloody beginner in this respect???

Forum Star
Posts: 19
Comments: 2110

#57

jrace:

I will try to help. Please attach the output of bcdedit /enum all to your reply as a text file. The easiest way to create a text file is to use the following command, run from an elevated command prompt:

bcdedit /enum all > %userprofile%\Desktop\bcd.txt

This command will create a text file on your desktop containing the output of the bcdedit /enum all command.

Beginner
Posts: 0
Comments: 8

#58

Mark,

Thanks for your reply. attached is the bcdedit you requested.

Mark S.

Attachment Size
57902-94165.txt 3.11 KB
Forum Star
Posts: 19
Comments: 2110

#59

Mark:

Could you also post a screen shot that shows your partition layout from Windows Disk Management, similar to the one below:

The Windows 7 Snipping Tool is handy for capturing a screen image.

Attachment Size
57904-94168.png 85.38 KB
Beginner
Posts: 0
Comments: 18

#60

Thank you much for your answer, Mark!

A short history before:

My system was upgraded from VISTA with a special hidden recovery section on the disk  to WIN7 ULT. After upgrade I removed the Sony recovery section (Vista) from HD.

A few times the system was recovered via Acronis 2010 and 2011 or via Windows recovery with a bootable rescue USB stick.

The attached BCD file is produced with Program "EasyBCD" which is in english laguage for you.

For me there are shown a lot of old (?) and obsolete (?) entries. How after all do I get rid of that? But primary for me is to get the "Repair my Computer" funktion back.

I have a hidden folder "C:\Recovery" which bares a folder named "39eafb20-7e9a-11de-8157-b3578c2b92f4" with files "boot.sdi" and "winre.wim" and a second folder "Logs" with a file "reload.xml".

My HD has 3 patitions: C:\(System), D:\(Own Data), Acronis Secure Zone.

Attachment Size
57923-94171.txt 5.76 KB
Forum Star
Posts: 19
Comments: 2110

#61

jrace:

I see what you mean about the obsolete entries! This may take some work, so let's go slowly. First, have a look at the attached file, which is a color-coded version of your bcdoutput.txt file. I believe that the entries that are highlighted in red should be removed, and the ones highlighted in yellow need to be repaired. Do you agree?

The first thing that you should do is to save a copy of your current BCD file. Can you do this with EasyBCD? If so, make a copy for safe keeping.

I am also assuming that you no longer have Windows XP on your disk, so the entry for booting XP is not needed. Is this correct?

I will wait for your answers before posting the commands needed to delete the obsolete entries. Let's try that first before doing any repairs. I probably won't be able to respond until the weekend; I hope that this is not a problem.

Attachment Size
57960-94177.pdf 61.43 KB
Beginner
Posts: 0
Comments: 18

#62

Hi Mark,

The schedule you proposed is perfectly ok with me! Anyway take your time for you it is the early afternoon right now, for me it is time to hit the sack (12:00 pm).

The red items on the list are corresponding to those I choosed already for myself. The Vista (not XP!) portion is not anymore on the system, so if that does not contain any vital information we can delete it.

"EasyBCD" can do a back up with the following restrictions:  "Note: This only backs up the Windows bootloader settings - the MBR is not included in this backup!"

If you decide that this will be good enough I can do it. I do not really understand much of that MBR, BCD ...

So far have a good day!

Forum Star
Posts: 19
Comments: 2110

#63

jrace:

Just to clarify - do you have a Windows XP installation on your disk? Yes or no?

Yes, go ahead and make a BCD backup using EasyBCD.

Beginner
Posts: 0
Comments: 18

#64

Good morning Mark,

clear statement:

I never had XP on my computer, I had Vista on it but upgraded to W7 Ult a year ago with no Vista remnants on the system.

Presently it is a pure Win7/32 bit system.

BCD Backup is done!

Regards, Jens

Forum Star
Posts: 19
Comments: 2110

#65

Jens:

Good. You will need a way to restore the BCD backup if something goes wrong. I would recommend storing a copy in the folder C:\boot as a file named bcd1.bak. If you need to restore the backup due to Windows not being able to boot then you will need to boot the PC from a Windows 7 restore CD. Do you have one of these?

If not, type "System Repair" in the Windows 7 search box and choose "Create a System Repair Disk". Follow the instructions to burn a bootable CD with the Windows 7 recovery environment on the disk. This is the same recovery environment that we will eventually restore when we fix the F8 "Repair Your Computer" function.

When you have tested your sytem repair CD and have a BCD backup, then let's delete all of the unused BCD entries as the first step. Here are the commands to remove the 10 unwanted or obsolete entries from the BCD. Copy and paste each of them, one at a time, into an elevated command prompt window.

The syntax for a delete operation is bcdedit /delete {id}

bcdedit /delete {39eafb1b-7e9a-11de-8157-b3578c2b92f4}
bcdedit /delete {39eafb25-7e9a-11de-8157-b3578c2b92f4}
bcdedit /delete {39eafb27-7e9a-11de-8157-b3578c2b92f4}
bcdedit /delete {572bcd55-ffa7-11d9-aae0-0007e994107d}
bcdedit /delete {d7b4b81c-a36b-11dc-98cc-d5a2bf59b169}
bcdedit /delete {bcc0bf6b-eb13-11de-aad2-806e6f6e6963}
bcdedit /delete {d7b4b81d-a36b-11dc-98cc-d5a2bf59b169}
bcdedit /delete {ntldr}
bcdedit /delete {39eafb26-7e9a-11de-8157-b3578c2b92f4}
bcdedit /delete {ramdiskoptions}

After removing these entries, copy the output of bcdedit /enum all to a text file:

bcdedit /enum all > %userprofile%\Desktop\bcd.txt

Reboot the PC to make sure that Windows 7 still boots properly with the above entries deleted.

If all goes well then attach the bcd.txt file to your next reply. Then we'll fix the entries that need repair.

Beginner
Posts: 0
Comments: 18

#66

Mark:

So far so good! Everything worked fine:

A backup of the system was conpleted with ATIH 2011 and also with w7 backup; bootmedia are all available; bcd1.bak sits in folder C:\boot.

With wet Fingers I started killing the first entries rebooting after each deletion (is it still alive?). Coming to Entry #5 (bcdedit /delete {d7b4b81c-a36b-11dc-98cc-d5a2bf59b169}) that old Vista stuff, I had to learn that this and the next 2 entries (bcdedit /delete {bcc0bf6b-eb13-11de-aad2-806e6f6e6963}   +  bcdedit /delete {d7b4b81d-a36b-11dc-98cc-d5a2bf59b169}) have been deleted already in conjunction with one of the first deleted entries. No problem, less work!

With entry #8 ( bcdedit /delete {ntldr}) and #10 (bcdedit /delete {ramdiskoptions}) i had a little trouble; they both returned the same message:

This entry cannot be deleted unless the /f switch is specified on the command line. Run bcdedit /? for more information.
Access denied.

Since I did not want to fool around with the /f switch which I do not know of what it does, I left those entries in there for your decision and proposel to remove it in the next session.

Facts: we are still on the green side, system works -ok-.

Regards, Jens

Attachment Size
58049-94183.txt 3.25 KB
Forum Star
Posts: 19
Comments: 2110

#67

Jens:

That's good! We can safely force deletion of the {ntldr} entry:

bcdedit /delete {ntldr} /f

A cosmetic change - eliminate the word "recovered" (wiederhergestellt) from the description in the Resume from Hibernation entry:

bcdedit /set {5f429bec-91bc-11df-8646-806e6f6e6963} description "Windows 7 Ultimate"

Make another backup of your BCD before continuing. Now to finally fix the F8 function, enter the following four commands. Each of them is one line long, so it's better to copy/paste each:

bcdedit /set {ramdiskoptions} ramdisksdidevice partition=C:

bcdedit /set {ramdiskoptions} ramdisksdipath \Recovery\39eafb20-7e9a-11de-8157-b3578c2b92f4\boot.sdi

bcdedit /set {39eafb1c-7e9a-11de-8157-b3578c2b92f4} device ramdisk=[C:]\Recovery\39eafb20-7e9a-11de-8157-b3578c2b92f4\winre.wim,{ramdiskoptions}

bcdedit /set {39eafb1c-7e9a-11de-8157-b3578c2b92f4} osdevice ramdisk=[C:]\Recovery\39eafb20-7e9a-11de-8157-b3578c2b92f4\winre.wim,{ramdiskoptions}

Post another copy of your BCD after doing these - there are several other entries that go with the Recovery Boot Loader entry that SHOULD automatically appear, but we should check. Finally, try it out by rebooting the machine and repeatedly tapping the F8 key get the Boot Manager selection screen to appear. The first entry should be "Repair your computer". Try it out.

Beginner
Posts: 0
Comments: 18

#68

Hi Mark,

   I did as instructed by you, Mark,and...                      ...it works like fresch from the Store!  

No happening no nothing just perfect knowledge and straight forward instruction.

Thank you for the cosmetics. One thing left for may be another cosmetical correction: The first "Device Options" right behind the "Resume Loader Settings" with the identifier {39eafb1d-7e9e-11de-8157-b3578c2b92f4} (marked yellow on your PDF) did not change a bit during the whole operation and still says "ramdisksdidevice   unknown". Does it mean we could erase that one too or is it needed? Please drop me a short note on that!

I do not know how to thank you for the investment of your free time and your admirable attitude to help other people. I will send you a personal message the next days via the forum message service.

What can I say, a short precise and perfect job!!!            

Thank you, Jens

Attachment Size
58086-94186.txt 7.37 KB
Forum Star
Posts: 19
Comments: 2110

#69

Jens:

Yes, you can remove the unused "Device Options" entry now that you've demonstrated that the {ramdiskoptions} entry is working correctly:

bcdedit /delete {39eafb1d-7e9a-11de-8157-b3578c2b92f4}

While you're at it you can also remove the (wiederhergestellt) notation in the Windows Recovery Environment section:

bcdedit /set {39eafb1c-7e9a-11de-8157-b3578c2b92f4} description "Windows Recovery Environment"

The rest looks good and I'm glad that this worked for you. Hopefully Microsoft will come out with a BCD editing tool that's easier to use some day!

Beginner
Posts: 0
Comments: 8

#70

Mark,

Attached is my partition layout.

Thanks.

Attachment Size
58098-94189.png 97.78 KB
58098-94192.txt 3.11 KB
Forum Star
Posts: 19
Comments: 2110

#71

Mark:

I see that you have an OEM recovery partition (partition 2 in your graphic) that does not have a drive letter assigned, so I will have to make an educated guess about the location of the WinRE image file. Like the prior posts, it is recommended that you back up your current BCD or use Acronis True Image to back up its partition (the one named "Recovery"), since the files that boot Windows are located on that partition.

The following three commands should be entered into an elevated command prompt window:

bcdedit /set {7a17869e-c7c3-11df-92d7-a4badbfacbd8} ramdisksdidevice partition=\Device\HarddiskVolume2

bcdedit /set {7a17869d-c7c3-11df-92d7-a4badbfacbd8} device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\winre.wim,{7a17869e-c7c3-11df-92d7-a4badbfacbd8}

bcdedit /set {7a17869d-c7c3-11df-92d7-a4badbfacbd8} osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\winre.wim,{7a17869e-c7c3-11df-92d7-a4badbfacbd8}

Each command needs to be on one line, so it is recommended that you use copy/paste to enter them.

After doing the above, try rebooting the PC into the recovery environment to see if it works. If you get any error messages, post back. Also, could you post the contents of the bcd again as a text file, after making the changes?

Beginner
Posts: 0
Comments: 8

#72

Mark,

I did as you directed, but it did not boot into the recovery environment -- it simply booted to Windows again. I did not get an error message. Attached is the bcdedit txt file you requested after I made the previous changes. Also, I am running Windows 7, 64 bit if you need to know that.

Thanks,
Mark S.

Attachment Size
58105-94195.txt 3.63 KB
Forum Star
Posts: 19
Comments: 2110

#73

Mark:

Just to confirm, when you rebooted the PC and were tapping the F8 key, did the boot sequence stop and display the boot menu screen? Was the first choice in the list "Recover Your Computer"?

If yes, and you selected this choice, you said that the computer then booted directly to Windows? Is this correct?

Beginner
Posts: 0
Comments: 18

#74

Hi Mark,

I guess you are one of those legendary people who are not just satisfied with a perfect job and drop their tools. You also clean up the system and do the finetuning till it looks like brandnew out of the developers hands.

I did the last changes and now it not only works perfect it also looks like a beauty.

As an attachment you find the final setup for your papers.

Thank you again, Jens

Attachment Size
58117-94198.txt 3.28 KB
Beginner
Posts: 0
Comments: 8

#75

Mark,

Yes that is exactly correct. I pressed the F8 key and the boot sequence stopped and displayed the boot menu screen. The first option was 'Recover Your Computer," but when I selected it and hit enter, instead of going into the recovery sequence, it booted directly to windows.

Mark S.

Forum Star
Posts: 19
Comments: 2110

#76

Mark:

I think that I see the problem. In the main {current} entry that boots Windows 7, the Recovery Option setting is linked to ID {2d1020e2-9b28-11df-a002-a4badbfacbd8}, and there is no entry in the BCD with that ID. It should link to the ID of the Windows Recovery Environment entry with ID {7a17869d-c7c3-11df-92d7-a4badbfacbd8}.

Try this:

bcdedit /set {current} recoverysequence {7a17869d-c7c3-11df-92d7-a4badbfacbd8}

Beginner
Posts: 0
Comments: 8

#77

Mark,

You are a genius That fixed the problem. It now boots into the recovery sequence. I have been so frustrated with this for so long, and I am so grateful for you resolving this for me. I really appreciate you resolving this for me.

I am curious if you know what can caused the file to get changed in the first place so it would not work?

Thanks,
Mark S.

Forum Star
Posts: 19
Comments: 2110

#78

Mark:

Did you ever use the automatic repair feature of Windows 7? I've seen a few cases where it will fix most of the booting problems on a system that has been broken but it doesn't seem to fix the links to the F8 "Repair your computer" function.

Beginner
Posts: 0
Comments: 8

#79

Mark:

Yes I have used that feature before as I recall.

Thanks for all your help.

Mark S.

Beginner
Posts: 0
Comments: 18

#80

Mark Skaggs wrote:

Yes I have used that feature before as I recall.

I could confirm this. I used that feature 4 or 5 times after resizing a patition with ACR Disk Director when during reboot the computer crashed and would not start anymore. After these attempts finally the computer came to live again and some time after that I noted that the F8 function did not work anymore.

I really could not make a connection to any certain instance at that time. Althought since that day I was looking to thousands of pages to find a solution. Coming to Mircosoft pages with BCD problems -no solutions. Only, seen from my point of view, procedures to manipulate the BCD file which I was far away from understanding.

Other pages giving just back street wisdom or smart idiots advice.

So anyway after more than half a year of surching and asking I finally came to this thread "powered by Mark Wharton" to get quick, effective and professional help and a perfect solution.

There are not very much people around like Mark Wharton!

BTW:    until yesterday I was also blaming somebody for killing my hibernation feature on the computer. I came to that idea looking at my brandnew BCD file and seeing this "Resume from Hibernate" part and just tried if it works again after repair. It did not! I learned in the internet that Win7 has this feature not activated by default. Since I upgraded from Vista it was off from that time.      Strange*) --- but a simple solution:

Elevated command prompt, enter:  powercfg /hibernate on

After that everything works like new.


*) One day I would really like to be inside one of those developers just to see what it feels like!

Beginner
Posts: 0
Comments: 3

#81

Hi,

I recently had problems with my laptop. After several tries I managed to recover my system using the Recovery partition in my drive. However, when I enter the advanced boot options and I choose repair computer, it goes strait into loading Windows 7. This are my booting configuration,

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume2
path                    \bootmgr
description             Windows Boot Manager
locale                  en-us
default                 {current}
resumeobject            {3ce08b95-50f1-11e0-b7b9-806e6f6e6963}
displayorder            {current}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 Ultimate (recovered)
locale                  en-us
recoverysequence        {502ec9f4-3399-11e0-9cd7-f04da26784f0}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {3ce08b95-50f1-11e0-b7b9-806e6f6e6963}

Windows Boot Loader
-------------------
identifier              {2fbc53a2-50f1-11e0-97f0-e4b0cdcd482a}
device                  ramdisk=[C:]\Recovery\9d905dfa-50fa-11e0-8391-b3cb339adf2b\Winre.wim,{2fbc53a3-50f1-11e0-97f0-e4b0cdcd482a}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered)
locale                  
osdevice                ramdisk=[C:]\Recovery\9d905dfa-50fa-11e0-8391-b3cb339adf2b\Winre.wim,{2fbc53a3-50f1-11e0-97f0-e4b0cdcd482a}
systemroot              \windows
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {2fbc53a4-50f1-11e0-97f0-e4b0cdcd482a}
device                  ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{2fbc53a5-50f1-11e0-97f0-e4b0cdcd482a}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered)
locale                  
osdevice                ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{2fbc53a5-50f1-11e0-97f0-e4b0cdcd482a}
systemroot              \windows
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {3ce08b95-50f1-11e0-b7b9-806e6f6e6963}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows 7 Ultimate (recovered)
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

Device options
--------------
identifier              {2fbc53a3-50f1-11e0-97f0-e4b0cdcd482a}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\9d905dfa-50fa-11e0-8391-b3cb339adf2b\boot.sdi

Device options
--------------
identifier              {2fbc53a5-50f1-11e0-97f0-e4b0cdcd482a}
ramdisksdidevice        partition=\Device\HarddiskVolume2
ramdisksdipath          \Recovery\windowsre\boot.sdi

And this is my disk configuration.

I will appreciate if anybody can give a hand fixing this issue.

Attachment Size
62787-95122.png 35.67 KB
Forum Star
Posts: 19
Comments: 2110

#82

Alberto:

In the main {current} entry that boots Windows 7, the Recovery Option setting is linked to ID {502ec9f4-3399-11e0-9cd7-f04da26784f0}, and there is no entry in the BCD with that ID. It should link to the ID of the Windows Recovery Environment entry {2fbc53a2-50f1-11e0-97f0-e4b0cdcd482a}.

From an elevated command prompt, try this:

bcdedit /set {current} recoverysequence {2fbc53a2-50f1-11e0-97f0-e4b0cdcd482a}

If you want to remove the word "Recovered" from the entries then also do:

bcdedit /set {current} description "Windows 7 Ultimate"
bcdedit /set {2fbc53a2-50f1-11e0-97f0-e4b0cdcd482a} description "Windows Recovery Environment"

Beginner
Posts: 0
Comments: 3

#83

Thank you very much Mark

I made the changes, however when I select the "Repair Computer" option the advanced boot options it gives me an error as if the object is not there.

Any ideas? I see that in the bcd there are two entries for the "Windows Recovery Environment"

Regards

Alberto

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-us
default {current}
resumeobject {3ce08b95-50f1-11e0-b7b9-806e6f6e6963}
displayorder {current}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Professional
locale en-us
recoverysequence {2fbc53a2-50f1-11e0-97f0-e4b0cdcd482a}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {3ce08b95-50f1-11e0-b7b9-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {2fbc53a2-50f1-11e0-97f0-e4b0cdcd482a}
device ramdisk=[C:]\Recovery\9d905dfa-50fa-11e0-8391-b3cb339adf2b\Winre.wim,{2fbc53a3-50f1-11e0-97f0-e4b0cdcd482a}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale
osdevice ramdisk=[C:]\Recovery\9d905dfa-50fa-11e0-8391-b3cb339adf2b\Winre.wim,{2fbc53a3-50f1-11e0-97f0-e4b0cdcd482a}
systemroot \windows
winpe Yes

Windows Boot Loader
-------------------
identifier {2fbc53a4-50f1-11e0-97f0-e4b0cdcd482a}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{2fbc53a5-50f1-11e0-97f0-e4b0cdcd482a}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Winre.wim,{2fbc53a5-50f1-11e0-97f0-e4b0cdcd482a}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {3ce08b95-50f1-11e0-b7b9-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Professional
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

Device options
--------------
identifier {2fbc53a3-50f1-11e0-97f0-e4b0cdcd482a}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\9d905dfa-50fa-11e0-8391-b3cb339adf2b\boot.sdi

Device options
--------------
identifier {2fbc53a5-50f1-11e0-97f0-e4b0cdcd482a}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\windowsre\boot.sdi

Forum Star
Posts: 19
Comments: 2110

#84

Alberto:

Yes, there are two Recovery Environment entries on your PC. The first one is the Windows 7 Recovery Environment that was created by the Windows Installer. The second one must be your OEM recovery entry that was created by the PC manufacturer. The latter one is usually used to restore the PC to factory state.

I don't see the error in the BCD at the moment. Could you post the exact text of the error message? To get to the first recovery environment, are you pressing the F8 key right before Windows starts loading? Timing is critical - you have to hit the F8 key at the precise time or else Windows will just start up. You can sometimes tap F8 repeatedly at the end of the PC power-on self test to get this to happen.

Legend
Posts: 172
Comments: 11125

#85

I use Mark's suggestion and begin tapping the F8 key repeatedly (about 2 times per second) and I start the tapping as soon as I press the Power on button.

Beginner
Posts: 0
Comments: 3

#86

Thanks Mark,

Actually, I changed the pointer to the second recovery environment and it did load as when it was new. Yes I am entering to the repair computer option by pressing F8 and it does work. I do not know why the first option did not work, but I am happy with this one since now, in case I need, I can do a Factory Image Recovery.

I appreciate very much your help.

Regards,

Alberto

Forum Star
Posts: 19
Comments: 2110

#87

Alberto:

For the first option to work, the recovery folder must exist on the main Windows partition. In your case it would be at C:\Recovery\9d905dfa-50fa-11e0-8391-b3cb339adf2b. Inside that folder you should find the two files Winre.wim and boot.sdi. If these files don't exist or if the recovery folder has a different name then booting into the Windows Recovery Environment would fail. That's one possibility.

You will need enable viewing of both hidden and of protected operating system files in order to view these file in Windows Explorer.

Otherwise, if you prefer having the manufacturer's Factory Image restore function, then you've done the right thing.

Beginner
Posts: 0
Comments: 3

#88

Hi Mark, I also need Your help. I have the same problem. I can't run recovery/backup.
I tried to do something myself.... I attached the second report of 'bcdedit /enum all' after doing something myself. I think I deleted something.
Thanks in Advance.

Attachment Size
62861-95146.txt 3.46 KB
62861-95149.txt 2.82 KB
Forum Star
Posts: 19
Comments: 2110

#89

Agshin:

It appears that several items are missing in the second bcd file that you posted. The first one doesn't seem quite right either. It may be easiest to try to completely rebuild your BCD. You will need a Windows 7 installation CD. If you don't have one then use your existing Windows 7 to create a System Repair Disk. Boot your PC from the disk to enter the Windows Recovery Environment and start a Command Prompt.

Follow the instructions in this Microsoft article: http://support.microsoft.com/kb/927392 for using the Bootrec tool. Be sure to follow the prcedure for saving a backup copy of your existing BCD, renaming the existing copy, and then rebuilding the BCD from scratch.

Beginner
Posts: 0
Comments: 3

#90

Hello Mark.
I did everything step-by-step as written on the microsoft site.
I attach bcdedit report and printscreen of DiskManagement.

by the way, "Repair computer" doesn't appear on the startup.
Thanks in advance.

Attachment Size
63387-95272.txt 2.88 KB
63387-95275.png 178.25 KB
Beginner
Posts: 0
Comments: 3

#91

Mark, don't worry. I have formatted my laptop... Better if You help me to create backup image on harddrive.

Forum Star
Posts: 19
Comments: 2110

#92

Agshin:

Does the reformatted laptop now boot correctly to the Windows Recovery Environment?

We'll be glad to help you create a backup image. Since creating an image is unrelated to the topic of this thread, the best way to proceed is to start a new thread. When you do, please let us know which version of True Image you are using.

Beginner
Posts: 0
Comments: 6

#93

Hi Mark,

I know you must be tired of helping everyone with their Windows Boot Manager issues but I'm also having the same problem as some of the previous posters. I have a Dell laptop that I'm trying to restore to the factory state by using the recovery partition on drive D:, but when I select F8 and choose repair options the PC just boots to Windows normally (as if I never chose repair).

I would REALLY appreciate any help you can provide on helping me repair the Boot Manager files. I have attached the output to the "bcdedit /enum all" file to this post along with a screenshot of the Windows Disk Manager.

Thanks a ton for any help you can provide!!!

Steven

Attachment Size
65641-95605.txt 3.59 KB
65641-95608.jpg 121.31 KB
Forum Star
Posts: 19
Comments: 2110

#94

Steven:

These two entries look incorrect:

===============================
Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
device partition=D:
path \Windows\System32\boot\winload.exe
description Windows Recovery Environment
osdevice partition=D:
systemroot \Windows
nx OptIn
detecthal Yes
winpe Yes

Windows Boot Loader
-------------------
identifier {62553a77-83ef-11e0-a1fd-b2d5c1bd71e7}
device partition=D:
path \������\Windows\system32\boot\winload.exe
description Windows (TM) Code Name "Longhorn" Preinstallation Environment (recovered)
osdevice partition=D:
systemroot \������\Windows
detecthal Yes
winpe Yes
====================================
The first one with ID {572bcd55-ffa7-11d9-aae0-0007e994107d} is the entry that is called by the recovery sequence function (when pressing F8). The second one isn't linked to anything else and it looks like it was created by a Windows automatic repair that went bad. We will probably end up deleting it eventually.

What is odd about the first recovery sequence is that it attempts to boot directly from the D: partition. Most recovery sequences use Windows PE (Windows Pre-Installation Environment) and load a RAMDisk with a Windows Image file called WinRE.wim and then boot the Windows PE image directly.

I'm not familiar with how Dell handles their restore to factory state function, so guessing would not be a good way to proceed. So before doing anything it would be very helpful to have a look at some of the contents of your recovery partition. Let's try confirming the location of the recovery image file, if any. Please post the output of the following commands, entered from an elevated command prompt window:

dir d:\ /a > %userprofile%\Desktop\d.txt
dir d:\Recovery /a /s > %userprofile%\Desktop\recovery.txt

Each of these will create a text file on your desktop; the first will list the directory structure of the recovery partition and the second will list the contents of the Recovery folder on D:, if any, and all of its contents.

Beginner
Posts: 0
Comments: 6

#95

Hi Mark,

Thanks a ton much for getting back to me so quickly. I have output the directories of the D: to files as you asked. In addition to the root D: (filename d.txt), I also included the D:\sources (filename sources.txt) directory as that is the parent to d:\sources\recovery (filename recovery.txt). I also included the directory for d:\dell (filename dell.txt) as that is the parent directory for d:\dell\image where I believe the image file is located (factory.wim is in this subdirectory which is 3.7gb).

Let me know if any other information would be helpful and again, I really appreciate your help!

Steven

Attachment Size
65655-95611.txt 1.58 KB
65655-95614.txt 1.16 KB
65655-95617.txt 731 bytes
65655-95620.txt 617 bytes
Forum Star
Posts: 19
Comments: 2110

#96

Steven:

Yes, apparently the recovery image file is at D:\dell\image\Factory.wim. This would be the image that the Dell recovery sequence would copy to the C: partition when restoring the PC to factory state, but it isn't the file that we want to boot to. We need to boot to something that starts the recovery manager and allows it to do the restoration. Based on the information that you posted, I suspect that my first hunch (in reply #94) was wrong. This first recovery entry is the one that is incorrect:

===============================
Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
device partition=D:
path \Windows\System32\boot\winload.exe
description Windows Recovery Environment
osdevice partition=D:
systemroot \Windows
nx OptIn
detecthal Yes
winpe Yes
===============================

It is incorrect because it attempts to boot to a recovery environment at D:\Windows\System32\boot. The problem is that there is no D:\Windows\ folder on the D: partition, so this obviously is wrong. However, your main entry (with identifier {current}) links to this as the recovery sequence, so that explains why it doesn't work.

I think I had it exactly backwards; the second entry is probably correct:
=============================================
Windows Boot Loader
-------------------
identifier {62553a77-83ef-11e0-a1fd-b2d5c1bd71e7}
device partition=D:
path \������\Windows\system32\boot\winload.exe
description Windows (TM) Code Name "Longhorn" Preinstallation Environment (recovered)
osdevice partition=D:
systemroot \������\Windows
detecthal Yes
winpe Yes
====================================

This entry attempts to start an installation of Windows at the path location shown. Note that the path is named with some unprintable unicode characters. I suppose Dell did this to hide the folder from prying eyes. The easiest way to tell is to just try it. You only need to change the recoverysequence pointer in the {current} Boot Loader entry from {572bcd55-ffa7-11d9-aae0-0007e994107d} to {62553a77-83ef-11e0-a1fd-b2d5c1bd71e7}.

From an elevated command prompt window, enter the following command:

bcdedit /set {current} recoverysequence {62553a77-83ef-11e0-a1fd-b2d5c1bd71e7}

Then try using F8 at boot time to see if you can boot to the Dell Recovery Environment. If this works, let me know and I'll also give you the commands needed to delete the erroneous BCD entries and to fix a couple of other things.

Also, as a side issue, does your PC hibernate and resume from hibernation correctly? I ask because the first Boot Manager entry has resume set to No.

Beginner
Posts: 0
Comments: 6

#97

Hi Mark,

Thanks for the fast response. Unfortunately, it didn't work.

I was able to input the command successfully, but now when I press F8 on restart and choose Repair Computer I get a Blue Screen and the computer freezes. The blue screen says "A Problem has been detected and windows has been shut down to prevent damage to your computer. PROCESS1_INITIALIZATION_FAILED" At the end of the blue screen it also says in technical information "*** STOP: 0X0000006b (0Xc0000003a, 0X00000002, 0X00000000, 0X00000000).

Any other ideas? Or is there another way that doesn't use Boot manager that will let me restore from the factory restore partition on D:?

Thanks again for your help.

Steven

Forum Star
Posts: 19
Comments: 2110

#98

Steven:

Believe it or not, that's progress. The fact that you receive a blue screen stop error means that you got past the boot manager and started loading Windows from the recovery partition. In searching for the meaning of the stop error code 06b, the main cause mentioned is missing or corrupted system files needed to boot Windows.

One of the first things that I would try is to start an elevated command prompt and run chkdsk D: /r to check for and correct errors and to remove any bad sectors on the recovery partition. If this doesn't work then there must be a damaged or missing file on the recovery partition. Your options from here would be to see if Dell can supply any disks that would restore your laptop to factory state, or to clean install Vista from someone else's installation DVD and activate it with the key supplied on your laptop.

Can you shed any light on the root cause that led you to try to restore the laptop to factory state? Was it a virus, or a hard disk problem?

Beginner
Posts: 0
Comments: 6

#99

Hi Mark,

Unfortunately, no luck on the Chkdsk. I still get the same stop problem and there were no errors found during the chkdsk.

As far as next options, I have one other idea that I'd like to get your thoughts on. In the boot manager file there are several points where the directory uses non-printable unicode text (as you mentioned). Is it possible to replace the unicode with a hard reference to the right location? If so, what files should I look for on the drive to know what that location should be?

As far as the underlying problem, its just general instability, programs crashing, strange OS issues (like menus not being visible after you click on them until the mouse passes over them).

Thanks again for your help.

Steven

Legend
Posts: 172
Comments: 11125

#100

Steven,
Just curious. Do you have any TrueImage backups which included all 3 partitions inside the backup?

Also, any chance you created a Recovery CD from a program offered by Dell?

Note. I am just asking questions as I have no experience with a Dell machine.