Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


VHD created on Hyper V won't boot as Windows 7 virtual.

Posted on 2012-03-30
Medium Priority
Last Modified: 2012-04-10
I have a fixed size VHD containing a Windows 2008 Standard SP2 (32-bit) NTFS boot and system partition built on Hyper V which runs in 4Gb of RAM on an Intel Xeon E5620 @ 2.40 GHz using a Virtual HA ATA Device as C:.  This VHD boots up with no problems on the Hyper V machine where it was created.

I'm trying to boot it as a Virtual on a 64 bit Windows 7 SP1 6.1.7601 HP Pavilion g6 laptop running on Intel Core i3-2350M 2.30 GHz processor with 6Gb of RAM (tried both 3 and 2Gb for the virtual) and it hangs with a black screen on the first try and when rebooted in Safe Mode it gets to Loaded: \windows\system32\drivers\crcdisk.sys, announces Please wait . . . and then nothing further happens.

I tried using DISM.exe version 6.1.7600.16385 to load the laptops drivers into the VHD by mounting the VHD using disk management and using the command:
DISM.exe /Image:g: /Add-Driver /Driver:c:\windows\inf /Recurse but this gets me an error 50, indicating an unsupported command against a Vista SP1 or Server 2008 target image.  In the DISM log an error "Failed validating command line" is shown.  The host is mysteriously shown in the log as 6.1.7601 running amd64 with 4 processors.  Why would Intel Core i3 show up as amd?  The Hyper V host on which the VHD was created is running on an Intel Xeon E5620 processor. Not that this explains why /Add-Driver is unsupported in DISM.

I've been trying to get this VHD to boot on this laptop for a few days now and would appreciate any help or suggestions.
Question by:VB6chuck
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
LVL 96

Expert Comment

by:Lee W, MVP
ID: 37789617
I haven't tried going from hyper-v to virtual pc, but I'm not surprised you're having issues. They are radically different hypervisors. You'd have a MUCH better chance pulling it into a win8 vm since 8 uses hyperv.  When you want to move vms between vm platforms you should treat them as any other major hardware change and use software designed for hardware independent restores like shadow protect or acronis.

Sorry I can't be of more help other than to say that what you're doing I.don't think will work as the technology wasn't meant to do what you're asking.
LVL 83

Expert Comment

by:David Johnson, CD, MVP
ID: 37790137
amd64 with 4 processors.  Why would Intel Core i3 show up as amd

There are 3 types of processor technology related to this
x86 == normal 32 bit cpu
amd64 = 64 bit operating system (developed by AMD licensed to Intel), most x64 processors are using AMD64 instruction set
Itanium = 64 bit operating system (developed by Intel, not licensed to others, very low usage in the marketplace)

Dism is used for IMAGE files (.wim files) of which a vhd is not

Author Comment

ID: 37796265
After much reading on Technet I'm thinking that the following MIGHT work:

Wait until Windows 8 is available. (don't think I want to do this in beta)
Install a native boot Windows 8 VHD on the laptop described above.  (if such a thing is possible)
Try running the Windows 2008 SP2 VHD in Hyper V under Windows 8.

Is there a high possibility this won't work due to different host hardware?

Alternative is to build a fresh Win 2008 SP2 VHD on the laptop and install 2 large complicated applications.  I have very high expectations that this will succeed, but it's a lot of work to build a disaster recovery solution that I hope the client will never need to use anyway.

I would appreciate feedback on these options . . .
Does Powershell have you tied up in knots?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

LVL 17

Expert Comment

by:James Haywood
ID: 37807233
Can you boot the VM from the original media and run a Startup Repair?

Author Comment

ID: 37809296
Might be able to boot the VM from media and run a Startup Repair, I haven't tried this as the original media used to create the VM is elsewhere.  May consider that line next.

Did get Server 2008 R2 on the laptop as a bootable VHD and have loaded Hyper V and copied a fresh (hash comparison checked) copy of the Server 2008 32 bit VHD onto the laptop drive after defragging the drive (not the fixed size VHD)  it now throws the following 2 errors when I try to start the virtual in Hyper V:

Windows Operating System; Version: 6.1.7600.16385; Event ID: 3430; Event Source: Microsoft-Windows-Hyper-V-Worker User: NETWORK SERVICE
'LaptopSQL' failed to set/change partition property: The system cannot find message text for message number 0xLaptopSQL in the message file for 3D54072C-C747-48B3-8317-2AD96CB888E7. '0x8007013D'.
Windows Operating System; Version: 6.1.7600.16385; Event ID: 3040; Event Source: Microsoft-Windows-Hyper-V-Worker User: NETWORK SERVICE
'LaptopSQL' could not initialize. (Virtual machine ID 3D54072C-C747-48B3-8317-2AD96CB888E7)

This is looking better, I guess.  Any suggestions would be welcome . . .

Accepted Solution

VB6chuck earned 0 total points
ID: 37813355
My situation is that I have a .VHD file created on Hyper V using an Intel® Xeon® Processor E5620 with no AVX which will not boot on a Hyper V equipped Server 2008 R2 host with an Intel® Core™ i3-2350M Processor which has AVX.

My understanding is that the SP1 will enable AVX for both Host and Guest - which might be a problem for the non-AVX guest, or the Hotfix will run a Guest without AVX, which is what I think will solve the problem.  

Perhaps I need just the hotfix (KB2517374) and should not use the SP1?  This is a disaster recovery install so there is no need to support VHD's which need AVX support unless the production Host has a processor upgrade.

Update:  Just the Hotfix is all I need to boot the virtual.  I'll skip SP1 and maybe try it someday on a copy to see what happens.

Problem solved.

Author Closing Comment

ID: 37826794
Information of use is included in the solution.

Featured Post

Enroll in October's Free Course of the Month

Do you work with and analyze data? Enroll in October's Course of the Month for 7+ hours of SQL training, allowing you to quickly and efficiently store or retrieve data. It's free for Premium Members, Team Accounts, and Qualified Experts!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

When you try to share a printer , you may receive one of the following error messages. Error message when you use the Add Printer Wizard to share a printer: Windows could not share your printer. Operation could not be completed (Error 0x000006…
IF you are either unfamiliar with rootkits, or want to know more about them, read on ....
This Micro Tutorial will give you a introduction in two parts how to utilize Windows Live Movie Maker to its maximum editing capability. This will be demonstrated using Windows Live Movie Maker on Windows 7 operating system.
How to install and configure Citrix XenApp 6.5 - Part 1. In this video tutorial we have explained step by step installation of Citrix XenApp 6.5 Server on Windows Server 2008 R2 is explained in this video. We have explained the difference between…
Suggested Courses

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question