up vote 30 down vote favorite
4
share [g+] share [fb]

I'm trying to install Windows 8 on my pc via Microsoft Virtual PC. However I get this annoying, non-descriptive error:

enter image description here

I'm looking to find out if Microsoft Virtual PC supports Windows 8, and if so how do I solve this issue?

NOTE: I'm NOT trying to ask for alternatives to Virtual PC, but rather trying to figure out if it's possible, and if so how, to use Virtual PC.

link|improve this question
72% accept rate
1  
I'd say "HAL INITIALIZATION FAILED" is descriptive, if not terribly good at narrowing it down. :) – Shinrai Sep 14 '11 at 20:42
5  
gotta love the new-style BSOD – Sathya♦ Sep 15 '11 at 5:06
@techie007 I've added a note to caution users to answer the actual question I'm shooting for, and not the dupe. – KronoS Sep 15 '11 at 16:20
1  
Do we need to coin a new acronym for the new version of the BSOD? I'd say BSOF, "Blue Screen Of Fail", should be a contestant. – music2myear Sep 28 '11 at 19:57
feedback

6 Answers

up vote 23 down vote accepted

Steven Sinofsky, head of Windows, wrote a blog post titled Running Windows 8 Developer Preview in a virtual environment where he goes into the subject in detail. It's a good read. Halfway down he says:

"... our baseline assessment is as follows:

Functional:

  • Hyper-V in Windows 8 Developer Preview
  • Hyper-V in Windows Server 2008 R2
  • VMware Workstation 8.0 for Windows
  • VirtualBox 4.1.2 for Windows

Non-functional:

  • Microsoft Virtual PC (all versions)
  • Microsoft Virtual Server (all versions)
  • Windows 7 XP Mode
  • VMWare Workstation 7.x or older"

So no, Microsoft Virtual PC does not official support Windows 8. If an unofficial hack comes out and gets it running, it will probably be a sub-par experience, but a cool trick none-the-less.

Update: It does seem odd that they wouldn't support their own product until you realize that they are getting rid of Virtual PC in favor of Hyper-V which will be included with the Windows 8 client. So it's actually an upgrade.

link|improve this answer
3  
Weird that Microsoft's own virtual machine doesn't support one of it's products. – KronoS Sep 28 '11 at 17:28
feedback
up vote 21 down vote

Windows 8 requires a new ACPI functionality mode (ACPI 2.0) which is not supported at all in many virtualisation products.

Thus far, I have only been able to get it working inside of VMWare Workstation 8 (which for some coincidence was launched today!).

I have just tested and it will also work in the newest version of VMWare Player (Version 4.0.0 build-471780).

If you want a free solution, I found a guide (located here) earlier today with instructions on how to get it working in Virtual Box.

link|improve this answer
1  
It also works in Hyper-V on Windows Server 2008 R2. – William Jackson Sep 14 '11 at 20:53
1  
It works in VirtualBox – Joel Coehoorn Sep 28 '11 at 1:32
feedback
up vote 8 down vote

I set it up in Virtual Box the latest version choosing Windows 7 64 bit as the "Version" under "VM Name and OS Type". It installed first try. I hope this helps.

You can not run Windows 8 in Virtual PC because it (Windows 8) does not support VPC. MSDN

link|improve this answer
feedback
up vote 5 down vote

You can use a Virtual HD.

Scott Hanselman's baby-steps solution here:

http://www.hanselman.com/blog/GuideToInstallingAndBootingWindows8DeveloperPreviewOffAVHDVirtualHardDisk.aspx

link|improve this answer
feedback
up vote 2 down vote

Yes. You will be able to install a virtualized instance of Windows 8 (provided you have a working, valid copy), in virtual applications like VirtualBox (free) and VMware Workstation 8 (paid).

Note: Previous versions of VMware Workstation are not able to run Windows 8, you will need the newer version, which currently is VMware Workstation 8

Also note that to virtualize Windows 8 Developer Preview you need hardware acceleration supported by your hardware.

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.