Salta al contenuto principale

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

Thread needs solution
Beginner
Messaggi: 0
Commenti: 21

@GroverH Thanks. Yes the boot order was correct in BIOS.

@Mark Thanks. After hours of searching I found this forum and saw your expertise and knew you could help. :) Below is what I have now after running all of the commands and F8 "Repair Your Computer" has returned to normal.

Allegato Dimensione
175265-112948.txt 4.38 KB
Beginner
Messaggi: 0
Commenti: 1

@Mark
I ran into similar problem today and I'm glad I found your post with solutions. It gave me relief and I hope my problem can be fixed as well. I appreciate your work. We'll now coming to my problem, can you tell me how can I copy he output into a notepad or something as I cannot login to my PC other than command prompt from recovery options . How can I copy and where should I from there.
Please guide and help.

Forum Star
Messaggi: 19
Commenti: 2110

Sundeep:

One way is to attach a USB flash drive to the PC when you boot into the recovery environment. Then open a command prompt window and find the drive letter of the flash drive. To copy the BCDEDIT output to a text file you would then use the following command:

bcdedit /enum all > X:\bcd.txt

Substitute the actual flash drive's letter for X: in the above command, which will direct the output of the bcdedit command to a text file named bcd.txt on the flash drive.

Beginner
Messaggi: 0
Commenti: 1

A CRY FROM RF TO MARK!

Respected, Mark Wharton!

We are your fan since read first time your post in the middle of 2010. Really like to read your post.

Please allow us to explain our problem. Using DELL XPS M1330. This laptop has two power buttons: one for DELL MEDIADIRECT boot in Windows XP environment and the other for Windows 7, 64 bit. For a long time facing problem with DELL MEDIADIRECT BUTTON crash: instead of booting MEDIADIRECT, it boots Windows 7. Because of this we are compelled to install the system completely several times. When we had purchased the said DELL laptop, it has no HIDDEN RECOVERY PARTITION. So that decided to create a F8 bootable hidden recovery partition, but till now didn't able. And by the time create another problem with booting......

Attaching herewith the output of elevated command prompt, please check.

We would be grateful to you so so much if you help us/give us some idea for making F8 bootable hidden recovery partition and booting from F8.

Regards!

Allegato Dimensione
175703-113071.txt 4.64 KB
Forum Star
Messaggi: 19
Commenti: 2110

Natalya:

I don't think that I can help you with your project because I do not have any experience with the Dell Media Direct system. However, I can refer you to Dan Goodell's web site: http://www.goodells.net/dellrestore/mediadirect.shtml where you can find all kinds of information about Dell recovery and Media Direct partitions.

Beginner
Messaggi: 0
Commenti: 10

Hi Mark Wharton.

I have dell xps 15 window 7 home premium and when i press F8 and choose "repair your computer" it will directly boot into window.
Could you take a look and help me with this.

Thanks in advance.

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
path \bootmgr
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {b78ffce2-6e99-11e3-bcad-f7fe86455168}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {0df292e6-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292ea-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292ee-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292f2-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292f6-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {2dcfa13c-6e5a-11e3-bf73-f7ae27687369}

Windows Boot Loader
-------------------
identifier {2dcfa140-6e5a-11e3-bf73-f7ae27687369}

Windows Boot Loader
-------------------
identifier {5b704674-6e7d-11e3-bc58-ada284c86269}

Windows Boot Loader
-------------------
identifier {66bc8203-f33b-11e3-83e1-d21975fea96a}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{66bc8204-f33b-11e3-83e1-d21975fea96a}
path \windows\system32\winload.exe
description Windows Recovery Environment (recovered)
locale
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{66bc8204-f33b-11e3-83e1-d21975fea96a}
systemroot \windows
winpe Yes

Windows Boot Loader
-------------------
identifier {8f5fdb46-6e69-11e3-80ee-a173fdd68b69}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
recoverysequence {9b9af826-5452-11e1-9ce1-88532e98afac}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {b78ffce2-6e99-11e3-bcad-f7fe86455168}
nx OptIn
bootstatuspolicy IgnoreShutdownFailures

Windows Boot Loader
-------------------
identifier {b78ffce4-6e99-11e3-bcad-f7fe86455168}

Resume from Hibernate
---------------------
identifier {b78ffce2-6e99-11e3-bcad-f7fe86455168}
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 {0df292e7-ae1b-11e1-9c7f-fa3972d05868}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {2dcfa13d-6e5a-11e3-bf73-f7ae27687369}
ramdisksdidevice unknown
ramdisksdipath \Recovery\windowsre\boot.sdi

Device options
--------------
identifier {66bc8204-f33b-11e3-83e1-d21975fea96a}
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {b78ffce5-6e99-11e3-bcad-f7fe86455168}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\b78ffce4-6e99-11e3-bcad-f7fe86455168\boot.sdi

Allegato Dimensione
177535-113593.txt 5.29 KB
Forum Star
Messaggi: 19
Commenti: 2110

Kouymz:

The pointer to the recovery sequence in your BCD is incorrect. Enter the following 3 commands in an elevated command prompt window to fix:

bcdedit /set {current} recoverysequence {66bc8203-f33b-11e3-83e1-d21975fea96a}
bcdedit /set {66bc8203-f33b-11e3-83e1-d21975fea96a} nx OptIn
bcdedit /set {66bc8203-f33b-11e3-83e1-d21975fea96a} description "Windows Recovery Environment"

Test to see if F8 now works correctly. If it does, you have 13 invalid entries in the BCD that can be deleted:

bcdedit /delete {0df292e6-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {0df292ea-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {0df292ee-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {0df292f2-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {0df292f6-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {2dcfa13c-6e5a-11e3-bf73-f7ae27687369}
bcdedit /delete {2dcfa140-6e5a-11e3-bf73-f7ae27687369}
bcdedit /delete {5b704674-6e7d-11e3-bc58-ada284c86269}
bcdedit /delete {8f5fdb46-6e69-11e3-80ee-a173fdd68b69}
bcdedit /delete {b78ffce4-6e99-11e3-bcad-f7fe86455168}
bcdedit /delete {0df292e7-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {2dcfa13d-6e5a-11e3-bf73-f7ae27687369}
bcdedit /delete {b78ffce5-6e99-11e3-bcad-f7fe86455168}

Beginner
Messaggi: 0
Commenti: 10

@Mark

This is what happen when I enter those command:

bcdedit /set {current} recoverysequence {66bc8203-f33b-11e3-83e1-d21975fea96a}
The operation completed successfully.

bcdedit /set {66bc8203-f33b-11e3-83e1-d21975fea96a} nx OptIn
An error occurred while attempting to reference the specific entry.
The system cannot find the specified.

bcdedit /set {66bc8203-f33b-11e3-83e1-d21975fea96a} description "Windows Recovery Environment"
An error occurred while attempting to reference the specific entry.
The system cannot find the specified.

After enter command:

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {b78ffce2-6e99-11e3-bcad-f7fe86455168}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {0df292e6-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292ea-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292ee-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292f2-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292f6-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {2dcfa13c-6e5a-11e3-bf73-f7ae27687369}

Windows Boot Loader
-------------------
identifier {2dcfa140-6e5a-11e3-bf73-f7ae27687369}

Windows Boot Loader
-------------------
identifier {5b704674-6e7d-11e3-bc58-ada284c86269}

Windows Boot Loader
-------------------
identifier {8f5fdb46-6e69-11e3-80ee-a173fdd68b69}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
recoverysequence {66bc8203-f33b-11e3-83e1-d21975fea96a}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {b78ffce2-6e99-11e3-bcad-f7fe86455168}
nx OptIn
bootstatuspolicy IgnoreShutdownFailures

Windows Boot Loader
-------------------
identifier {b78ffce4-6e99-11e3-bcad-f7fe86455168}

Resume from Hibernate
---------------------
identifier {b78ffce2-6e99-11e3-bcad-f7fe86455168}
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 {0df292e7-ae1b-11e1-9c7f-fa3972d05868}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {2dcfa13d-6e5a-11e3-bf73-f7ae27687369}
ramdisksdidevice unknown
ramdisksdipath \Recovery\windowsre\boot.sdi

Device options
--------------
identifier {b78ffce5-6e99-11e3-bcad-f7fe86455168}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\b78ffce4-6e99-11e3-bcad-f7fe86455168\boot.sdi

Allegato Dimensione
177542-113596.txt 4.49 KB
Forum Star
Messaggi: 19
Commenti: 2110

Koyumz:

That's really strange - the boot loader entry for the recovery environment completely disappeared from your BCD. Let's try to re-create its contents in the first orphaned OS Loader, which I think used to belong to the recovery environment entry. Enter each of the following commands, one at a time, into an elevated command prompt window. Each command should be on one line, so be sure that line breaks in the web browser view do not make it into the command prompt window. You should probably use cut and paste to be sure:

bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{0df292e7-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} path \windows\system32\winload.exe
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} description "Windows Recovery Environment"
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} locale en-US
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} inherit {bootloadersettings}
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{0df292e7-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} systemroot \Windows
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} nx OptIn
bcdedit /set {0df292e6-ae1b-11e1-9c7f-fa3972d05868} winpe yes

This should result in an OS Loader entry for the recovery environment. Now you will need to change pointers to refer to this entry:

bcdedit /set {current} recoverysequence {0df292e6-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /set {0df292e7-ae1b-11e1-9c7f-fa3972d05868} ramdisksdidevice partition=\Device\HarddiskVolume2
bcdedit /set {0df292e7-ae1b-11e1-9c7f-fa3972d05868} ramdisksdipath \Recovery\WindowsRE\boot.sdi

Then do NOT delete the unused entries listed in my reply #607 yet. First check to see if this works, then reply with your new BCD contents listed.

Beginner
Messaggi: 0
Commenti: 10

@Mark

I entered all the command successfully and after choosing F8 "repair you computer" it take me directly into Dell DataSafe Local Backup to restore factory image setting. I think it should go into a few option first before reaching to that point. I attach the new BCD content.

Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=\Device\HarddiskVolume2
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {b78ffce2-6e99-11e3-bcad-f7fe86455168}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {0df292e6-ae1b-11e1-9c7f-fa3972d05868}
device ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{0df292e7-ae1b-11e1-9c7f-fa3972d05868}
path \windows\system32\winload.exe
description Windows Recovery Environment
locale en-US
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume2]\Recovery\WindowsRE\Winre.wim,{0df292e7-ae1b-11e1-9c7f-fa3972d05868}
systemroot \Windows
nx OptIn
winpe Yes

Windows Boot Loader
-------------------
identifier {0df292ea-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292ee-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292f2-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {0df292f6-ae1b-11e1-9c7f-fa3972d05868}

Windows Boot Loader
-------------------
identifier {2dcfa13c-6e5a-11e3-bf73-f7ae27687369}

Windows Boot Loader
-------------------
identifier {2dcfa140-6e5a-11e3-bf73-f7ae27687369}

Windows Boot Loader
-------------------
identifier {5b704674-6e7d-11e3-bc58-ada284c86269}

Windows Boot Loader
-------------------
identifier {8f5fdb46-6e69-11e3-80ee-a173fdd68b69}

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
recoverysequence {0df292e6-ae1b-11e1-9c7f-fa3972d05868}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {b78ffce2-6e99-11e3-bcad-f7fe86455168}
nx OptIn
bootstatuspolicy IgnoreShutdownFailures

Windows Boot Loader
-------------------
identifier {b78ffce4-6e99-11e3-bcad-f7fe86455168}

Resume from Hibernate
---------------------
identifier {b78ffce2-6e99-11e3-bcad-f7fe86455168}
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 {0df292e7-ae1b-11e1-9c7f-fa3972d05868}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume2
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier {2dcfa13d-6e5a-11e3-bf73-f7ae27687369}
ramdisksdidevice unknown
ramdisksdipath \Recovery\windowsre\boot.sdi

Device options
--------------
identifier {b78ffce5-6e99-11e3-bcad-f7fe86455168}
description Ramdisk Options
ramdisksdidevice unknown
ramdisksdipath \Recovery\b78ffce4-6e99-11e3-bcad-f7fe86455168\boot.sdi

Allegato Dimensione
177546-113599.txt 5.04 KB
Forum Star
Messaggi: 19
Commenti: 2110

Koyumz:

In order to figure this out we will have to see what files Dell put on the recovery partition. Could you do this?
1. Use Windows Disk Management to assign a temporary drive letter to the second partition. Choose any letter that isn't currently being used.
2. Use Windows Explorer to browse the contents of the partition. You will have to enable viewing of both hidden files and of protected operating system files in order to see everything.
3. If possible, post a few screenshots showing what's on the partition, and in the folders on the partition.
4. When you're done, you can use Disk Management again to remove the temporary drive letter from the recovery partition.

Beginner
Messaggi: 0
Commenti: 10

@Mark

I attach the screenshots of the partition. Hope this will help.
Thank you so much for your great support.

Allegato Dimensione
177549-113602.png 25.94 KB
177549-113605.png 76.67 KB
177549-113608.png 71.42 KB
Forum Star
Messaggi: 19
Commenti: 2110

I would be especially interested in seeing what's in the folder "Recovery", and in any subfolders inside this folder.

Beginner
Messaggi: 0
Commenti: 10

@Mark

I can't access inside all the subfolder.

Allegato Dimensione
177552-113611.png 42.65 KB
Forum Star
Messaggi: 19
Commenti: 2110

Can you open an administrative command prompt window and then list the contents from there?
h:
cd Recovery
dir /ah
dir /as

the /ah switch lists hidden files, the /as switch lists system files

Beginner
Messaggi: 0
Commenti: 10

@Mark

Here what i got.

Allegato Dimensione
177554-113614.png 53.59 KB
177554-113617.png 51.48 KB
Forum Star
Messaggi: 19
Commenti: 2110

Koyumz:

I don't understand why that didn't work. You entered the correct command to change directory to H:\Recovery, but when you list the contents they appear to be the language files that are also at H:\

What happens if you are at H:\Recovery and you type "cd Recovery" again?

Beginner
Messaggi: 0
Commenti: 10

@Mark

If type another "cd Recovery":
The system cannot find the path specified.

But im hoping this could help.

Allegato Dimensione
177558-113620.png 42.26 KB
177558-113623.png 25.5 KB
Forum Star
Messaggi: 19
Commenti: 2110

Koyumz:

Yes, that's what I was looking for. The recovery environment is in the image file WinRE.wim. Yours is 217 MB in size while the one furnished by Microsoft for Windows 7 x86 is 138 MB, so Dell must have added some extra stuff to the recovery image. So we appear to be starting the correct file when booting to the recovery environment. However, I have no idea what Dell has done from here. You may need to get that information from someone on a Dell forum.

If you want the standard, non-Dell version of the recovery environment then there may be a copy on your C partition. With a command prompt, browse the C partition to see if there is a folder named "Recovery" at the root of the C partition, and then see what's inside. If the files are there we could link the F8 key to them and bypass the Dell recovery.

Beginner
Messaggi: 0
Commenti: 10

@Mark

Im using Windows7 x64..is it same with x84?

Is this the file we looking for?

Allegato Dimensione
177566-113626.png 62.17 KB
Forum Star
Messaggi: 19
Commenti: 2110

Koyumz:

No; the recovery folder that you would need would be located in the root of the C: partition.
For Windows 7 x64 the recovery environment image is 160 MB, so that sounds reasonable that Dell would add enough extra to the image to allow users a choice of repair or reinstall, making the WinRE.wim file a little bigger; 217 MB in this case. The image file needed for reinstalling the factory image is much, much larger; several GB, so we have the right one.

One thing to check - when you boot into the recovery environment do you see any menus allowing you to do anything other than just restoring the factory image? I would think that you should.

Beginner
Messaggi: 0
Commenti: 10

@Mark

After the second time choosing "repair your computer" it boot into a menu like it should be.
I don't know why the first time it directly into factory image restore.
I think it should be working fine now.
Thank you so much for your help.

I attach the latest BCD. Is there anything I should do or just leave it as it is?

Allegato Dimensione
177572-113629.txt 5.04 KB
Forum Star
Messaggi: 19
Commenti: 2110

Kouymz:

That sounds more like it! Glad to hear that it works.

If you want to leave your BCD as it is, the orphaned boot loader entries won't do any harm. However, if you want to remove them and clean things up, here are 11 entries that you can delete:

bcdedit /delete {0df292ea-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {0df292ee-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {0df292f2-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {0df292f6-ae1b-11e1-9c7f-fa3972d05868}
bcdedit /delete {2dcfa13c-6e5a-11e3-bf73-f7ae27687369}
bcdedit /delete {2dcfa140-6e5a-11e3-bf73-f7ae27687369}
bcdedit /delete {5b704674-6e7d-11e3-bc58-ada284c86269}
bcdedit /delete {8f5fdb46-6e69-11e3-80ee-a173fdd68b69}
bcdedit /delete {b78ffce4-6e99-11e3-bcad-f7fe86455168}
bcdedit /delete {2dcfa13d-6e5a-11e3-bf73-f7ae27687369}
bcdedit /delete {b78ffce5-6e99-11e3-bcad-f7fe86455168}

You can also remove  the temporary drive letter from the recovery partition and change the settings back on Windows Explorer to once again hide protected operating system files (and hidden files if you want).

Beginner
Messaggi: 0
Commenti: 10

@Mark

You are awesome.
I am so grateful of your help.
I have deleted all the 11 entries. It should look like the attach file right?

Allegato Dimensione
177574-113632.txt 3.66 KB
Forum Star
Messaggi: 19
Commenti: 2110

Koyumz:

Yes - that looks perfect. Glad to help out.

Beginner
Messaggi: 0
Commenti: 6

I have a asus laptop and having problem with my restoring f8 button,cant use my installation cd. And cant load window. How do i get to this command prompt. I tried the one with safe mode it did not work also.

Forum Star
Messaggi: 19
Commenti: 2110

Oladeni:

You will need an installation DVD or a repair CD. If your system runs Windows 7 and you have access to another Windows 7 PC, either at work, home, or a friend's PC, make a System Repair Disk: http://www.7tutorials.com/how-create-system-repair-disc-cddvd

Beginner
Messaggi: 0
Commenti: 1

Hi Mark:
My wife's computer will not allow a login and gives messages in repair mode that it cannot repair the problem. It says it is a patch problem. I have been reading some of the previous posts and explanations and it sounds like a similar problem. I am able to get to the command window but I am uncertain how to transfer the information to a flash drive. The cursor is flashing after the following x:\windows\system32>
Where do I enter the command which I believe is (bcdedit /enum all > X:\bcd.txt) and are there any spaces?

Beginner
Messaggi: 0
Commenti: 6

I think i have d same problem like others, but dont really know how to get to the command promt. Can u help mark. I tried d one from the boot manager but didnt work. May be dere is a special key one can tap or what. Pls help.

Beginner
Messaggi: 0
Commenti: 6

When i use the cd it jst shows windows starting and blank for hours.maybe u can also help with this command prompt cos i find all way to get that but i cant. Pls help. I i dinnt find the command prompt in the boot manager

Forum Star
Messaggi: 19
Commenti: 2110

Scullynv:

It sounds like you are successfully entering the Windows Recovery Environment, so there is no need to list the contents of your BCD - it's apparently doing what it is supposed to. Your problem sounds like it's with Windows itself, and I don't think I can help you with that. This thread was about getting the Windows Recovery Environment working again if its entry in the BCD is invalid or missing.

Forum Star
Messaggi: 19
Commenti: 2110

oladeni:

The usual way to get to the "Repair Your Computer" selection is to press the F8 key right after the PC's POST (Power-on self-test) completes but before Windows starts to load. Timing is very critical. Here is a description: http://www.sevenforums.com/tutorials/666-advanced-boot-options.html

Beginner
Messaggi: 0
Commenti: 1

Hello Sir Mark could you help me with this one, my "Repair Your Computer" doesn't work, below is my Windows Boot manager... tnx in advance! =)

Windows Boot Manager
--------------------
identifier {bootmgr}
device locate=unknown
description Windows Boot Manager
locale en-us
inherit {globalsettings}
default {current}
resumeobject {f784ec5f-7daa-11e0-831f-b870f4530bab}
displayorder {current}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device locate=\Windows\system32\winload.exe
path \Windows\system32\winload.exe
description Windows 7
locale en-us
inherit {bootloadersettings}
recoverysequence {f784ec61-7daa-11e0-831f-b870f4530bab}
recoveryenabled Yes
osdevice locate=\Windows
systemroot \Windows
resumeobject {f784ec5f-7daa-11e0-831f-b870f4530bab}
nx OptIn

Windows Boot Loader
-------------------
identifier {f784ec61-7daa-11e0-831f-b870f4530bab}
device ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{f784ec62-7daa-11e0-831f-b870f4530bab}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{f784ec62-7daa-11e0-831f-b870f4530bab}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {f784ec5f-7daa-11e0-831f-b870f4530bab}
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

Windows Memory Tester
---------------------
identifier {memdiag}
device locate=\boot\memtest.exe
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 {f784ec62-7daa-11e0-831f-b870f4530bab}
description Ramdisk Options
ramdisksdidevice partition=\Device\HarddiskVolume1
ramdisksdipath \Recovery\WindowsRE\boot.sdi

Forum Star
Messaggi: 19
Commenti: 2110

Kevin:

You didn't describe your symptom. What does the PC do or fail to do?

The only thing that I see wrong in your BCD is a missing entry for finding the Windows Boot Manager at startup. The symptom would then be that the PC doesn't boot. Is this what you see?

Beginner
Messaggi: 0
Commenti: 6

Yes i tried that it shows all other command except repair your computer. And i tried all other command also but will jst go straight to the window logo and every thing is blank again. Like a bqckground. I even wait for hours it is still like that.

Beginner
Messaggi: 0
Commenti: 6

Yes i tried that it shows all other command except repair your computer. And i tried all other command also but will jst go straight to the window logo and every thing is blank again. Like a bqckground. I even wait for hours it is still like that.mark pls.

Forum Star
Messaggi: 19
Commenti: 2110

oladeni:

I can't think of a way to help you out if you cannot get to a command prompt from a Windows installation DVD or a repair CD. Sorry.

Beginner
Messaggi: 0
Commenti: 6

Danke

Beginner
Messaggi: 0
Commenti: 4

Hi Mark.

Im using Dell Inspiron..
When i enter F8 "repair your computer". I cant find Factory Image Restore.
The RECOVERY partition is still there. Could you help me out.

Allegato Dimensione
178290-113863.txt 4.37 KB
Forum Star
Messaggi: 19
Commenti: 2110

Norazam:

The reason is that the recovery sequence value is one that starts the standard Windows recovery environment on the C partition. You want the Dell recovery environment on partition 2. You can change the pointer by entering the following command in an elevated command prompt window:

bcdedit /set {current} recoverysequence {b4c0fcd4-bb53-11e2-b175-89de07113121}

That's all that you should need to do; however, there are a few things missing in the boot loader for the Dell recovery environment that can be fixed as follows:

bcdedit /set {b4c0fcd4-bb53-11e2-b175-89de07113121} inherit {bootloadersettings}
bcdedit /set {b4c0fcd4-bb53-11e2-b175-89de07113121} nx OptIn
bcdedit /set {b4c0fcd4-bb53-11e2-b175-89de07113121} locale en-US
bcdedit /set {b4c0fcd4-bb53-11e2-b175-89de07113121} description "Windows Recovery Environment"

Beginner
Messaggi: 0
Commenti: 1

Hello Mark,
I have the following problems:
-"Repair your computer" is missing (F8 key)
- recdisc.exe (CD / DVD recovery ) does not work
- C: \ Recovery directory is missing

OS is windows 7 pro 64 bit.
Thank you for any help you can provide.

Allegato Dimensione
178964-114001.txt 4.47 KB
178964-114004.png 25.13 KB
Beginner
Messaggi: 0
Commenti: 1

Dear Mark Wharton

I having a problem where I couldn't find the " Reset/restore to factory setting" at this screen...
If can, is there any other way to reset my laptop to factory setting??
My laptop is HP Pavilion dv 6
I don't have Recovery Disc nor Recovery Manager installed.
Thanks in advance.

Allegato Dimensione
181119-114142.jpg 1.13 MB
Beginner
Messaggi: 0
Commenti: 4

Great, problem SOLVED,
thanks Mark,

Beginner
Messaggi: 0
Commenti: 4

mark,

please help me.

i have problem to restore from recovery, dell windows 7 64bit

here i attch bcdoutput.txt

Allegato Dimensione
186458-114343.txt 4.82 KB
Forum Star
Messaggi: 19
Commenti: 2110

Norazam:

I see from your bcdoutput.txt file that you have two recovery environments set up in the BCD. One with ID {87ff3239-1335-11e4-a4eb-a28d900e1525} looks like it was set up by Windows 7 and the other with ID {b4c0fcd4-bb53-11e2-b175-89de07113121} looks like one set up by Dell. The second one is linked to correctly and should be working. I don't see why it isn't from the BCD listing unless the files are missing from your disk.

You could use Windows Disk Management to assign a temporary drive letter to the second partition on your disk, which should contain the Dell recovery environment. Search for the files Recovery\WindowsRE\Winre.wim and \Recovery\WindowsRE\boot.sdi to see if they are present on the disk. You will have to change the settings on Windows Explorer so that you can view both hidden files and protected operating system files to see them.

Beginner
Messaggi: 0
Commenti: 4

Dear Mark,

ignore my previous bcdoutput,

this is my latest bcdoutput, after restore from F8, "factory image"
but at my " Dell Datasafe Local BackUp" still missing

see attach

tq Mark

Allegato Dimensione
186596-114385.txt 4.82 KB
186596-114388.jpg 47.92 KB
Forum Star
Messaggi: 19
Commenti: 2110

Norazam:

OK; that makes more sense. The variable "recoverysequence" is wrong and can be corrected as follows. Enter the following command into an elevated command prompt window:

bcdedit /set {current} recoverysequence {b4c0fcd4-bb53-11e2-b175-89de07113121}

Beginner
Messaggi: 0
Commenti: 2

"HELP" cry to Stephane Maurice from France!!!

Hello Mark,
I recently lost all the partitions on the hard drive of my Toshiba. I managed to rewrite them and my windows 7 64 bits works fine but F8 boot option not working.
I looked at this forum and I start repairing my bcd but I'm afraid to make a mistake.
So can you help me to clean my bcd, the bcd01.txt is before beginning repairing and the bcd02.txt is my current BCD.

Thank you very much

Allegato Dimensione
188294-114511.txt 4.25 KB
188294-114514.txt 5.29 KB
Forum Star
Messaggi: 19
Commenti: 2110

Stephane:

Your problem with F8 not working is the same issue as reply #647, above. To fix this issue in your current BCD (bcd02.txt) enter the following command in an elevated command prompt window:

bcdedit /set {current} recoverysequence {b785a228-412b-11df-ad69-00266c464d6e}

Test this change to be sure that it's working. If it is, and if you want to remove unneeded items from your BCD, then enter the following commands:

bddedit /delete {b785a225-412b-11df-ad69-00266c464d6e}
bddedit /delete {b785a226-412b-11df-ad69-00266c464d6e}
bddedit /set {b785a228-412b-11df-ad69-00266c464d6e} locale fr-FR
bddedit /set {b785a228-412b-11df-ad69-00266c464d6e} description "Windows Recovery Environment"
bddedit /set {current} description "Windows 7 Home Premium"
bcdedit /set {73f2f486-1ca1-11e4-8e2d-806e6f6e6963} description "Windows Resume Application"

The last 3 commands just change the description that appears on the boot menu, so you can change the text within quotes, like "Windows 7 Home Premium" to whatever description you prefer. Type them in your native language if you want.

Beginner
Messaggi: 0
Commenti: 2

Mark

Thanks a lot, everything works fine, it's all right.
You are the only help I found on internet for this problem.

Merci.