Direkt zum Inhalt

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

Thread needs solution
Sai
Forum Member
Beiträge: 0
Kommentare: 52

Mark:

There are no BSOD's on startup, choosing disable auto restart has the same effect of just immediately booting into the recovery environment, no changes have been made to the BIOS so it's nothing to do with ATA vs AHCI..

 

Perhaps there is a drive letter change after the update? It's a real head scratcher...

Beginner
Beiträge: 0
Kommentare: 9

Just want to add something I just detected with my computer that if the BIOS have Secure Boot enabled this can prevent the computer to boot if the bootsector have been altered by whatever the reason good or bad but it won´t anything to why but just the "no bootable device".

Happened to me and over a week of frustration down the drain.

Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

Sometimes the BSOD screen flashes by so quickly that it isn't noticed. What made me suspicious is your comment that this started after a Windows Update. If the update changed one of the drivers required to boot (disk, video, etc.) and the new driver isn't compatible with your hardware for some reason, then the machine won't boot normally and will fail over to the recovery environment.

Is it possible to get it to boot into Safe Mode?

Harry:

Sai's BCD shows that his machine is MBR, not UEFI, so Secure Boot isn't available.

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Yeah sorry Mark, as I stated it doesn't matter how I try to boot, it goes immediately to the recovery environment. It never even attempts to boot normally, not in any mode safe or otherwise. I have even tried to boot directly to the drive MBR using hiren's boot CD and it still instantly begins loading the PE recovery with the white loading bar.

Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

Could you try this - post the BCD contents but this time add the /v switch to the command:

bcdedit /enum all /v

 

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Sure! I'll get right on it. BRB

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Here you are, thanks for looking further in to the problem.

Anhang Größe
358856-129190.txt 4.06 KB
Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

Thanks for posting the expanded listing. I wanted to see exactly which {identifier} was listed with each part of the BCD. I think I may have found the problem with the Main Boot Manager entry:

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {default}
resumeobject            {e32882d1-3b5b-11e3-b922-c81f661f516d}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Here the first entry in the boot manager menu is {default} . {Default} is a friendly name for the default operating system, which in your case should be Windows 7. But from your expanded listing:

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=C:
description             Windows Boot Manager
locale                  en-us
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {e32882d2-3b5b-11e3-b922-c81f661f516d}
resumeobject            {e32882d1-3b5b-11e3-b922-c81f661f516d}
displayorder            {e32882d2-3b5b-11e3-b922-c81f661f516d}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 30

The ID {e32882d2-3b5b-11e3-b922-c81f661f516d} translates to the loader for WinRE instead of to the loader for Windows 7. These two IDs should be {e32882d3-3b5b-11e3-b922-c81f661f516d}.

To fix, try this:

bcdedit /set {bootmgr} default {e32882d3-3b5b-11e3-b922-c81f661f516d}
bcdedit /set {bootmgr} displayorder {e32882d3-3b5b-11e3-b922-c81f661f516d}

The ID used in the above commands is the one for the Windows 7 loader.

If that doesn't work then I'm out of ideas since I can't see anything else wrong with the BCD. To undo the previous changes:

bcdedit /set {bootmgr} default {e32882d2-3b5b-11e3-b922-c81f661f516d}
bcdedit /set {bootmgr} displayorder {e32882d2-3b5b-11e3-b922-c81f661f516d}

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Hi Mark. So in a roundabout fashion this got me booted to the desktop, at first when I entered the commands and rebooted it did the same old thing of booting directly into recovery, however on startup repair it found the Windows installation this time and then offered to repair it. I figured if it didn't work I could always restore the BCD.backup.0002 it was going to create. Well it gave me 2 options to select from, "ramdisk options" and "Windows 7 Home Premium Edition (Recovered)". I chose W7 and it gave me a 0xc000009e error pertaining to a corrupt rdyboost.sys file in system32\drivers. I booted back into the recovery, grabbed a clean copy from another W7 Home Premium machine and copied it over, it now boots perfectly albeit with a screwy boot selection menu. Thought I'd give you the info and give you copies of the new bcd outputs. Hopefully I can clean up the boot options so the F8 Keypress is back to normal and the boot options menu goes away.

Thanks again for all your help, you are an invaluable resource and I appreciate your assistance.

 

Sai.

Anhang Größe
359148-129313.txt 4.46 KB
359148-129316.txt 5.13 KB
359148-129319.jpg 104.82 KB
Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

My apologies  - I messed up the prior post. I interchanged the IDs of the Win7 and WinRE boot loaders. Your BCD was correct before. The problem appears to have been the corrupt rdyboost.sys file.

Do you have a backup copy of the BCD before entering the commands in reply #858 and before running startup repair? If so, can you restore it?

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Yes, I have a backup but if I restore it to before the commands you provided it will then just boot straight into the recovery environment as it was before correct?

 

Forum Star
Beiträge: 19
Kommentare: 2110

No, it shouldn't. The failover to the recovery environment was caused by the corrupted Readyboost driver.

Save a copy of your current BCD, restore the older copy and I think it should work.

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Duly noted. I'll let you know if I have any further issues. Cheers!

Sai
Forum Member
Beiträge: 0
Kommentare: 52

So at this point none of the backup BCD's worked, the computer failed to boot when they were chosen.
I restored the latest BCD and it booted again but it still has the option to choose "ramdisk options" and "Windows 7 Home Premium Edition (Recovered)". The F8 button yields no results, including the options to choose safe mode, + networking, etc...

 

Everything should be the same as in post  #859  but I will get new bcd outputs if you need them. Thanks in advance!

Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

Now I see something that I missed earlier. The first entry in the BCD for "Windows Boot Manager" is missing a path statement to the location of the boot manager. Can you try the following? Go back to the BCD before you ran Automatic Repair; the one that I refer to in reply # 860. Restore this BCD then add the path statement to it:

bcdedit /set {bootmgr} path \bootmgr

See if that works. If it does, this is the easy way out. The BCD that currently works for you has so many problems that it would take dozens of commands to fix it.

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Strangely enough, none of the BCD's I had backed up liked the entries you mentioned, the original BCD just complained about winload.exe and startup repair wanted to fix it. I made a copy of the old BCD and entered your commands. It did nothing. So I let startup repair do what it wanted just to see what might happen. Well... Now it boots to windows normally and F8 works, it also gets to the original recovery environment with the dell recovery options. I removed (Recovered) from the BCD boot entry "Windows 7 Home Premium (Recovered)" and called it good. Thanks for the suggestions and the bump in the right direction.

Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

While I'm glad that you got things working, I'm at a loss to understand what was wrong with some of your posted BCDs. I must have missed something else.

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Be that as it may, it all worked out in the end. Thanks for your dilligence as usual, considering your track record and the fact that you do this just to help people I'd say not to feel bad.

Cheers mate!

Beginner
Beiträge: 0
Kommentare: 5

Hi Mark,

I have a laptop with windows 7 its french version of windows 7, what happen windows 10 start automatically the installation then the laptop run out of battery and it turned off.

after that the windows 7 start going into loop, here is my bcdedit.

Gestionnaire de d‚marrage Windows
---------------------------------
identificateur          {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
locale                  fr-FR
default                 {default}
displayorder            {default}
timeout                 30

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {default}
device                  partition=D:
path                    \Windows\system32\winload.exe
description             
locale                  fr-FR
osdevice                partition=D:
systemroot              \Windows
resumeobject            {656a62c9-2462-11e6-b2e7-806e6f6e6963}

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {db56fc44-2483-11e6-a12c-dff7669e3d84}
device                  ramdisk=[D:]\Recovery\7ae1a78e-f772-11e4-89e8-b29af97e8c23\Winre.wim,{db56fc45-2483-11e6-a12c-dff7669e3d84}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (r‚cup‚r‚) 
locale                  
osdevice                ramdisk=[D:]\Recovery\7ae1a78e-f772-11e4-89e8-b29af97e8c23\Winre.wim,{db56fc45-2483-11e6-a12c-dff7669e3d84}
systemroot              \windows
winpe                   Yes

Reprendre … partir de la mise en veille prolong‚e
-------------------------------------------------
identificateur          {656a62c9-2462-11e6-b2e7-806e6f6e6963}
device                  partition=D:
path                    \Windows\system32\winresume.exe
description             
locale                  fr-FR
inherit                 {resumeloadersettings}
filedevice              partition=D:
filepath                \hiberfil.sys
debugoptionenabled      No

Testeur de m‚moire Windows
--------------------------
identificateur          {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  fr-FR

Options de p‚riph‚rique
-----------------------
identificateur          {db56fc45-2483-11e6-a12c-dff7669e3d84}
ramdisksdidevice        partition=D:
ramdisksdipath          \Recovery\7ae1a78e-f772-11e4-89e8-b29af97e8c23\boot.sdi
 

thanks.

Forum Star
Beiträge: 19
Kommentare: 2110

Robert:

I don't see anything wrong with your BCD. It has all of the entries needed to boot Windows 7, so if Windows 7 won't start then the Windows 10 installer must have partially replaced some of the files before the laptop shut down due to low battery.

Perhaps you can download the ISO version of the Windows 10 installer and start the upgrade process again.

Beginner
Beiträge: 0
Kommentare: 5

Hi all,

Mark: What you have been doing on this thread for the past few years is fantastic. I am not done reading it yet but so far I find it is the best resource for understanding (if not solving!) BCDs related issues.

I also have some issues booting to the recovery partition on my Asus 1225B. Maybe once I have read the whole thread I will be knowledgeable enough to identify some solution track that could work for me but I figured I would eventually ask for advice about that hypothetical solution of mine and also that my case could maybe help others. Hence this post!

Some context:

I was trying to set up a dual boot (LMDE2 Betsy with Windows 7 Home Premium 64).

The netbook was originally preinstalled with Win 7 HP 64 on C:\ and there was a recovery partition wich worked fine. While preparing the dual boot I resized (shrinked) the C:\ partition (no problem, I could boot again from C:\) and moved the recovery partition next to C:\ (actually I copied the recovery partition to a new one - and to other places for backup). I was able to restore C:\'s content to factory default by booting on the copied recovery partition.

After that though I was unable to boot to recovery again, either through F8/F9 at ² or by making this partition the active one. In trying to repair this I have probably made some unnecessary changes here and there. The first error I got when trying to boot on the recovery partition again was BCD related (Windows boot manager: failed while attempting to read boot configuration data file:\Boot\Bcd).

Among other things I tried, I got hands on a Win 7 HP 64 iso in order to use the startup repair and the command line and ended up installing it (a bit out of despair). It sort of works but not as well as when I had the Asus image installed. Some drivers seem not ok (Wireless for instance). I could probably fix it from there but if possible I would appreciate being able to use the recovery partition again since it makes quite a good work when it does work!

From what I have read so far I understand that my BCD on C:\Boot\BCD doesn't map properly to the recovery resources on D:\ (the copy of the recovery partition).

In D:\ I have:

* EN1225B_WW_W71HP_64H_01.042.wim  EN1225B_WW_W71HP_64H_01.04.wim EN1225B_WW_W71HP_64H_01.043.wim

(it looks like what the C:\ factory image would look like) and it is in D:\recovery\windowsre\) I have to check again but there may be a BCD inside de recovery image if it helps.

* boot.wim  btup.wim winre.wim
in D:\SOURCES\

* BOOT.SDI BCD
in D:\BOOT\

Also I assume there also was a BCD on the recovery partition which now no longer maps properly to anything since (1) it has moved to a different place on the disk and (2) the C:\  partition has been modified as well. If useful I add the results of bcdedit /store C:\BOOT\BCD /enum all and bcdedit /store D:\BOOT\BCD /enum all at the end of this message. I also have some backups of the D:\'s BCD since the current one may have been modified subsequently to my attempts at fixing it.

Well, there is a lot of confusion on my side obviously - I hope this makes some sense though!

Thanks in advance to anyone taking a look a this and best of luck to everyone currently navigating this thread in search for a solution!

All the best,

Bastien

 

bcdedit /store C:\BOOT\BCD /enum all
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {bcd80461-2603-11e6-83ff-91e6638c1e74}
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}
recoveryenabled         No
osdevice                partition=C:
systemroot              \Windows
resumeobject            {bcd80461-2603-11e6-83ff-91e6638c1e74}
nx                      OptIn
 
Resume from Hibernate
---------------------
identifier              {bcd80461-2603-11e6-83ff-91e6638c1e74}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No
 
Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes
 
EMS Settings
------------
identifier              {emssettings}
bootems                 Yes
 
Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200
 
RAM Defects
-----------
identifier              {badmemory}
 
Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}
 
Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}
 
Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200
 
Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

 

bcdedit /store D:\BOOT\BCD /enum all
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  boot
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
resumeobject            {1f8184a2-14de-11df-9734-f08c6d8c50b0}
toolsdisplayorder       {memdiag}
timeout                 10
 
Windows Memory Tester
---------------------
identifier              {memdiag}
device                  boot
path                    \Boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes
 
EMS Settings
------------
identifier              {emssettings}
bootems                 Yes
 
Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200
 
RAM Defects
-----------
identifier              {badmemory}
 
Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}
 
Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}
 
Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200
 
Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}
 
Device options
--------------
identifier              {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description             Ramdisk Options
ramdisksdidevice        unknown
ramdisksdipath          \Recovery\1f8184a4-14de-11df-9734-f08c6d8c50b0\boot.sdi

 

Forum Star
Beiträge: 19
Kommentare: 2110

Bastien:

It looks like the BCD on the C: partition has recovery disabled, and there are no references to WinRE anywhere. So that makes sense from your description (you did a clean install of Windows 7 that was unaware of the factory recovery partition).

The BCD on the D: partition has one piece of information (Ramdisk Options) about WinRE, but it is missing the Recovery Boot Loader, which would contain the rest of the information needed to boot into the Recovery Environment.

You mentioned that you might have some backups of the BCD from the D: partition. Could you post one of those?

bcdedit /store D:\BOOT\BCD.bak /enum all

(Substitute the correct filename for the backup copy in the above command)

Beginner
Beiträge: 0
Kommentare: 5

Hi again,

EDIT

**Mark: thanks a lot for your reply and sorry our posts crossed - some news below - I will get back to you with the output of bkp_bcd though I am not sure it is pristine. There are other backups probably left there by some Startup Repair attemps or the likes (it is some sort of a BCD fair here right now).

Some progress but still some trouble ahead:

I have managed to boot on the recovery partiton (through F8 >> Repair your computer) after editing the bcd on C:\, editing mostly inspired bye the discussions on the first page.

Now I am stuck at the Asus recovery screen and I am not sure this falls whithin this thread's scope: Choosing the recovery option  (over 'exit' and 'langage settings') I am asked to choose whether I want the recovery to be made on a partition or on a full disk.

Either way I am prompted to connect an externel usb device (never had that) and that is where I am stuck. The strange thing is that at this point I am now told I am about to do a 'backup'  (Not my first pick, but better than nothing!).

I suspect this may be due to the recovery process 'not seeing' a possible target for the install (i.e. C:\ , the rest of the disk being currently used by Mint). And again I don't know of this is BCD-related (but why not?), I'll try a few things lile adding a device option entry for C:\ in D:\BOOT\BCD.

'The currently modified/added sections in C:\BOOT\BCD are as follow:

Windows Boot Loader
-------------------
identifier              {1f8184a4-14de-11df-9734-f08c6d8c50b0}
device                  ramdisk=[D:]\SOURCES\Winre.wim,{1f8184a5-14de-11df-9734-f08c6d8c50b0}
path                    \windows\system32\winload.exe
description             Asus Recovery Environment
osdevice                ramdisk=[D:]\SOURCES\Winre.wim,{1f8184a5-14de-11df-9734-f08c6d8c50b0}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {1f8184a4-14de-11df-9734-f08c6d8c50b0}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {bcd80461-2603-11e6-83ff-91e6638c1e74}
nx                      OptIn

Device options
--------------
identifier              {1f8184a5-14de-11df-9734-f08c6d8c50b0}
description             Ramdisk Options
ramdisksdidevice        partition=D:
ramdisksdipath          \BOOT\BOOT.sdi

All the best,

Bastien

 

 

Beginner
Beiträge: 0
Kommentare: 5

Mark,

Your help is very appreciated, I am really grateful. I came this far thanks to your very first replies in this thread :)

I have made some significant progress, but I believe I am not completely done at the BCD level:

Here is the output of bcdedit /store D:\BOOT\BDC.BKP. I do believe I made this one too late, possibly after I had tried the Startup Repair.

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

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 Home Premium
locale                  en-US
osdevice                partition=C:
systemroot              \Windows

Yes, this is unedited....

 

Fortunately some other backups were made (two and they are identical at glance).

They have very specific parameters so I am enclined to believe the reflect strongly the original file. . 

Windows Boot Manager
--------------------
identifier              {bootmgr}
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {default}
device                  ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
path                    \windows\system32\boot\winload.exe
description             Windows Setup
locale                  en-US
inherit                 {bootloadersettings}
osdevice                ramdisk=[boot]\sources\boot.wim,{7619dcc8-fafe-11d9-b411-000476eba25f}
systemroot              \windows
detecthal               Yes
winpe                   Yes
ems                     Yes

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  boot
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}

EMS Settings
------------
identifier              {emssettings}
bootems                 Yes

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
description             Hypervisor Settings
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Device options
--------------
identifier              {7619dcc8-fafe-11d9-b411-000476eba25f}
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi

 

I am not sure if I can roll back straight to this version, it doesn't seem to point in any fashion to my current C:\ as it is. Still, I can probably assume the structure is correct.

I have to sleep over it a little (it is 5 AM here) so I apologize if I am not able to reply quickly (but there is no rush on my side - and again I am already really grateful for the 'collateral teaching')

All the best,

Bastien

Beginner
Beiträge: 0
Kommentare: 5

OK, I was able to restore to factory default by transfering some references from the extra backup to C:\BOOT\BCD (mainly replacing winre.wim by boot.wim). Unfortunately this last version vas then erased through the recovery process (I was expecting to be asked to choose/confirm the target partition before anything - I even feared it would use the whole disk, erasing the recovery partition as well! - it didn't!).

On first reboot after the recovery procedure began I started to have a warning message about some device not being recognized, the ID looked a lot like the former UUID for C:\ under Mint and updating GRUB seemed to have solved this.

I am really close to being back to normal: I am back to factory default on C:\ and I know I can get the manufacturer's recovery tool running by doing what I just did.

Some remaining minor troubles I could probably try to solve, even though I am already quite happy (and help and advices if any is indeed greatly appreciated :) :

I think the original settings allowed to boot directly from the recovery partition which I find useful. I believe what I did today was booting on C:\ and only then accessing the resources on D:\. Maybe I just need a proper "Device option" entry in its BCD or take example for the Boot Manager section from C:\. Well something around that.

"F8 >> Repair your computer" now maps to the recovery environment hosted in C:\. I would rather have it pointing toward the RE in D:\ but I think I now know how to do that. Maybe I can even have a menu entry for each...not a big deal BUT this probably implies that upon each factory reset I will have to edit the BCD so that its recovery parameters point correctly to D:\ and its resources. If that is what I expect the only solution I see would be to make sure the Asus RE creates the correct C:\BOOT\BCD upon recovery. But that's probably just a fancy way to make the partition's images useless...

D:\BOOT\BCD seems unchanged

C:\BOOT\BCD looks like this now:

 
Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
description             Windows Boot Manager
locale                  fr-FR
inherit                 {globalsettings}
default                 {default}
resumeobject            {6ceb4f8c-2900-11e6-98a6-d2fc9b2941f1}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30
 
Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \windows\system32\winload.exe
description             Windows 7
locale                  fr-FR
inherit                 {bootloadersettings}
recoverysequence        {current}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \windows
resumeobject            {6ceb4f8c-2900-11e6-98a6-d2fc9b2941f1}
nx                      OptIn
 
Windows Boot Loader
-------------------
identifier              {current}
device                  ramdisk=[C:]\Recovery\6ceb4f8e-2900-11e6-98a6-d2fc9b2941f1\Winre.wim,{6ceb4f8f-2900-11e6-98a6-d2fc9b2941f1}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\6ceb4f8e-2900-11e6-98a6-d2fc9b2941f1\Winre.wim,{6ceb4f8f-2900-11e6-98a6-d2fc9b2941f1}
systemroot              \windows
nx                      OptIn
winpe                   Yes
 
Resume from Hibernate
---------------------
identifier              {6ceb4f8c-2900-11e6-98a6-d2fc9b2941f1}
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
 
Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  fr-FR
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              {6ceb4f8f-2900-11e6-98a6-d2fc9b2941f1}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\6ceb4f8e-2900-11e6-98a6-d2fc9b2941f1\boot.sdi

 

All the best,

Bastien

 

Forum Star
Beiträge: 19
Kommentare: 2110

Bastien:

My apologies for not getting back to you sooner - it has been a very busy time at work.

I see that you have things mostly sorted out. If you prefer booting from and having F8 map to the WinRE version on the recovery partition, then you should be able to do that. In the BCD that is located on the recovery partition, make sure that the Windows Boot Manager section references the correct partition. Check the device and osdevice path references in the Windows Boot Loader section for the recovery environment and in the Ramdisk Options, then make the recovery partition active. Your PC should then boot from the recovery partition, use that BCD, and map F8 to your desired recovery environment.

Personally, I prefer a system set up like that with a separate Boot partition that contains the Boot Manager, BCD, and the Recovery Environment. So I have my system set up with all of that stuff on the Boot partition (the so-called "System Reserved Partition"). If you put the boot files and the Recovery Environment on the main Windows partition, and if that partition ever develops any file system errors then you can't boot the PC or get to the Recovery Environment to fix them.

I'm on Windows 10 now and every time Microsoft issues a major update they put WinRE back on the Windows partition. Then I have to move it back to the Boot partition and fix the BCD. It's happened twice now. For the life of me I can't figure out why they would want the Recovery Environment to be located on the main C: partition. From a reliability standpoint, that does not make any sense.

Beginner
Beiträge: 0
Kommentare: 5

Hi Mark,

i have a windows wich suddenly when booting it goes to a black screen with a cursor (right before the desktop to appear), i can boot from safe mode and i did system restore to a 2 weeks from today still same black screen.

here is my bcdedit, do you think its something related?

Gestionnaire de d‚marrage Windows
---------------------------------
identificateur          {bootmgr}
device                  partition=\Device\HarddiskVolume2
description             Windows Boot Manager
locale                  fr-FR
inherit                 {globalsettings}
default                 {current}
resumeobject            {d1e16c87-b18b-11e0-a345-ea81a7bb0da5}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  fr-FR
inherit                 {bootloadersettings}
recoverysequence        {d1e16c89-b18b-11e0-a345-ea81a7bb0da5}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {d1e16c87-b18b-11e0-a345-ea81a7bb0da5}
nx                      OptIn

Chargeur de d‚marrage Windows
-----------------------------
identificateur          {d1e16c89-b18b-11e0-a345-ea81a7bb0da5}
device                  ramdisk=[C:]\Recovery\d1e16c89-b18b-11e0-a345-ea81a7bb0da5\Winre.wim,{d1e16c8a-b18b-11e0-a345-ea81a7bb0da5}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\d1e16c89-b18b-11e0-a345-ea81a7bb0da5\Winre.wim,{d1e16c8a-b18b-11e0-a345-ea81a7bb0da5}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Reprendre … partir de la mise en veille prolong‚e
-------------------------------------------------
identificateur          {d1e16c87-b18b-11e0-a345-ea81a7bb0da5}
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\HarddiskVolume2
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          {d1e16c8a-b18b-11e0-a345-ea81a7bb0da5}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\d1e16c89-b18b-11e0-a345-ea81a7bb0da5\boot.sdi

Forum Star
Beiträge: 19
Kommentare: 2110

Robert:

No, if you can start booting Windows then the BCD has done its job correctly. From this point on if there is a problem then the problem is with Windows itself. Most likely this is a driver issue if you are able to boot in safe mode.

From your symptom, it is likely not the disk driver since you are able to almost get to the desktop. I would be suspicious of the video driver. Try updating it from safe mode.

 

Beginner
Beiträge: 0
Kommentare: 5

Hi Mark,

No need for an apology, we all have commitments IRL, and it is already quite amazing what you volunteering has brought to this thread :D

I haven't found the time to do those final tweaks yet but I am confident since it is not very different from what I have already done. I would like to make a system image before tweaking any further and I need to find some space on an external HDD first. I'll post my final BCDs after all that in case it is useful for someone (there are probably similar cases here already but sometimes a slightly different wording is also helpful).

I like the idea of having a separate boot partition (thanks!) though that means I would have to repartition/resize and reinstall which I am not going to do before I have backed up the fresh install (because getting this install up to date took some 24 hours...).

I have been away from Windows for quite a while so I am assuming a lot about what is and what people (MS, users) want but regarding the way Windows deals with WinRE on major updates, I'll make some guesses (in any case it doesn't really suit me - but you can't please everyone): They probably assumed most people in most cases will want to restore their system to a previous state (by default stored on the Windows partition) but not necessarily to factory default (stored on the hidden recovery partition). Aslo I never had to transition to a newer Windows version on the same PC but some users might find troubling that after having, say Windows 10 installed, the winRE would be the Windows 7 one the hidden partition... Basically you are prevented from going (too far) back...

Mark I really mean to thank you for the time spent on this thread and more specifically on my BCD issues. I can't return the favor directly (I wish I could) so for now it is just a bunch of 'thanks' and the promise I'll do what you do here whenever I am in position to provide assistance. You have been really inspiring!

Again I'll try post my results (maybe as an edit to this post, for continuity's sake), once I am fully through, if it may help.

All the best,

Bastien

 

 

 

 

 

 

Beginner
Beiträge: 0
Kommentare: 7

Hello Mark! can you please help me out?

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

C:\Windows\system32>bcdedit / enum all
An unknown command was specified.
Run "bcdedit /?" for command line assistance.

C:\Windows\system32>bcdedit/enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {a3f6fce8-60ad-11e4-8bcd-b8fcf069790f}
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        {a3f6fcea-60ad-11e4-8bcd-b8fcf069790f}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {a3f6fce8-60ad-11e4-8bcd-b8fcf069790f}
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {a3f6fcea-60ad-11e4-8bcd-b8fcf069790f}
device                  ramdisk=[C:]\Recovery\a3f6fcea-60ad-11e4-8bcd-b8fcf06979
0f\Winre.wim,{a3f6fceb-60ad-11e4-8bcd-b8fcf069790f}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\a3f6fcea-60ad-11e4-8bcd-b8fcf06979
0f\Winre.wim,{a3f6fceb-60ad-11e4-8bcd-b8fcf069790f}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {a3f6fce8-60ad-11e4-8bcd-b8fcf069790f}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
pae                     Yes
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              {a3f6fceb-60ad-11e4-8bcd-b8fcf069790f}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\a3f6fcea-60ad-11e4-8bcd-b8fcf069790f\boot.sdi

C:\Windows\system32>

Forum Star
Beiträge: 19
Kommentare: 2110

juku:

What is the nature of your problem? Describe the symptoms, please.

 

Beginner
Beiträge: 0
Kommentare: 7

Hi Mark. after pressing F8 and then "repair your computer" i get the  "launch startup repair or start windows normally" screen every time since i installed Dell Backup and Recovery Manager    .....correlation does not necessarily imply causation though

Thanks!

Beginner
Beiträge: 0
Kommentare: 3

Hello Mark,

your post is already pretty old, but yet I try my luck, since I'm so desperate to find help for my problem.

There was NO "recovery" file in C:/ but well in C:Windows/system32/ and in C:Windows/SysWOW64

Anyway I've just created ( an empty ) one in C:/ ... ???

Here the results of bcdetid / enumall :

Thanks in advance for your kind support

* * *

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

C:\windows\system32>bcdedit /enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {a3e96dad-2697-11e6-91cc-8406e9601dc3}
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        {a3e96daf-2697-11e6-91cc-8406e9601dc3}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \windows
resumeobject            {a3e96dad-2697-11e6-91cc-8406e9601dc3}
nx                      OptIn
bootlog                 No

Resume from Hibernate
---------------------
identifier              {a3e96dad-2697-11e6-91cc-8406e9601dc3}
device                  partition=C:
path                    \windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

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

EMS Settings
------------
identifier              {emssettings}
bootems                 Yes

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

C:\windows\system32>

 

Forum Star
Beiträge: 19
Kommentare: 2110

juku:

Still don't quite understand. Are you saying that the Recovery Environment never loads after you press F8 and then choose "Repair Your Computer"?

The BCD looks like it correctly links to the recovery environment. But are these files present on your disk?

C:\Recovery\a3f6fcea-60ad-11e4-8bcd-b8fcf069790f\Winre.wim

C:\Recovery\a3f6fcea-60ad-11e4-8bcd-b8fcf069790f\boot.sdi

To see them you may have to view them from a recovery CD if Windows won't let you view them.

Forum Star
Beiträge: 19
Kommentare: 2110

Iklees:

What is the nature of the problem that you're trying to fix? Is it that the Recovery Environment won't start, or is there something else wrong with your computer?

Beginner
Beiträge: 0
Kommentare: 3

Hi Mark, thanks for your answer.

Well, it's a long story, but I'll try to be not too long myself ...

Any effort I'm asking to my laptop is too much... a few internet windows open ? is too much... the searching of virus, spyware etc, is too much... the conversion of a video format to another, is too much... sometimes, even nothing is too much... the laptop is first freezing for 10 to 30 seconds long, then it's simply shuting down by itself... So when I put it on again, I read the choice : " start normally " or " launch start repair "... so, when I click on " launch start repair " the screen vanished for a few seconds before coming back... until I'm clicking on " start normally "... No choice... With the F8 option, I'm also able to read " repair my computer " but when I'm electing that option, ... Windows just start normally... I thought ( and I still believe ) that there was/still is a very strong & bad virus deep inside the machine,... so a few days ago I decided to use the intern Toshiba's recovery program to format ( erase ) the whole C: disk... ( 23 hours long, in vain ???... ) After the formatting, I've been able to reinstall the original Win7 Home Premium still via the same recovery program ( and that was really not easy too, but it's another story ...  )... Despite all my efforts, the symptoms are still there... I am not able to get/install the SP1 Service Pack, nor via Windows Update nor via any other way... When I am launching any original Microsoft CD/DVD ( by "original", I mean : downloaded on their site ) in order to upgrade to Win7 SP1 or Windows 10, it never works until the end ... Saying it's corrupted or there is something missing, or there is a device not working... All my drivers are up to date ( Drivers Booster says )... I have Malwarebytes and Avast running ... This laptop always run on AC, because there is no battery anymore... but there was no problem at all with this. "before"... All this misery came after(from ?) a Microsoft upgrade from Win7 Home Premium to Windows 10, kindly suggested by Microsoft. An upgrade that was first okay. But, after an innocent Windows Update made a few weeks later, all the problems came, not only on this Toshiba, but also on a Packard Bell Easynote TK85, exactly for the same reasons: Upgrade to Win10, then the same Windows Update... That PBell is now sleeping on my desk, ... I was forced to take it's battery out, because if I don't, the PBell is non-stop switching on, switching off, switching on, switching off, by itself ... I don't know what to think or do anymore...

Beginner
Beiträge: 0
Kommentare: 7

Yes, the recovery environment never loads. Before it worked just fine though. I can't open C:\Recovery. by recovery cd do you mean the windows 7 factory image disc? i dont have it and my computer will not let me create one because it says i have allready done it and now it won't let me do it.

 

Thankyou Mark!

Forum Star
Beiträge: 19
Kommentare: 2110

Iklees:

Your symptom sounds like what happens when you have a bad hard disk. The computer slows down because it continually has to try and retry any time it reads from the disk. You should first check your disk for bad sectors:

chkdsk x: /R

where x: is the letter of the disk partition that you want to check (C: or D: or whatever). If this program finds several bad sectors then you should probably just get a new disk. Laptop hard disks are more likely to develop bad sectors because of shock and vibration.

Forum Star
Beiträge: 19
Kommentare: 2110

juku:

For Windows 7, type "create a system repair disk" in the START/SEARCH box. One of these can be made on any Windows 7 PC. If you need to, borrow one from a friend. Or borrow a Windows 7 installation DVD and boot from it to enter the recovery environment. Use one of these to confirm that you have the files mentioned in reply #884 above.

Beginner
Beiträge: 0
Kommentare: 7

i made the disc and i booted my computer with it. but i couldn't figure out how to check if i have the files :P

Forum Star
Beiträge: 19
Kommentare: 2110

juku:

You have to use a command prompt window to search for the files. Drive letters may be different in the recovery environment, so your Windows partition may not be called C: in the recovery environment. Do the following:

C:
DIR
D:
DIR

etc, until you locate your Windows partition. Then look for the Recovery folder and the files.

Beginner
Beiträge: 0
Kommentare: 7

I found   X:\sources\recovery> and there were two files in it: RecEnv.exe and StartRep.exe. I couldn't find Winre.wim and boot.sdi

Beginner
Beiträge: 0
Kommentare: 3

LO Mark,

I've made the chkdsk c: /R as you suggested to do but there was nothing particulary wrong. No bad sectors at all.

Symptoms are still the same

Crystaldisk info already told me that the hard disk was ok.

Thank you anyway, and if you have another idea, please share it with me ( with us, I'm sure ... )

Forum Star
Beiträge: 19
Kommentare: 2110

Iklees:

The X: disk is the RAMDISK created when you boot to the recovery environment. You need to look on your main Windows partition for the Recovery folder. Remember that it is a hidden folder, so to see the contents from a command prompt you need to add the /a switch to the dir command:

If the Windows partition is C: when booted to the recovery environment, then the commands would be:

C:
cd Recovery
dir /a

Beginner
Beiträge: 0
Kommentare: 7

Thanks Mark! i just checked and both files are there.

Forum Star
Beiträge: 19
Kommentare: 2110

juku:

I've looked carefully at your BCD posted in reply #880 and cannot see anything wrong with it. If the recovery environment won't start, and the files are present on your disk, then there is something else wrong. Sorry, but I don't know what else to suggest.

Beginner
Beiträge: 0
Kommentare: 7

...and now the recovery environment is working again. i tried it like 15 times before and it didn't work. strange. Thanks Mark for your time. Atleast now i know how to navigate DOS better :) 

Beginner
Beiträge: 0
Kommentare: 3

Hello Mark Sir!

can you please help me out?

thanks

 

 

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=J:
description             Windows Boot Manager
locale                  en-us
inherit                 {globalsettings}
default                 {current}
resumeobject            {7a82d5b2-7634-11e1-8e2d-bce9bfac6809}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {current}
device                  locate=\Windows\{26b0a390-e1c2-4ce2-8352-7ec1b31b2db6}
path                    \windows\system32\winload.exe
description             Microsoft Windows
locale                  en-us
inherit                 {bootloadersettings}
custom:17000077         352321653
osdevice                locate=\Windows\{26b0a390-e1c2-4ce2-8352-7ec1b31b2db6}
systemroot              \windows
custom:22000005         \Windows\{26b0a390-e1c2-4ce2-8352-7ec1b31b2db6}
resumeobject            {7a82d5b2-7634-11e1-8e2d-bce9bfac6809}
nx                      OptIn
custom:250000c2         1
detecthal               Yes

Resume from Hibernate
---------------------
identifier              {7a82d5b2-7634-11e1-8e2d-bce9bfac6809}
device                  locate=unknown
path                    \windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-us
inherit                 {resumeloadersettings}
custom:17000077         352321653
filedevice              partition=C:
filepath                \hiberfil.sys
custom:25000008         1
pae                     Yes
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=J:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-us
inherit                 {globalsettings}
badmemoryaccess         Yes
custom:17000077         352321653

EMS Settings
------------
identifier              {emssettings}
bootems                 No

Debugger Settings
-----------------
identifier              {dbgsettings}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {badmemory}

Global Settings
---------------
identifier              {globalsettings}
inherit                 {dbgsettings}
                        {emssettings}
                        {badmemory}

Boot Loader Settings
--------------------
identifier              {bootloadersettings}
inherit                 {globalsettings}
                        {hypervisorsettings}

Hypervisor Settings
-------------------
identifier              {hypervisorsettings}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {resumeloadersettings}
inherit                 {globalsettings}

Device options
--------------
identifier              {600676fd-1f26-44be-8a28-e0a15855f258}
ramdisksdidevice        partition=\Device\HarddiskVolume1
ramdisksdipath          \Recovery\boot.sdi

Anhang Größe
369819-130846.png 90.5 KB
369819-130849.png 115.34 KB
369819-130852.png 81.33 KB
369819-130855.png 39.94 KB
369819-130858.png 117.69 KB
Forum Star
Beiträge: 19
Kommentare: 2110

Naren:

Please describe the issue or problem that you are experiencing.

Beginner
Beiträge: 0
Kommentare: 3

Namaste @Great Mark respected Sir

thanku for reply :)

i can't write in english, i can only read.

My problems are :

1-  F8 Advavanced boot option not working Repair your computer. i cant use racovery option :(

2- when i m using hibernate after some time turn of windows

 

sorry for my bad english

 

thanks