Windows does not boot anymore - winload.exe could not be loaded

[QUOTE=Kaktussoft;1680463]

silverangel said:

So here it is (it's in French ;-) )

Code:

Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Tous droits réservés.
 
C:\Windows\system32>bcdedit /enum all
 
Gestionnaire de démarrage Windows
---------------------------------
identificateur          {bootmgr}
device                  boot
description             Windows Boot Manager
locale                  fr-FR
inherit                 {globalsettings}
default                 {current}
resumeobject            {8cb2d9b0-7c05-11de-842e-b4611d44fefa}
displayorder            {current}
toolsdisplayorder       {memdiag}
timeout                 30
 
Chargeur de démarrage Windows
-----------------------------
identificateur          {572bcd56-ffa7-11d9-aae0-0007e994107d}
device                  ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa
0f-11da-8ddf-0013200354d8}
path                    \windows\system32\boot\winload.exe
description             Windows Recovery Environment
osdevice                ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa
0f-11da-8ddf-0013200354d8}
systemroot              \windows
nx                      OptIn
detecthal               Yes
winpe                   Yes
 
Chargeur de démarrage Windows
-----------------------------
identificateur          {current}
device                  boot
path                    \Windows\system32\winload.exe
description             Windows 7
locale                  fr-FR
inherit                 {bootloadersettings}
recoverysequence        {8cb2d9b4-7c05-11de-842e-b4611d44fefa}
recoveryenabled         Yes
osdevice                boot
systemroot              \Windows
resumeobject            {8cb2d9b0-7c05-11de-842e-b4611d44fefa}
nx                      OptIn
 
Chargeur de démarrage Windows
-----------------------------
identificateur          {8cb2d9b4-7c05-11de-842e-b4611d44fefa}
device                  ramdisk=[C:]\Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fe
fa\Winre.wim,{8cb2d9b5-7c05-11de-842e-b4611d44fefa}
path                    \windows\system32\winload.exe
description             Windows Recovery Environment
inherit                 {bootloadersettings}
osdevice                ramdisk=[C:]\Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fe
fa\Winre.wim,{8cb2d9b5-7c05-11de-842e-b4611d44fefa}
systemroot              \windows
nx                      OptIn
winpe                   Yes
 
Reprendre à partir de la mise en veille prolongée
-------------------------------------------------
identificateur          {8cb2d9b0-7c05-11de-842e-b4611d44fefa}
device                  boot
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=C:
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          {8cb2d9b5-7c05-11de-842e-b4611d44fefa}
description             Ramdisk Options
ramdisksdidevice        partition=C:
ramdisksdipath          \Recovery\8cb2d9b4-7c05-11de-842e-b4611d44fefa\boot.sdi
 
Options de périphérique
-----------------------
identificateur          {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}
description             Ramdisk Device Options
ramdisksdidevice        partition=\Device\HarddiskVolume1
ramdisksdipath          \boot.sdi
 
C:\Windows\system32>

[QUOTE]
Chargeur de démarrage Windows
-----------------------------
identificateur {572bcd56-ffa7-11d9-aae0-0007e994107d}
device ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa
0f-11da-8ddf-0013200354d8}
path \windows\system32\boot\winload.exe
description Windows Recovery Environment
osdevice ramdisk=[\Device\HarddiskVolume1]\winre.wim,{ad6c7bc8-fa
0f-11da-8ddf-0013200354d8}
systemroot \windows
nx OptIn
detecthal Yes
winpe Yes

Nothing points to {572bcd56-ffa7-11d9-aae0-0007e994107d} and C:\winre.wim doesn's exits.
Same for {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}

bcdedit /export C:\bcdout (just to get a backup)
bcdedit /delete {572bcd56-ffa7-11d9-aae0-0007e994107d}
bcdedit /delete {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}

post bcdedit /enum all
again and reboot

Have you confirmed the Win7 partition is marked Active and run Startup Repair 3 separate times with reboots? It sounds like you quit after second repair attempt which was starting to make headway.

I'm not sure what all this file nitpicking is about - maybe you could clue the rest of us? All repair commands including System File Checker are automated in Startup Repair.

Again, Linux can corrupt Win7 beyond Repair. You may need to reinstall using your Recovery Partition, Recov Disks you made when you set up your computer, or a Win7 installation DVD for your bit rate and version which you fail to list: Reinstalling Windows 7

Please mark your thread Not Solved at top so others will contribute.

gregrocker said:

Have you confirmed the Win7 partition is marked Active and run Startup Repair 3 separate times with reboots? It sounds like you quit after second repair attempt which was starting to make headway.

I'm not sure what all this file nitpicking is about - maybe you could clue the rest of us? All repair commands including System File Checker are automated in Startup Repair.

Again, Linux can corrupt Win7 beyond Repair. You may need to reinstall using your Recovery Partition, Recov Disks you made when you set up your computer, or a Win7 installation DVD for your bit rate and version which you fail to list: Reinstalling Windows 7

Please mark your thread Not Solved at top so others will contribute.

His BCD store is a little strange and I advised him to cleanup.

bootrec/fixmbr and bootrec/fixboot are run automatically in recovery environment I know. But he still has GRUB as main bootloader .. sounds impossible if MBR has been fixed by recovery environment

gregrocker said:

Have you confirmed the Win7 partition is marked Active and run Startup Repair 3 separate times with reboots? It sounds like you quit after second repair attempt which was starting to make headway.

I'm not sure what all this file nitpicking is about - maybe you could clue the rest of us? All repair commands including System File Checker are automated in Startup Repair.

Again, Linux can corrupt Win7 beyond Repair. You may need to reinstall using your Recovery Partition, Recov Disks you made when you set up your computer, or a Win7 installation DVD for your bit rate and version which you fail to list: Reinstalling Windows 7

Please mark your thread Not Solved at top so others will contribute.

Sorry to say but I don't understand you.

• Recovery Env can rebuild MBR
• Recovery Env can rebuild bootsector
• Recovery Env can update BCD store
• Recovery Enc can rebuild BCD from scratch

So how can linux corrupt Win7 beyond repair? Just curious what you mean

Over the past 2+ years we have seen repeated cases where when GRUB is on the HD it makes Win7 irreparable by normal methods requiring reinstall - preferably to separate HD's booted via BIOS so there is not GRUB corruption. Dual boot Ubuntu-Win7

To even reinstall Win7 when GRUB is present often requires wiping the HD with Diskpart Clean command to clear the boot sector.

What about Startup Repair?

If it won't repair you may need to clean reinstall after wiping the HD first:
SSD - HDD Optimize for Windows Reinstallation
Dual-Boot Windows 7 and Ubuntu in Perfect Harmony
Reinstalling Windows 7

I'm a little lost about what I should do or not...

Indeed, I had run startup repair only twice; I just ran it three times with restarts between. They were very quick these times. And yes, the windows partition is active.

Also, why should I reinstall windows? If Linux had corrupted windows beyond repair, there would be some signs or something else I guess.

I'm not sure what's wrong by now (except Grub should have been replaced by windows bootloader, from what kaktussoft is saying).

My windows version is 6.1 (number 7601 sp1)

nothing is wrong now!! Did you do:

bcdedit /export C:\bcdout (just to get a backup)
bcdedit /delete {572bcd56-ffa7-11d9-aae0-0007e994107d}
bcdedit /delete {ad6c7bc8-fa0f-11da-8ddf-0013200354d8}

These are just stupid entries. not used at all. an not working at all, because files are not there. You can leave entries if you wish

What edition of Win7? 32 or 64-bit?

Keep working with Kaktussoft as he has line commands to possibly recover Win7 to GRUB menu.

you have done nothing wrong!
situation now:

1. you have a MBR which has code that jumps to linux partition and loads grub from it.
2. GRUB list menu items like win7 and linux. In grub is win7 defined as an item to start from hd(0,0) [sort of] and "chainloader +1". So it runs bootsector from C-partition which is bootmgr the windows 7 bootloader
3. it read the bcd store (bcdedit /enum all lists the contents)

What you can do as a test:
bcdedit /create /d “Linux this is just a description” /application BOOTSECTOR


BCDEdit will return an alphanumeric identifier for this entry that I will refer to as {ID} in the remaining steps. You’ll need to replace {ID} by the actual returned identifier. An example of {ID} is {d7294d4e-9837-11de-99ac-f3f3a79e3e93}. Write down ID somehwere. Next, let’s specify which partition hosts a copy of the linux.bin file:
bcdedit /set {ID} device partition=c:


The path to our linux.bin file:
bcdedit /set {ID} path \linux.bin


An entry to the displayed menu at boot time:
bcdedit /displayorder {ID} /addlast


and finally, let’s specify how long the menu choices will be displayed:
bcdedit /timeout 5
===============
now try to boot and select win7. linux is displayed in windows bootmanager? you can start it? most likely grub shows again but there you can select linux. Is this true?
================
bcdedit /delete {ID}
and linux is gone from windows boot menu. So it's save to test