esSJae's Virtualization Blog

Virtualization and other IT topics

Posts Tagged ‘virtual pc’

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:

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


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.


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

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.

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:

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
    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
Collapse this tableExpand this table
File name File version File size Date Time Platform
Vpcvmm.sys 6.1.7600.16782 296,064 17-Mar-2011 04:44 x86
Vpcvmm.sys 6.1.7600.20926 296,064 17-Mar-2011 06:58 x86
Vpcvmm.sys 6.1.7601.17580 296,192 17-Mar-2011 04:40 x86
Vpcvmm.sys 6.1.7601.21685 296,192 17-Mar-2011 06:57 x86
For all supported x64-based versions of Windows 7
Collapse this tableExpand this table
File name File version File size Date Time Platform
Vpcvmm.sys 6.1.7600.16782 360,704 17-Mar-2011 05:19 x64
Vpcvmm.sys 6.1.7600.20926 360,704 17-Mar-2011 05:19 x64
Vpcvmm.sys 6.1.7601.17580 360,832 17-Mar-2011 05:29 x64
Vpcvmm.sys 6.1.7601.21685 360,832 17-Mar-2011 05:06 x64

Posted in Virtualization, VPC, Win7, Windows | Tagged: , , , , , , | 2 Comments »

How to access XP Mode’s Network Settings

Posted by essjae on January 3, 2012

Changing the Networking settings from Shared Networking (NAT) to the host’s physical network card (NIC) comes up a lot in the forums for XPmode-WinVPC, here are a couple ways to do it.  The XP Mode settings or any WinVPC virtual machine are accessed from Windows 7.  When selecting the NIC you want to use, make sure you select your active NIC.  Your active NIC is the one that is connected to your local network and is how you access your network.  The active NIC can be wireless or wired, or in some cases both your wireless and wired connections may be active.

1. Goto the virtual machines directory on physical computer via explorer, or paste the path below in run or search:

C:\Users\%username%\Virtual Machines

Click once to select XP Mode.  Next, click Settings from the menu bar.    Select Networking.  From the Adapter 1 drop list you can select the host’s active  NIC to allow XP Mode to be on your local network.  You will need an available IP address for XP Mode. 

2. From the XP Mode window, click the Tools menu on the XP Mode window menu.  Select Networking. From the Adapter 1 drop list you can select the host’s active NIC to allow XPMode to be on your local network. You will need an available IP address for XP Mode. 


In this case, the active NIC is a Broadcaom NetXtreme 57xx Gigabit controller.  Your NIC may not be the same.

Click OK to close the window.

Once the setting is changed, you need to trigger XP Mode to release the old IP address can get a new one. If you have DHCP you can: simply reboot XP Mode or drop to a command prompt in XP Mode and do the following commands

ipconfig /release

ipconfig /renew

If you do not have a DHCP server, then you will manually need to enter a unique IP address for XP Mode in the same way you did on your Windows 7 computer.


If you get a 169.x.x.x IP address in XP Mode, there are several things that could be the issue:

1. The network card selected is not the active NIC

2. There are no DHCP servers available to lease an IP address or there are no available IP addresses on your network.

Posted in Virtualization, VPC, Win7, WinXP | Tagged: , , , , , , | Leave a Comment »

Windows VPC Networking Options explained

Posted by essjae on November 30, 2011

Reposted from the Windows Virtual PC help file (it always amazes me how many people ask for explanations about this on the forums, when they have the answer in their local help file):

Configure networking for virtual machines

You can configure networking to provide virtual machines with different types of network connectivity. A virtual machine can have as many as four network adapters enabled, each of which can be configured to use a different type of networking. You can use the following types of networking in a virtual machine:

  • Internal network. This option provides networking between virtual machines only. This type of network connection is useful when you want to provide a networking communications channel to the virtual machines on one physical computer while isolating the virtual machines from all external networks, both wired and wireless, as well as the host operating system.
  • <Network adapter name> (on host operating system). This option is sometimes referred to as “bridged mode”. It uses a physical network adapter to connect the virtual machine to a physical TCP/IP-based network as a separate computer. The virtual machine appears and operates like a separate physical computer on the network. You use this option by selecting the name of the physical network adapter that is connected to the network you want to use. You can choose from both wired and wireless network adapters.
  • Shared networking (NAT). This option is available for the first network adapter in the virtual machine. It allows the virtual machine to share one connection to a physical TCP/IP network with the host operating system. When you use this option, the virtual machine is not listed as a separate computer on the network. This is useful if you regularly move the host between different network configurations, if you want to connect the virtual machine to the Internet through a broadband or dial-up connection used by the host, including a virtual private network (VPN) connection, or if there is a shortage of IP addresses. However, performance is not as fast as the performance offered by bridged mode.
    If the Windows 7 host uses a wireless WAN (WWAN) device to connect to the Internet and you want a virtual machine to be able to use this connection, you must configure the virtual machine to use shared networking (NAT).
A network adapter that is disconnected from all available networks is listed as Not Connected. You can connect a network adapter to a network regardless of the state of the virtual machine. However, a virtual machine must be off before you can add or remove a network adapter—it cannot be running or hibernated. For information about closing a virtual machine, see Close a virtual machine.
To configure networking for a virtual machine
  1. Open the settings for the virtual machine. Do one of the following:
    • In the Virtual Machines folder, right-click the name of the virtual machine, and then click Settings.
    • From the virtual machine window, click the Tools menu, and then click Settings.
  2. In the left pane of the Windows Virtual PC Settings page, click Networking.
  3. To add or remove a network adapter, click the new number of network adapters you want. When you add a network adapter, it is disconnected.
  4. To connect the network adapter to an available type of connection, select it from the drop-down list next to an available network adapter.
  5. Click OK to save the change.


Posted in Virtualization, VPC, Win7 | Tagged: , , , , | 1 Comment »

Script to attach a USB device to a virtual machine [VPC]

Posted by essjae on September 21, 2011

Ben posted this a long time ago, but it’s still important for WVPC

# Connect to Virtual PC
$vpc = new-object -com VirtualPC.Application
# Get VM name
$vmName = Read-host "Specify the name of the virtual machine that you want to use"

# List available USB devices
write-host "The following USB devices are available:"
$vpc.USBDeviceCollection | select -ExpandProperty DeviceString
# Get the USB device name
$usb = Read-host "Enter the name of the USB device that you want to connect to the virtual machine"
# Get the VM object
$vm = $vpc.findVirtualMachine($vmName)
# Get the USB object
$usbDevice = $vpc.USBDeviceCollection | ? {$_.DeviceString -eq $usb} | select -first 1

# Attach the device - this will fail if the VM is not running

Get all the details at Ben’s blog:

You can also download the script from Ben’s page



Posted in Virtualization, VPC, Win7, Windows | Tagged: , , , , , | Leave a Comment »

Updated Windows Virtual PC Installer

Posted by essjae on March 14, 2011

This is a little old, but I’ve been meaning to get this post up.

This is the direct download for the updated Windows VPC installer.  It works with Win7 SP1 and includes the No VT patch.

Posted in Virtualization, VPC, Win7 | Tagged: , , , , | Leave a Comment »

Slow Windows VPC Networking speed/access to hard drive

Posted by essjae on August 8, 2010

This is a little old, but it still pops up from time to time.

If you’re having network speed issues, VPC Genius Bob Comer has the fix:

The problem is TCP Offloading and Windows VPC not getting along, here’s how to work around the problem by turning off offloading:
The fix is to edit the registry, use at your own risk and only if you are comfortable with editing the registry!

To turn off TCP Offloading, add a DWORD value in


label it  DisableTaskOffload , and change the value to 1, then reboot.

Posted in Virtualization, VPC | Tagged: , , , | Leave a Comment »

XP Mode to no longer require hardware virtualization

Posted by essjae on March 18, 2010

Well, it looks like the public was loud enough.  MS has removed the requirement for hardware virtualization to use XP Mode.

From the link: 

“Windows XP Mode no longer requires hardware virtualization technology. This change simplifies the experience by making virtualization more accessible to many more PCs for small and midsize businesses wanting to migrate to Windows 7 Professional or higher editions, while still running Windows XP-based productivity applications.”

The update will be made available later today:

Posted in Virtualization, VPC, Win7 | Tagged: , , , , , | Leave a Comment »

Getting Win95 to run on Windows VPC

Posted by essjae on March 9, 2010

Thanks to Derek Wong, he’s compiled a lot of info on this and posted it on his site.  He sent me an email a long time ago with his results and I just got around to updating my WWADW site.

Links to his procedure and the patch:

Posted in Virtualization, VMWare | Tagged: , , , | 1 Comment »

Missing Physical Adapters for WinVPC: Windows VPC and Kaspersky Anti-Virus NDIS 6 Filter

Posted by essjae on January 21, 2010

After working with someone in the TechNet forums for a week trying to figure out why she couldn’t get the physical NICs to appear in WinVPC, she was finally able to track down that it was the Kaspersky Anti-Virus NDIS 6 Filter blocking them.  “After unchecking it on my host’s Local Area Connection, the Settings for the Networking adapter on my VPC’s had the physical adapter available.”

Thanks Loretta!

Posted in Virtualization, VPC, Win7 | Tagged: , , , | Leave a Comment »

Booting from CD after installing an OS in WinVPC

Posted by essjae on November 30, 2009

After you install an OS in Windows VPC, you’ll notice that you can’t boot from a CD after that…the reason, the boot order is hard drive then CD.  As long as your hard drive (VHD) is bootable, the VM won’t bother with your CD.

It’s fairly simple to change: first you need to get into the BIOS of the VM, to do this, you need to be able to see the VM’s boot window, press SHIFT+ESC as the VM starts to unhide this, next you need to be very quick and press the DEL key to enter the BIOS, as soon as your VM starts, rapidly hit the DEL key.  If you’re successful then you will be rewarded with the blue and gray BIOS screen.  Go to Boot–>Boot device priority, and change the 1st boot device to CD, the BIOS will automatically swap the Hard drive to the 2nd boot device.  Save your changes in the BIOS and now you will be able to boot from a CD or DVD.

Posted in Virtualization, VPC, Win7 | Tagged: , , , | Leave a Comment »