Windows 7, "Repair your computer" F8 boot option not working (SOLVED)
Hello, sorry for reviving this thread but i have similar problems.
Here's my short story, i upgraded my alienware laptop to windows 10 and decided to go downgrade again in windows 7.
Since then my system was extremely slow and things werent working properly. I decided to restore my laptop to factory settings. F8 repair would'nt load giving me an "inaccessible boot device" or something like that.
I tried to tweak my way through using bdc and fixboot.I failed miserably, now F8 wont even give me a repair option. I tried repairing everything using my windows 7 cd. Still no chance. Also Alienrespawn (dell's backup application) is not working for me and i can't reinstall it cause i get a message that my pc doesn't have windows RE enviroment so it can't run.
My laptop has a factory image that works through 'repair your computer' where it restores all the factory settings.
I also tried restoring winRE.wim, still nothing works. So now under this thread im trying to find my way through.
reagentc commands arent working properly for me:
E:\>reagentc /setreimage /path C:\recovery\ REAGENTC.EXE: Operation failed: b7 Cannot create a file when that file already exists.E:\>reagentc /disable REAGENTC.EXE: Operation failed: 2 The system cannot find the file specified.
E:\>reagentc /boottore REAGENTC.EXE: Operation failed: 2 The system cannot find the file specified.
here's my bcd enum:
--------------------
identifier {bootmgr}
device partition=E:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {current}
{e876fe16-5b3a-11e5-861a-983bcfd66506}
toolsdisplayorder {memdiag}
timeout 10
displaybootmenu Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium (recovered)
locale en-US
recoverysequence {a852e228-36df-11e1-9d5f-9cb70d003abc}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {cdc3e981-5ade-11e5-a4f1-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {e876fe16-5b3a-11e5-861a-983bcfd66506}
device ramdisk=[C:]\Recovery\windowsRE\winRE.wim,{e876fe15-5b3a
-11e5-861a-983bcfd66506}
path \Windows\System32\Boot\winload.exe
description NST WinPE Image
locale en-US
osdevice ramdisk=[C:]\Recovery\windowsRE\winRE.wim,{e876fe15-5b3a
-11e5-861a-983bcfd66506}
systemroot \Windows
detecthal Yes
winpe Yes
Resume from Hibernate
---------------------
identifier {cdc3e981-5ade-11e5-a4f1-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=E:
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 {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0\boot.sdi
---------------------
identifier {ramdiskoptions}
description RamdiskOptions
ramdisksdidevice partition=E:
ramdisksdipath \NST\boot.sdi
Device options
--------------
identifier {e876fe15-5b3a-11e5-861a-983bcfd66506}
description NST WinPE Image
ramdisksdidevice partition=E:
I'm not sure how to proceed from this point.. thank you in advance!
Update!
I managed to restore factory image using Command line with my windows CD.
However as some of you already know, there is no way to restore the factory MBR even with a factory image. So F8 "repair your computer" still doesn't show up and i m having troulbe with alienrespawn also, probably gonna have with other things too.
So i'm at this point where I found out that Dell uses a custom MBR to boot up. I found on the web some tools, including this one:
http://www.goodells.net/dellrestore/fixmbr.shtml
The only thing i m missing is a dell factory MBR to import it but i can't find one nowhere.
Dell's support doesnt seem to even realise my problem, suggesting all kind of things like reinstall windows blah blah blah (most of them i tried already) and they can't provide me with a factory MBR.
So if you guys know where I can find one or any of you can kindly upload yours for me i would be greatful.
Thank you in advance and sorry for the long post!
stelios:
Sorry for the delay in responding - busy at work.
Now that you have restored the PC to factory image, please re-post your BCD. Please attach it as a .txt file. From Windows, open an administrative command prompt window and type:
bcdedit /enum all > %userprofile%\Desktop\bcd.txt
Hello mark. I have more news. I was too tired of this mess, and since dell uses custom MBR and I couldnt find it anywhere (Dell and microsoft wouldnt help, i had to wait days in customer service to get a reply).
What I did: Backed up all the secret "RECOVERY"partition including "factory.wim"
Deleted recovery partition and merged it with the windows one.
Formatted them. Clean installation of windows 7 64.
I just finished installing the drivers.
However i think i stil have an issue with the MBR since the last time i Booted it made me select which OS to boot (while only windows 7 is installed)
ALSO, i think i'm experiencing the exact same problem that made me want to system restore in the first place
The disk is in constant low-activity.
I can see things lagging, especially games, java applications (facebook, browser games) Everytime i open resource monitor i see things like $mft $logfile and system volume information folder being used constantly. example:
http://i.imgur.com/2lu49hR.png
Also here is my bcd:
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {faaed59f-5c63-11e5-9220-e6b565ec541e}
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 {faaed5a1-5c63-11e5-9220-e6b565ec541e}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {faaed59f-5c63-11e5-9220-e6b565ec541e}
nx OptIn
Windows Boot Loader
-------------------
identifier {faaed5a1-5c63-11e5-9220-e6b565ec541e}
device ramdisk=[C:]\Recovery\faaed5a1-5c63-11e5-9220-e6b565ec541e\Winre.wim,{faaed5a2-5c63-11e5-9220-e6b565ec541e}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\faaed5a1-5c63-11e5-9220-e6b565ec541e\Winre.wim,{faaed5a2-5c63-11e5-9220-e6b565ec541e}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {faaed59f-5c63-11e5-9220-e6b565ec541e}
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 {faaed5a2-5c63-11e5-9220-e6b565ec541e}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\faaed5a1-5c63-11e5-9220-e6b565ec541e\boot.sdi
stelios:
I don't see any issues with your BCD and am not sure why you would see a boot menu at startup - you only have one OS listed in your BCD. One thing you could check is the setting of the Default operating system in the Startup and Recovery part of the Advanced tab on System Properties, shown in the screenshot below.
Hello mark.
It seems that i managed to fix few things using your instructions but the problem remains
Ii'm still experiencing the issues i had before the format, that made me want to recover in the first place. Everything is TOO slow, even web pages in browser are slow. not to mention freezes in games. Also when using more than one program the screen might freeze for few seconds.
However, There is an issue it seems i disregarded even before the corrupted MBR.
Everytime I boot up, before the windows loading screen i get a message that my AC adapter is not recognized and it will run on 150W and the system will run on less power, something like that. Then i have to press F1 to continue to boot.
This happens EVERYtime i boot. I never gave much attention to this since this was happening occasionaly and i usualy just rebooted or turn off the laptop, remove the adapter and connect it again, then it was all ok.
Dell tech said that my system is running on much lower power than it should and it might be the reason my MBR got corrupted in the first place. They re sending me a new AC adapter which i ll get prob tomorrow. I hope this will solve the problem and it s not a motherboard issue,MBR virus or something else.
Thanks alot for your help so far!
stelios:
While you wait for the replacement AC adapter you might want to check your disk(s) for bad sectors. Constant disk activity and/or delays while opening files are symptomatic of hard disk problems. For each partition that is visible in Windows, open an administrative command prompt and run
chkdsk X: /r
where X: is the drive letter of the disk. For the Windows partition you will be prompted to schedule a disk check the next time the PC reboots, so do that. For any partitions that are not visible in Windows, boot from your Windows 7 DVD and run chkdsk from there.
Since your system boots, the MBR is doing its job properly.
Mark,
My name is Joe. I'm obviously new but I sent you a PM regarding the bcdedit for my Win7 install and I too am stuck like the OP from 2013.
I am hoping you can help me. If so, feel free to respond here here, PM or at the email I provided.
Thanks,
Joe
Joe:
My apologies for the delay but I had a situation develop at work that required my full-time attention for the past week.
When you say that you keep getting errors, please describe what you are doing that produces the error and include the exact text of the error message. You also say that you want to reinstall Windows 7. To do this you have to have a manufacturer's recovery partition with the necessary files. Otherwise, the "Repair Your Computer" option in Windows 7 is just for repair; it doesn't contain the files needed to reinstall Windows.
Who made your PC and does it have a feature for restoring to factory state? If not, then you could borrow a Windows 7 DVD from someone to use for the purpose of reinstalling Windows on your PC.
I don't see any obvious errors in your BCD, so that doesn't appear to be the issue.
Hi Mark you look like the guy i need now :)
I upgraded my Surface Pro 3 to Win 10 from Win 8.1 a few months ago i did a clean install but something isnt working anymore. Now i cant boot anymore from my Surface :(
First i got this:
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."
I struggle since hours and i seems it got even worse. I tried with programs like EasyBCD or Visual BSD to fix it but now i doesnt even show my bootable USB at startup.
This is what i get from bcdedit:
Microsoft Windows [Version 10.0.10240]
(c) 2015 Microsoft Corporation. All rights reserved.
C:\Windows\system32>bcdedit /enum all
Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {6ad24b4d-71e2-11e5-aec8-60029283c868}
{30cccae1-71e3-11e5-aec9-806e6f6e6963}
{25ca094b-71ec-11e5-aed1-806e6f6e6963}
{bootmgr}
timeout 2
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {default}
resumeobject {507afc21-71e5-11e5-aecd-60029283c868}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 10
Firmware Application (101fffff)
-------------------------------
identifier {25ca094b-71ec-11e5-aed1-806e6f6e6963}
device unknown
description USB Drive
Firmware Application (101fffff)
-------------------------------
identifier {30cccae1-71e3-11e5-aec9-806e6f6e6963}
device unknown
description USB Drive
Firmware Application (101fffff)
-------------------------------
identifier {6ad24b4d-71e2-11e5-aec8-60029283c868}
device unknown
description USB Drive
Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \windows\system32\winload.efi
description Windows 10
locale en-us
inherit {bootloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=C:
systemroot \windows
resumeobject {507afc21-71e5-11e5-aecd-60029283c868}
nx OptIn
bootmenupolicy Standard
Resume from Hibernate
---------------------
identifier {507afc21-71e5-11e5-aecd-60029283c868}
device partition=C:
path \windows\system32\winresume.efi
description Windows Resume Application
locale en-us
inherit {resumeloadersettings}
isolatedcontext Yes
allowedinmemorysettings 0x15000075
filepath \hiberfil.sys
bootmenupolicy Standard
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \EFI\Microsoft\Boot\memtest.efi
description Windows Memory Diagnostic
locale en-us
inherit {globalsettings}
badmemoryaccess Yes
EMS Settings
------------
identifier {emssettings}
bootems No
Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200
RAM Defects
-----------
identifier {badmemory}
Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}
Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{hypervisorsettings}
Hypervisor Settings
-------------------
identifier {hypervisorsettings}
hypervisordebugtype Serial
hypervisordebugport 1
hypervisorbaudrate 115200
Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}
Device options
--------------
identifier {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0\boot.sdi
C:\Windows\system32>
I hope you can help me otherwise i think i have to send it to MSFT to fix it :D
Thanks,
Matthias
Matthias:
I have very limited experience with UEFI systems, but it looks to me like your firmware is not recognizing the hardware devices. See the three "Firmware Application (101fffff)" entries in your BCD. They all say "device unknown". In my one and only UEFI system, these three entries are for the optical drive, the hard disk, and the UEFI OS partition.
I believe that to fix these you need to be able to get to the UEFI settings. I'm not sure how you do this on the Surface, but in general you can reach them through Windows settings, provided that you are able to boot into Windows. http://answers.microsoft.com/en-us/surface/forum/surfpro-surfgetstart/a…
Thanks for your reply!
I was there multiple times already but the Options there are very limited as you can see here:
http://sebastianbrandes.com/wp-content/uploads/2014/11/WP_20141123_0021…
http://www.surfaceinside.de/wp-content/uploads/uefi1.jpg
kr Matthias
/edit: i tried a repair program once again and now i get this
//edit2 It works now, dont know what i did. But it allowed me no to install a clean version of Windows 10!!
Hello Experts!
I need some help, please!
On my Lenovo X61 notebook (Win 7), after automatic Windows Update, I got a BSOD, and when I start without a Repair disc, I boot automatically in Recovery tool and always get an unsuccessful automated repair: missingOsloader. Same with Repair disc.
I read forums, and make some changes in the cmd window, just like this:
“bcdedit /export C:\BCD_Backup
C:
cd boot
attrib bcd -s -h -r
ren C:\boot\bcd bcd.old
bootrec /RebuildBcd”
After that change the error message changed to “windows can not verify the digital signature of this file” winload.exe. And when I hit the enter and F8 the machine back to this message, and no way to enter Safe Mode or any other repair stage.
I read this article, and I know my BCD setting maybe wrong, but not sure how to fix it. Here is my “bcdedít /emun all” result, the Recovery folder (on D: partition) and the boot partition (C: )
What is the sollution?
Thanks in advance!
Zoli
Zoli:
Your BCD is missing a couple of lines that enable the F8 "Repair Your Computer" option. To fix, boot your PC from the Recovery Disk that you used to list the contents of the BCD. Enter the following commands into a Command Prompt window:
bcdedit /set {default} recoverysequence {efdfa581-7a7f-11e5-bb90-f5a272478d35}
bcdedit /set {default} recoveryenabled Yes
bcdedit /set {default} nx OptIn
bcdedit /set {efdfa581-7a7f-11e5-bb90-f5a272478d35} locale de-DE
bcdedot /set {efdfa581-7a7f-11e5-bb90-f5a272478d35} nx OptIn
This should fix the F8 function, but it might not fix the problem that produced the error message “windows can not verify the digital signature of this file” winload.exe. If you still get this message then boot again from the Recovery Disk and find a copy of Winload.exe on the RAMDisk X: and replace the file on your Windows partition with this file after renaming the existing file (just in case you need to go back to the old file).
ren D:\Windows\System32\winload.exe D:\Windows\System32\winload.bak
copy X:\Windows\System32\winload.exe D:\Windows\System32\winload.exe
Dear Mark Wharton, I found this forum and I hope that you can really help with this issue please!
I own a Toshiba Qosmio X770 PSBY5A-04T01W that I have never manipulated the disk neither the original partitions. I did a factory reset 3 years ago with success but now it is not working anymore.
This is what I did at the beginning
- I shut down the laptop
- I turn it on.
- Immediatelly I hit F12 to list the boot options
- HDD Recovery YES YES
- The laptop restarts
- I see the black screen with the message WINDOWS LOADING FILES.
- Then I see the logo of Microsoft with the message STARTING WINDOWS
- It displays the windows 7 wallpaper with the cursor of loading trying to load the recovery
- HERE IS THE PROBLEM. It restarts and then tries to find the boot from network
- I use a CD a windows 7 DVD which allows to fix the boot partition and then I can restart Windows 7 without problems. Inside the option from CD I only have the INSTALL NOW and Repair... but it doesn't find a system image
I found this interesting article : Windows 8 - Recovery partition not recognized after hard drive swapping But as in the picture my type is not a GUID, it is just a number
Then I went to c:\windows\system32\Recovery\ where I found the file Reagent.xml
I tried to force replacing manually the empty GUIDs with the guid that I found with the bcdedit command but then when I apply the **reagentc /disabled** and **reagentc /enable**, this reset the reagent.xml file to the empty guid {0000...}
<?xml version='1.0' encoding='utf-8'?>
<WindowsRE version="1.0">
<WinreBCD id="{020841ce-ccaf-11e1-984c-c00e6b91fbd9}"/>
<WinreLocation path="\Recovery\WindowsRE" id="3760468764" offset="1048576" guid="{00000000-0000-0000-0000-000000000000}"/>
<ImageLocation path="\Recovery\WindowsRE" id="3760468764" offset="1048576" guid="{00000000-0000-0000-0000-000000000000}"/>
<OsInstallLocation path="" id="0" offset="0" guid="{020841be-ccaf-11e1-984c-c00e6b91fbd9}"/>
<InstallState state="1"/>
<OsInstallAvailable state="0"/>
<WinREStaged state="0"/>
<OperationParam path=""/>
<OsBuildVersion path="7601.18933.amd64fre.win7sp1_gdr.150715-0600"/>
<OemTool state="0"/>
<BootKey state="0"/>
<IsServer state="0"/>
<ScheduledOperation state="4"/>
</WindowsRE>I tried to do what you did from the first page but it looks like that now I have a new Windows Boot Loader pointing to ramdiskc=[c:].... but it doesn't change the problem. Here my info
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
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 {020841ce-ccaf-11e1-984c-c00e6b91fbd9}
recoveryenabled Yes
osdevice partition=C:
systemroot \windows
resumeobject {d7224c79-880c-11e5-9dbe-806e6f6e6963}
nx OptIn
Windows Boot Loader
-------------------
identifier {020841c6-ccaf-11e1-984c-c00e6b91fbd9}
device ramdisk=[C:]\Windows\System32\Recovery\020841c6-ccaf-11e
1-984c-c00e6b91fbd9\Winre.wim,{020841c6-ccaf-11e1-984c-c00e6b91fbd9}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Windows\System32\Recovery\020841c6-ccaf-11e
1-984c-c00e6b91fbd9\Winre.wim,{020841c6-ccaf-11e1-984c-c00e6b91fbd9}
systemroot \windows
nx OptIn
winpe Yes
Windows Boot Loader
-------------------
identifier {020841ce-ccaf-11e1-984c-c00e6b91fbd9}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
re.wim,{020841cf-ccaf-11e1-984c-c00e6b91fbd9}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Win
re.wim,{020841cf-ccaf-11e1-984c-c00e6b91fbd9}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {d7224c79-880c-11e5-9dbe-806e6f6e6963}
device partition=C:
path \windows\system32\winresume.exe
description Windows 7
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 {020841c7-ccaf-11e1-984c-c00e6b91fbd9}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi
Device options
--------------
identifier {020841cf-ccaf-11e1-984c-c00e6b91fbd9}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi
Then I followed these steps in order to verify if the content of my recovery partition has not been deleted.
1. I opened a command line prompt as administrator
2. I executed the diskpart command
3. I selected the volume which contains the recovery partition
4. I executed the command **assign**
5. This "mount" a new drive F: which in fact it makes my partition visible
6. I did F: ENTER, then I found a Recovery folder but inside there's no files seen from Windows Explorer(even if I set the option to "Show the hidden files")
7. So I realized that the files and folders are hidden. I went to that drive F: and I executed the command **dir /a**. I found everything inside.
These are the folders and files that I found inside the Recovery folder
\Recovery
\Logs
\Reload.xml
\System32
\Recovery
\Reagent.xml
\WindowsRE
\boot.sdi
\winre.wim
The Logs folder is new after I executed the command **bootrec rebuildbcd** from the CD of Windows after of my failed attempts to recover my windows.
Finally, I tried to do the recovery from Windows.
1. I when to **Control Panel** > **System and Security** > **Backup and Restore**
2. Recover system settings or your computer
3. Advanced recovery methods
4. Use a system image you created earlier to recover your computer
5. Do you want to backup your files? SKIP
6. Restart your computer and continue the recovery. RESTART
7. I saw after a restart the Windows 7 Theme Wallpaper with message dialog with the brand of Toshiba .... I thought maybe this time is gonna work!!!!!
8. Error: F3-F100-0009
Thank you in advance.
Luis:
I searched online for the error message "Error: F3-F100-009". It appears that this is a Toshiba error message indicating a hard disk problem.
Have you checked your disk for errors and bad sectors? Boot again from your Windows 7 DVD and enter the command prompt environment. For each of the three partitions on your hard disk, run chkdsk /R. You will first need to figure out the drive letters of each partition as seen in the recovery environment. The first (Recovery) partition is marked as Active, so it will probably have the drive letter C:, so do this:
C:
chkdsk C: /R
Repeat for the other two partitions, substituting the drive letters of the other partitions in place of C: for the remaining two.
If you're lucky, chkdsk may be able to repair any file damage, if that is the issue. If it finds any bad sectors then you should replace the hard disk. Laptop hard disks are notorious for developing bad sectors due to the shock and vibration they encounter in normal use.
Mark, I've followed your suggestion. But unfortunately, I got same behavior and the CHKDSK didn't find any error or bad sector. If I have no other choice to install a new instance of Windows from CD, do you know how can I retrieve or get the drivers of the laptop model during the installation?
Luis:
You can probably find drivers on Toshiba's web site, but Windows 7 has a pretty extensive drive set, so you may not need them.
Before you reinstall Windows you might want to try a repair installation first: http://www.sevenforums.com/tutorials/3413-repair-install.html
Thanks for your advice. I'm gonna try a clean installation then. However I have a partition that cannot be accessible at all if you can see my picture of disk management. It weights 15gb and I don't know what it is!! I wanted to avoid a clean installation because the recovery includes all the drivers and toshiba tools that are very helpful for me and downloading and installing all that could be a nightmare too.
I recently run this command reagentc /info and I receive this info. What do you think about it.
F:\>reagentc /enable
REAGENTC.EXE: Operation successful
F:\>reagentc /info
Extended configuration for the Recovery Environment
Windows RE enabled: 1
Windows RE staged: 1
Setup enabled: 0
Custom Recovery Tool: 0
WinRE.WIM directory: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\Wi
ndowsRE
Recovery Environment: \\?\GLOBALROOT\device\harddisk0\partition1\Recovery\Wi
ndowsRE
BCD Id: 020841ce-ccaf-11e1-984c-c00e6b91fbd9
Setup Files:
Recovery Operation: 4
Operation Parameter:
Boot Key Scan Code 0x0
REAGENTC.EXE: Operation successful
I'm planning to build my own Recovery disk like I found on this video but you know how can I assign a partition for all the drivers and toshiba tools? Do have an article. I can't find a useful one. The last link that you send me was useful too.
https://www.youtube.com/watch?v=S8n-G9Rv2zo
Thanks
Luis:
The 15 GB partition is probably the Toshiba recovery partition that lets you restore to factory settings.
I'm not sure what you mean by "assigning a partition for all the drivers and Toshiba tools". Like I mentioned previously, the Windows 7 installation DVD and Windows Update probably have all of the drivers that you need. If not, you should be able to find any customized Toshiba drivers on Toshiba's web site. Having a partition for them doesn't seem to make sense since they may get updated periodically. Just copy them to a flash drive or CD to have when needed.
Hey Mark, been awhile. You helped me so successfully in the past that I wanted to inquire if you have a Windows 8/8.1 repair thread or if I could just ask here? Anyway I have an HP with its boot settings completely borked and need to at least get the recovery partition booting so i can reimage the drive. If you can help that would be great. Thanks again.
Sai:
Could you post the output of bcdedit /enum all? Also, it would be helpful to know the partition structure on your disk.
Thanks for the reply Mark. Here are the outputs from Diskpart, the disk structure hooked externally to a windows 7 machine, and the bcdedit output txt. Thanks again for your time. :)
Cheers!
Sai:
Can you tell me a little about what caused this? I can seen from your BCD that the partition references are all listed as "unknown", including the ones that reference the Windows partition and the ones that reference the Recovery files.
The Windows partition references should be easy; they should be on partition 3, drive letter F: when connected as described in reply #774. So connect your disk to the Windows 7 machine as you did previously and enter the following in an elevated command prompt window. Make sure that the commands are targeted to the correct disk. It may be easiest to boot the Windows 7 machine from a recovery CD and disconnect all disks except the one that you want to fix. If you do this, the drive letters may change, so first check the drive letter of the Windows partition and if it isn't F: then modify these commands appropriately:
bcdedit /set {default} device partition=F:
bcdedit /set {default} osdevice partition=F:
bcdedit /set {09459a6a-aad9-11e4-ad45-84546b1cdaaf} device partition=F:
bcdedit /set {09459a6a-aad9-11e4-ad45-84546b1cdaaf} filedevice partition=F:
These should get Windows booting again but without support for the Recovery environment. Next we need to figure out where the recovery files are located. See if you can browse and find the file \Recovery\WindowsRE\Winre.wim. Is it on partition 3 or on partition 4 (referring to your file disk_structure.jpg)?
Next see if you can find where the memory diagnostic file is located. See if you can find \EFI\Microsoft\Boot\memtest.exe. Which partition is it on?
IN all honesty I am not completely sure why the computer began having these issues, it was either an upgrade to 8.1 ( maybe upgrade to 10?) or a virus infection. Trying to repair this computer for a friend and it came pretty damaged and you know how regular users can be when asked how they managed to devastate their computer lol...
So I entered the bcdedit commands and it did not boot into windows because there are other issues (normal boot returns a "0xc0000225" error, advanced boot options are now available again and when safe mode is selected it then returns a "The OS could'nt be loaded because the kernel is missing or contains errors" message and ntoskrnl.exe is referenced with an error code: 0xc000000f). I'm going to try to source a replacement from the windows component store and place it back into the system32 folder so we'll see if that fixes it... onward...
In answer to your other inquiries the winre.wim file exists on both volume 2 and 3 as viewed from diskpart while booted into a windows 8 disk. The structure in diskpart is as follows
Volume 0 -- DVD Windows 8 dvd
Volume 1 -- Windows (NTFS)
Volume 2 -- Recovery Image (NTFS)
Volume 3 -- Windows RE (Recovery Partition)
Volume 4 -- System (EFI System Partition)
both of the winre.wim files in \Recovery\WindowsRE\winre.wim have a size of 348,351,983 bytes ...
As far as the memtest.exe location goes there are copies of this file in both Volume 2 and 4
both volumes have the directory \EFI\Microsoft\Boot with a memtest.efi file in them, on volume 2 the file size is 1,493,344 bytes and the one on Volume 4 is 1,500,504 bytes.
Sai:
Then it would seem that you should use the memtest.efi file on partition 2 (System EFI Partition):
bcdedit /set {memdiag} device partition=\Device\HarddiskVolume2
The other "unknown" entries in the BCD should probably reference partition 1 (Recovery Partition) for the standard Microsoft repair tools.
bcdedit /set {09459a6e-aad9-11e4-ad45-84546b1cdaaf} device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{09459a6f-aad9-11e4-ad45-84546b1cdaaf}
bcdedit /set {09459a6e-aad9-11e4-ad45-84546b1cdaaf} osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{09459a6f-aad9-11e4-ad45-84546b1cdaaf}
bcdedit /set {09459a6f-aad9-11e4-ad45-84546b1cdaaf} ramdisksdidevice partition=\Device\HarddiskVolume1
The 0xc0000225 error may mean that the contents of the partition cannot be read and could be due to file corruption. You should probably run chkdsk /R on the Windows partition.
Yeah, I have already run CHKDSK on the windows partition. At this point I just want to wipe the drive and start over so I need to be able to get access to the HP recovery options. I will enter these commands and see what I get. Thanks! should only take me a few minutes to get anywhere with it so I'll get right back to you .
so the first two commands entered without any issues, when I entered the third command I recieved an error.
"The element data type specified is not recognized, or does not apply to the specified entry. Run "bcdedit /?" for command line assistance.
Element not found.
I feel as though I should note on post #776 I described the volume structure from diskpart while booted on the original machine and the volume #'s differ from what you posted on #777. I altered them to reflect the changes but wanted you to note them for any further instruction as I will be doin all BCDEDIT commands from a booted win8 DVD on the original machine. Thanks!
I was going by the disk management picture showing that the Recovery partition was the first on the disk. If this is incorrect when viewed from the Win8 machine, then change the partition number(s) in the commands.
That being said, as I commented above I recieved an error while entering the commands. The first command bcdedit /set {memdiag} device partition=\Device\HarddiskVolume2 which I changed to volume4 and the second command bcdedit /set {09459a6e-aad9-11e4-ad45-84546b1cdaaf} device ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{09459a6f-aad9-11e4-ad45-84546b1cdaaf}
was also successful, however both
bcdedit /set {09459a6e-aad9-11e4-ad45-84546b1cdaaf} osdevice ramdisk=[\Device\HarddiskVolume3]\Recovery\WindowsRE\Winre.wim,{09459a6f-aad9-11e4-ad45-84546b1cdaaf}
and
bcdedit /set {09459a6f-aad9-11e4-ad45-84546b1cdaaf} ramdisksdidevice partition=\Device\HarddiskVolume3
returned an error:
"The element data type specified is not recognized, or does not apply to the specified entry. Run "bcdedit /?" for command line assistance.
Element not found.
Consequently Windows no longer immediately goes to an error screen but just sort of hangs at the blue HP Circle logo and never goes any further unless I press ESC for boot options or F9/F10 etc immediately as it boots.... So something is definitely different but it doesnt seem to have changed for the better lol...
Thanks again for your time, I have found various missing or corrupt files on the boot drive and I am hoping to just restore the ability to press F11 and get to the HP restore feature. Anything you can do to help is greatly appreciated. Cheers!
Sai:
The volume numbers returned by DiskPart do not necessarily correspond with partition numbers; they are simply a numeric listing of all mounted volumes on the machine. Since the view that you see now may not the same as the pictures you posted in reply #774, I am confused. What is the actual partition layout? I don't see why it would be any different from the picture in reply #774 from Disk Management console:
Partition 1 - Recovery Partition
Partition 2 - EFI System Partition
Partition 3 - Windows Partition
Partition 4 - Recovery Image Partition
You won't have Disk Management Console to work with when booted from the Win8 DVD, but you should still be able to use DiskPart:
>DiskPart
>Select Disk 0
>List Partition
Mark, I'm a computer technician by trade so I understand diskpart and I understand basics about the BCD structure but don't know enough to make alterations, however I don't need much in the way of "layman" clarification... lol.
I gave you the actual diskpart volume structure from the machine in question on post #776 to clarify why I was changing the volume numbers to be accurate.
For further clarification here is an image I took with my phone of the diskpart output. Furthermore I entered the commands you gave me with the correct volume numbers and I got errors as evidenced in post #782. The error I got was
"The element data type specified is not recognized, or does not apply to the specified entry. Run "bcdedit /?" for command line assistance.
Element not found.
I really appreciate the help and just wanted to clarify so we are on the same page, I seem to have lost you a few posts back and was not just going my own direction and messing things up. TIA.
Sai:
We're not on the same page. Your phone image does not show the partition layout, which I need to be able to get the commands correct. You're entering volume numbers. The volume numbers shown by Diskpart's "List Volume" command are not what go into the BCD commands. The bcdedit commands need partition numbers, not volume numbers.
In DiskPart, please type the commands listed in reply #783 and then post that output.
Ah, I see my mistake. Thanks for the clarification. :-)
Here is the correct list. Thanks agian.
Sai:
OK - that makes sense now. The other piece of information needed is to find out if any of the 5 partitions have drive letters assigned when booted to the recovery disk. If they do, it makes entering partition references easier. Can you explore using a Command Prompt and let me know which drive letter is assigned to which partition?
for drive letters reference the "list volume" jpg I put on Post # 784?
Also there are only 4 partitions, one is a removable disk I had hooked up to it... lol.
Sai:
The external disk showed up on post #784 since you were listing mounted volumes. The MSRP (Microsoft Reserved Partition) was not a mounted volume and did not show up then. But in your most-recent picture on post #787, you were listing partitions, and there are five including the MSRP.
Putting two and two together, the drive letters are none for partitions 1, 2, and 3, C: for partition 4 and D: for partition 5.
It's getting late, so I'll collect all of the BCD commands tomorrow morning and repost them with correct partition references.
Sai:
OK - this should fix the Windows boot loader:
bcdedit /set {default} device partition=C:
bcdedit /set {default} osdevice partition=C:
And this for the Resume from Hibernation loader:
bcdedit /set {09459a6a-aad9-11e4-ad45-84546b1cdaaf} device partition=C:
bcdedit /set {09459a6a-aad9-11e4-ad45-84546b1cdaaf} filedevice partition=C:
And this for the memory test loader:
bcdedit /set {memdiag} device partition=\Device\HarddiskVolume2
And this for the Windows Recovery Environment loader:
bcdedit /set {09459a6e-aad9-11e4-ad45-84546b1cdaaf} device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{09459a6f-aad9-11e4-ad45-84546b1cdaaf}
bcdedit /set {09459a6e-aad9-11e4-ad45-84546b1cdaaf} osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{09459a6f-aad9-11e4-ad45-84546b1cdaaf}
bcdedit /set {09459a6f-aad9-11e4-ad45-84546b1cdaaf} ramdisksdidevice partition=\Device\HarddiskVolume1
This assumes that Windows is on volume C:, partition 4; Memtest is on the EFI System partition, partition 2; and that you're using the Windows Recovery Environment on partition 1 "Recovery"; not the one on partition 5 "Recovery Image".
If you get any error messages then please post a fresh copy of the BCD.
Hi Mark.
Thanks again for the followup, all your commands were successful except these last two:
bcdedit /set {09459a6e-aad9-11e4-ad45-84546b1cdaaf} osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{09459a6f-aad9-11e4-ad45-84546b1cdaaf}
bcdedit /set {09459a6f-aad9-11e4-ad45-84546b1cdaaf} ramdisksdidevice partition=\Device\HarddiskVolume1
Attached is an output of BCDEDIT /ENUM ALL
The error recieved on these last two commands was:
The element data type specified is not recognized, or does not apply to the specified entry. Run "bcdedit /?" for command line assistance. Element not found.
Ok Mark. You can discontinue working on this project. The windows install was borked and several files all over the drive were either missing or corrupt, I'm guessing it was a rather pervasive infection. I got all the files backed up and was able to replace a couple of the files on the recovery partition to where pressing F11 finally got me to the recovery options. I am in the process of reinstalling windows back to factory defaults. Thanks again for your help, at least I was able to recover it without ordering media.
Cheers!
Hi Mark
I have windows 7 and when I press F8, I am not getting any Repair your computer option or any recovery option. I am able to log into windows 7, and if I try to run recovery from option given in control panel, it says windows recovery failed to restart your computer. I have backed up all my data, and I want to run windows recovery but its not working. I could see Repair your Computer option in F8 menu till few days back but not sure if any virus got to it or what happened. The BCD details are as follows. Please help. I dont have any other windows 7 disc, just the windows backup partition drive.
Also I dont see any C:\Recovery folder ..... not sure what wrong with the Lenovo Recovery (Q:)
C:\Windows\system32>bcdedit/enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=S:
path \bootmgr
description Windows Boot Manager
locale en-US
extendedinput Yes
default {current}
resumeobject {ac4edc4a-b208-11e5-982b-806e6f6e6963}
displayorder {current}
bootsequence {current}
timeout 30
customactions 0x10000ba000001
0x54000001
custom:54000001 {572bcd55-ffa7-11d9-aae0-0007e994107d}
Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
device ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
path \windows\system32\boot\winload.exe
description WinPE
osdevice ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
systemroot \windows
nx OptIn
detecthal Yes
winpe Yes
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
recoverysequence {f43fbb2b-ff99-11e1-9c6e-685d43f6cc45}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {ac4edc4a-b208-11e5-982b-806e6f6e6963}
Resume from Hibernate
---------------------
identifier {ac4edc4a-b208-11e5-982b-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
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=S:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description Ramdisk options
ramdisksdidevice boot
ramdisksdipath \boot\boot.sdi
C:\Windows\system32>
Please help me get into recovery mode.
Ashish:
The recovery sequence entry in your main Windows 7 loader is set to a non-existent ID. Try the following from an elevated command prompt window:
bcdedit /set {current} recoverysequence {572bcd55-ffa7-11d9-aae0-0007e994107d}
Hi Mark,
I ran the above mentioned command , and now i have this
F8 still not showing repair my computer option.
C:\Windows\system32>bcdedit/enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=S:
path \bootmgr
description Windows Boot Manager
locale en-US
extendedinput Yes
default {current}
resumeobject {ac4edc4a-b208-11e5-982b-806e6f6e6963}
displayorder {current}
timeout 30
customactions 0x10000ba000001
0x54000001
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {ac4edc4a-b208-11e5-982b-806e6f6e6963}
Resume from Hibernate
---------------------
identifier {ac4edc4a-b208-11e5-982b-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
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=S:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description Ramdisk options
ramdisksdidevice boot
ramdisksdipath \boot\boot.sdi
C:\Windows\system32>
seems something is gone wrong, i dont see recoverysequence or the identifier entries
Ashish:
I've never seen that happen before. What happens if you redo the last command?
bcdedit /set {current} recoverysequence {572bcd55-ffa7-11d9-aae0-0007e994107d}
Does the "recoverysequence" show up in the main Windows loader portion of the BCD here:
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
recoverysequence {572bcd55-ffa7-11d9-aae0-0007e994107d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {ac4edc4a-b208-11e5-982b-806e6f6e6963}
Hi Mark,
I reran the command and now I can see the recoverysequence. This is what I have now. Please tell how should I run Windows Recovery now?
C:\Windows\system32>bcdedit/enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=S:
path \bootmgr
description Windows Boot Manager
locale en-US
extendedinput Yes
default {current}
resumeobject {ac4edc4a-b208-11e5-982b-806e6f6e6963}
displayorder {current}
timeout 30
customactions 0x10000ba000001
0x54000001
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Premium
locale en-US
recoverysequence {572bcd55-ffa7-11d9-aae0-0007e994107d}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {ac4edc4a-b208-11e5-982b-806e6f6e6963}
Resume from Hibernate
---------------------
identifier {ac4edc4a-b208-11e5-982b-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
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=S:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
Setup Ramdisk Options
---------------------
identifier {ramdiskoptions}
description Ramdisk options
ramdisksdidevice boot
ramdisksdipath \boot\boot.sdi
C:\Windows\system32>
I restarted my laptop and using F8, got the repair my computer option. But as soon as I press Repair my computer, the system begins with logging into windows instead of going into recovery mode.
Before I first posted here (and before you told me to do anything), I tried to change bcd file because I had trouble starting up windows. I went into recovery mode and started command prompt in that mode and used bootrec rebuildbcd to create new bcd and created a backup of the original bcd file. I had important data in the system then so didnt ran full recovery. I have made backup of all my data now. Just waiting to run the full recovery.
I used these commands from microsoft website. https://support.microsoft.com/en-gb/kb/927392
- bcdedit /export C:\BCD_Backup
- c:
- cd boot
- attrib bcd -s -h -r
- ren c:\boot\bcd bcd.old
- bootrec /RebuildBcd
Do you think the changing of bcd file created more issues.
Ashish:
Yes, I do think that rebuilding the BCD resulted in the loss of the factory restore option. The bcd rebuild command and the automatic repair options, from what I've seen, are not able to recognize custom OEM recovery partitions or multiboot setups. They are usually only able to get Windows booting again.
But if the information in your first post, reply #794, is correct then you should be able to add the missing loader information back:
bcdedit /create {572bcd55-ffa7-11d9-aae0-0007e994107d} /d "WinPE" /application osloader
bcdedit /set {572bcd55-ffa7-11d9-aae0-0007e994107d} device ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
bcdedit /set {572bcd55-ffa7-11d9-aae0-0007e994107d} osdevice ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
bcdedit /set {572bcd55-ffa7-11d9-aae0-0007e994107d} path \windows\system32\boot\winload.exe
bcdedit /set {572bcd55-ffa7-11d9-aae0-0007e994107d} systemroot \windows
bcdedit /set {572bcd55-ffa7-11d9-aae0-0007e994107d} nx OptIn
bcdedit /set {572bcd55-ffa7-11d9-aae0-0007e994107d} detecthal yes
bcdedit /set {572bcd55-ffa7-11d9-aae0-0007e994107d} winpe yes
What you are attempting to achieve is to get the loader with the identifier identifier {572bcd55-ffa7-11d9-aae0-0007e994107d} to look like this:
Windows Boot Loader
-------------------
identifier {572bcd55-ffa7-11d9-aae0-0007e994107d}
device ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
path \windows\system32\boot\winload.exe
description WinPE
osdevice ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
systemroot \windows
nx OptIn
detecthal Yes
winpe Yes
What I would do is to enter only the first command, then list the BCD contents. Sometimes I've seen the previous information magically appear again after doing this. If the loader entry looks like above after doing the first command then you don't need to enter the rest of the commands. If not, keep entering the commands until you get the above result.