Hotfix for Windows Virtual PC and AMD Bulldozer based CPUs
Posted by essjae on January 19, 2012
If you have an AMD Bulldozer based CPU, you probably can’t install Windows VPC successfully. AMD Bulldozer based CPUs includes the new FX series (FX-8170, FX-8150, FX-8120, FX-8100, FX-6200, FX-6120, FX-6100, FX-4170, FX-4150, FX-4120, FX-4100)
Microsoft released a hotfix yesterday for this: http://support.microsoft.com/kb/2519949
You cannot install Windows XP Mode on a Windows 7-based computer that has an AMD Bulldozer-based multicore processor installed
A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a “Hotfix download available” section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
NoteIf additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:
NoteThe “Hotfix download available” form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
To apply this hotfix, you must be running Windows 7 or Windows 7 Service Pack 1 (SP1).
For more information about how to obtain a Windows 7 or a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
To resolve this issue for OEM partners, integrate the hotfix package into the installation image of Windows 7. To do this, follow these steps:
- Download all the necessary files and tools. To do this, follow these steps:
- Install the Windows 7 OEM Preinstallation Kit (OPK).
- Copy the hotfix package to a folder on the computer. For example, copy the package to the folder C:\Test\Updates.
- Copy the Install.wim file from the Windows 7 installation media to the computer. For example, copy the Install.wim file to the folder C:\Test\Images.
- Add the hotfix to a Windows 7 image. To do this, follow these steps:
- Click Start, click All Programs, click Windows OPK, right-click Deployment Tools Command Prompt, and then click Run as administrator.
- At the command prompt, retrieve the name or the index number for the image that you want to change. To do this, type the following command, and then press Enter:
Dism /Get-WIMInfo /WimFile:C:\test\images\install.wim
- Notice the index number or the name of the Windows 7 image to which you will add the hotfix.
- Use a DISM command to mount the image by using the index number or the name that you noticed in step 2C. For example, the index number of the image to which you will add the hotfix is 3. The following command mounts Index 3 to a folder that is named “offline” in the test directory:
Dism /Mount-Wim /WimFile:C:\test\images\install.wim /Index:3 /MountDir:C:\test\offline
Note You must create the C:\Test\Offline folder before you mount the image.
- At the command prompt, type the appropriate command to add the hotfix, and then press Enter.
For x86-based versions of Windows 7:Dism /Image:C:\test\offline /Add-Package /PackagePath:C:\test\updates\Windows6.1-KB2519949 -x86.msu
For x64-based versions of Windows 7:Dism /Image:C:\test\offline /Add-Package /PackagePath:C:\test\updates\Windows6.1-KB2519949 -x64.msu
- At the command prompt, type the following command to commit the changes and to unmount the image, and then press Enter:
Dism /Unmount-WIM /MountDir:C:\test\offline /Commit
To use the hotfix in this package, you do not have to make any changes to the registry.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 file information notes
- The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Collapse this tableExpand this table
Version Product Milestone Service branch 6.1.760 0.16xxx Windows 7 RTM GDR 6.1.760 0.20xxx Windows 7 RTM LDR 6.1.760 1.17xxx Windows 7 SP1 GDR 6.1.760 1.21xxx Windows 7 SP1 LDR
- GDR service branches contain only those fixes that are widely released to address widespread, very important issues. LDR service branches contain hotfixes in addition to widely released fixes.
- The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the “Additional file information for Windows 7” section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are very important for maintaining the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
|File name||File version||File size||Date||Time||Platform|
For all supported x64-based versions of Windows 7
|File name||File version||File size||Date||Time||Platform|