Error adding VHD boot on Acer laptop

C

cryback79

Member
Hello and first of all, thank you for your great software.

I have an Acer laptop with preinstalled Software in 4 partitions:
* Acer Recovery
* Windows
* Data
* XP Multimedia

I'm upgrading it with a bigger HDD and memory, and installing my company's corporative Win7 Ultimate (x64). Thanks to your software I succeded in installing kubuntu and win7 ultimate.

Then I used disk2vhd to virtualize only the partition with my original Windows from Acer. I added it to the BCD but all I get when I boot is a blank screen. No error messages, no cursor, nothing.
The most important I think it's that blank screen appears whatever option you choose, not only with the new VHD boot.
To recover it, I simply boot from Win7 DVD, delete BCD entry from VHD file, and everything works again fine.

Any solution?
Thanks in advance.

-------------------------- BCD MENU ---------------------------------------------

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device partition=C:
path \bootmgr
description Windows Boot Manager
locale es-ES
default {baf05bfa-3b66-11df-91a2-c6eb9ec2825b}
displayorder {baf05bfa-3b66-11df-91a2-c6eb9ec2825b}
{466f5a88-0af2-4f76-9038-095b170dc21c}
{62f01868-3b6c-11df-b3a4-001b24c8437e}
{ccdca3ad-4161-11df-a931-00805a40ba1a}
timeout 20
Windows Boot Loader
-------------------
identifier {baf05bfa-3b66-11df-91a2-c6eb9ec2825b}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 x64
locale es-ES
osdevice partition=C:
systemroot \Windows
resumeobject {368be093-3b60-11df-9bbb-806e6f6e6963}

Windows Legacy OS Loader
------------------------
identifier {466f5a88-0af2-4f76-9038-095b170dc21c}
device partition=C:
path \ntldr
description XP MultiMedia
Real-mode Boot Sector
---------------------
identifier {62f01868-3b6c-11df-b3a4-001b24c8437e}
device partition=C:
path \NST\AutoNeoGrub0.mbr
description kUbuntu

Windows Boot Loader
-------------------
identifier {ccdca3ad-4161-11df-a931-00805a40ba1a}
device vhd=[C:]\Temp\Acer.vhd,locate=custom:12000002
path \Windows\system32\winload.exe
description Windows Acer
locale en-US
osdevice vhd=[C:]\Temp\Acer.vhd,locate=custom:22000002
systemroot \Windows
detecthal Yes
 
I used 2.0 build 91.

I also added VHD boot using the Microsoft Technet instructions (bcdedit copy, set,...) and got the same situation.
 
Well, I'm not sure 100% since it's a corporative HDD. But I recieved it formatted and I also format it during Win7 installation.
Could this be a problem? If I format and install Win7, isn't that boot loaded?

TIA
 
Hey, it "half-worked", thanks!

I reset BCD and create entries again. Now it ONLY boots with Real-mode (ubuntu, xp) and VHD. Normal Windows 7 Boot shows blank screen. Even looping back from ubuntu GRUB2 to Win7 gets blank screen.

Is locale parameter relevant? I have no other idea
 
When I say XP boots, I mean loader starts booting XP, but I finally get an 0x00000000 stop.
It's Acer Multimedia partition, cloned with Clonezilla.

At this moment for me it's not relevant, I performed no search on inet about it, I assume I have to do something else, since it's an originaryly hibernated XP for playing purposes.

The focus is with installed Win7, here's detailed BCD:

Windows Boot Manager
--------------------
identifier {9dea862c-5cdd-4e70-acc1-f32b344d4795}
device boot
description Windows Boot Manager
locale en-US
inherit {7ea2e1ac-2e61-4728-aaa3-896d9d0a9f0e}
default {bd4813b1-4181-11df-9eea-00805a40ba1a}
resumeobject {1f8184a2-14de-11df-9734-f08c6d8c50b0}
displayorder {bd4813b1-4181-11df-9eea-00805a40ba1a}
{bd4813b2-4181-11df-9eea-00805a40ba1a}
{bd4813b3-4181-11df-9eea-00805a40ba1a}
{bd4813b4-4181-11df-9eea-00805a40ba1a}
toolsdisplayorder {b2721d73-1db4-4c62-bf78-c548a880142d}
timeout 10
Windows Boot Loader
-------------------
identifier {bd4813b1-4181-11df-9eea-00805a40ba1a}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7 x64
locale en-US
osdevice partition=C:
systemroot \Windows

Real-mode Boot Sector
---------------------
identifier {bd4813b2-4181-11df-9eea-00805a40ba1a}
device partition=C:
path \NST\AutoNeoGrub1.mbr
description Ubuntu
Real-mode Boot Sector
---------------------
identifier {bd4813b3-4181-11df-9eea-00805a40ba1a}
device boot
path \NTLDR
description XP Multimedia
Windows Boot Loader
-------------------
identifier {bd4813b4-4181-11df-9eea-00805a40ba1a}
device vhd=[C:]\Temp\Acer.vhd,locate=custom:12000002
path \Windows\system32\winload.exe
description NeoSmart VHD Image
locale en-US
osdevice vhd=[C:]\Temp\Acer.vhd,locate=custom:22000002
systemroot \Windows
detecthal Yes
 
If you used CloneZilla, all your partition IDs will be incorrect.

You'll need to deleted the MountedDevices registry key in order to boot into Windows. Not easy - you'll need to mount the registry hive from each Windows from another install in order to do so.
 
Well, I'm not sure if we are talking about the same.
I was warned about GUIDs problem when cloning, so I installed original HDD into a USB adapter and connected it. I got an error in disk administration and selected an option to initialize disk, which seems to change those GUIDs.
Isn't that enough?

Addendum:

I feel quite confused,

After some work, I tried booting from installed Win7 and booted perfectly, with no previous action performed over BCD. Then, after rebooting and nothing done over BCD, I got the same problem, no partition booted, until I deleted the .VHD boot entry.

Addendum:

I have another "idea". Do you think that pluging original disk through USB, generalizing its BCD with the parameters:
bcdedit /store X:\boot\bcd /set {default} osdevice boot
bcdedit /store X:\boot\bcd /set {default} device boot
bcdedit /store X:\boot\bcd /set {bootmgr} device boot
bcdedit /store X:\boot\bcd /set {memdiag} device boot

and then create VHD file again will solve? or is it dangerous? For the moment, that disk boots if i install it again on the laptop. Shall is create VHD file with boot partition or 4 partitions are necessary?

TIA
 
Last edited:
Making drive bootable (i suppose it's "Create bootable media" in bootloader setup) allows me to boot from any partition with de VHD entry, but VHD fails, with 0x0000000d error

My next step would probably be, if there's no other suggestion, re-creating VHD file.

Regards
 
Last edited:
Well, I think checking this box wasn't effective. In fact, it created a Windows 7 entry, with boot partition, like the Win7 x64 recently installed. And booted it, not the VHD file.

VHD file is in that boot partition C:, is it a problem??

Here's the entry:
Windows Boot Loader
-------------------
identifier {bd4813bf-4181-11df-9eea-00805a40ba1a}
device boot
path \Windows\system32\winload.exe
description Windows Acer
locale en-US
osdevice boot
systemroot \Windows
resumeobject {3586bec9-4372-11df-8c5d-806e6f6e6963}
detecthal Yes

 
Thank you so much, your help is really appreciated. I'll wait for next build and test it thoroughly.

BTW, what really bothers me (of course not ur fault) is, after adding sometimes the VHD entry, it allowed me to boot any entry on the system (although VHD returned 0x stop) but only once. Next reboot prompted blank screen after selecting any operating system.

Regards
 
Hi again and sorry for the delay in giving you some feedback, had to change ISP.

The new build worked perfectly, all issues are fixed. BCD entry now looks good, after using portable check, but my laptop keeps the blank screen.
I finally give up trying to boot with my original Win7 on VHD, now I'll try booting it throuth USB, with HDD attached to a case.

...for the moment, all i get is the infamous 7b stop...

BTW, thank you so much again, I've learnt a lot about BCD
 
Back
Top