Skip to main content

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

Thread needs solution
Forum Star
Posts: 19
Comments: 2110

#251

John:

OK. We will need to manually enter the missing OS Loader and Ramdisk Options sections of the BCD. I have attached a text file, JR bcd.txt, that shows what your BCD should look like when it is finished. You can compare the output of bcdedit /enum all to this file to see if all of the commands have come out correctly.

Enter the following commands in an elevated command prompt window. It may be better to copy/paste them, but if a command returns an error then be sure that it is entered all on one line without any line breaks. This first set of commands enters the missing OS Loader for the Windows Recovery Environment with ID {ef339fda-8dae-11e0-8970-83f5d21005d8}:

bcdedit /create {ef339fda-8dae-11e0-8970-83f5d21005d8} /d "Windows Recovery Environment" /application osloader

bcdedit /set {ef339fda-8dae-11e0-8970-83f5d21005d8} device ramdisk=[C:]\Recovery\ef339fda-8dae-11e0-8970-83f5d21005d8\Winre.wim,{ef339fdb-8dae-11e0-8970-83f5d21005d8}

bcdedit /set {ef339fda-8dae-11e0-8970-83f5d21005d8} osdevice ramdisk=[C:]\Recovery\ef339fda-8dae-11e0-8970-83f5d21005d8\Winre.wim,{ef339fdb-8dae-11e0-8970-83f5d21005d8}

bcdedit /set {ef339fda-8dae-11e0-8970-83f5d21005d8} path \windows\system32\winload.exe

bcdedit /set {ef339fda-8dae-11e0-8970-83f5d21005d8} inherit {bootloadersettings}

bcdedit /set {ef339fda-8dae-11e0-8970-83f5d21005d8} systemroot \windows

bcdedit /set {ef339fda-8dae-11e0-8970-83f5d21005d8} nx OptIn

bcdedit /set {ef339fda-8dae-11e0-8970-83f5d21005d8} winpe Yes

The next set enters the missing device options for the Ramdisk:

bcdedit /create {ef339fdb-8dae-11e0-8970-83f5d21005d8} /d "Ramdisk Options" /device

bcdedit /set {ef339fdb-8dae-11e0-8970-83f5d21005d8} ramdisksdidevice partition=C:

bcdedit /set {ef339fdb-8dae-11e0-8970-83f5d21005d8} ramdisksdipath \Recovery\ef339fda-8dae-11e0-8970-83f5d21005d8\boot.sdi

Finally, these two correct errors in the Resume from Hibernate Loader:

bcdedit /set {274ca636-0ae5-11e2-b366-b09ff4517b69} description "Windows Resume Application"

bcdedit /set {274ca636-0ae5-11e2-b366-b09ff4517b69} inherit {resumeloadersettings}

Then check the bcd contents against the attached text file. If correct, try it out.

Attachment Size
119254-105238.txt 2.79 KB
Beginner
Posts: 0
Comments: 4

#252

Mark,

Thank you so much!!! It worked like a charm. :)

You are a saviour, I want to express my deepest gratitude. Your students are lucky to have you (I looked you up).

Thanks again,
John

Forum Star
Posts: 19
Comments: 2110

#253

John:

I'm glad that worked. While I appreciate the expressions of gratitude, saying that I'm a "Saviour" is a little over the top.

After working with bcdedit for the last few years, some of it is starting to make sense. That's scary...

Forum Star
Posts: 19
Comments: 2110

#254

Ascanio:

The Windows Boot Loader entry for the Recovery Environment is missing all of its values. I can list the commands needed to make it work, but I'm not sure that is enough to get HP Recovery (to restore factory settings) working. But you can try.

The commands listed below are the English versions. Since your system language is French, I'm not sure that they will be the same, but your BCD listing had everything in English except for the titles and the identifier (identificateur) so they probably are.

Enter each of these commands in an elevated command prompt window:

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} device ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{564a65cc-2b77-11e1-941e-f70bf23216e3}

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} path \Windows\system32\Winload.exe

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} description "Windows Recovery Environment"

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} inherit {bootloadersettings}

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} osdevice ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{564a65cc-2b77-11e1-941e-f70bf23216e3}

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} systemroot \Windows

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} nx OptIn

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} winpe Yes

bcdedit /set {564a65cc-2b77-11e1-941e-f70bf23216e3} ramdisksdidevice partition=E:

This should enable the Windows Recovery (Repair Your Computer). Let me know if it also allows you to access the HP Recovery.

Beginner
Posts: 0
Comments: 19

#255

Hi Mark,
thank you to answer me
I entered the first command, but he replied :

The type of the specified data element is not recognized or does not apply to the specified input.
Run "bcdedit /?" to get help on the command line.
Item not found
======================================================================
I entered the second order also,,,,, without success :(

I'm told that the disk is dynamic, is that it can be the prolème???

Attachment Size
119334-105241.jpg 277.02 KB
Beginner
Posts: 0
Comments: 19

#256

oooh, i am sorry Mark, i forgot the space between "device" and "ramdisk" in the first command ,,, so now I fix it but he replied :

<<<<<< an error occurred during the translation of the data item.
this request is not supported. >>>>>>>

Forum Star
Posts: 19
Comments: 2110

#257

Asconio:

The first command is all entered on one line without line breaks, even though it appears on two lines in the forum post. Try copy and paste instead of typing.

Could you also confirm that the file winre.wim is located at E:\Recovery\WindowsRE\winre.wim?

Beginner
Posts: 0
Comments: 19

#258

I know the command is on one line
I try to "copy and paste" with "Ctrl + C"and "Ctrl + V" but it's doesn't work ... I must write the command
and confirm that the file is in the path "E: \ Recovery \ WindowsRE", its size is 160 MB

Attachment Size
119347-105247.jpg 227.41 KB
Forum Star
Posts: 19
Comments: 2110

#259

Ascanio:

To paste into a command prompt window, click the small icon at the top-left edge of the window and choose "Edit" and then "paste"

Ctrl + V does not work in a command prompt window.

Attachment Size
119348-105250.png 52.22 KB
Beginner
Posts: 0
Comments: 19

#260

the result is the same :
<< an error occurred during the definition of the data item.
this request is not supported. >>

Attachment Size
119349-105253.jpg 191.35 KB
Beginner
Posts: 0
Comments: 19

#261

Mark,
i try now to enter the second command ((( bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} path \Windows\system32\Winload.exe ))) ;; and the opération is GOOOODDDD
can i enter all the command without the first ??????

Forum Star
Posts: 19
Comments: 2110

#262

Ascanio:

Enter all of the commands and let me know which ones fail. At the moment, I can't find the reason for the failure of the first command, but I'll keep looking.

Beginner
Posts: 0
Comments: 19

#263

ok thank you
I'll let you know the results

Beginner
Posts: 0
Comments: 19

#264

so, all commands runexcept the FIRST - the FIFTH - and NINTH (last)

1): bcdedit / set {564a65cb-2b77-11e1-941st-f70bf23216e3} device ramdisk = [E:] \ Recovery \ WindowsRE \ Winre.wim, {564a65cc-2b77-11e1-941st-f70bf23216e3}

5): bcdedit / set {564a65cb-2b77-11e1-941st-f70bf23216e3} osdevice ramdisk = [E:] \ Recovery \ WindowsRE \ Winre.wim, {564a65cc-2b77-11e1-941st-f70bf23216e3}

9): bcdedit / set {564a65cc-2b77-11e1-941st-f70bf23216e3 ramdisksdidevice} partition = E:

at the end of the 3 commands failed it always displays the same message
this message :
<<< an error occurred during the definition of the data element.
this request is not supported. >>>

Attachment Size
119366-105265.jpg 253.88 KB
Forum Star
Posts: 19
Comments: 2110

#265

Ascanio:

You have extra spaces in the first and fifth commands. You may not be entering them that way but the spaces are in the commands shown in your last post. The ninth command has the curly brace character "}" in the wrong place. The {} characters should surround the ID. Here are the three commands repeated again so that you can copy and paste them:

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} device ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{564a65cc-2b77-11e1-941e-f70bf23216e3}

bcdedit /set {564a65cb-2b77-11e1-941e-f70bf23216e3} osdevice ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{564a65cc-2b77-11e1-941e-f70bf23216e3}

bcdedit /set {564a65cc-2b77-11e1-941e-f70bf23216e3} ramdisksdidevice partition=E:

If that doesn't work then please attach a copy of your BCD to your next reply. A simple way to do this is to enter the following command, which will result in a text file on your desktop. Attach the text file to your reply.

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

Beginner
Posts: 0
Comments: 19

#266

I don't add spaces in the command prompt in the elevated command prompt window
it's just "Google Translate" add the space when I do the translation for do you send the message in English
look at the picture "Google Translate"

and this is my BCD:

Gestionnaire de démarrage Windows
---------------------------------
identificateur {bootmgr}
device partition=\Device\HarddiskVolume1
description Windows Boot Manager
locale fr-FR
inherit {globalsettings}
extendedinput Yes
default {current}
resumeobject {564a65c9-2b77-11e1-941e-f70bf23216e3}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 0
displaybootmenu Yes
customactions 0x1000085000001
0x5400000f
custom:5400000f {564a65cb-2b77-11e1-941e-f70bf23216e3}

Chargeur de démarrage Windows
-----------------------------
identificateur {current}
device partition=C:
path \windows\system32\winload.exe
description Windows 7
locale fr-FR
inherit {bootloadersettings}
recoverysequence {564a65cb-2b77-11e1-941e-f70bf23216e3}
recoveryenabled Yes
osdevice partition=C:
systemroot \windows
resumeobject {564a65c9-2b77-11e1-941e-f70bf23216e3}
nx OptIn
detecthal Yes

Chargeur de démarrage Windows
-----------------------------
identificateur {564a65cb-2b77-11e1-941e-f70bf23216e3}

Reprendre … partir de la mise en veille prolong‚e
-------------------------------------------------
identificateur {564a65c9-2b77-11e1-941e-f70bf23216e3}
device partition=C:
path \windows\system32\winresume.exe
description Windows Resume Application
locale fr-FR
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

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

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

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

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

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

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

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

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

Options de périphérique
-----------------------
identificateur {564a65cc-2b77-11e1-941e-f70bf23216e3}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Options de périphérique
-----------------------
identificateur {564a65cd-2b77-11e1-941e-f70bf23216e3}
description Recovery
ramdisksdidevice partition=C:
ramdisksdipath \NST\boot.sdi

Options Ramdisk du programme d'installation
-------------------------------------------
identificateur {ramdiskoptions}
description RamdiskOptions
ramdisksdidevice partition=C:
ramdisksdipath \NST\boot.sdi

Attachment Size
119373-105268.jpg 425.42 KB
Forum Star
Posts: 19
Comments: 2110

#267

Ascanio:

I understand about Google Translate and the added spaces. The BCD in your last post is unchanged from your original post. This probably means that your system has more than one BCD and we are changing the wrong one.

Could you try this? Assign a drive letter (D:) to the first partition on your disk. Use Windows Disk Management console, right-click on the first partition and choose "Change Drive Letter and Paths...". This will make the contents of the System partition visible in Windows Explorer and make it easier to find files. When you are finished you can remove the temporary drive letter.

How many BCD files are on your disk? There should be one in D:\boot\ and there may be one in C:\boot\ and one in E:\boot\. Which one has the most recent file date and time? The one that the system is supposed to use will be in the Active partition, at D:\boot\bcd

Can you list the contents of any BCD that you find and determine which one is different? To list a particular BCD you use the /store modifier in the bcdedit command:

bcdedit /store D:\boot\bcd /enum all

bcdedit /store C:\boot\bcd /enum all

bcdedit /store E:\boot\bcd /enum all

Beginner
Posts: 0
Comments: 19

#268

Mark:
I have 3 partition in my hard drive (C - E - and F) but I haven't partition named "D"
3 partitions are assigned a letter and I can to enter in from the workstation - I made a screenshot -
I enter the following command: <<< bcdedit /store C:\boot\bcd /enum all >>>
the result ::::

Gestionnaire de démarrage Windows
---------------------------------
identificateur {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {default}
resumeobject {cfd2e53a-7abe-11de-ba4e-be6b01c0306f}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 30

Chargeur de démarrage Windows
-----------------------------
identificateur {default}
device partition=C:
path \windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
osdevice partition=C:
systemroot \windows
resumeobject {cfd2e53a-7abe-11de-ba4e-be6b01c0306f}
nx OptIn

Reprendre … partir de la mise en veille prolongée
-------------------------------------------------
identificateur {cfd2e53a-7abe-11de-ba4e-be6b01c0306f}
device ramdisk=[C:]\sources\boot.wim,{ramdiskoptions}
path \windows\system32\boot\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Testeur de mémoire Windows
--------------------------
identificateur {memdiag}
device partition=C:
path \boot\memtest.exe
description Windows Memory Diagnostic
locale en-US
inherit {globalsettings}
badmemoryaccess Yes

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

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

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

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

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

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

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

Options Ramdisk du programme d'installation
-------------------------------------------
identificateur {ramdiskoptions}
description Ramdisk options
ramdisksdidevice partition=C:
ramdisksdipath \boot\boot.sdi
=======================================================================================
and I enter the following command: <<< bcdedit /store E:\boot\bcd /enum all >>>
and the result :::

Gestionnaire de démarrage Windows
---------------------------------
identificateur {bootmgr}
device boot
description Windows Boot Manager
locale fr-FR
default {default}
displayorder {default}

Chargeur de démarrage Windows
-----------------------------
identificateur {default}

Options Ramdisk du programme d'installation
-------------------------------------------
identificateur {ramdiskoptions}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \boot\boot.sdi
=======================================================================================
and i try this commande : <<< bcdedit /store F:\boot\bcd /enum all >>> and I made a screenshot and uload it in image file

Attachment Size
119394-105271.jpg 264.33 KB
119394-105274.jpg 269 KB
Forum Star
Posts: 19
Comments: 2110

#269

Ascanio:

You do have an additional partition on your disk. It is the system partition and it currently does not have a drive letter assigned to it, so you don't see it in Windows Explorer. But you can see it in your screenshot of Windows Disk Management.

I wanted you to assign drive letter D: to this first partition. You can do this in Windows Disk Management. If you do, then you can see the BCD and list its contents. This BCD is supposedly the one in use by your system that we were unsuccessful at editing. I'm just trying to figure out why.

Beginner
Posts: 4
Comments: 2

#270

X

Beginner
Posts: 0
Comments: 19

#271

hi Mark:
I assigned the letter "D" for the partition "System" and I entered this command <<< bcdedit / store D: \ boot \ bcd / enum all >>>
and here is the result:

Gestionnaire de démarrage Windows
---------------------------------
identificateur {bootmgr}
device partition=D:
description Windows Boot Manager
locale fr-FR
inherit {globalsettings}
extendedinput Yes
default {default}
resumeobject {564a65c9-2b77-11e1-941e-f70bf23216e3}
displayorder {default}
toolsdisplayorder {memdiag}
timeout 0
displaybootmenu Yes
customactions 0x1000085000001
0x5400000f
custom:5400000f {564a65cb-2b77-11e1-941e-f70bf23216e3}

Chargeur de démarrage Windows
-----------------------------
identificateur {default}
device partition=C:
path \windows\system32\winload.exe
description Windows 7
locale fr-FR
inherit {bootloadersettings}
recoverysequence {564a65cb-2b77-11e1-941e-f70bf23216e3}
recoveryenabled Yes
osdevice partition=C:
systemroot \windows
resumeobject {564a65c9-2b77-11e1-941e-f70bf23216e3}
nx OptIn
detecthal Yes

Chargeur de démarrage Windows
-----------------------------
identificateur {564a65cb-2b77-11e1-941e-f70bf23216e3}

Reprendre … partir de la mise en veille prolongée
-------------------------------------------------
identificateur {564a65c9-2b77-11e1-941e-f70bf23216e3}
device partition=C:
path \windows\system32\winresume.exe
description Windows Resume Application
locale fr-FR
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

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

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

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

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

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

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

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

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

Options de périphérique
-----------------------
identificateur {564a65cc-2b77-11e1-941e-f70bf23216e3}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Options de périphérique
-----------------------
identificateur {564a65cd-2b77-11e1-941e-f70bf23216e3}
description Recovery
ramdisksdidevice partition=C:
ramdisksdipath \NST\boot.sdi

Options Ramdisk du programme d'installation
-------------------------------------------
identificateur {ramdiskoptions}
description RamdiskOptions
ramdisksdidevice partition=C:
ramdisksdipath \NST\boot.sdi

Attachment Size
119456-105286.jpg 192.24 KB
Forum Star
Posts: 19
Comments: 2110

#272

Ascanio:

Thank you for posting all of the information about your system. I really don't understand what's going on. Your System partition (D:) is the one that contains the BCD that the system boots from, I believe, but none of our bcdedit commands had any effect on it. The contents of D:\boot\bcd are exactly the same as they were before we started.

The BCD at C:\boot\bcd is unusual - I don't understand the entries in the "Resume from Hibernate" loader in this BCD, but it may not matter since the PC does not boot from this partition anyway.

I can only think of one explanation for what's happening. I've read that bcdedit sometimes can get confused if there is more than one BCD on a disk. In cases like that it is recommended to target the bcdedit commands to a particular BCD store by using the /store command modifier. So that may be worth a try. Let's start with the three commands that failed:

bcdedit /store D:\boot\bcd /set {564a65cb-2b77-11e1-941e-f70bf23216e3} device ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{564a65cc-2b77-11e1-941e-f70bf23216e3}

bcdedit /store D:\boot\bcd /set {564a65cb-2b77-11e1-941e-f70bf23216e3} osdevice ramdisk=[E:]\Recovery\WindowsRE\Winre.wim,{564a65cc-2b77-11e1-941e-f70bf23216e3}

bcdedit /store D:\boot\bcd /set {564a65cc-2b77-11e1-941e-f70bf23216e3} ramdisksdidevice partition=E:

If these are successful, then list the BCD again:

bcdedit /store D:\boot\bcd /enum all

Do the changes now appear in the BCD listing?

Beginner
Posts: 0
Comments: 19

#273

Mark :
thanks to you to helping me to solve my problem
I entered the 3 commands that you gave me and I still get the same result :( :
<<<
this request is not supported.>>>>

Beginner
Posts: 0
Comments: 19

#274

if I enter in the elevated command prompt window from a "DVD repair windows 7" and I enter new orders is that has a chance to succeed?

Forum Star
Posts: 19
Comments: 2110

#275
Ascanio Tozzi wrote:

if I enter in the elevated command prompt window from a "DVD repair windows 7" and I enter new orders is that has a chance to succeed?

This may work but you will first need to determine the correct drive letters to use in each command. Drive letters will be different than when you are running Windows. You will need to change the drive letters in each command to the ones assigned by the recovery environment when booted from the repair DVD.

For example, the partition named "SYSTEM" is drive letter D: when booted into Windows 7; it will probably be C: when booted from the DVD. The others may be different also. That's not a problem, but you just need to figure out what drive letter is assigned to the partitions that Windows 7 is labeling as C:, D:, and E: when you are running Windows Recovery Environment from the DVD. Use the new drive letters in the commands.

Beginner
Posts: 0
Comments: 4

#276

Hey Mark. Seen this post and all the great help you've given others. I am also having the same problem. Mine looks as if another drive letter has been added. Pointing toward multiple recovery files. Heres my output readout. Thanks for your time.

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale en-US
inherit {globalsettings}
integrityservices Enable
default {default}
resumeobject {55b4dec7-e07c-11dd-9aba-c08d2c476297}
displayorder {a720a4c4-d893-11de-ba2c-00238b8b8976}
{default}
toolsdisplayorder {memdiag}
timeout 30
custom:26000025 Yes

Windows Boot Loader
-------------------
identifier {default}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-US
inherit {bootloadersettings}
recoverysequence {current}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {55b4dec7-e07c-11dd-9aba-c08d2c476297}
nx OptIn

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

Windows Boot Loader
-------------------
identifier {current}
device ramdisk=[C:]\Recovery\a720a4c1-d893-11de-ba2c-00238b8b8976\Winre.wim,{a720a4c2-d893-11de-ba2c-00238b8b8976}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\a720a4c1-d893-11de-ba2c-00238b8b8976\Winre.wim,{a720a4c2-d893-11de-ba2c-00238b8b8976}
systemroot \windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {a720a4c4-d893-11de-ba2c-00238b8b8976}
device partition=D:
path \Windows\system32\winload.exe
description Windows Developer Preview
locale en-US
inherit {bootloadersettings}
recoverysequence {a720a4c5-d893-11de-ba2c-00238b8b8976}
integrityservices Enable
recoveryenabled Yes
osdevice partition=D:
systemroot \Windows
resumeobject {a720a4c3-d893-11de-ba2c-00238b8b8976}
nx OptIn
custom:250000c2 1

Windows Boot Loader
-------------------
identifier {a720a4c5-d893-11de-ba2c-00238b8b8976}
device ramdisk=[E:]\Recovery\a720a4c5-d893-11de-ba2c-00238b8b8976\Winre.wim,{a720a4c6-d893-11de-ba2c-00238b8b8976}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
custom:15000065 3
osdevice ramdisk=[E:]\Recovery\a720a4c5-d893-11de-ba2c-00238b8b8976\Winre.wim,{a720a4c6-d893-11de-ba2c-00238b8b8976}
systemroot \windows
nx OptIn
custom:250000c2 1
winpe Yes

Resume from Hibernate
---------------------
identifier {55b4dec7-e07c-11dd-9aba-c08d2c476297}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
debugoptionenabled No

Resume from Hibernate
---------------------
identifier {a720a4c3-d893-11de-ba2c-00238b8b8976}
device partition=D:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale en-US
inherit {resumeloadersettings}
filedevice partition=D:
filepath \hiberfil.sys
custom:25000008 1
debugoptionenabled No

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

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device unknown
path \ntldr
description Earlier Version of Windows

EMS Settings
------------
identifier {emssettings}
custom:26000022 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 {a720a4c2-d893-11de-ba2c-00238b8b8976}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\a720a4c1-d893-11de-ba2c-00238b8b8976\boot.sdi

Device options
--------------
identifier {a720a4c6-d893-11de-ba2c-00238b8b8976}
description Windows Recovery
ramdisksdidevice partition=E:
ramdisksdipath \Recovery\a720a4c5-d893-11de-ba2c-00238b8b8976\boot.sdi

Forum Star
Posts: 19
Comments: 2110

#277

DJ0007:

You seem to have multiple operating systems installed. Could you post a screenshot from Windows Disk Management so that I can see which is which?

Beginner
Posts: 0
Comments: 4

#278

Sorry I cannot get either OS to start. I have win 7 on the C: drive. I can not remember which drive win 8 preview is on I believe it is D:, I was puzzled to see the E drive pointed to in the bootloader. Which is my DVDrom. The repair doesn't work on Win 7 or 8. Really don't care about Win 8. Just wanted to boot up to windows 7.

Forum Star
Posts: 19
Comments: 2110

#279

DJ0007:

I assume then that the BCD contents listed in reply #276 were obtained by booting to the Windows Recovery Environment; correct? Which recovery environment - Windows 7 or Windows 8? Did you boot from a Windows DVD or Repair CD, or from the hard disk?

The drive letters that you will see in the Recovery Environment are different than those that you'll see when booted to Windows. Drive letters are not unique; they are assigned by the operating system that is currently running. So to get anywhere with this, you first need to figure out which drive letter belongs to which partition when you are in the Recovery Environment. You can do this several ways. One is to go to a command prompt and do this for each drive letter:

C:
dir
D:
dir
E:
dir
...etc...

Looking at the directory listings will allow you to figure out which partition contains which OS. Could you do this and post the results?

My initial guess is that when running WinRE, C: is Windows 7, D: is Windows 8, E: is a recovery partition from your PC OEM. Is that correct?

When you boot your PC do you see the boot menu? Is it the Windows 7 text-based boot menu or the Windows 8 graphical boot menu?

Beginner
Posts: 0
Comments: 4

#280

The drive orders are correct win 7 C: and so on. I get the windows 7 interface after I set it as defaut OS to chose an operation system. Either one I chose I will get to recovery for that OS. They both try to repair itself. Both fail. The above BcDedit report is from win 7 CMD.

Forum Star
Posts: 19
Comments: 2110

#281

DJ0007:

Based on your description and the BCD contents posted, the low-level boot process is correct. You get all the way to loading Winload.exe and then something fails, so Windows automatically boots to the Recovery Environment. So there must be something else going wrong at a higher level.

Have you tried booting Windows 7 using one of the Advanced Boot Options? This article explains how to do this and it contains links to several other methods of repairing Windows: http://www.sevenforums.com/tutorials/666-advanced-boot-options.html

I cannot see anything wrong with the BCD and I believe that it is doing its job properly in starting the boot process for your PC. I believe that the failure is somewhere else later in the boot process.

Beginner
Posts: 0
Comments: 4

#282

Ok. Thanks for your time. I will keep researching. I am trying to get windows 7 into safe mode. From what else I've read maybe the error is being caused by memtest.exe. Thanks again.

Forum Star
Posts: 19
Comments: 2110

#283

Ascanio:

I really don't understand what's going on with your computer and why the BCD cannot be modified. I am sorry that I have not been able to help. Perhaps you should try posting in an HP forum.

Beginner
Posts: 0
Comments: 19

#284

Mark :
sorry if I wasn't given my news, I am studying from 8am until 6pm and when I come aback to home, i sleep
I tried to create a CD / DVD recovery system but I cann't, it says "ERROR" IMPOSSIBLE !!!!
I boot with windows 7 Ultimate DVD, I chose repair system to access to the "elevated command prompt window " ..... also "IMPOSSIBLE" mee he said it's not the same system (home premium / ultimate)
and at startup the computer, I press "F1", "F2", "F3", ....... "F12" but I was not able to get to a "guest orders"
Friday I'll try to come in the "elevated command prompt window " and I'll let you know
Maybe it will work, I hope ... : P
In any case, thank you so much that try to help me :)

Beginner
Posts: 0
Comments: 19

#285

Hi Mark
sorry for my absence, i leave my HP this week because i didn't have time, so i will ask my problem in "HP FORUM" and if i have a solution i will let you knows :)

Beginner
Posts: 0
Comments: 1

#286

Mark this is just a wonderful post. I bet you are hoping for a day that windows fixes this issue so you can get some peace! But as it stands I have a similar problem, I can't even get my F8 menu to open on start up :(. I'm going to go grab some blank discs and get a repair disc set up and see if I can make some headway in that direction right now, but I thought I'd throw up my specs and maybe you'll get a chance to look at them sometime. Thanks you so much for this post, there are not enough helpful people out there anymore!

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

C:\Windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-US
inherit {globalsettings}
default {current}
resumeobject {ad91f3b4-1bbd-11df-aff5-0026b92433e2}
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 {ad91f3b6-1bbd-11df-aff5-0026b92433e2}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {ad91f3b4-1bbd-11df-aff5-0026b92433e2}
nx OptIn

Windows Boot Loader
-------------------
identifier {ad91f3b6-1bbd-11df-aff5-0026b92433e2}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{ad91f3b7-1bbd-11df-aff5-0026b92433e2}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Win
re.wim,{ad91f3b7-1bbd-11df-aff5-0026b92433e2}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {ad91f3b4-1bbd-11df-aff5-0026b92433e2}
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 {ad91f3b7-1bbd-11df-aff5-0026b92433e2}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi

C:\Windows\system32>

This is windows 7 btw. Let me know if i can anything else to help! Who would have thought microsoft would make it this difficult to reset a computer!

Sam

Attachment Size
120247-105439.png 60.95 KB
Forum Star
Posts: 19
Comments: 2110

#287

Sam:

I don't see anything wrong with the BCD entries, and your Disk Management screenshot shows that the second partition is set as Active and, I presume, the recovery files are located there also.

Timing is everything when hitting the F8 key to enter the recovery environment. Some PCs are pretty fast and you have to hit the key at the precise time to get this to work. One method involves watching the PC BIOS boot screen and then repeatedly tapping the F8 key right after the self-test completes and before the disk is recognized. If this doesn't work then try holding down the shift key  (sorry; the space bar) after the BIOS self-test completes. This should display the boot manager window and you can select "Repair your computer" from there.

Beginner
Posts: 0
Comments: 14

#288

Hi Mark, really appreciating everything your doing but I have a problem that is probably quite easy for you to fix, you see I have the same problem as the first person but when I try to do the repair it says my disk isn't compatible with the version when it is, anyway I have attached the bsdedit/enum all file, please could you have a look at it and see what you make of it?

Attachment Size
120944-105592.txt bytes
Beginner
Posts: 0
Comments: 14

#289

Thanks mark:)

Forum Star
Posts: 19
Comments: 2110

#290

Horatio:

Your text file did not attach - it's zero bytes long.

Which operating system are you using and is it 32-bit or 64-bit? When you try to repair are you using a recovery CD, a Windows installation DVD, or are you booting to the recovery environment (F8 repair your computer)? If you are using a recovery CD is it a 32-bit or a 64-bit recovery CD? If you are using a Windows installation DVD is it 32-bit or 64-bit?

Beginner
Posts: 0
Comments: 14

#291

Hi sorry it didnt attach, i was using a tablet.
I am using a 64bit windows and I hold F8 and boot the windows 7 recovery disk which is also the installation disk and on the start installation screen I click repair and it searches for an operating system and finds the windows 7 on the D: drive. I click next and it says the the disk is not compatible with the windows.

Attachment Size
120954-105595.txt 4.79 KB
Forum Star
Posts: 19
Comments: 2110

#292

Horatio:

I don't see any issues with your BCD.

Retail Windows 7 installation DVDs came with two disks - one for 32-bit Windows 7 and the other for 64-bit. Make sure that you're using the 64-bit disk.

If that's not it, please read this thread: http://social.technet.microsoft.com/Forums/en/windowsbackup/thread/5ea5135f-d6b8-4caa-a0bd-ce4e1a6ed463 to see if it applies to your situation.

Instead of using the DVD can you access the recovery environment on your disk? Reboot your PC and right after the BIOS self-test finishes and just before Windows starts, hold down the space bar. You should see the Windows boot manager screen. Hit the F8 key to access the "Repair Your Computer" choice. This should boot you into the Windows Recovery Environment on your disk. The BCD entries appear correct for doing this.

Beginner
Posts: 0
Comments: 14

#293

OK thanks, I think ill try putting the recovery media onto a blank CD, can you do this in safe mode?

Beginner
Posts: 0
Comments: 14

#294

I'm using the recovery to try and repair this ntoskrnl.exe driver that causes my PC to randomly bsod

Beginner
Posts: 0
Comments: 14

#295

Made this post by accident

Beginner
Posts: 0
Comments: 14

#296

Can I open an elevated cmd in safe mode? I am trying to do "copy D:\sources\dlmanifests\ntoskrnl-dl.man c:\windows\system32\ntoskrnl.exe" to replace the ntoskrnl.exe file but it keeps saying access denied

Forum Star
Posts: 19
Comments: 2110

#297

Horatio:

I doubt that you can replace that file in any mode, safe or otherwise. The file will be in use by the Windows kernel so you will be unable to replace it. You'd have to do this when Windows is shut down and you're booted to some other OS like the Recovery Environment, or a Live Linux CD or the like.

Does your PC work properly without bluescreen errors in safe mode? If so, I doubt that ntoskrnl.exe is the culprit. It may be caused by something else; most likely a driver if there are no errors in safe mode.

Beginner
Posts: 0
Comments: 14

#298

Yeah it only works in safe mode and in normal mode, the screen goes black just randomly and restarts the pc , I go into safe mode and the report says its a blue screen error, I scan the mini dump file and it says its caused by the ntoskrnl.exe driver, I've tried bootcfg /rebuild but it says bootcfg /?. I'm lost.

Forum Star
Posts: 19
Comments: 2110

#299

Horatio:

Then this isn't a boot issue but probably a driver issue. As a first guess I would suspect the video driver. You could try uninstalling it in safe mode, then reboot normally and let Windows Update find the correct driver and reinstall it. Otherwise, look back in Action Center to find when the problem first started occurring and see what was installed or updated right before this all started. That might give you a clue where to begin.

Do you have an image of your system from when it was working properly, or a Windows Restore Point to roll back to?

Beginner
Posts: 0
Comments: 14

#300

Thanks so much for the help by the way but no, unfortunately I don't because I bought the PC in September and it ran fine for a bit then started doing that, I'll try the video drivers thing though