Windows 7, "Repair your computer" F8 boot option not working (SOLVED)
I cannot boot into windows mbr problem
I have a problem when I type
bcdedit /enum all
I get this message
The boot configuration data store could not be opened.
The requested system device cannot be found
Any help please, how do I fix this?
Hello,
Apologies for reviving an old thread. I’m having a similar issue like others here with respect to the “Repair Your Computer” option missing from the F8 menu. To start with I used to get this error:
“Status:0xc000000f Info: The boot selection failed because a required device is inaccessible”.
After trying a few workarounds I’d come across on the Microsoft forums and other sites, the ‘Repair’ option has now completely disappeared at start-up.
I did read through a few cases here but can’t seem to figure out what’s wrong in my case. So, here I’m posting my BCDedit output. Any help would be appreciated.
C:\Windows\system32>BCDEDIT /ENUM ALL
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-US
default {current}
resumeobject {40f165b7-d498-11e4-a593-806e6f6e6963}
displayorder {current}
timeout 30
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Home Basic
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {40f165b7-d498-11e4-a593-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {2a4362d7-d509-11e4-b17b-f0fb39b7ba95}
device ramdisk=[C:]\Recovery\54b07484-1c1e-11e4-8d2f-adcc9d73ae
b2\Winre.wim,{2a4362d8-d509-11e4-b17b-f0fb39b7ba95}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[C:]\Recovery\54b07484-1c1e-11e4-8d2f-adcc9d73ae
b2\Winre.wim,{2a4362d8-d509-11e4-b17b-f0fb39b7ba95}
systemroot \windows
winpe Yes
Windows Boot Loader
-------------------
identifier {2a4362d9-d509-11e4-b17b-f0fb39b7ba95}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Win
re.wim,{2a4362da-d509-11e4-b17b-f0fb39b7ba95}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\windowsre\Win
re.wim,{2a4362da-d509-11e4-b17b-f0fb39b7ba95}
systemroot \windows
winpe Yes
Resume from Hibernate
---------------------
identifier {40f165b7-d498-11e4-a593-806e6f6e6963}
device partition=C:
path \Windows\system32\winresume.exe
description Windows 7 Home Basic
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No
Windows Memory Tester
---------------------
identifier {memdiag}
device partition=\Device\HarddiskVolume2
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
Device options
--------------
identifier {2a4362d8-d509-11e4-b17b-f0fb39b7ba95}
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\54b07484-1c1e-11e4-8d2f-adcc9d73aeb2\boot.sdi
Device options
--------------
identifier {2a4362da-d509-11e4-b17b-f0fb39b7ba95}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\windowsre\boot.sdi
Also, I get a different output when I run ‘bcdedit /enum all’ at the system start-up command prompt (via installation disk). In place of “device: partition=\Device\HarddiskVolume2” it’s “partition=C” in ‘Windows Boot Manager’ & “partition=F” (which is my normal data drive) in place of “device: partition=C” in ‘Windows Boot Loader’.
The system itself is performing normally otherwise. In fact I wasn’t even aware there was an issue until I tried booting to the built-in ‘Diagnostics utility partition’ to run some tests which failed with a “Missing Operating System” message.
Thank you
I've attached the image of my recovery folder.
DISKPART Info:
DISKPART> LIST PARTITION
Partition ### Type Size Offset
------------- ---------------- ------- -------
Partition 1 OEM 39 MB 31 KB
Partition 2 Primary 12 GB 40 MB
Partition 3 Primary 232 GB 12 GB
Partition 0 Extended 221 GB 244 GB
Partition 4 Logical 172 GB 244 GB
Partition 5 Logical 49 GB 416 GB
DISKPART> DETAIL PARTITION
Partition 2
Type : 07
Hidden: No
Active: Yes
Offset in Bytes: 41943040
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 2 RECOVERY NTFS Partition 12 GB Healthy System
DISKPART> SELECT PARTITION 3
Partition 3 is now the selected partition.
DISKPART> DETAIL PARTITION
Partition 3
Type : 07
Hidden: No
Active: No
Offset in Bytes: 13195280384
Volume ### Ltr Label Fs Type Size Status Info
---------- --- ----------- ----- ---------- ------- --------- --------
* Volume 3 C OS NTFS Partition 232 GB Healthy Boot
BRAC:
Yeah, the automated recovery offered on Windows installation DVDs often messes up the Windows Recovery Environment. In your case it removed the lines needed to activate the recovery environment. Try entering these commands into an elevated command prompt window. You can do this from Windows; no need to boot to the installation disk:
bcdedit /set {current} recoverysequence {2a4362d9-d509-11e4-b17b-f0fb39b7ba95}
bcdedit /set {current} recoveryenabled Yes
bcdedit /set {current} inherit {bootloadersettings}
bcdedit /set {current} nx OptIn
Test the above steps first to see if it works before doing anything else.
You have two versions of the recovery environment referenced in the BCD. I picked the one on the hidden System Reserved partition because that's the one installed by your PC vendor. The other one was probably added by the Windows Automatic Repair and is not needed. If the above steps worked, then you can remove the unneeded BCD entries:
bcdedit /delete {2a4362d7-d509-11e4-b17b-f0fb39b7ba95}
bcdedit /delete {2a4362d8-d509-11e4-b17b-f0fb39b7ba95}
And a cosmetic change to remove the word "Recovered" from the description:
bcdedit /set {2a4362d9-d509-11e4-b17b-f0fb39b7ba95} description "Windows Recovery Environment"
The different listings seen for bcdedit /enum all when viewed in Windows vs. when viewed in the recovery environment is completely normal. These are two different Windows operating systems. Each issues drive letters differently. The notation “device: partition=\Device\HarddiskVolume2” is seen when running Windows because the partition being referenced is the System Reserved partition, which does not have a drive letter assigned by Windows. The recovery environment does assign a drive letter to this partition, and since it's the active partition, it gets drive letter C.
Mark :
Thanks for the reply. Will give it a try and see how it goes and post back :)
Hello Mark,
It worked. The "Repair your computer " option is available again and seems to be working alright. Hope it doesn't go corrupt again. Now to delete the unnecessary entries.:)
Thank you very much again
Hello,
I upgraded my computer with a new SSD: I copied from the original HDD to the SSD using paragon, then Same F8 "Repair your computer" error. The option is not available even when I have the recovery partition in the disk (SSD). When I reinstall the old HDD in order to compare it works properly. I can see some differences but I do not how to fix them...
I have a Dell Vostro 3640 laptop. See the attachment for disk management info. Thanks in advance!
Results of my bcdedit WITH THE SSD:
C:\Users\Administrator>bcdedit /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {8d1e4de2-a9ac-11e4-b36f-806e6f6e6963}
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
osdevice partition=C:
systemroot \Windows
resumeobject {8d1e4de2-a9ac-11e4-b36f-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {b7a69a0b-15ae-11e2-8c4b-e006e6d713ac}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\
re.wim,{b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\
re.wim,{b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {8d1e4de2-a9ac-11e4-b36f-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}
BCDEDIT WITH ORIGINAL HDD:
C:\Users\Administrator>bcdedit /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {3bdeb5e6-15b3-11e2-94b5-5cf9dd4ef9a8}
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 {b7a69a0b-15ae-11e2-8c4b-e006e6d713ac}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {3bdeb5e6-15b3-11e2-94b5-5cf9dd4ef9a8}
nx OptIn
numproc 4
usefirmwarepcisettings No
Windows Boot Loader
-------------------
identifier {b7a69a0b-15ae-11e2-8c4b-e006e6d713ac}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {3bdeb5e6-15b3-11e2-94b5-5cf9dd4ef9a8}
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 {b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi
C:\Users\Administrator>
If it can be useful: I unhide momentarily the recovery partition IN THE SSD and got the info attached.
Abdel:
You seem to have the same issue as the previous poster; there are some entries missing that describe and enable the Windows Recovery Environment. Try entering the following commands from an elevated command prompt window. Do this while running Windows 7 from your SSD:
bcdedit /set {current} recoverysequence {b7a69a0b-15ae-11e2-8c4b-e006e6d713ac}
bcdedit /set {current} recoveryenabled Yes
bcdedit /set {current} inherit {bootloadersettings}
bcdedit /set {current} nx OptIn
Also, your listing for the BCD on the SSD ends with the group "Global Settings". If you compare this with the BCD on the hard disk, there are four more groups following "Global Settings". They are "Boot Loader Settings", "Hypervisor Settings", "Resume Loader Settings", and "Device Options". The last of these, "Device Options" is required to be able to boot into the Windows Recovery Environment. But before attempting to re-create these, are they really missing, or are they just missing from the listing that you posted?
Mark,
You are right it was my mistake, here you have the whole info running from SSD:
Results of my bcdedit
C:\Users\Administrator>bcdedit /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {8d1e4de2-a9ac-11e4-b36f-806e6f6e6963}
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
osdevice partition=C:
systemroot \Windows
resumeobject {8d1e4de2-a9ac-11e4-b36f-806e6f6e6963}
Windows Boot Loader
-------------------
identifier {b7a69a0b-15ae-11e2-8c4b-e006e6d713ac}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\
re.wim,{b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\
re.wim,{b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {8d1e4de2-a9ac-11e4-b36f-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 {b7a69a0c-15ae-11e2-8c4b-e006e6d713ac}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi
C:\Users\Administrator>
Mark,
I am going to proceed with your recommendations, I'll let you know about results.
It worked!!!!!!!!!!!!!
Thanks a lot Mark!!!
.
Abdel:
Glad to hear it!
Having a similar boot problems with repair and not running chkdsk.
Hard drive was changed a year ago due to sectors going bad.
Thanks in advance for help.
- CT
Chris:
Enter the following commands in an elevated command prompt window. Do this from Windows 7:
bcdedit /set {current} recoverysequence {ea81cd8d-e2c3-11e1-9e56-047d7be96ff0}
bcdedit /set {ea81cd8d-e2c3-11e1-9e56-047d7be96ff0} locale en-US
bcdedit /set {current} inherit {bootloadersettings}
bcdedit /set {current} nx OptIn
Test this to see if the recovery environment works. If so, you can delete the orphaned BCD entries as follows (Optional step):
bcdedit /delete {713f70dc-b4b8-11e1-8081-047d7be96ff0}
bcdedit /delete {ea81cd8a-e2c3-11e1-9e56-047d7be96ff0}
bcdedit /delete {713f70db-b4b8-11e1-8081-047d7be96ff0}
bcdedit /delete {ea81cd8b-e2c3-11e1-9e56-047d7be96ff0}
And you can remove the word "recovered" from some of the descriptions as follows (Optional step):
bcdedit /set {current} description "Windows 7"
bcdedit /set {ea81cd8d-e2c3-11e1-9e56-047d7be96ff0} description "Windows Recovery Environment"
bcdedit /set {b04e5b4f-c62d-11e3-b0d3-806e6f6e6963} description "Windows Resume Application"
@Mark Wharton: Last year you helped me get back the F8 repair option and I'm very thankful!
https://forum.acronis.com/forum/6758?page=11#comment-175263
Since then I've downloaded the Windows 10 Technical Preview and dual booted it as a VHD file with my HP Windows 7. Now I want to delete the Windows 10 and the dual boot option. Besides deleting Windows Technical Preview from the System Configuaration boot options,
https://www.dropbox.com/s/s9v4ug260tdxkik/windows-boot.PNG?dl=0
what else do I need to do to get back the F8 option?
Below is my current bcd and partitions:
Byron:
I would go ahead and delete the Windows Technical Preview from the System Configuration boot options and see what happens. Your current BCD contains the W7 OS loader, resume loader, and Recovery Environment loader entries, and they still look correct so perhaps it will all just work.
I see multiple OS, resume, and recovery loader entries in the BCD that don't do anything but they shouldn't cause any harm. After you get things working correctly then you can delete them. However, I also see that the Custom Actions entries are missing from the Windows Boot Manager entry. We may have to restore those manually.
For now, just delete the Technical Preview and then post your BCD afterwards.
Byron:I would go ahead and delete the Windows Technical Preview from the System Configuration boot options and see what happens. Your current BCD contains the W7 OS loader, resume loader, and Recovery Environment loader entries, and they still look correct so perhaps it will all just work.
I see multiple OS, resume, and recovery loader entries in the BCD that don't do anything but they shouldn't cause any harm. After you get things working correctly then you can delete them. However, I also see that the Custom Actions entries are missing from the Windows Boot Manager entry. We may have to restore those manually.
For now, just delete the Technical Preview and then post your BCD afterwards.
Thanks Mark. Below is the current BCD after deleting the Technical Preview. Also the vhd=[C:]\w7.vhd is not used either. When I use F8 now it takes me to the F8 screen where I can choose Repair Computer. After choosing repair computer, it takes me to the HP Recovery Manager. If I remember correctly, shouldn't it take me to repair screen like this?
https://www.dropbox.com/s/10biw5ko3630on0/recovery-options.png?raw=1
Byron:
The custom actions items are not in your current BCD, whereas they were present in the BCD that we first worked on in April of 2014. These link the OEM recovery to the standard Windows recovery. Try adding them back and see if the behavior changes:
bcdedit /set {bootmgr} custom:0x000000005400000f {027782c6-7c31-11e2-9a2e-9c977d2528ff}
bcdedit /set {bootmgr} customactions 0x0001000085000001 0x000000005400000f
Also, for some reason the path statement is missing from the {bootmgr} entry, but your PC obviously boots so it mustn't matter. You can add it:
bcdedit /set {bootmgr} path \bootmgr
If this works, let me know if you want to delete all of the non-working BCD entries.
Byron:
The custom actions items are not in your current BCD, whereas they were present in the BCD that we first worked on in April of 2014. These link the OEM recovery to the standard Windows recovery. Try adding them back and see if the behavior changes:
bcdedit /set {bootmgr} custom:0x000000005400000f {027782c6-7c31-11e2-9a2e-9c977d2528ff}
bcdedit /set {bootmgr} customactions 0x0001000085000001 0x000000005400000fAlso, for some reason the path statement is missing from the {bootmgr} entry, but your PC obviously boots so it mustn't matter. You can add it:
bcdedit /set {bootmgr} path \bootmgr
If this works, let me know if you want to delete all of the non-working BCD entries.
I ran all the commands above but still seeing the HP Recovery Manager. Below is what I have now. Also would it be possible to use the backup I made of the bcd when you first helped me or do the values change over time? I ran the command below of the bcd and saved it from last year:
bcdedit /export "C:\Users\byron\Documents\bcd\bcd-backup"
Byron:
The changes to the BCD look correct. The {bootmgr} entry looks identical to the one from 2014.
Yes, you can try using the backup of the bcd made last year. Save a copy of your current BCD then import the saved BCD:
bcdedit /export "C:\Users\byron\Documents\bcd\bcd-backup2"
bcdedit /import "C:\Users\byron\Documents\bcd\bcd-backup"
Still seeing the HP Recovery Manager so I checked the file paths in my D:\Recovery partion to compare the file names or check if a file was missing. According to this line in the bcd:
[D:]\Recovery\WindowsRE\Winre.wim,{027782c7-7c31-11e2-9a2e-9c977d2528ff}
I should see a file name Winre.wim and as you can see from the command prompt it's missing or changed to WinUCRD.wim
https://www.dropbox.com/s/mhmj4u895836jq5/recovery.PNG?raw=1
Disregard my previous post. I was able to see the Winre.wim file by showing hidden files and folders. Still get the HP Recovery Manager.
Byron:
Please post your BCD again.
Isn't there supposed to be a keystroke that you use when booting to enable the HP Recovery Manager? Have you power cycled the computer to be sure that the BIOS picks up the change?
Mark:
Tapping F11 when booting takes me to the same HP Recovery Manager. F8 takes me to the options to repair my computer and the other safe mode options etc. but clicking Repair My Computer takes me down the same path as the F11 option.
Still the same after a complete power down. Having a BIOS password wouldn't matter would it? Also I'm not able to create a repair disc anymore. I get this error:
https://www.dropbox.com/s/s6oy8rt0biim9p4/repair-disc-error.png?raw=1
Could you post a copy of your current BCD?
Sure
Byron:
Thanks. One more request? From an elevated command prompt window, list the contents of the recovery setup:
reagentc /info > "C:\Users\byron\Desktop\reagent info.txt"
This will write a text file to your desktop. Then open the file C:\Windows\System32\Recovery\ReAgent.xml with Notepad and then save it as a text file to your desktop.
Please post these two files.
Mark:
Here's the files you requested. Neither rendered anything. The first file returned an error from the command prompt:
https://www.dropbox.com/s/2qun47x9gli8uf1/reagentc-error.png?raw=1
I could see the contents of C:\Windows\System32\Recovery\ReAgent.xml using Notepad++ and I'll attach it too.
Byron:
The inability to create a repair disk is related to the inability to run the reagentc /info command. I don't know how to fix that one. However, you can create a repair disk on any other Windows 7 PC (32-bit or 64-bit to match your OS) and it will work on your machine too. They are generic; not customized.
The recovery environment boot issue is perplexing since the {bootmgr} section of your BCD is identical to last year's version, so I don't understand why it behaves differently. There is more than one way to enter the generic recovery environment, so if you are interested in alternate solutions here are two.
1. You can list the BCD entry for Windows PE 2.0 in the boot menu by adding an entry to the menu:
bcdedit /set {bootmgr} displayorder {027782c6-7c31-11e2-9a2e-9c977d2528ff} /addlast
You may not like this because you'll see the menu each time that you boot Windows.
2. An alternative is available if you don't use or never plan to use the HP Recovery Environment. You could switch the recoverysequence variable to the generic Windows Recovery Environment:
bcdedit /set {current} recoverysequence {572bcd60-ffa7-11d9-aae0-0007e994107d}
Ifyou tap F8 while the computer is starting you'll then be directed to the generic Windows Recovery Environment.
Mark:
I actually have a Windows Repair Disk for this computer and I burned a set of recovery disks about a year ago. I don't ever see myself going back to the pc like it was when I bought it. Now that this has come up, I'm thinking about just deleting the HP Recovery files and use the partition for something else. HP Recovery Manager gives me the option to delete the recovery files, not sure what changes take place. What would need to be changed in the bcd if I were to do that? Also could I still use your suggestion for the F8 option?
bcdedit /set {current} recoverysequence {572bcd60-ffa7-11d9-aae0-0007e994107d}
Byron:
I think that I overlooked something. One explanation for the PC not booting to the generic Windows Recovery Environment is that its files are missing and it fails over to the HP recovery environment. Installing Windows 10 may have done this.
To find out, try this. Use Windows Disk Management to assign a drive letter to the first partition. For this example let's assume that you assign drive letter Z:. Browse the partition with Windows Explorer. Set viewing of both hidden and protected operating system files set to be visible. Do you see the files Z:\boot\boot.sdi and Z:\sources\boot.wim? [If you get an "Access Denied" message you may need to use an elevated command prompt window to do the browsing].
If yes, you can switch the recovery environment to this one using the command in your last post.
If no, you might need to figure out where these files went. They may be at C:\Recovery or somewhere else on the first (Z:) partition.
Mark:
Is there any downside to assigning a drive letter to the system partition? So it's actually looking for the files in the system partition to restore with and not the recovery partition d?
As far as the files you've mentioned, they're all found in the D:Recovery partition, if it matters?
https://www.dropbox.com/s/x9oqk2d1cs3pxyf/d-recovery-files.png?raw=1
https://www.dropbox.com/s/why3jvqkb5ckyxu/boot-boot.png?raw=1
Byron:
There isn't any downside to assigning a drive letter to the system partition. You can remove the drive letter after we figure out what is on the partition.
The files on the recovery partition will be removed if you remove the partition. We need to see if your PC has a standard installation of WindowsRE. The files will either be on the System Reserved partition (the entries in your BCD say that they are) or on the Windows partition. We need to get this working so that you are free to delete the HP Recovery partition, if that's what you want to do.
Thanks Mark:
I think I have another solution to seeing the files in the system partition. I make an image backup of my pc every Sunday with the Windows backup software. Windows backup makes a .vhd file of each partition. I should be able to just mount the .vhd file of the system partition and see the files that way. I'll try that later this afternoon when I have more time and let you know.
Mark:
These are the folders and files i see when I mount the backup of the system partition:
https://www.dropbox.com/s/30xq1tjn241feib/system-partition.png?raw=1
Byron:
Since there isn't a file \sources\boot.wim on the System Reserved partition, the entry in your BCD for booting to Windows PE 2.0 is invalid.
At this point I have no idea why the F8 "repair your computer" option boots directly to the HP recovery manager instead of to the Windows Recovery Environment like it used to. Your BCD entries for recovery are set up the same way they were when it worked in April of 2014.
I've restored my pc from image backups several times, could the files have been deleted this way? As long as I have the backup discs and the repair disc, I should be ok to delete the recovery partition shouldn't I?
I guess if it were really so important to restore boot\boot.sdi and sources\boot.wim, I could use the Recovery manager to restore my pc like new and recover the System files that way and then go back to my current backup. Is it really that important?
Byron:
Having a recovery environment on-disk is really just a convenience. You can do the same with a recovery disc. So to answer your question, it isn't that important.
Thanks Mark! You've REALLY been a great help!
Please disregard
Please disregard.
Please disregard.
Please disregard these last 4 messages. The forum flagged them as spam a few days ago and now they have been added to the thread as multiple posts. I resolved my issue through PM with Mark. Thanks again Mark.
Hi Mark,
I was wondering if there is a way so that I can use my F8 key when booting up Windows 7 and choose the recovery environment?
I had the 100MB reserved system partition originally, but deleted it. I then had to use my Windows 7 installation DVD to use Windows Repair in order to boot my Windows 7 OS. I can boot Windows 7 just fine now.
But, I am wondering if there is a way to use the F8 key and get the recovery environment? Or, does one have to have that system reserved partition in order to have WindowsRE as an available option when pressing the F8 key during Windows 7 boot-up?
If it helps, here is the output from my system for bcdedit /enum all:
C:\Windows\system32>bcdedit /enum all
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {33b199ec-5c51-11e3-bfa4-c807ef60c8e4}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Windows Boot Loader
-------------------
identifier {33b199ed-5c51-11e3-bfa4-c807ef60c8e4}
device locate=\Windows\system32\winload.exe
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoveryenabled No
osdevice locate=\Windows
systemroot \Windows
resumeobject {33b199ec-5c51-11e3-bfa4-c807ef60c8e4}
nx OptIn
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 Professional (recovered)
locale en-US
osdevice partition=C:
systemroot \Windows
resumeobject {79d71447-2ca6-11e5-a558-806e6f6e6963}
Resume from Hibernate
---------------------
identifier {33b199ec-5c51-11e3-bfa4-c807ef60c8e4}
device locate=\Windows\system32\winresume.exe
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 {79d71447-2ca6-11e5-a558-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
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}
C:\Windows\system32>
Mark, you are truly an amazing person to still be helping folks solve these issues all these years later. I'm going to just thank you in advance for that and ask if you could help me get rid of this same annoying thing on my machine that I've been screwing around with for months now because I never had the right Google search that led me here. Thank you sir.
Firmware Boot Manager
---------------------
identifier {fwbootmgr}
displayorder {bootmgr}
{10f2a7f2-96b3-11e4-b86a-806e6f6e6963}
{b60e7d0a-3d46-11e5-a05d-806e6f6e6963}
{b60e7d0b-3d46-11e5-a05d-806e6f6e6963}
{32a521ab-96b4-11e4-bc37-806e6f6e6963}
{b50cf284-82ce-11e3-9df6-97c6015ef18c}
{71d68ece-2f85-11e4-9e0d-806e6f6e6963}
{f9b77da6-96b0-11e4-93d2-806e6f6e6963}
{7329ab5e-7cbc-11e4-a21c-806e6f6e6963}
timeout 1
Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume6
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {b50cf287-82ce-11e3-9df6-97c6015ef18c}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30
Firmware Application (101fffff)
-------------------------------
identifier {10f2a7f2-96b3-11e4-b86a-806e6f6e6963}
device partition=\Device\HarddiskVolume1
path \EFI\BOOT\BOOTX64.EFI
description UEFI: SanDisk SDSSDHP128G
Firmware Application (101fffff)
-------------------------------
identifier {32a521ab-96b4-11e4-bc37-806e6f6e6963}
description SanDisk SDSSDHP128G
Firmware Application (101fffff)
-------------------------------
identifier {71d68ece-2f85-11e4-9e0d-806e6f6e6963}
description TOSHIBA DT01ACA300
Firmware Application (101fffff)
-------------------------------
identifier {7329ab5e-7cbc-11e4-a21c-806e6f6e6963}
description KINGSTON SV300S37A240G
Firmware Application (101fffff)
-------------------------------
identifier {b50cf284-82ce-11e3-9df6-97c6015ef18c}
description TOSHIBA DT01ACA300
Firmware Application (101fffff)
-------------------------------
identifier {b60e7d0a-3d46-11e5-a05d-806e6f6e6963}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
Firmware Application (101fffff)
-------------------------------
identifier {b60e7d0b-3d46-11e5-a05d-806e6f6e6963}
device partition=\Device\HarddiskVolume6
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
Firmware Application (101fffff)
-------------------------------
identifier {f9b77da6-96b0-11e4-93d2-806e6f6e6963}
description HL-DT-ST DVDRAM GH24NS95
Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.efi
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {b50cf289-82ce-11e3-9df6-97c6015ef18c}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {b50cf287-82ce-11e3-9df6-97c6015ef18c}
nx OptIn
Windows Boot Loader
-------------------
identifier {b50cf289-82ce-11e3-9df6-97c6015ef18c}
device ramdisk=[C:]\Recovery\b50cf289-82ce-11e3-9df6-97c6015ef1
8c\Winre.wim,{b50cf28a-82ce-11e3-9df6-97c6015ef18c}
path \windows\system32\winload.efi
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\b50cf289-82ce-11e3-9df6-97c6015ef1
8c\Winre.wim,{b50cf28a-82ce-11e3-9df6-97c6015ef18c}
systemroot \windows
nx OptIn
winpe Yes
Resume from Hibernate
---------------------
identifier {b50cf287-82ce-11e3-9df6-97c6015ef18c}
device partition=C:
path \Windows\system32\winresume.efi
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\HarddiskVolume6
path \EFI\Microsoft\Boot\memtest.efi
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 {b50cf28a-82ce-11e3-9df6-97c6015ef18c}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\b50cf289-82ce-11e3-9df6-97c6015ef18c\boot.sdi
s.larson:
I don't see anything wrong in your BCD - you do have recovery enabled and all of the required entries seem to be in place.
A few comments:
1. Did the recovery environment use to work at one time or did it never work?
2. If it never worked, on fast PCs there is an issue of timing. There is a very small window of time in which you have to hit the F8 key. If you aren't quick enough the PC moves on to the rest of the boot cycle and starts Windows 7. Sometimes madly tapping the F8 key immediately after the BIOS splash screen finishes and immediately before "Loading Windows" appears is necessary.
3. Are you going to upgrade to Windows 10? If yes, chances are good that the installer will fix this because it sets up the Windows 10 Recovery Environment as separate BCD entries. In Windows 10 the F8 key is disabled (Windows 8 and 10 boot so fast that there is less than 250 milliseconds in which to hit the key) so Microsoft designed an alternate way to get to the recovery environment through a menu in the OS.
I can't say for certain that the recovery environment ever worked or not, I never had a reason to use it.
Let me add some details that I probably should have included in my previous post. I get the error below every time I reboot my computer, not when trying to use F8 at boot (something I haven't actually had a need to do for a while). It will always come up twice, and if I hit Enter each time, it clears and the computer goes on to boot normally and works just fine. This has been going on ever since I cloned my original boot SSD to the current one when I upgraded capacity.
I have also tried downloading the install ISO from Microsoft again and burning it to DVD and attempting to access the repair utilities only to be told that they are not compatible with this version of Windows.
I did attempt to upgrade to Windows 10 three times today and all three times ended in the same scenario. The image downloads, the box restarts and switches to a black screen with a progress bar that says Loading Files, then it flashes a quick graphic about starting windows then screen goes blank and the monitor reports No Signal. It will sit there like that as long as I let it. When I hit the reset button on the tower though, we get the inaccessible boot media error twice again and go right back into Win 7. I'm guessing that whatever is triggering this boot error is might also be contributing to my problems completing the Win10 upgrade. I have also noticed that I do not have a C:\Recovery folder after enabling hidden files and folders. So maybe that is part of the issue.
Thanks very much for the help.
**Edit** - Including the boot error.
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.
s.larson:
To see the recovery folder you also need to enable viewing of protected operating system files.
The symptom you're describing sounds like your motherboard is having problems detecting the boot disk drive. Have a look in your settings. Make sure that the disk is detected and visible in the settings, that it is the first boot device, and that it is reliably detected. You may need to change a setting for the disk type from "autodetect" to something else. I recall having this problem recently with a new motherboard and I had to find the right setting that allowed the disk to be detected immediately after a reboot, and to work reliably every time.
There may be two places to look in the settings - one for the disk hardware and another for selecting the default boot device order.
You might see if there is a forum for your particular PC or motherboard or SSD that has a thread about this issue. I would bet that if you fix this, Windows 10 will finish installing.