You cannot install Windows XP Mode on a Windows 7-based computer that has an AMD Bulldozer-based multicore processor installed

Article ID: 2519949 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you have an AMD Bulldozer-based multicore processor installed on a computer that is running Windows 7, you cannot install Windows XP Mode. Additionally, you receive an error message that resembles the following:
Could not complete Setup. Please try again.

CAUSE

This issue occurs because of a compatibility issue between Windows XP Mode and AMD Bulldozer-based multicore processors.

RESOLUTION

Hotfix information

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.

Note If 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:
http://support.microsoft.com/contactus/?ws=support
Note The "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.

Prerequisites

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:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Installation instructions

To resolve this issue for OEM partners, integrate the hotfix package into the installation image of Windows 7. To do this, follow these steps:
  1. Download all the necessary files and tools. To do this, follow these steps:
    1. Install the Windows 7 OEM Preinstallation Kit (OPK).
    2. Copy the hotfix package to a folder on the computer. For example, copy the package to the folder C:\Test\Updates. 
    3. 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. 
  2. Add the hotfix to a Windows 7 image. To do this, follow these steps:
    1. Click Start, click All Programs, click Windows OPK, right-click Deployment Tools Command Prompt, and then click Run as administrator.
    2. 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
    3. Notice the index number or the name of the Windows 7 image to which you will add the hotfix.
    4. 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.
    5. 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
    6. 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

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

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.

File information

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
    VersionProductMilestoneService branch
    6.1.760 0.16xxxWindows 7RTMGDR
    6.1.760 0.20xxxWindows 7RTMLDR
    6.1.760 1.17xxxWindows 7SP1GDR
    6.1.760 1.21xxxWindows 7SP1LDR
  • 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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Vpcvmm.sys6.1.7600.16782296,06417-Mar-201104:44x86
Vpcvmm.sys6.1.7600.20926296,06417-Mar-201106:58x86
Vpcvmm.sys6.1.7601.17580296,19217-Mar-201104:40x86
Vpcvmm.sys6.1.7601.21685296,19217-Mar-201106:57x86
For all supported x64-based versions of Windows 7
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Vpcvmm.sys6.1.7600.16782360,70417-Mar-201105:19x64
Vpcvmm.sys6.1.7600.20926360,70417-Mar-201105:19x64
Vpcvmm.sys6.1.7601.17580360,83217-Mar-201105:29x64
Vpcvmm.sys6.1.7601.21685360,83217-Mar-201105:06x64

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows 7

Additional files for all supported x86-based versions of Windows 7
Collapse this tableExpand this table
File nameUpdate.mum
File versionNot applicable
File size1,917
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameX86_3b601baef0e168e225c463ccb7209540_31bf3856ad364e35_7.1.7600.16782_none_881344cfb1df57c5.manifest
File versionNot applicable
File size701
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameX86_81bc1a975c5511f595da1f4b5a2e707e_31bf3856ad364e35_7.1.7601.21685_none_e8fd731600977f04.manifest
File versionNot applicable
File size701
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameX86_bd9dbdbee6a4ba2e71a404ca490cf19e_31bf3856ad364e35_7.1.7601.17580_none_f93ba0a29cd468e2.manifest
File versionNot applicable
File size701
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameX86_c3031a9029e82d02e90fdb67aaacce4d_31bf3856ad364e35_7.1.7600.20926_none_f43bb33798fa22fc.manifest
File versionNot applicable
File size701
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameX86_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7600.16782_none_397da2f4452b3b68.manifest
File versionNot applicable
File size2,913
Date (UTC)17-Mar-2011
Time (UTC)05:12
PlatformNot applicable
File nameX86_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7600.20926_none_3a4c22555e14960f.manifest
File versionNot applicable
File size2,913
Date (UTC)17-Mar-2011
Time (UTC)07:22
PlatformNot applicable
File nameX86_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7601.17580_none_3b61ff66425374a6.manifest
File versionNot applicable
File size2,913
Date (UTC)17-Mar-2011
Time (UTC)05:11
PlatformNot applicable
File nameX86_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7601.21685_none_3bf09da35b6c9323.manifest
File versionNot applicable
File size2,913
Date (UTC)17-Mar-2011
Time (UTC)07:26
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7
Collapse this tableExpand this table
File nameAmd64_0ec100d8154de7db3d3fbce79decfcdd_31bf3856ad364e35_7.1.7601.17580_none_231a7e4e49a7ff16.manifest
File versionNot applicable
File size705
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameAmd64_352a38f934e207576a553faed0103803_31bf3856ad364e35_7.1.7600.20926_none_ca11c0b12f68939a.manifest
File versionNot applicable
File size705
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameAmd64_3571feb14fb71059a67b84ba6270770d_31bf3856ad364e35_7.1.7600.16782_none_aba7d2abbcfd2210.manifest
File versionNot applicable
File size705
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameAmd64_460b504f42bf1c7595f03af9bb1b9cee_31bf3856ad364e35_7.1.7601.21685_none_1fd5e5a3d010d8ee.manifest
File versionNot applicable
File size705
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable
File nameAmd64_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7600.16782_none_959c3e77fd88ac9e.manifest
File versionNot applicable
File size2,917
Date (UTC)17-Mar-2011
Time (UTC)06:22
PlatformNot applicable
File nameAmd64_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7600.20926_none_966abdd916720745.manifest
File versionNot applicable
File size2,917
Date (UTC)17-Mar-2011
Time (UTC)08:25
PlatformNot applicable
File nameAmd64_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7601.17580_none_97809ae9fab0e5dc.manifest
File versionNot applicable
File size2,917
Date (UTC)17-Mar-2011
Time (UTC)06:02
PlatformNot applicable
File nameAmd64_microsoft-windows-virtualpc-vmm_31bf3856ad364e35_7.1.7601.21685_none_980f392713ca0459.manifest
File versionNot applicable
File size2,917
Date (UTC)17-Mar-2011
Time (UTC)08:22
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,929
Date (UTC)17-Mar-2011
Time (UTC)21:30
PlatformNot applicable

Properties

Article ID: 2519949 - Last Review: January 18, 2012 - Revision: 2.0
APPLIES TO
  • Windows 7 Enterprise
  • Windows 7 Professional
  • Windows 7 Ultimate
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2519949

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com