Direkt zum Inhalt

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

Thread needs solution
Beginner
Beiträge: 0
Kommentare: 12

HI Mark

So after entering these commands one by one and listing BCD contents just as you said. I have got the following (but the information in first post #794 is after I made changes to BCD). I created a backup of the original BCD file. Do you think I need to use that Backup file to restore the correct information? I have attached here that backup file. File name was bcd.old but had to change it to bcd_old.jpg to upload here. I dont know how to view the contents of this file.

 

C:\Windows\system32>bcdedit/enum all

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=S:
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
extendedinput           Yes
default                 {current}
resumeobject            {ac4edc4a-b208-11e5-982b-806e6f6e6963}
displayorder            {current}
timeout                 30
customactions           0x10000ba000001
                        0x54000001

Windows Boot Loader
-------------------
identifier              {572bcd55-ffa7-11d9-aae0-0007e994107d}
device                  ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
path                    \windows\system32\boot\winload.exe
description             WinPE
osdevice                ramdisk=[boot]\tvtos\winpe.wim,{ramdiskoptions}
systemroot              \windows
nx                      OptIn
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 Home Premium
locale                  en-US
recoverysequence        {572bcd55-ffa7-11d9-aae0-0007e994107d}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {ac4edc4a-b208-11e5-982b-806e6f6e6963}

Resume from Hibernate
---------------------
identifier              {ac4edc4a-b208-11e5-982b-806e6f6e6963}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows 7 Home Premium
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=S:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US

Setup Ramdisk Options
---------------------
identifier              {ramdiskoptions}
description             Ramdisk options
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi

C:\Windows\system32>

Anhang Größe
322153-125047.jpg 32 KB
Beginner
Beiträge: 0
Kommentare: 12

HI Mark

I also found a bcdinfo.txt file in Q:\FactoryRecovery folder. This folder has 6 files - cdrivebackup.wim, sdrivebackup.wim, populateini.log, bcdinfo.txt, flush.dat, and RECOVERY.INI 

Dont know if this is helpful to intiate recovery process. 

Windows Boot Manager
--------------------
identifier              {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device                  partition=S:
description             Windows Boot Manager
locale                  en-us
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default                 {be8120d0-f175-11e1-9c19-3c970e24ef08}
resumeobject            {be8120cf-f175-11e1-9c19-3c970e24ef08}
displayorder            {be8120d0-f175-11e1-9c19-3c970e24ef08}
                        {5294fec2-9af8-11dd-9fa0-f9e85e02c230}
toolsdisplayorder       {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout                 0

Windows Boot Loader
-------------------
identifier              {5294fec2-9af8-11dd-9fa0-f9e85e02c230}
device                  ramdisk=[C:]\SWWORK\AUDITPE.WIM,{ae5534e0-a924-466c-b836-758539a3ee3a}
path                    \windows\system32\boot\winload.exe
description             AuditPE
osdevice                ramdisk=[C:]\SWWORK\AUDITPE.WIM,{ae5534e0-a924-466c-b836-758539a3ee3a}
systemroot              \windows
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {be8120d0-f175-11e1-9c19-3c970e24ef08}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-us
inherit                 {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
osdevice                partition=C:
systemroot              \Windows
resumeobject            {be8120cf-f175-11e1-9c19-3c970e24ef08}
nx                      OptIn

Resume from Hibernate
---------------------
identifier              {be8120cf-f175-11e1-9c19-3c970e24ef08}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-us
inherit                 {1afa9c49-16ab-4a5c-901b-212802da9460}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {b2721d73-1db4-4c62-bf78-c548a880142d}
device                  partition=S:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-us
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
badmemoryaccess         Yes

EMS Settings
------------
identifier              {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
bootems                 Yes

Debugger Settings
-----------------
identifier              {4636856e-540f-4170-a130-a84776f4c654}
debugtype               Serial
debugport               1
baudrate                115200

RAM Defects
-----------
identifier              {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Global Settings
---------------
identifier              {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
inherit                 {4636856e-540f-4170-a130-a84776f4c654}
                        {0ce4991b-e6b3-4b16-b23c-5e0d9250e5d9}
                        {5189b25c-5558-4bf2-bca4-289b11bd29e2}

Boot Loader Settings
--------------------
identifier              {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
                        {7ff607e0-4395-11db-b0de-0800200c9a66}

Hypervisor Settings
-------------------
identifier              {7ff607e0-4395-11db-b0de-0800200c9a66}
hypervisordebugtype     Serial
hypervisordebugport     1
hypervisorbaudrate      115200

Resume Loader Settings
----------------------
identifier              {1afa9c49-16ab-4a5c-901b-212802da9460}
inherit                 {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}

Setup Ramdisk Options
---------------------
identifier              {ae5534e0-a924-466c-b836-758539a3ee3a}
description             Ramdisk options
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi
 

Beginner
Beiträge: 0
Kommentare: 12

Hi Mark,

 

I also tried to reboot and press F8 to initiate recovery, but recovery failed again. It said - The boot selection failed because a required device is inaccessible (attached pic).

So my guess is probably information from bcd.old (#801) has to be used OR information from Q:\FactoryRecovery folder (#802) has to be used.

 

PLease let me know what to do next

Anhang Größe
322168-125050.jpg 199.3 KB
Forum Star
Beiträge: 19
Kommentare: 2110

Ashish:

Yes, you can't post bcd files since they are binary and will only be interpreted properly on the system they came from. I think that you're correct that we have to have a look at the original bcd file that you (thankfully) backed up. To list it as a text file please type the following command. I'm assuming from one of your earlier posts that you exported the backup file to C:\BCD_Backup. If you put the file somewhere else or named it differently, then modify the filename or location (the part in red) in this command:

bcdedit /store C:\BCD_Backup /enum all > "%userprofile%\Desktop\BCD Backup.txt"

This should put a text file on your desktop listing the contents of the backup BCD. Please post this.

Beginner
Beiträge: 0
Kommentare: 12

Hi Mark,

After following the above steps, this is what I got as BCD_Backup (the original BCD file)

 

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=S:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
extendedinput           Yes
default                 {default}
resumeobject            {be8120cf-f175-11e1-9c19-3c970e24ef08}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 0
customactions           0x10000ba000001
                        0x54000001
custom:54000001         {f43fbb2b-ff99-11e1-9c6e-685d43f6cc45}
custom:5400000f         {f43fbb2b-ff99-11e1-9c6e-685d43f6cc45}

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {f43fbb2b-ff99-11e1-9c6e-685d43f6cc45}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {be8120cf-f175-11e1-9c19-3c970e24ef08}
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {f43fbb2b-ff99-11e1-9c6e-685d43f6cc45}
device                  ramdisk=[S:]\Recovery\WindowsRE\Winre.wim,{f43fbb2c-ff99-11e1-9c6e-685d43f6cc45}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[S:]\Recovery\WindowsRE\Winre.wim,{f43fbb2c-ff99-11e1-9c6e-685d43f6cc45}
systemroot              \windows
nx                      OptIn
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {be8120cf-f175-11e1-9c19-3c970e24ef08}
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=S:
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}

Setup Ramdisk Options
---------------------
identifier              {ramdiskoptions}
description             Ramdisk options
ramdisksdidevice        boot
ramdisksdipath          \boot\boot.sdi

Device options
--------------
identifier              {f43fbb2c-ff99-11e1-9c6e-685d43f6cc45}
description             Ramdisk Options
ramdisksdidevice        partition=S:
ramdisksdipath          \Recovery\WindowsRE\boot.sdi
 

Forum Star
Beiträge: 19
Kommentare: 2110

Ashish:

Your original BCD in #805 looks correct. So what happened to the PC that caused you to replace it?

Beginner
Beiträge: 0
Kommentare: 12

So my computer kept crashing and then one time it said BCD file is corrupt and computer could not be started. I was not able to boot into windows. That time I could not run the windows recovery because I didnt have data backup. So I tried to change the BCD file and finally was able to log into windows. 

I also posted bcdinfo.txt from Q:\FactoryRecovery folder #802. You think that might be helpful. If you think original BCD file is correct, then how do I use original file instead of this new one. Probably if I use original BCD file then I can run Windows Recovery (which is the aim of this whole process)

Forum Star
Beiträge: 19
Kommentare: 2110

Ashish:

Yes, that's where I was heading but I wanted to be sure that there wasn't an issue with the old BCD before asking you to restore it. Why don't you try this:

1. Back up the current BCD file and give it a different name; let's say BCD_Backup2:

bcdedit /export C:\BCD_Backup2

2. Next, restore the old BCD:

bcdedit /import C:\BCD_Backup

3. Try rebooting to see what happens. If Windows won't boot (and I don't see any reason why it shouldn't) then enter the Recovery Environment or you can restart the PC from a recovery DVD. Then restore the BCD backed up in step 1 above:

bcdedit /import C:\BCD_Backup2

Beginner
Beiträge: 0
Kommentare: 12

Hey Mark

 

Thanks a lot. It worked. The laptop is running windows recovery now - factory settings. This is what I wanted to do. Thanks a ton for your help. You have been immensely helpful. Highly appreciated.

Cheers Mate

Forum Star
Beiträge: 19
Kommentare: 2110

Ashish:

Glad to hear it!

Going back to reply #807, I am still wondering why this happened. It might be prudent to check your disk for bad sectors after you get the PC recovered. From an elevated command prompt window do:

chkdsk X: /R

but substitute for X: the drive letter of each volume on the disk, one at a time. For the C: volume you will need to let the PC reboot to run this. I'm thinking that you may have had a disk problem that corrupted some files and prevented the PC from booting. In any event, it wouldn't hurt to check the disk just to be sure.

Beginner
Beiträge: 0
Kommentare: 1

Hello, I am attempteing to get a Fujisu laptop with windows Vista booting, I did a chkdsk on all partitions; and did some BCD commands that gave me 'Total identified Windows installations: 0'. The computer only boots into recovery mode no matter what is chosen. Thanks Mark.

 

here is the bcdoutput:

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {default}
resumeobject            {e5931c8b-3ece-11de-abcb-a04c2800ab7b}
displayorder            {default}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {572bcd56-ffa7-11d9-aae0-0007e994107d}
device                  ramdisk=[F:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
path                    \windows\system32\boot\winload.exe
description             Windows Recovery Environment
osdevice                ramdisk=[F:]\sources\boot.wim,{ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
systemroot              \windows
nx                      OptIn
detecthal               Yes
winpe                   Yes

Windows Boot Loader
-------------------
identifier              {default}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Microsoft Windows Vista
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {572bcd56-ffa7-11d9-aae0-0007e994107d}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {e5931c8b-3ece-11de-abcb-a04c2800ab7b}
nx                      OptIn

Resume from Hibernate
---------------------
identifier              {e5931c8b-3ece-11de-abcb-a04c2800ab7b}
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=C:
path                    \boot\memtest.exe
description             Windows Memory Diagnostic
locale                  en-US
inherit                 {globalsettings}
badmemoryaccess         Yes

Windows Legacy OS Loader
------------------------
identifier              {ntldr}
device                  partition=C:
path                    \ntldr
description             Earlier Version of Windows

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}

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

Device options
--------------
identifier              {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
description             Ramdisk Device Options
ramdisksdidevice        partition=F:
ramdisksdipath          \boot\boot.sdi

 

here is the disk part info:

Partition ###  Type              Size     Offset
-------------  ----------------  -------  -------
Partition 1    OEM               1536 MB  1024 KB
Partition 2    Primary            146 GB  1537 MB
Partition 3    Primary           1588 MB   147 GB

 Volume ###  Ltr  Label        Fs     Type        Size     Status     Info
 ----------  ---  -----------  -----  ----------  -------  ---------  --------
 Volume 0     C                NTFS   Partition    146 GB  Healthy
 Volume 1     D                NTFS   Partition   1588 MB  Healthy
 Volume 2     G   HITMANPRO    FAT32  Removable   3820 MB  Healthy
 Volume 3     E   VISTA_32_PR  CDFS   DVD-ROM     3043 MB  Healthy
 Volume 4     F                NTFS   Partition   1536 MB  Healthy    Hidden

Forum Star
Beiträge: 19
Kommentare: 2110

Jacob:

I don't see anything wrong with your BCD - it is configured to boot directly into Windows by default. Since it doesn't, there must be something wrong with the Windows installation on partition 2. If you have or can borrow a Vista DVD can you try a repair installation?

Beginner
Beiträge: 0
Kommentare: 12

Hi Mark

 

Indeed there were some disk problems that prevented startup and kept crashing. I am not sure though what that means. I mean what are the repercussions and do u think there are some permanent disk damages. Will chkdsk fix the disk problems for good. 

 

Also I am facing another problem. After finishing windows recovery, windows update keep failing. After installing updates computer says restart windows for updates to take effect. But when I restart windows it says windows update configuration failed. And it rolled back to previous state without updates. 

 

I am not sure whats happening

Forum Star
Beiträge: 19
Kommentare: 2110

Ashish:

Chkdsk is capable of repairing many different types of file system errors but it can't fix every issue. If your disk had only a few bad sectors and doesn't start developing more then yes, it can usually fix this kind of problem. But if there are many bad sectors and the disk starts developing more then it would be time to replace the disk.

I'm afraid that I can't help you with Windows Update issues, but you can probably find help in one of the Microsoft forums.

Beginner
Beiträge: 0
Kommentare: 12

Ok thanks a lot for your help Mark. Your comments have been extremely helpful. 

So far there are no bad sectors and chkdsk is running stage 5 - checking free space. 

Beginner
Beiträge: 0
Kommentare: 1

I have create REW7 item in UEFI and it boot.

But after a while the boot freeze with blank screen and cursor.

Do it is possible to fix?

Windows Boot Loader
-------------------
identifier              {b0903287-c7b1-11e5-b71d-3065ec89e04b}
device                  ramdisk=[C:]\Recovery\b0903287-c7b1-11e5-b71d-3065ec89e04b\Winre.wim,{b0903283-c7b1-11e5-b71d-3065ec89e04b}
path                    \windows\system32\winload.efi
description             Windows Recovery Environment WinRE
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\b0903287-c7b1-11e5-b71d-3065ec89e04b\Winre.wim,{b0903283-c7b1-11e5-b71d-3065ec89e04b}
systemroot              \Windows
nx                      OptIn
detecthal               Yes
winpe                   Yes

Device options
--------------
identifier              {b0903283-c7b1-11e5-b71d-3065ec89e04b}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\b0903287-c7b1-11e5-b71d-3065ec89e04b\boot
.sdi

 

 

 

Forum Star
Beiträge: 19
Kommentare: 2110

Mark:

If the Recovery Environment starts to boot then that is proof that your BCD entries are correct.

The problem is most likely with your WinRE image file, WinRE.wim.

Beginner
Beiträge: 0
Kommentare: 1

thanks mark 

very nice

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Hello Mark,

cloned a Toshiba Satellite Win7 x64, computer didn't boot at first just gave one of those black screen errors, let the repair disk repair startup and it booted fine, tested recovery partition (holding 0 while powering on) and it booted to the Toshiba recovery screen just fine, only thing that doesn't work is the PE "Repair your Computer". Hope you can give me a bit of quick help. Thanks in advance!

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=\Device\HarddiskVolume1
path                    \bootmgr
description             Windows Boot Manager
locale                  en-US
inherit                 {globalsettings}
default                 {current}
resumeobject            {6dcca188-f597-11e0-bd1d-fd5ddfcfd093}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30

Windows Boot Loader
-------------------
identifier              {6dcca189-f597-11e0-bd1d-fd5ddfcfd093}
device                  unknown
path                    \windows\system32\winload.exe
description             Windows 7
locale                  en-US
inherit                 {bootloadersettings}
recoverysequence        {6dcca18a-f597-11e0-bd1d-fd5ddfcfd093}
recoveryenabled         Yes
osdevice                unknown
systemroot              \windows
resumeobject            {6dcca188-f597-11e0-bd1d-fd5ddfcfd093}
nx                      OptIn

Windows Boot Loader
-------------------
identifier              {6dcca18a-f597-11e0-bd1d-fd5ddfcfd093}

Windows Boot Loader
-------------------
identifier              {current}
device                  partition=C:
path                    \Windows\system32\winload.exe
description             Windows 7 Home Premium (recovered)
locale                  en-US
recoverysequence        {6dcca18a-f597-11e0-bd1d-fd5ddfcfd093}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows
resumeobject            {8e1466b4-dce4-11e5-8fb7-806e6f6e6963}

Windows Boot Loader
-------------------
identifier              {6dcca18d-f597-11e0-bd1d-fd5ddfcfd093}
device                  ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{6dcca18e-f597-11e0-bd1d-fd5ddfcfd093}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered)
locale                  
osdevice                ramdisk=[\Device\HarddiskVolume1]\Recovery\WindowsRE\Winre.wim,{6dcca18e-f597-11e0-bd1d-fd5ddfcfd093}
systemroot              \windows
winpe                   Yes

Resume from Hibernate
---------------------
identifier              {6dcca188-f597-11e0-bd1d-fd5ddfcfd093}
device                  unknown
path                    \windows\system32\winresume.exe
description             Windows Resume Application
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              unknown
filepath                \hiberfil.sys
debugoptionenabled      No

Resume from Hibernate
---------------------
identifier              {8e1466b4-dce4-11e5-8fb7-806e6f6e6963}
device                  partition=C:
path                    \Windows\system32\winresume.exe
description             Windows 7 Home Premium (recovered)
locale                  en-US
inherit                 {resumeloadersettings}
filedevice              partition=C:
filepath                \hiberfil.sys
debugoptionenabled      No

Windows Memory Tester
---------------------
identifier              {memdiag}
device                  partition=\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              {6dcca18b-f597-11e0-bd1d-fd5ddfcfd093}
description             Ramdisk Options
ramdisksdidevice        unknown
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

Device options
--------------
identifier              {6dcca18e-f597-11e0-bd1d-fd5ddfcfd093}
ramdisksdidevice        partition=\Device\HarddiskVolume1
ramdisksdipath          \Recovery\WindowsRE\boot.sdi

 

Anhang Größe
332665-126049.jpg 210.34 KB
Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

Try this:

bcdedit /set {current} recoverysequence {6dcca18d-f597-11e0-bd1d-fd5ddfcfd093}

The current value of recoverysequence in the main Windows 7 loader is set to {6dcca18a-f597-11e0-bd1d-fd5ddfcfd093} instead of {6dcca18d-f597-11e0-bd1d-fd5ddfcfd093}

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Thanks Mark, should I enter this into CMD from a boot disk or is it ok to enter it in an elevated CMD in windows ?

Forum Star
Beiträge: 19
Kommentare: 2110

You can enter it from an elevated CMD prompt in Windows.

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Got it, it works! Thanks a ton!

Starting to get an inkling about how these commands work, still foggy on the drive identifiers and how to figure out when one is correct or not...

Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

The long, cryptic identifiers (GUIDs) like this: {6dcca18d-f597-11e0-bd1d-fd5ddfcfd093} don't lend themselves well to human interpretation. But here is a trick to make it somewhat easier. The IDs are in a sequence of 32 hex characters grouped like this {8-4-4-4-12}. Most of the identifiers in a BCD differ only in the last character or two of the first 8-character group. The rest of the characters are usually the same, so you can just look at characters 7 and 8 when searching the text of a BCD for a matching identifier.

Beginner
Beiträge: 0
Kommentare: 4

Hi Mark and everyone i really need your help, am an IT student and have been have big issues with my dell since i reset the cmos battery.

Now I get BOOTMGR MISSING

I tried to use Window 7 DVD to do repair and I keep getting "This version of System Recovery Options is not compatible with the version of windows you are trying to repair. Try using a recovery disc that is compatible with this version of windows."

I am so frustrated now because I have assignments to turn in.

Below is a copy of the bcdedit \enum all query from CMD

X:\Sources > bcdedit /enum all > g:\bcdoutput.txt

 

Windows Boot Manager
--------------------
identifier              {bootmgr}
device                  partition=C:
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 Ultimate (recovered) 
locale                  en-US
recoverysequence        {a85e2392-ef6f-11e5-86e9-b564663086a2}
recoveryenabled         Yes
osdevice                partition=C:
systemroot              \Windows

Windows Boot Loader
-------------------
identifier              {a85e2392-ef6f-11e5-86e9-b564663086a2}
device                  ramdisk=[C:]\Recovery\2a531749-27af-11e1-83ad-d574c9cd571e\Winre.wim,{a85e2393-ef6f-11e5-86e9-b564663086a2}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment (recovered) 
locale                  
osdevice                ramdisk=[C:]\Recovery\2a531749-27af-11e1-83ad-d574c9cd571e\Winre.wim,{a85e2393-ef6f-11e5-86e9-b564663086a2}
systemroot              \windows
winpe                   Yes

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

Device options
--------------
identifier              {a85e2393-ef6f-11e5-86e9-b564663086a2}
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\2a531749-27af-11e1-83ad-d574c9cd571e\boot.sdi

 

 

Thanks for your help

Forum Star
Beiträge: 19
Kommentare: 2110

Jay:

From your symptoms it sounds like the machine is attempting to boot from the wrong disk or partition.

Check the BIOS settings to see if they are set correctly to boot from the desired hard disk.

If this isn't the problem, then which partition on the disk you are attempting to boot from is set as active? You can tell from Windows Disk Management console (if Windows is running) or by running DiskPart from a command prompt from the recovery environment.

The BCD you listed looks correct, but it indicates that there is only one partition involved in the boot process, and that the \Boot folder, the \Recovery folder, and the \Windows folder are all located on the same partition. Is this the case?

The error message that you get when attempting to boot from a Windows 7 DVD could be because it is the wrong version (32-bit when 64-bit is needed, or vice-versa), or it could be caused by one of the problems listed in this thread: http://answers.microsoft.com/en-us/windows/forum/all/this-version-of-sy…

 

Beginner
Beiträge: 0
Kommentare: 4

Thanks Mark
Yes all exist in same disk. When computer was okay I usually see only partition C when I go to My Computer. But when I check using DISKPART - SELECT DISK 0 (which is the only disk) - LIST PARTITION, I see C 100MB (System Reserved) & D 74GB.
Initially drive C: was active and I get that BOOTMGR is missing. Now I made C inactive and made D: active and it boots to where the 4 coloured cubes tries to come together, seizes and flash the BSoD so quickly and restarts.
When I reboot and press F8 then select Disable Restart on Error. Then when it boots the BSoD shows the below error code.

STOP: 0x0000007B

Forum Star
Beiträge: 19
Kommentare: 2110

Jay:

Sounds like your machine was formerly set up to boot from the System Reserved partition but got changed somewhere along the way. Using the Windows Automatic Repair function will sometimes do this.

OK, so now you are attempting to boot from the Windows partition, which starts correctly but then terminates in a blue-screen stop error. The error code that you see partway through the boot process means that when Windows switches from the low-level disk driver to the full Windows driver, an error occurs. This is usually caused by an improper setting in the BIOS. Did you recently switch the disk mode setting? Or, did you recently reset the BIOS to its default settings? Check to see which disk mode settings are available (IDE/AHCI/RAID) and which one is in use. Try the other.

Beginner
Beiträge: 0
Kommentare: 4

Hi Mark. 

Yes I reset the bios to default like 2 times. I also switch between IRRT & AHCI mode.  Now am using AHCI,  I also have ATA option available.

Forum Star
Beiträge: 19
Kommentare: 2110

Jay:

Try ATA mode to see if the machine will boot. If so, there must be an issue with your IRRT disk driver.

Beginner
Beiträge: 0
Kommentare: 4

Wow!  It boots using ATA mark. Am so happy. Thanks Bro,  you are the man!

Is there anything you suggest I do?

Forum Star
Beiträge: 19
Kommentare: 2110

Jay:

Something must have happened to your IRRT disk driver installation. You could download the driver from your PC's manufacturer and reinstall it. Then try setting the BIOS to IRRT mode and try again. If your PC manufacturer has a help forum, try posting there if you can't get the driver working correctly.

Beginner
Beiträge: 0
Kommentare: 9

Ok, I have W7 and the boot option menu dissapared some time ago but I never use it so I didnt care and it might even have been my self that set it not to show some time ago.

After an update from MS and a restart all I got was this:

Disk boot failure - insert system disk and press Enter

This was something you could get in the FAT32 days not in modern time but obviously you could.

 

This is among the tings I have tested during almost two weeks:

I can not for my life find my W7 disc (OEM btw) but I had made a rescue disk once wich I found and tested and it found some problems but when i clicked "use" it immediately said:

Start alternatives could not be saved

And nothing more.

Have also got this:

Boot sector for system disk partition is corrupt

0x490

Which didnt sounded good but thought it should be easily fixed so I then run this from bootrec with restart between each one:

Fixmbr

Fixboot

RebuildBCD

Nothing made any difference what so ever which surprised me. These should rebuild the boot sector and boot system!

 

There are other things to test as well with fex bootrec or bcdedit but Im to afraid to mess with that without anyone with knowledge.

The disk is GPT and UEFI is involved.

 

I have made a surface scan of the entire disk (1GB, that took time) and it was prestine with no problems what so ever which surprised me a little, but the disk is only litle over 2 years old so it should be fine.

Btw bcdedit /enum all gives this:

The boot configuration data storage could not be opened.

 

Anyone who have clue to fix the boot issue? Im pulling my hair out since Im out of options. I have made a copy of the disk where when it did it said it couldnt read some sectors, strangely enough, but at least i have a copy.

chkdsk is lying to me straight up in the face that say the disk is all dandy with no problems, sigh..

Something is really messed up here but it should be possible to fix it can´t be that bad? Anyone have clue what to do?

Regards Henry

Forum Hero
Beiträge: 70
Kommentare: 8349

This article is for Windows 8/8.1/10, but should still apply.  The generic bootfix commands don't always work.  I've had some luck in Windows 10 using this process which basically has you mount the EFI system parition (100MB fat32) as a volume letter.  Then copy the necessary boot files from the original hard drive which live in the Windows directory.  Then repair the bootloader and hopefully things will boot after that.  Even though not booting now, you may still want to take a full disk backup first (just to be on the safe side in case things get worse before they get better).

http://blog.d0zingcat.xyz/2015/09/28/Windows/How%20to%20repair%20the%20…

 

Beginner
Beiträge: 0
Kommentare: 9

Interesting page, thanks a lot!

Oh yes I have made a backup of the harddrive the same day it happened and I will only test and play with the copy and when I know something will work so it will boot so would I do the same with original one, or just copy it all over I will se, I dont take any chances here be sure of that.

Btw it say in the link about to assign the 100MB partition a letter and so on but that partion don´t have that normally so shouldnt that be removed again or that will be fixed automatically perhaps when the rebuild is done?

Forum Hero
Beiträge: 70
Kommentare: 8349

No need to worry about the mounted volume letter.  It only applies in the recovery command prompt but does not remain static after you reboot.  Recovery mode is a bit like WinPE - it's its own bootable environment. 

Beginner
Beiträge: 0
Kommentare: 9

Aha so thats how it works thats cool, good to know.

I could assign a letter to the EFI volume but the filesystem in this partition was RAW (how the hell?!) not FAT32 so no command would touch it since well it didn´t have a filesystem, I dont get it how that could have happened.

Had thus planned to convert it to FAT32 if that would work with RAW and see if that would make any difference, but I accidently format it instead and wiped any files so I will make a new backup. An system repair didn´t fixed it and I didn´t really expect it to either, oh well.

Btw the EFI partition was not set to active but I guess it should and also C? Quite important that some would if the disk should ever be able to boot.

Forum Hero
Beiträge: 613
Kommentare: 8747

Only one partition per disk can be marked as active unless you have a multiple OS system with a boot loader that can change the active flag per OS system partition, so in your case only the system or C: partition would be marked as active.

A partition marked as RAW may not actually be raw, if the file system is one that Windows doesn't recognise (for example I have an HPFS for OS2, on my OS diskexit) it will report it as RAW.

If you have another PC with True Image installed, I suggest mounting your image and running a malware or antivirus program over it, just in case your partition was made raw by a nasty on your system rather than a mechanical or electronic malfunction.

Be aware that some nasties are designed to hide in the Windows Restore Point folder and that some malware and antivirus programs ignore this hidden system folder when run. It is wise to unhide temporarily this golfer if you have System Restore switched on.

Beginner
Beiträge: 0
Kommentare: 9

Yes only one active but as I have understood it about Windows 7 so is the boot partition (hidden) the one that have to be active so BIOS can start with that and then start Windows, but I can be wrong, but it doesn't really matter since I cant make any partition active by whatever the reason.

I think any virus was the cause since I´m not easily tricked into clicking on things and stuff and I always let virustotal go through any file no matter what and I only download from sites that looks legit. But I did a virus scan anyway and it came up clean and it all also started righ after a windows update wanted me to restart the computer.

I have now used some different programs among partition wizard and that and other programs report the boot partition as NTFS, strange it should actually be FAT32.

However I could with partition wizard see the files in the 100MB boot partition and one folder with really important files was pretty much all deleted, but I could salvage all the files.

 

I have backup but its a little old so I really would like the other hard drive to work and be able to run. For pun so did I make a copy of the backup boot partition and copied it right over the other boot partition and did some /fixboot and such, not to surprisingly did It did not work, a BCD rebuild did not work either, but worth a shot.

But I just realized that I could of course test to put back the salvaged files back to the boot partition folder and see.

Btw I have seen in this thread that the boot partition sometimes have to be linked in some way to the windows partition or such with a number, is this something I need to do?

Beginner
Beiträge: 0
Kommentare: 9

Ok, I reformat the hidden partition on the backup to FAT32 (was RAW before), copied the recovered, formely corrupted, files from the same hidden partition on the original harddrive to this partition and I could now finally get the /enum all to work. I dont really know but it look like a mess here and with many "unknown" which can´t be good so it´s probably really messed up.

The only rescue disk I could get (lost the original E-OEM) was from a friend and that was in Swedish language so sorry guys for the Swedish, but I hope you might be able to figure it out with the path and other stuff, otherwise just haul and will try to translate:

 

Starthanteraren for inbyggd programvara
-------------------------------------
identifier              {fwbootmgr}
displayorder            {bootmgr}
                        {218ee779-f834-11e5-80e3-fe5950bd9c34}
                        {218ee77a-f834-11e5-80e3-fe5950bd9c34}
                        {218ee77c-f834-11e5-80e3-fe5950bd9c34}
                        {218ee778-f834-11e5-80e3-fe5950bd9c34}
                        {218ee77b-f834-11e5-80e3-fe5950bd9c34}
timeout                 0

Starthanteraren
---------------
identifier              {bootmgr}
device                  partition=V:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager
locale                  sv-SE
default                 {default}
displayorder            {default}
timeout                 30

Inbyggd programvara (101fffff)
------------------------------
identifier              {218ee778-f834-11e5-80e3-fe5950bd9c34}
description             CD/DVD Drive

Inbyggd programvara (101fffff)
------------------------------
identifier              {218ee779-f834-11e5-80e3-fe5950bd9c34}
description             UEFI: TSSTcorp CDDVDW SH-224DB

Inbyggd programvara (101fffff)
------------------------------
identifier              {218ee77a-f834-11e5-80e3-fe5950bd9c34}
device                  partition=V:
path                    \EFI\Microsoft\Boot\bootmgfw.efi
description             Windows Boot Manager

Inbyggd programvara (101fffff)
------------------------------
identifier              {218ee77b-f834-11e5-80e3-fe5950bd9c34}
description             Hard Drive

Inbyggd programvara (101fffff)
------------------------------
identifier              {218ee77c-f834-11e5-80e3-fe5950bd9c34}
device                  partition=E:
description             UEFI: KingstonDataTraveler 2.0

Startinl„saren
--------------
identifier              {default}
device                  unknown
path                    \Windows\system32\winload.efi
description             Windows 7 Home Premium
locale                  sv-SE
recoverysequence        {218ee776-f834-11e5-80e3-fe5950bd9c34}
recoveryenabled         Yes
osdevice                unknown
systemroot              \Windows
resumeobject            {d0dcb861-f82b-11e5-ae7d-806e6f6e6963}
nx                      OptIn
custom:250000c2         0

Startinl„saren
--------------
identifier              {218ee776-f834-11e5-80e3-fe5950bd9c34}

Start fr†n vilol„ge
-------------------
identifier              {d0dcb861-f82b-11e5-ae7d-806e6f6e6963}
device                  unknown
path                    \Windows\system32\winresume.efi
description             Windows 7 Home Premium
locale                  sv-SE
inherit                 {resumeloadersettings}
filedevice              unknown
filepath                \hiberfil.sys
debugoptionenabled      No

Minnestestaren
--------------
identifier              {memdiag}
device                  unknown
path                    \EFI\Microsoft\Boot\memtest.efi
description             Windows Memory Diagnostic
locale                  sv-SE

Enhetsalternativ
----------------
identifier              {218ee777-f834-11e5-80e3-fe5950bd9c34}
description             Windows Recovery
ramdisksdidevice        unknown
ramdisksdipath          \Recovery\218ee776-f834-11e5-80e3-fe5950bd9c34\boot.sdi

 

The F8 or any boot at all does not come up but the harddrive contain a /Rescue folder.

Thanks guys!

Forum Hero
Beiträge: 70
Kommentare: 8349

Henry, in I don't see anything that stands out.  I can't remember (or find in the thread) if this was a UEFI install or a Legacy install - assuming legacy MBR still.  Perhaps a third party tool may be more useful for attempting to repair the bootloader at this point - if it's even possible.  As always, still recommend taking a backup of what you have (or what you started with - just in case).

http://www.disk-partition.com/gpt-mbr/repair-corrupted-mbr-1004.html

 

Beginner
Beiträge: 0
Kommentare: 9

Oh so it did look ok? Never thought with all those missing unknown device and such, good to know.

This is a UEFI install with a GPT disk.

 

I have not touched the original harddrive and will not until I have something that absolutely works. I play with a backup of the backup of that disc right now so no worries if something go south, altough it takes 2 hours to make a copy again which is a pain.

I have tested mbr, rebuildbcd and many other things I dont even remember righ now both on the primary partition as on the hidden one but nothing fix the drive which surprise me a little.

I will absolutely test the one in the link, wasnt aware of that, thanks!

Forum Hero
Beiträge: 70
Kommentare: 8349

The only 2 items that I see that it couldnt' identify is a Ramdisk (virtual hard disk loaded into Ram - this is WinPE usually, but ramdisks can also be created in Windows for fast, temorary data storage) and  what appears to be an unknown path to where the hibernation file should live, but could be because hiberfile.sys was ignored during the backup anyway. 

Your boot order is:  

TSSTcorp CDDVDW SH-224DB {218ee779-f834-11e5-80e3-fe5950bd9c34}

Windows boot manager {218ee77a-f834-11e5-80e3-fe5950bd9c34}

UEFI Kingston data traveler {218ee77c-f834-11e5-80e3-fe5950bd9c34}

CD/DVD drive{218ee778-f834-11e5-80e3-fe5950bd9c34}

Hard drive (218ee77b-f834-11e5-80e3-fe5950bd9c34)

Any chance you still have the CD or a UsB drive plugged in when attempting to boot as well?  

Curious to know how the other software pans out too.  Keep us posted. 

Beginner
Beiträge: 0
Kommentare: 9

No, I remove every disc, flashdrive and such when I attempt to boot or if leave in I go into BIOS and force it to boot from whatever I want it to or just press a buttom to get a meny up to choose from what to boot from. The reason all that is in this file is because I did bcdedit /enum ALL through Windows Recovery CD and copied the text to a flashdrive I had connected and thus are these seen.

The CD/DVD player and USB them selfs are always shown if connected but if there is no bootable disc or drive it will go on to the next device and so on until it see something that will boot. If not "no bootable device" and such.

------

The freeware program could unfortunatly not do anything at all, it was to simple, so that was a dead end. I have also paid for another program a week ago that could do much more but that still couldnt fix it so I will not buy the better version of that program. There are also some strange problems with the disc so fex the very capable Partition Wizard boot thing cant fix the boot since it cant write what is needed to the disc, why I have no idea.

But after what feelt like the hundreds time that I put the backup through the Revovery CD Repair Startup thingy so did it change quite many things with these numbers involved and after that it actually booted into Windows!

However it was not the normal thing in the begining with the typical animated moving windows but just black and a short time shown a green bar (very old style) in the bottom that moved (just like in the beginning of the GUI recovery session) until it booted into windows, but I thought that I could live with that.

After a reboot of the computer however it all went south again "no boot disk can be found", I just don´t get it.

Frequent Poster
Beiträge: 4
Kommentare: 566

Henry, sorry to hear about boot problems, but are you saying you do not have a backup, made with Acronis before startup issue occurred? Have you created disk backup after Windows failed to boot for the first time?

If that is correct and you do not succeed in fixing the boot issue, my only advice would be to save your files somewhere, reinstall Windows, copy files back and make sure that system backups are executed regularly, for example, schedule daily incrementals. And of course, define a rule to delete old backups in Options so that your backup storage is not filled up with backups.

Currently we do not have a program that would fix already broken/damaged/corrupted Windows. Acronis True Image software allows to recover your system only if the backup was made before problems occurred, not after.

Regards,

Slava

Forum Hero
Beiträge: 70
Kommentare: 8349

Unfortunately, Slava is correct. I'm running out of ideas for helping repair the bootloader, but it's really outside of the scope of the Acronis product itself.  The only other third party tool, you may want to consider is EasyBCD.  I've never used the paid version, personally (haven't had to), but I hear good things about it. Not only is it supposed to help you customize the bootloader for multiboot installs, but it is also supposed to have bootloader recovery capability. 

http://neosmart.net/EasyBCD/

 

Forum Hero
Beiträge: 70
Kommentare: 8349

Looks like they actually have a bootloader recovery tool that "guarantee's" to recover the bootability of your system.  If it's truly a guarantee, and doesn't work, hopefully you'd  be able to get a refund:

http://neosmart.net/EasyRE/

I've never personally used it and don't endorse it, but it may very well be the type of tool to resolve your issue.  Unfortunately, looks like you have to pay to get it so if it doesn't work, you're either out the money, or hopefully they stick by their guarantee and help you resolve it or refund you if you do give it a shot.

 

Beginner
Beiträge: 0
Kommentare: 9

Slava and Bobbo_3C0X1:  No worries I have a backup made with Acronis but it was a little old and some work was not on that one but on the messed up one so I really wanted to get that one going, but to no awail. The copies I talked about that I played with sort of speak was another copy I made from the messed up disk just to not destroy anything one that one if I would play with that instead. I have always had a real backup that worked but as i said it was a little old since I had forgot to make a backup for the past month and thus some importent work was not on it.

But I have now tried even more things but nothing works so i grabbed what I could from the important work and just format it to copy the content from the real backup over it. I did manage to get much of the work over to the other but unfortenatly not all so there will be some work to get it all back to where I was before it broke down but it will not take more then a week and I´m ok with that.

I have tried EasyBCD before but actually no luck there either, wouldnt matter what I did.

 

I now removed all partitions from the messed up harddrive and format it and when it was finished 2.5 hours later it showed that there actually was missing around 100MB from the real size! When I tried to make a backup of the little old real backup so did Acronis actually say:

 

Failed to write data to the disk.

Failed to write to sector 470760 of hard disk "3"         (the messed up one)

Failed to write to the snapshot manager volume. (0x1000D3)

Unknown status. (0x9)

Access denied (0xFF0)

 

And there were about 40 similar ones as the one above but with different sectors.

A chkdsk and surface scan gave nothing though said it was all ok wich was not true so Im confused about that.

But I dont have more time to deal with this now and I got got things going quite ok witht he backup so tomorrow Im taking it to the store I bought it from and hear if I still have guarantee on it, soon 3 years since I bought it there but a harddrive should hold far longer then that.

 

Thanks once again guys with this, very helpful even if we now didn´t managed to fix it and it probably wouldn´t be possible either since it seem there is a bad fault with it after all.

Thanks!

Regards Henry

 

Edit: I will add that the reson the disc didn´t boot was not actually as it now seem any erronous bootsectors or anything that should prevent it from start.

I had a backup that I was able to recover to an earlier state and that booted up fine after that but after I downloaded the same updates from Microsoft it all went the same again, it just didnt boot with the "non bootable device" message.

At this point I realised my computer had Secure Boot so I turned this of and voila the computer booted like nothing and would probably have doent the same in the first place.

So one of the updates change someting in the bootsector (legit I might ad) but for whatever the reason BIOS saw this as a virus and thus prevent the disc from booting. Im all good with that accept that it could f*****n tell me this instead of just the message "not bootable disc" !!

I spent over a week for nothing, a simple "The bootsector have been altered this could be a virus, would you like to contune to boot?" but nooo, nothing at all.

Sai
Forum Member
Beiträge: 0
Kommentare: 52

Hi Mark, I have an issue with this Dell I was hoping you'd help me with. The darn thing goes straight into "Repair your computer" no matter what option is chosen, it seems to have occurred right after a Windows Update. I'm guessing the BCD is pointing to the recovery rather than the windows drive. here is the BCD output text and the diskpart List partition.

Anhang Größe
358778-129175.txt 3.43 KB
358778-129178.jpg 2.43 MB
Forum Star
Beiträge: 19
Kommentare: 2110

Sai:

The BCD appears to be set up correctly. See reply #828 above; I'll bet that you have a similar issue. If there is a BSOD on startup, Windows should fail over to the Recovery Environment. It appears that it is, based on your description.