EasyBCD creates windows 7 vhd entries wrong

Status
Not open for further replies.
shinji

shinji

Member
Ok. They are "right" in that they work but they are incomplete. It ends up showing the Vista bootloader instead of the Windows 7 one and it also gets inserted twice. In addition it doesn't use the name specified but rather just enters generically calls it "Microsoft Windows". Of course later I found that Windows 7 Starter can't be booted from VHD but that doesn't affect my report.

Good:
Windows Boot Loader
-------------------
identifier {a2527ec7-ac62-11de-97ab-005056c00008}
device vhd=[C:]\vhd\6.1.7600.16385.x86fre.win7_rtm.090713-1255.Starter.en-US.vhd,locate=custom:12000002
path \Windows\system32\winload.exe
description Windows 7 Starter
locale en-US
inherit {6efb52bf-1766-41db-a6b3-0ee5eff72bd7}
recoverysequence {5333b967-5e20-11de-b300-a4a6bfa555bf}
recoveryenabled Yes
osdevice vhd=[C:]\vhd\6.1.7600.16385.x86fre.win7_rtm.090713-1255.Starter.en-US.vhd,locate=custom:22000002
systemroot \Windows
resumeobject {5333b960-5e20-11de-b300-a4a6bfa555bf}
nx OptIn
detecthal Yes
Click to expand...
Bad:
Windows Boot Loader
-------------------
identifier {a2527ec8-ac62-11de-97ab-005056c00008}
device vhd=[C:]\vhd\6.1.7600.16385.x86fre.win7_rtm.090713-1255.Starter.en-US.vhd,locate=custom:12000002
path \Windows\system32\winload.exe
description Microsoft Windows
osdevice vhd=[C:]\vhd\6.1.7600.16385.x86fre.win7_rtm.090713-1255.Starter.en-US.vhd,locate=custom:22000002
systemroot \Windows

Windows Boot Loader
-------------------
identifier {a2527ec9-ac62-11de-97ab-005056c00008}
device vhd=[C:]\vhd\6.1.7600.16385.x86fre.win7_rtm.090713-1255.Starter.en-US.vhd,locate=custom:12000002
path \Windows\system32\winload.exe
description Microsoft Windows
osdevice vhd=[C:]\vhd\6.1.7600.16385.x86fre.win7_rtm.090713-1255.Starter.en-US.vhd,locate=custom:22000002
systemroot \Windows
Click to expand...
 
Thanks. Here is the commands I went through to get the correct boot entry if it is of any help at all

bcdedit /copy {current} /d "<Installation Name>"
(make note of new guid output now)

bcdedit /set {newguid} device vhd=[Drive:]\<vhd location>
bcdedit /set {newguid} osdevice vhd=[Drive:]\<vhd location>
bcdedit /set {newguid} detecthal on
 
Me too but worse ...

I tried to add an entry to boot from a vhd. Entry ended up incomplete and twice. The critical entry created is "Device:[E:]\VHD\Server" while the real entry should be the full file name. I also got the default title "Microsoft Windows". Since I don't currently have full knowledge of BCDEDIT I cannot tell if the "BCD ID" is correct.
 
Is there a space in the vhd location? If so then try again without a space in the folder. The entry works but the bootloader ends up using the wrong animation. That and it is duplicated. Your case sounds like there was a space in there. I don't know if we can quote a file location with spaces in it.
 
There was indeed a space in the file name. I replaced these, re-ran the commands you used and got what seems like a good entry. My machine refuse to load the OS however. Get to a generic screen stating that I need to repair my system using setup disk etc
 
Please do one of the following.

a) Open an administrative command prompt, type bcdedit, and paste in the output

b) Open EasyBCD and in the View Setting section switch it to Detailed. Copy and paste the output there

Both will give the same kind of output.
 
In the meantime you might be able to get it to work by adding "s or 's at the start and end of the path.
 
Didn't realize that the bootmgr had to be from Win 7 for this to work. Succeeded after replacing bootmgr from a win7 installation to my testmachine. Works now.
 
Status
Not open for further replies.
Back
Top