Primary OS (Win 10) cannot boot after boot into VHDX

grb

Member
I used EasyBCD to create a second boot option into a VHDX that contained an image of my Win 10 OS (EFI partition and C: drive). This was for the purpose of testing the bootability of a backup image of my OS. I followed the instructions provided by Acronis in a KB article on the topic (Acronis True Image 2018: configuring Windows native boot from VHD/VHDX files created by "Convert to VHD" feature | Knowledge Base).

Initially, everything seemed fine -- when I restarted the computer, the Metro bootloader was launched, showing my original Windows 10 OS as the first (default) option, and the VHDX-based image as the second option. I selected the VHDX OS, and it booted properly. However, when I restarted my computer again, nothing was working anymore.

The system became stuck at the black Dell splash screen (with rotating dots) and never reached the Metro bootloader.

The only thing I am able to do at this point is to enter the Windows Startup Repair tool, select Advanced options and then select booting into another operating system, which does then show the Metro bootloader (with the two boot options as before -- the original Windows 10 installation and the VHDX-based image). If I select the VHDX-based OS, it does boot successfully, but if I select the original Windows 10 installation, it never boots (it just hangs at the black "Dell" screen).

I just want to return the computer to the way it was before I added the VHDX boot option, so that I can use my computer again!

I did save a backup in EasyBCD before making the bootloader modifications, so one idea I have is to install EasyBCD in the VHDX-based OS, and restore the backup from there. However, I am worried that this will make it worse. If the restore operation doesn't fix whatever it was that broke the bootability of my original Win 10 OS, then I may not be able to boot at all after restoring (since I presumably will not be able to even use the VHDX version of the OS anymore).

Please help! Thank you.
 
If it wasn't clear, I'm on a UEFI/GPT system. The EasyBCD settings (after adding the VHDX boot option) are pasted below. I noticed just now that both boot loader entries use the same "identifier"... that seems like it could be a cause of problems. If you agree that this is the issue, how do I fix it? I don't care about being able to boot into the VHDX anymore, I just want my original OS to work again. Thanks!

---

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=\Device\HarddiskVolume1
path \EFI\Microsoft\Boot\bootmgfw.efi
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {b9c3b10c-61ef-11e9-bbe6-c8f75055a0d1}
resumeobject {b9c3b10b-61ef-11e9-bbe6-c8f75055a0d1}
displayorder {b9c3b10c-61ef-11e9-bbe6-c8f75055a0d1}
{b9c3b10f-61ef-11e9-bbe6-c8f75055a0d1}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 30

Windows Boot Loader
-------------------
identifier {b9c3b10c-61ef-11e9-bbe6-c8f75055a0d1}
device partition=E:
path \windows\system32\winload.efi
description Windows 10
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {b9c3b10d-61ef-11e9-bbe6-c8f75055a0d1}
displaymessageoverride Recovery
recoveryenabled Yes
isolatedcontext Yes
allowedinmemorysettings 0x15000075
osdevice partition=E:
systemroot \windows
resumeobject {b9c3b10b-61ef-11e9-bbe6-c8f75055a0d1}
nx OptIn
bootmenupolicy Standard

Windows Boot Loader
-------------------
identifier {b9c3b10f-61ef-11e9-bbe6-c8f75055a0d1}
device vhd=[F:]\win10-ati-convert.vhdx,locate=custom:12000002
path \Windows\system32\winload.efi
description VHDX Boot Test
locale en-US
osdevice vhd=[F:]\win10-ati-convert.vhdx,locate=custom:22000002
systemroot \Windows
nx OptIn
detecthal Yes
 
Back
Top