Skip to main content

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

Thread needs solution
Beginner
Posts: 1
Comments: 9

I was wondering if any of you knowledgeable people out there could help resolve this issue i'm having with the F8 "Repair your computer" advanced boot option.

The issue is when i boot my system and choose the above boot option i get the message below on screen, i have already used the instalation DVD to repair the boot options a number of times and i've also rebuilt and recreated all entries in the BCD file using "bcdedit" aswell as "bootrec" to write a new MBR but the issue persists, Windows boots normaly and all other F8 boot options work fine, the only issue is the "Repair your computer" option.

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.

All this seemed to happen after doing a full disk restore with ATI 2010 build 5055 and 6053 to a new HDD (warranty replacement) that was an identicle HDD with the same firmware.

Thanks!

0 Users found this helpful
Beginner
Posts: 0
Comments: 1

An information for those, who have Nokia Booklet 3G or PCs with two different "wim" files:

"winRE.wim" - is Windows 7 Recovery Disk to boot to and repair the system.
"restore.wim" - is a drive C (system disk) image, which contains an pre-INSTALLED Windows 7 with all Nokia Software.
When loaded to Windows RE, use "Image X Restore" to execute the process of deploying "restore.wim" image on your system disk.

The system repair disk image is "winRE.wim".
Do not use "restore.wim" when trying to set up F8 repair BCD menu - you will get BlueScreen.

---
P.S. I have a very same problem as those described here: can't reset my device to factory state - I have F8 "repair" menu item disappeared. Still trying to fix my bcd.

Beginner
Posts: 0
Comments: 2

Hello all, I have the same, yet a bit specific problem that I'm not able to solve. I have HP laptop ProBook 4530s that came preinstalled with Windows 7 and partitioning scheme that included 4 Primary partitions:

  • 1st HP System partition, not accessible from Windows (300 MB)
  • 2nd C: Partition with Windows
  • 3rd HP_Recovery partition that contains \Recovery\WindowsRE\Winre.wim and some other *.wim files (17 GB)
  • 4th HP_Tools partition (5 GB)

I was not happy by partitioning scheme and I wanted to add a separate partition for Data. Since 4 Primary partitions were already there I needed to delete/convert one to Extended. This is the procedure:

  1. I Made an image of HP_Tools partition with Clonezilla
  2. I Deleted HP_Tools partition with GParted
  3. I Created new Extended partition with GParted
  4. I Copied existing Primary partition HP_Recovery inside Extended partition, thus creating a new Logical partition (again with GParted)
  5. I deleted original Primary partition HP_Recovery with GParted
  6. I created 6GB empty Logical partition HP_Tools with GParted
  7. I created partition D: and arranged sizes in GParted

I rebooted into Windows, there was a standard CHKDSK screen, after which Win 7 booted w/o problems.

However, when I tried starting Repair Your Computer at the startup menu, and I got the 0xc0000225 Error code and a message: The selected entry could not be loaded because the application is missing or corrupt.

I tried this solution: Using GParted to Resize Your Windows 7 or Vista Partition, no success.

I also tried solving the problem with BCDEasy, manually pointing to *.wim file. But with BCDEasy I can only add a new entry (there's no entry for Repair Your Computer option). Either way, when I try this solution I get 0xc0000017 Error: Ramdisk device creation failed due to insufficient memory

I see there are some BCD gurus here and I hope you can help me. I'm attaching current partitioning scheme and BcdEdit /enum all results.

Attachment Size
99178-100975.png 36.78 KB
99178-100978.txt 4 KB
Forum Star
Posts: 19
Comments: 2110

imagodei:

Your recoverysequence now has a new identifier, {650c99ba-5631-11e1-ab11-e45175e11ce3}. The original identifier was {650c99b8-5631-11e1-ab11-e45175e11ce3}, and several items in the BCD are still using the old (and now blank) identifier. Here are the commands needed to fix this. Enter each of them from an elevated command prompt window while booted to Windows 7:

bcdedit /set (bootmgr} custom:5400000f {650c99ba-5631-11e1-ab11-e45175e11ce3}
bcdedit /set {current} recoverysequence {650c99ba-5631-11e1-ab11-e45175e11ce3}
bcdedit /set {650c99ba-5631-11e1-ab11-e45175e11ce3} inherit {bootloader settings}
bcdedit /set {650c99ba-5631-11e1-ab11-e45175e11ce3} description "Windows Recovery Environment"
bcdedit /set {650c99ba-5631-11e1-ab11-e45175e11ce3} locale sl-SI
bcdedit /set {650c99ba-5631-11e1-ab11-e45175e11ce3} nx optin
bcdedit /delete {650c99b9-5631-11e1-ab11-e45175e11ce3}
bcdedit /set {650c99bb-5631-11e1-ab11-e45175e11ce3} description "Ramdisk Options"
bcdedit /delete {650c99b8-5631-11e1-ab11-e45175e11ce3}

Here is what each of the above commands does, in order:
1. Changes the pointer for a custom boot action (probably a function key used by HP) for Windows Boot Manager to the new ID.
2. Changes the pointer to the recovery sequence to the new ID.
3. Adds a missing entry to the Windows Recovery Environment Loader.
4. Removes the word "Recovered" from the description "Windows Recovery Environment".
5. Adds an entry to the Windows Recovery Environment Loader for your local language.
6. Adds a missing entry to the Windows Recovery Environment Loader
7. Deletes a now invalid Device Options section of the BCD
8. Adds a missing description to the current Device Options section of the BCD
9. Deletes the original (and now blank) Windows Recovery Environment Loader entry.

Beginner
Posts: 0
Comments: 1

Hi there,

I have the same problem... i can't access the recovery partition with F11 at boot up. (HP Elitebook). Attached is the output of doing a bcdedit /enum all and screen shot of partition layout

Can someone help me please?

Thanks
James

Attachment Size
100100-101128.png 113.93 KB
100100-101131.txt 4.97 KB
Forum Star
Posts: 45
Comments: 4263

James,

You could try pointing it to the existing Recovery entry:

bcdedit /set {bootmgr} custom:5400000f {da48181f-def4-11df-a67c-a73c96b347ff}
bcdedit /set {current} recoverysequence {da48181f-def4-11df-a67c-a73c96b347ff}

Beginner
Posts: 0
Comments: 1

Hi,
Im having similar issues.... I was using my computer then all of a sudden everything closed and it shut down, It said it was shutting down, and looked like it froze so i manually pressed the power button until it turned off. Now it wont boot, and no repair is fixing it. It says it has the boot/memtest.exe 0xc0000428 cannot verify digital signature, and my f8 key isnt doing anything. I have a 64bit windows 7. I do have a previous image of the computer but I was wondering if this is possible without losing all of my files.

Beginner
Posts: 0
Comments: 2

@Mark Wharton,

I'm just writing an entry in my personal problems&solutions knowledge base regarding this case and I remembered I still owe you thanks.

So there - thanks :)

Beginner
Posts: 0
Comments: 1

Having the same problems everyone else is with getting F8 Repair to work. This is on a Thinkpad T60p that I switched from an HDD to an SSD. The laptop came with a Lenovo recovery partition, which I can still acess, but lost access to the F8 repair after the clone. My diskmanager screenshot is attached. My C:\Recovery\7b4c1f53-b921-11de-9080-a8731c1e97be directory exists with boot.sdi and winre.wim in it. My bcdedit entries are below. Any help you could provide would be greatly appreciated.

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 {1e42550d-28c9-11e0-80cb-806e6f6e6963}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
customactions 0x10000ba000001
0x54000001
custom:54000001 {7b4c1f53-b921-11de-9080-a8731c1e97be}

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

Windows Boot Loader
-------------------
identifier {7b4c1f52-b921-11de-9080-a8731c1e97be}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {7b4c1f53-b921-11de-9080-a8731c1e97be}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {7b4c1f51-b921-11de-9080-a8731c1e97be}
nx OptIn

Windows Boot Loader
-------------------
identifier {7b4c1f53-b921-11de-9080-a8731c1e97be}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Professional (recovered)
locale en-US
recoverysequence {7b4c1f53-b921-11de-9080-a8731c1e97be}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {1e42550d-28c9-11e0-80cb-806e6f6e6963}
numproc 2
usefirmwarepcisettings No

Windows Boot Loader
-------------------
identifier {7b4c1f56-b921-11de-9080-a8731c1e97be}
device ramdisk=[C:]\Recovery\7b4c1f53-b921-11de-9080-a8731c1e97be\Winre.wim,{7b4c1f57-b921-11de-9080-a8731c1e97be}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\7b4c1f53-b921-11de-9080-a8731c1e97be\Winre.wim,{7b4c1f57-b921-11de-9080-a8731c1e97be}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {1e42550d-28c9-11e0-80cb-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Professional (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {7b4c1f51-b921-11de-9080-a8731c1e97be}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
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 {7b4c1f54-b921-11de-9080-a8731c1e97be}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\7b4c1f53-b921-11de-9080-a8731c1e97be\boot.sdi

Device options
--------------
identifier {7b4c1f57-b921-11de-9080-a8731c1e97be}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\7b4c1f53-b921-11de-9080-a8731c1e97be\boot.sdi

Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description Ramdisk options
ramdisksdidevice unknown
ramdisksdipath \boot\boot.sdi

Any help you could give would be appreciated.

Attachment Size
100712-101242.doc 160.5 KB
Beginner
Posts: 1
Comments: 5

Well I'm using two disks, but only can boot from the old one. I removed the old one, tried to repair nothing. can you help me out please?

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {dc1b2342-62f7-11e1-93a6-dc228179e895}
displayorder {default}
{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 {dc1b2340-62f7-11e1-93a6-dc228179e895}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {dc1b233e-62f7-11e1-93a6-dc228179e895}
nx OptIn

Windows Boot Loader
-------------------
identifier {dc1b2340-62f7-11e1-93a6-dc228179e895}
device ramdisk=[C:]\Recovery\dc1b2340-62f7-11e1-93a6-dc228179e895\Winre.wim,{dc1b2341-62f7-11e1-93a6-dc228179e895}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\dc1b2340-62f7-11e1-93a6-dc228179e895\Winre.wim,{dc1b2341-62f7-11e1-93a6-dc228179e895}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {default}
device unknown
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {dc1b2344-62f7-11e1-93a6-dc228179e895}
recoveryenabled Yes
osdevice unknown
systemroot \Windows
resumeobject {dc1b2342-62f7-11e1-93a6-dc228179e895}
nx OptIn

Windows Boot Loader
-------------------
identifier {dc1b2344-62f7-11e1-93a6-dc228179e895}

Resume from Hibernate
---------------------
identifier {dc1b233e-62f7-11e1-93a6-dc228179e895}
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 {dc1b2342-62f7-11e1-93a6-dc228179e895}
device unknown
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath \hiberfil.sys
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 {dc1b2341-62f7-11e1-93a6-dc228179e895}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\dc1b2340-62f7-11e1-93a6-dc228179e895\boot.sdi

Device options
--------------
identifier {dc1b2345-62f7-11e1-93a6-dc228179e895}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\dc1b2344-62f7-11e1-93a6-dc228179e895\boot.sdi

Attachment Size
105120-102196.png 133.07 KB
Forum Hero
Posts: 613
Comments: 8747

Girons,

Could you make a new thread with your problem please, this thread says solved so not too many people will look at it

Beginner
Posts: 1
Comments: 5

ok

Forum Star
Posts: 19
Comments: 2110

All:

I have been responding to most of the requests for help in this thread for the past 2 1/2 years. Due to heavy work and home commitments, I am unable to continue offering support at the present time. Perhaps I will have more time when the weather turns colder this fall and winter.

Beginner
Posts: 1
Comments: 5

Ok, sure u'r doing a great job here. It's 2 and 20 am here in portugal and I have to deliver the pc tomorrow at 10am :-(

Forum Hero
Posts: 613
Comments: 8747

Girons,

I'd prefer to reply to you in a new thread, but what error message do you see?

Beginner
Posts: 1
Comments: 5

I cant boot on the new disk. I have cloned with acronis, but even if I remove the old disk, the new one doesnt boot. if I insert a win7 DVD for repair i got the message:

"System Recovery Option is not compatible with..."

Forum Hero
Posts: 613
Comments: 8747

OK, are you using the auto recovery option of the Winows 7 DVD or are you at the command prompt?

You could try selecting the command prompt (alt + F2 I think) and then run bootcfg and see if that solves the problem. If it doesn't then you might need to play around with bcdedit (http://technet.microsoft.com/en-us/library/cc709667(v=ws.10).aspx).

I see there is an entry in your BCD database that has no device attached to it. I think your problem si that Windows has probably moved to a different sector so it is now refusing to boot.

What will probably save you a lot of time is to download EasyBCD install it on a USB stick and remake the BCD using their utility. All you need to do with EasyBCD is point it to the Windows folder or the boot folder and it will make all the correct entries to at least get you booting again.

http://neosmart.net/EasyBCD/

Forum Hero
Posts: 613
Comments: 8747

You could try selecting the command prompt (alt + F2 I think) and then run bootcfg and see if that solves the problem. If it doesn't then you might need to play around with bcdedit (http://technet.microsoft.com/en-us/library/cc709667(v=ws.10).aspx).

I see there is an entry in your BCD database that has no device attached to it. I think your problem si that Windows has probably moved to a different sector so it is now refusing to boot.

What will probably save you a lot of time is to download EasyBCD install it on a USB stick and remake the BCD using their utility. All you need to do with EasyBCD is point it to the Windows folder or the boot folder and it will make all the correct entries to at least get you booting again.

http://neosmart.net/EasyBCD/

Beginner
Posts: 1
Comments: 5

I'm using this on a Mac architecture, so no boot options as you speak. I will try easyBCD TY

Forum Member
Posts: 14
Comments: 16

I'm in the same boat, chkdsk won't run and F8 won't bring up SAFE MODE menu after a restore of OS partition C: to a new drive.

Any help would be appreciated!

Michael

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {692b38a7-d2a5-11e1-aa8c-782bcbacc6aa}
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 {692b38a9-d2a5-11e1-aa8c-782bcbacc6aa}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {692b38a7-d2a5-11e1-aa8c-782bcbacc6aa}
nx OptIn

Windows Boot Loader
-------------------
identifier {692b38a9-d2a5-11e1-aa8c-782bcbacc6aa}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{692b38aa-d2a5-11e1-aa8c-782bcbacc6aa}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{692b38aa-d2a5-11e1-aa8c-782bcbacc6aa}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {692b38a7-d2a5-11e1-aa8c-782bcbacc6aa}
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 {692b38aa-d2a5-11e1-aa8c-782bcbacc6aa}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Forum Member
Posts: 14
Comments: 16

I'm creating a new topic for this issue, as this topic is marked as solved.

Beginner
Posts: 0
Comments: 1

Hi Mark,

Need your help on the topics... here is my result from bcdedit...
it's a headache to most of us, but it seems very simple and easy for you.. - respect!!

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=DeviceHarddiskVolume1
path bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {45cc25a7-67d6-11e0-9cf0-806e6f6e6963}
displayorder {current}
{96f2dc3b-4499-11e0-9563-f95850751ccc}
toolsdisplayorder {memdiag}
timeout 1
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {79a3cdd6-659d-11e0-9015-c075e34784d1}
device unknown
path Windowssystem32winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {79a3cdd7-659d-11e0-9015-c075e34784d1}
recoveryenabled Yes
osdevice unknown
systemroot Windows
resumeobject {79a3cdd5-659d-11e0-9015-c075e34784d1}
nx OptIn

Windows Boot Loader
-------------------
identifier {79a3cdd7-659d-11e0-9015-c075e34784d1}

Windows Boot Loader
-------------------
identifier {current}
device partition=C
path Windowssystem32winload.exe
description Windows 7 Professional
locale en-US
recoverysequence {79a3cdd7-659d-11e0-9015-c075e34784d1}
recoveryenabled Yes
osdevice partition=C
systemroot Windows
resumeobject {45cc25a7-67d6-11e0-9cf0-806e6f6e6963}
sos No
debug No

Windows Boot Loader
-------------------
identifier {79a3cdda-659d-11e0-9015-c075e34784d1}

Windows Boot Loader
-------------------
identifier {96f2dc3b-4499-11e0-9563-f95850751ccc}
device boot
path windowssystem32bootwinload.exe
description Recover BackUp
osdevice boot
systemroot windows
resumeobject {8dc0f3cc-449a-11e0-b3bb-806e6f6e6963}
detecthal Yes
winpe Yes

Resume from Hibernate
---------------------
identifier {45cc25a7-67d6-11e0-9cf0-806e6f6e6963}
device partition=C
path Windowssystem32winresume.exe
description Windows 7 Professional (recovered)
locale en-US
inherit {resumeloadersettings}
filedevice partition=C
filepath hiberfil.sys
pae Yes
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {79a3cdd5-659d-11e0-9015-c075e34784d1}
device unknown
path Windowssystem32winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice unknown
filepath hiberfil.sys
pae Yes
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {8dc0f3cc-449a-11e0-b3bb-806e6f6e6963}
device boot
path windowssystem32bootwinresume.exe
description Recover BackUp
inherit {resumeloadersettings}
filedevice partition=DeviceHarddiskVolume1
filepath hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=DeviceHarddiskVolume1
path bootmemtest.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 {79a3cdd8-659d-11e0-9015-c075e34784d1}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath Recovery79a3cdd7-659d-11e0-9015-c075e34784d1boot.sdi

Device options
--------------
identifier {79a3cddb-659d-11e0-9015-c075e34784d1}
ramdisksdidevice unknown
ramdisksdipath Recovery79a3cdd7-659d-11e0-9015-c075e34784d1boot.sdi

Beginner
Posts: 0
Comments: 1

Hi Mark,

Need your help on the topics,please. Here is my result from bcdedit...
it's a headache to most of us, but it seems very simple and easy for you.. - respect!!

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

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {95b0f22b-dc52-11e1-a8d7-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {691449c2-dc6e-11e1-9ae2-82335aa8ed78}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
re.wim,{691449c3-dc6e-11e1-9ae2-82335aa8ed78}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
re.wim,{691449c3-dc6e-11e1-9ae2-82335aa8ed78}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {95b0f22b-dc52-11e1-a8d7-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Premium
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

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

Device options
--------------
identifier {691449c3-dc6e-11e1-9ae2-82335aa8ed78}
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Attachment Size
106300-102400.jpg 193.14 KB
Beginner
Posts: 0
Comments: 1

Hello. I have a Dell XPS L502X. The booting procedure in my laptop is like this: The recovery partition (from dell) is the active one, not the windows partition (both primary). So the computer boots from "boot" folder inside recovery partition, and when pressing F8, it calls contents of "recovery" folder inside recovery partition. (Windows partition does not have a "recovery" folder. But, the problem is: earlier I installed ATIH, activated Startup recovery of that, then installed ADD, and installed OS selector. The active partition changed to Windows partition. Before all these I had installed Ubuntu with GRUB 2 bootloader, and so, after all these mess , I noticed Launch System Recovery is crashed with this GUID errors. So I wanted to repair boot to it's defaults, so inserted the Recovery Disk I created earlier & inside that, there was a "recovery" folder with contents so similar to the recovery partition's "recovery" folder, so I copied & overwrited the whole recovery folder from Disk to the partition.
But the situation didn't change at all. Besides, when I read your instructions, I couldn't put them in use because there isn't any {e55hg8ij...} like folder or path neither in "recovery" nor the "boot" folder of recovery partition! nor the "boot" folder of windows partition! boot.sdi & winre.wim are located in a folder named "windowsre" inside "recovery" folder.
Now I've edited the BCD of recovery partition using easyBCD.
Here are exact specs of my boot:
dev/sda2 : Windows 7 >> the recovery partition.
dev/sda3 : Windows 7 >> the windows partition.
dev/sda5 : Ubuntu 12.04
==================================
also i boot with grub 2 and here are entries:
Ubuntu 12.04 generic...(can't remember rest)
Ubuntu 12.04 generic... (recovery mode)
memtest+86
memtest+86 (serial console)
windows 7 (loader) on dev/sda2 >> (recovery partition)
windows 7 (loader) on dev/sda3 >> (Windows partition)
Windows 7 >> I created this manually with grub (on dev/sda2)
Acronis True Image Home Recovey Manager
==================================
Also this is my bcdedit/enum all:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
resumeobject {c6ce8cb8-d1e5-11e1-a88e-b24ea5e9a6e6}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {c6ce8cba-d1e5-11e1-a88e-b24ea5e9a6e6}

Windows Boot Loader
-------------------
identifier {c6ce8cbc-d1e5-11e1-a88e-b24ea5e9a6e6}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Win
re.wim,{c6ce8cbd-d1e5-11e1-a88e-b24ea5e9a6e6}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Win
re.wim,{c6ce8cbd-d1e5-11e1-a88e-b24ea5e9a6e6}
systemroot \windows
detecthal Yes
winpe Yes

Windows Boot Loader
-------------------
identifier {fb86b163-1c7b-11e1-bd82-4c80932d8b41}

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \boot\memtest.exe
description Windows Memory Diagnostic

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 {c6ce8cbd-d1e5-11e1-a88e-b24ea5e9a6e6}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\windowsre\boot.sdi

=============================================
I just want to reset to it's default stats (Boot from recovery partition, then it chainloads ( or anything)
to windows partition, & when I press f8, the Recovery Options loads good)

*Currently only the "Boot" folder exists in windows folder.

*I said every bit of information I could, wishing to solve this problem which can ONLY be done by you, Mr. Wharton. You're a wise man, now my only wish in solving this bad ass problem is this forum & YOU!
Thank You very much in advance!

Attachment Size
109895-103225.png 18.17 KB
Beginner
Posts: 0
Comments: 2

please help. i think that my disk partition tables have problems.... this the text obtained of console
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {54ea8ac8-584c-11e1-94c5-d4bed9039b74}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {54ea8acc-584c-11e1-94c5-d4bed9039b74}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
recoverysequence {54ea8acc-584c-11e1-94c5-d4bed9039b74}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {eca7872b-1c0b-11e2-bf50-806e6f6e6963}

Windows Boot Loader
-------------------
identifier {54ea8ad2-584c-11e1-94c5-d4bed9039b74}
device ramdisk=[D:]\Recovery\windowsre\Winre.wim,{54ea8ad3-584c
-11e1-94c5-d4bed9039b74}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[D:]\Recovery\windowsre\Winre.wim,{54ea8ad3-584c
-11e1-94c5-d4bed9039b74}
systemroot \windows
winpe Yes

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

Resume from Hibernate
---------------------
identifier {eca7872b-1c0b-11e2-bf50-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
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 {54ea8acd-584c-11e1-94c5-d4bed9039b74}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {54ea8ad0-584c-11e1-94c5-d4bed9039b74}
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\windowsre\boot.sdi

Device options
--------------
identifier {54ea8ad3-584c-11e1-94c5-d4bed9039b74}
ramdisksdidevice partition=D:
ramdisksdipath \Recovery\windowsre\boot.sdi

Device options
--------------
identifier {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
description Ramdisk loader
ramdisksdidevice unknown
ramdisksdipath \windows\boot\dvd\pcat\boot.sdi

Forum Star
Posts: 19
Comments: 2110

edgar:

F8 isn't working for you because the recoverysequence entry in the main Windows 7 loader is pointing to the incorrect location. Also, you have several orphaned BCD entries that don't do anything; they seem to be the result of many automatic repair attempts that didn't succeed. The fourth command below should fix the main problem and the other commands are to clean up the orphaned entries. Enter each of them in an administrative command prompt, one at a time. Copy/paste is recommended since it's very easy to miss a digit in the long GUID entries.

bcdedit /set {bootmgr} resumeobject {eca7872b-1c0b-11e2-bf50-806e6f6e6963}
bcdedit /delete {54ea8acc-584c-11e1-94c5-d4bed9039b74}
bcdedit /set {current} description "Windows 7 Home Premium"
bcdedit /set {current} recoverysequence {54ea8ad2-584c-11e1-94c5-d4bed9039b74}
bcdedit /set {current} nx OptIn
bcdedit /set {54ea8ad2-584c-11e1-94c5-d4bed9039b74} description "Windows Recovery Environment"
bcdedit /set {54ea8ad2-584c-11e1-94c5-d4bed9039b74} locale en-US
bcdedit /set {54ea8ad2-584c-11e1-94c5-d4bed9039b74} nx OptIn
bcdedit /set {54ea8ad2-584c-11e1-94c5-d4bed9039b74} inherit {bootloadersettings}
bcdedit /delete {572bcd55-ffa7-11d9-aae0-0007e994107d}
bcdedit /set {eca7872b-1c0b-11e2-bf50-806e6f6e6963} description "Windows Resume Application"
bcdedit /delete {54ea8acd-584c-11e1-94c5-d4bed9039b74}
bcdedit /delete {54ea8ad0-584c-11e1-94c5-d4bed9039b74}
bcdedit /set {54ea8ad3-584c-11e1-94c5-d4bed9039b74} description "Ramdisk Loader"
bcdedit /delete {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}

Beginner
Posts: 0
Comments: 2

thanks... the system is working correctly...

best regards...

good help...

Beginner
Posts: 0
Comments: 5

Hello Mark,

I was wondering if you would be kind enough to help me with my F8 problem. I can imagine that you are now ultimately fed up with spending time on this issue, but I would most greatly appreciate if you could help me out as well. Here comes my BCD file and also a snapshot of my drives.

Thanks in advance

Dennis

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {b3748ed5-2880-11e2-b2dc-ea7d503641d4}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
displaybootmenu Yes

Windows Boot Loader
-------------------
identifier {a6fca4ca-22b7-11e2-8d7b-fb228c42bf0b}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{a6fca4cb-22b7-11e2-8d7b-fb228c42bf0b}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{a6fca4cb-22b7-11e2-8d7b-fb228c42bf0b}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {a6fca4ce-22b7-11e2-8d7b-fb228c42bf0b}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\a6fca4ce-22b7-11e2-8d7b-fb228c42bf0b\Winre.wim,{a6fca4cf-22b7-11e2-8d7b-fb228c42bf0b}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-GB
inherit {bootloadersettings}
custom:15000065 3
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\a6fca4ce-22b7-11e2-8d7b-fb228c42bf0b\Winre.wim,{a6fca4cf-22b7-11e2-8d7b-fb228c42bf0b}
systemroot \windows
nx OptIn
custom:250000c2 1
winpe Yes

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {b3748ed7-2880-11e2-b2dc-ea7d503641d4}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {b3748ed5-2880-11e2-b2dc-ea7d503641d4}
nx OptIn

Windows Boot Loader
-------------------
identifier {b3748ed7-2880-11e2-b2dc-ea7d503641d4}
device ramdisk=[C:]\Recovery\b3748ed7-2880-11e2-b2dc-ea7d503641d4\Winre.wim,{b3748ed8-2880-11e2-b2dc-ea7d503641d4}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\b3748ed7-2880-11e2-b2dc-ea7d503641d4\Winre.wim,{b3748ed8-2880-11e2-b2dc-ea7d503641d4}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {cb54800d-286b-11e2-b46a-e8fef447dfd4}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\7bcb8fe3-e25b-11e1-8016-a36ff61609fc\Winre.wim,{cb54800e-286b-11e2-b46a-e8fef447dfd4}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\7bcb8fe3-e25b-11e1-8016-a36ff61609fc\Winre.wim,{cb54800e-286b-11e2-b46a-e8fef447dfd4}
systemroot \windows
winpe Yes

Resume from Hibernate
---------------------
identifier {b3748ed5-2880-11e2-b2dc-ea7d503641d4}
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 {a6fca4cb-22b7-11e2-8d7b-fb228c42bf0b}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {a6fca4cf-22b7-11e2-8d7b-fb228c42bf0b}
description Windows Recovery
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\a6fca4ce-22b7-11e2-8d7b-fb228c42bf0b\boot.sdi

Device options
--------------
identifier {b3748ed8-2880-11e2-b2dc-ea7d503641d4}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\b3748ed7-2880-11e2-b2dc-ea7d503641d4\boot.sdi

Device options
--------------
identifier {cb54800e-286b-11e2-b46a-e8fef447dfd4}
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\7bcb8fe3-e25b-11e1-8016-a36ff61609fc\boot.sdi

Attachment Size
115816-104578.jpg 193.89 KB
Forum Star
Posts: 19
Comments: 2110

Dennis:

I'm having difficulty making sense of your partition layout shown in the picture that you attached (diskmanagement.jpg). The figure shows four partitions; let's call them (in order from left to right) partition 1 (2.07 GB), partition 2 (277.46 GB), partition 3 (4.88 GB), and partition 4 (13.67 GB).

The labels on the figure show that partitions 1, 3, and 4 are all called a "Recovery Partition". The BCD has links to the recovery files on both partitions 1 and 2. What are the contents of partitions 3 and 4?

It would be helpful if you could use Disk Management to assign temporary drive letters to partitions 1, 3, and 4 so that they become visible in Windows Explorer. Then have a look at the contents of each partition. You will need to set Windows Explorer to display both hidden and protected operating system files.

Before making any changes we need to know where the recovery files are located. I see BCD entries that show them on partition 1 in a folder named "Recovery" and also on the main C partition (2) in a folder named "Recovery". Are they? And what is on partitions 3 and 4? Nothing in the BCD references anything on these partitions.

Beginner
Posts: 0
Comments: 5

Hello Mark,

Thank you very much for dedicating your time on this.

Here comes the snapshots for each partition.

Dennis

Attachment Size
115884-104584.jpg 174.75 KB
115884-104587.jpg 154.23 KB
115884-104590.jpg 125.75 KB
115884-104593.jpg 125.44 KB
Forum Star
Posts: 19
Comments: 2110

Dennis:

Good. So partitions 3 and 4 are used as recovery partitions by Fujitsu.

In the partition 1 screen shot could you expand the two folders a6fca4c3-... and 7bcb8fe3-... so that I can see their contents?

Beginner
Posts: 0
Comments: 5

Hello again,

Here it comes.

Dennis

Attachment Size
115903-104596.jpg 184.87 KB
Forum Star
Posts: 19
Comments: 2110

Thanks, Dennis.

I'm trying to be careful because I've never seen so many recovery images on a system and I don't want to recommend any changes that would mess up Toshiba's recovery scheme.

Two more questions:
1. Can you expand the Recovery folder on partition 1 to show its contents?
2. Is your operating system Windows 7 64-bit?

Beginner
Posts: 0
Comments: 5

No problem Mark,

Here comes the contents that you requested.

And yes it is Windows 7 64-bit.

the computer is Fujitsu AH531

Thank you very much

Dennis

Attachment Size
115906-104599.jpg 105.66 KB
Forum Star
Posts: 19
Comments: 2110

Dennis:

Thanks. Let me study these for a while to see if I can figure it out.

Forum Star
Posts: 19
Comments: 2110

Dennis:

If you look at your BCD, the entry that boots Windows 7 is the third Windows Boot Loader entry starting from the top with the identifier {current}. It is referencing the recovery sequence {b3748ed7-...}, which is described in the 4th Windows Boot Loader entry starting from the top. This one is the entry used when pressing F8 while the computer is booting that is supposed to boot into the Windows Recovery Environment. The files referenced in this entry are located in the second partition, which is the main Windows C partition. The file dates on these files are recent, which suggests that they were just added by an automatic recovery attempt.

The confusing thing about your setup is that there are also three other sets of Recovery folders located on the first partition and corresponding entries in the BCD for each of them (entry 1, entry 2 - a custom Toshiba recovery entry, and entry 5). I don't see any BCD entries that look incorrect, so perhaps you're just pointing to the wrong set of recovery files.

On a clean Windows 7 x64 installation the file boot.sdi is 3.02 MB and the file WinRE.wim is 160.59 MB. All of your boot.sdi files are the correct size, and none of your WinRE.wim files are the correct size, but perhaps because Toshiba has customized them. You have one on partition 2 that is 258.92 MB, one on partition 1 that is 274.77 MB, and two more on partition 1 that are 190.96 MB. I have no idea which is the correct one.

Currently you're using the one on partition 2. I'm going to guess that the one (\Recovery\winre.wim) that's in partition 1 may be the one you want since it's the first in the sequence and the file dates are older than the others. To test this, just change the Recoverysequence entry in the main Windows Boot Loader from {b3748ed7-2880-11e2-b2dc-ea7d503641d4} to {a6fca4ca-22b7-11e2-8d7b-fb228c42bf0b} by starting an elevated command prompt and entering:

bcdedit /set {current} recoverysequence {a6fca4ca-22b7-11e2-8d7b-fb228c42bf0b}

If this doesn't work or if it starts a Toshiba "return to factory settings" function or something other than the standard Recovery Environment then change it back:

bcdedit /set {current} recoverysequence {b3748ed7-2880-11e2-b2dc-ea7d503641d4}

Beginner
Posts: 0
Comments: 5

Mark!

You are a genious. Thank you very much for all help. It works flawlessly.
I have a quick question. When I installed Windows 8, I could not get to the f8 screen. Instead i can got into "Restore your windows" from settings/general menu. But from there I can't access Fujitsu's own restore function.

This is why I asked for your help. In case I decide to install windows 8 again, do you know a way to access the Fujitsu image?

Thanks again for everything.
Dennis

Forum Star
Posts: 19
Comments: 2110

Dennis:

I'm going to install Windows 8 during Thanksgiving week so I don't have any direct experience to go on yet. The following is just a hypothesis. I suspect that the Win 8 installer will replace the BCD if you're doing a clean install, or keep the existing BCD but replace the Windows Boot Loader entry for Windows 7 with an entry for Windows 8 if you're doing an upgrade install. Remember, I'm just guessing here.

If the installer does remove the Windows 7 Boot Loader entry then the link to the recovery sequence (recoverysequence {a6fca4ca-22b7-11e2-8d7b-fb228c42bf0b}) will be replaced with a new link to the Windows 8 Recovery folder. But you should be able to change the link back to the Toshiba Recovery folder the same way as you just did, provided that the installer doesn't also delete the Recovery folder in partition 1. I really doubt that it would do this, however.

Since you're posting in the Acronis True Image forum then just create an image of your machine just before the upgrade. If things go south then just restore the image. If everything works except F8, post again and attach a copy of the Windows 8 BCD and I'll try to figure out what happened.

Forum Star
Posts: 19
Comments: 2110

Dennis:

I just installed Windows 8 and have some feedback about the loss of the F8 key. It is disabled by default in Windows 8 but there are alternate ways of accessing the recovery environment. Or, you can edit the BCD to restore Windows 7 type behavior.

I did a clean install and the Windows Installer put the Recovery folder on the hidden System Reserved partition. That makes a lot more sense than the Windows 7 default location in the Windows partition. So I'm fairly certain that what I said in reply #237 is accurate. You will need to change the recoverysequence pointer back to your Toshiba recovery folder.

Since Windows 8 disables the F8 key by default, to reach the recovery manager you can do one of two things. First, from the GUI, go to PC Settings --> General --> Advanced Startup. Upon reboot you'll enter the recovery environment. Or, you can edit the BCD to restore the Windows 7 behavior by the following command:

bcdedit /set {default} bootmenupolicy legacy

The F8 key will then function as normal. To return to the new Windows 8 behavior enter the following command:

bcdedit /set {default} bootmenupolicy standard

The legacy boot menu is the black on white text menu. The standard boot menu is graphical and icon based. If you have more than one OS installed then you select via clicking an icon.

For tablet PCs without keyboards, WinPE 4.0 allows touch or pen input.

Beginner
Posts: 0
Comments: 4

Hello Mark,

This seems to be the only online souce that has been succesful in helping people with problems similar to mine. My problem is that after switching to SSD, I no longer get the Repair My Computer option when booting with F8. I noticed that there is a folder named Recovery in my C: drive, which contains 2 files (Winre.wim and boot.sdi), if that helps diagnose the problem. I do not have any other active drives/partitions in my system.

I see that everyone in here have posted the results of bcdedit /enum all, so here are mine:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {274ca636-0ae5-11e2-b366-b09ff4517b69}
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}
osdevice partition=C:
systemroot \windows
resumeobject {274ca636-0ae5-11e2-b366-b09ff4517b69}
nx OptIn
detecthal Yes

Resume from Hibernate
---------------------
identifier {274ca636-0ae5-11e2-b366-b09ff4517b69}
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=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}

Hope that you can help me. Thank you in advance. :)

JR

Beginner
Posts: 0
Comments: 19

hi everybody, I have the same problem, I can not boot on "Repair your computer" with F8 and F11 (to restore the factory settings).
First, I apologize for my english, it's bad.
I have a HP ProBook 4530s with Windows 7 Home Premium 64-bit.
so, I read what you wrote but I can not seem to find where is the problem
can you help me please and explain me step by step (I easily lost: P).
Here are the screenshots I've made
I need to reset the computer to the default settings because I have lots of problem
thank you

Attachment Size
119197-105217.jpg 225.68 KB
119197-105220.jpg 186.38 KB
119197-105223.jpg 175.36 KB
119197-105226.txt 4 KB
119197-105229.jpg 205.38 KB
Beginner
Posts: 0
Comments: 19

and there is a picture display when I click "F11" to boot from the recovery partition to restore factory settings

Attachment Size
119198-105232.jpg 634.11 KB
Forum Star
Posts: 19
Comments: 2110

John:

Your BCD does not contain a loader entry for the recovery environment, its RAMdisk, or a pointer to the recovery sequence. One possibility is that the Recovery Environment is disabled. If disabled, all of the above items are removed from the BCD.

The simplest thing to try first is to enable the Recovery Environment. Windows provides a command-line tool to do this. Here is the syntax:

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

C:\Windows\system32>reagentc /?
Configures the Windows Recovery Environment (RE).
REAGENTC.EXE [options]
  where the following operations can be specified:
  /setreimage /path <dir_name> [/target <dir_name>] [/bootkey <scan_code>]
             Sets the location of the user-provided Windows RE image.
             The optional /target switch specifies the path to the location
             that contains the Windows installation.
             The optional /bootkey switch specifies the scan code for an
             OEM-specific launch button.
  /setosimage [/path <dir_name> [/target <dir_name>]] [/customtool]
             /path sets the location of the user-provided OS Setup files.
             Alternatively /customtool specifies that a an imaging tool
             was specified inside Windows RE.
  /info [/target <dir_name>]
             Displays Windows RE configuration information.
             The optional /target switch specifies the path to the location
             that contains the Windows installation.
  /enable
             Enable Windows RE for auto-failover and recovery.

  /disable
             Disable Windows RE auto-failover and recovery.
  /boottore
             Configure the BCD to launch Windows Recovery next time the system
             starts up.
REAGENTC.EXE: Operation successful

Try it by entering the following into an elevated command prompt:

reagentc /enable

Then re-list your BCD contents to see if the entries were added back. If so, you can then enter the following command:

reagentc /boottore

This configures the PC to boot into the recovery environment at the next reboot. Reboot to test.

See if that works first. If not, we'll go from there.

Forum Star
Posts: 19
Comments: 2110

Asconio:

Please post the output of the following command:

reagentc /info

Enter the command into an elevated command prompt window.

Beginner
Posts: 0
Comments: 4

Mark,

Hello and thanks for taking the time to help me!

I apologize, but meanwhile I panicked and decided to try some BCDEDIT commands on my own. This is all new to me and I am not technically skilled, but in my desperation I thought it made sense. I promise I will not do any of that from now on and just follow your advice. Anyway, what I did was manually add the following two lines:

recoverysequence {ef339fda-8dae-11e0-8970-83f5d21005d8}
recoveryenabled Yes

As you can guess, this made the "Repair My Computer" option to reappear at the F8 menu, but without actually entering the receovery environment.

Now, regarding you suggestion, REAGENTC /enable was successful, but REAGENTC /boottore returned the following:

REAGENTC.EXE: Operation failed: 2
The system cannot find the file specified.

My current BCDEDIT is:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {274ca636-0ae5-11e2-b366-b09ff4517b69}
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 {ef339fda-8dae-11e0-8970-83f5d21005d8}
recoveryenabled Yes
osdevice partition=C:
systemroot \windows
resumeobject {274ca636-0ae5-11e2-b366-b09ff4517b69}
nx OptIn
detecthal Yes

Resume from Hibernate
---------------------
identifier {274ca636-0ae5-11e2-b366-b09ff4517b69}
device partition=C:
path \windows\system32\winresume.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
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}

Many thanks,
John

Beginner
Posts: 0
Comments: 19

Mark
hi, thank you to answer me and thanks for taking the time to help me
i used < Google traslate > because my "CMD" is in FRENCH
I use google translation because my "elevated command prompt window" is French
I entered the following command: ""reagentc / info"" and here is the result:

extended configuration for the recovery environment
Windows RE on : 1
RE through windows : 0
activated installation : 1
custom recovery tool : 1
WinRE.WIM directory :
recovery environment :
BCD ID for windows RE : 564a65cb-2b77-11e1-941st-f70bf23216e3
installation files :
recovery operation: 1
operation parameter :
scan code of the ignition key 0x8500
REAGENTC.EXE: The operation completed successfully

Forum Star
Posts: 19
Comments: 2110

John:

That's OK - no harm done. We will have to add the loader entries manually then. First, could you post the output of the following command from an elevated command prompt:

reagentc /info

I'd like to see if your system remembers any of the stored WinRE configuration information. If not, we'll dig it out ourselves. We will need to know the exact path to the files WinRE.wim and boot.sdi in the recovery folder.

Beginner
Posts: 0
Comments: 4

Alright. Here it is:

Extended configuration for the Recovery Environment

Windows RE enabled: 1
Windows RE staged: 0
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory:
Recovery Environment: \\?\GLOBALROOT\device\harddisk2\partition1\Recovery\ef339fda-8dae-11e0-8970-83f5d21005d8
BCD Id: ef339fda-8dae-11e0-8970-83f5d21005d8
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful

The Recovery folder has the following structure:

c:\Recovery\ef339fda-8dae-11e0-8970-83f5d21005d8\boot.sdi [3.02 MB (3,170,304 bytes)]
c:\Recovery\ef339fda-8dae-11e0-8970-83f5d21005d8\Winre.wim [161 MB (169,213,970 bytes)]

Thanks,
John

Beginner
Posts: 0
Comments: 19

hi Mark,
please, can you help me to solve my problem
thank you

Forum Star
Posts: 19
Comments: 2110

Asconio:

Yes, but it may be later today. I am still working on John's problem (reply #239).

Beginner
Posts: 0
Comments: 19

ah sorry I did not know
I waiting for you when you finished ( tomorrow, next week,... lol )
thank you and good luck