No USB 2.0 support in Windows Virtual PC for MSI motherboard?

When I try to attach any USB device to USB 2.0 ports in Windows Virtual PC I get the following error message "Could not attach the USB device. you can attach the USB device to a different USB port or restart the VM and try again".Neither different USB port nor restart helps.Win7 Ent 64bit OS is installed on host machine with all the latest drivers and BIOS for this motherboard (MSI B85-G41 PC MATE).Win7 Ent 32bit OS is installed on the guest machine with Integration Components enabled.USB devices work perfectly on host machine and all appear in the USB drop down box in Virtual PC.Where is the problem?

Hi there

FORGET Virtual PC -- use VMware vmplayer (free) -- works far better and supports USB3 as well.
Use VMware converter (also free) to convert virtual PC to VMware format.

Cheers
jimbo

Hi Vsochy, welcome to the Seven Forums.

The error message you get usually means that the USB device you are trying to attach is connected to a USB3 port. Virtual PC's virtual hardware cannot read USB3. As I do not know VMware which Jimbo recommended above, I do not know if it can read USB3.

The simple solution is to connect your USB3 device you want to use on any Virtual PC vm to a USB2 port, It should now attach to vm without any issues.

Kari

to jimbo45: I'll try wmplayer, thanks
to Kari: I know that USB3 is not supported in Virtual PC, but my problem is that USB device (regardless it's USB2 or 3) could not be attached to USB2 ports

OK. Sorry for my assumption, the error message you get is the one shown when a USB3 device is connected to a USB3 port.

What kind of devices you are trying to attach?

kingston usb flash drives, HP webcam, Logitech USB headset, etc. I used them on my previous host machine without any problem.

I removed Intel USB 3.0 driver https://downloadcenter.intel.com/Detail_Desc.aspx?DwnldID=22824&lang=eng&ProdId=3467 and guess what? attach is now working ok on VM, but lost of support for USB 3.0 on host is high price for this It seems that the driver somehow cripple the way 2.0 ports are accessed by guest machine.