Windows Virtual PC Hotfix for AMD Bulldozer Processors
We have just published a hotfix for Windows Virtual PC that addresses a compatibility problem when trying to install on an AMD Bulldozer system.
You can download it here: https://support.microsoft.com/kb/2519949
Cheers,
Ben
Comments
Anonymous
January 18, 2012
The comment has been removedAnonymous
January 19, 2012
It's a hotfix for Windows 7/Server 2008 R2 related to Windows Virtual PC. Meaning it can be applied without Virtual PC installed? Or it needs to be applied only after installing WVPC?Anonymous
January 19, 2012
XPClient - technically, Windows Virtual PC is a feature of Windows. So a hotfix for Windows Virtual PC is actually a hotfix for Windows.Anonymous
January 20, 2012
The comment has been removedAnonymous
January 24, 2012
Was the following bug resolved with this Hotfix:
- when a Differencing VHD is created with Diskpart on the same PC instead of using WVPC Create Virtual Disk feature, WVPC can't boot from it despite its parent wasn't changed, showing message: "One of the parent hard disks of 'L:...Test.vhd' appears to have been modified without using differencing disk." Why such incompatibility with MS own software?
Anonymous
January 29, 2012
The comment has been removedAnonymous
February 02, 2012
I wanted to give a follow-up. I was able to get past my problem by using a dynamic disk instead of a fixed volume size.Anonymous
February 25, 2012
The comment has been removedAnonymous
April 13, 2012
The comment has been removedAnonymous
April 13, 2012
@scubabeme you don't need the OPK. Install VirtualPC, next install the hotfix, reboot and downlaod the XP Mode setup and run it.Anonymous
August 29, 2012
Thanks for sharing this great content, I really enjoyed the insign you bring to the topic, awesome stuff!Anonymous
April 21, 2013
Application of the Hotfix got XP Mode working for me.Anonymous
October 25, 2013
I, too, was misled by the OPK directions (penalized for taking the KB instructions at face value). Once the MS tech sent me the Hotfix link I downloaded, unzipped, clicked Run, then rebooted and can now launch XP Mode in VPC. If anybody at MS is listening, a simple note on the KB Article that consumers simply download and run would have saved me several hours over the course of this week. And neither of the two techs I engaged with via email thought to give me this simple clarification either. In the end it works and is easy enough to employ so I am grateful. Thanks