Change History

I have the same issue with USB in virtualbox 4.2.6, host OS is Windows 8 64, guest OS is Windows XP Pro 32 bit. Trying to attach any USB device does not bring any visible results, and futher efforts to do this cause an error message telling that device is busy, for example: "USB device 'JetFlash Mass Storage Device' with UUID {0bfa92ef-936c-4558-ab6a-5e04b2bf3777} is busy with a previous request. Please try again later."
I have got this problem only on Windows 8 host, I have never seen it in other host OS, such as Windows XP, Windows 7, Ubuntu 12.04, Ubuntu 12.10. Log is attached as "Vbox.log.1".
Waiting with hope for solution of this problem.

Similar problem with Macbook pro running Mac Os 10.8.2 and VB 426 with windows 7 or windows 8 on the top of it. Any USb device is not launched and a driver problem is reported. Really a big problem for me,

I think this is right context and set of symptoms to match my own experience. Host is WIndows 7 x86_64, Guest is Fedora 20. VB 4.3.x won't mount my HTC phone via USB, complaining of being busy. Reverting to 4.2.16 ~Resolves The Problem~. However, my kernel is then too recent for 4.2.16 so that version of VB doesn't want to support shared folders. Rather than downgrade the kernel I un-reverted (?) to the most recent VB 4.3. Once again, no USB.

Is there anything I might submit that would be of help? It seems to me that I've got a "critical case" potentially useful to root cause analysis.

BTW, my USB is 2.x, not 3.x. At the moment, I'm plugged into a slow 2.x port and Windows is trying to teach me to do otherwise.

The same issue still exists in 5.0.20 ,
Host is Windows 7 64 bit , guest is Ubuntu 14.0.4LTS 4.2.0.36 kernel
Prolific USB to Serial :0300
work around is with USB filter for the Prolific
but when you have more than one Prolific cable and you want to use one on the host and one the Guest is a bit more tricky when plugin and unplug the cables

The same issue also exists in 5.0.20 on Windows 7 Professional (Host) with guest Windows 7 Professional with all PEAK PCAN USB dongles und KEIL ulink (1/2 and ME) adapters.

When a filter for the adapter is applied, the device can indeed be used in the VM, but disconnect or connect of a device is in operation of the VM impossible. If you try this, the device in both systems blocks.

Additional Informations: (disconnect Peak Adapter via usb device Manager and try to capture it after one minute again). In both systems the Adapter is not available anymore, up to this moment then i'm closing the VM.

Thank you sgraves!! I have been searching on here for a day and a half, and your mention of the UpperFilters key issue was the first I had seen anywhere....it fixed my problem of an XP SP2 guest on a Win 7 Pro host always having USB device status of "Busy"...

I still have this issue. I have tried the solution specified here and others. I have not been able to get any USB device forwarded from my Windows 10 host to my Arch linux guest.

As described above, I am able to get a device into the "captured" state which prevents Windows from accessing the device but it never appears in the guest. Trying to "reattach" the device by selecting it again via the USB menu results in the busy error described.

Using a filter instead means the device is always "captured" but I am unable to detect it in the guest.

I've tried the following to resolve this issue, all with no success;

A few different ports of both USB3.0 and USB2.0.

USB2.0 and USB3.0 settings on the machine settings.

Manually installing VirtualboxUSB driver

Deleting HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{36fc9e60-c465-11cf-8056-444553540000}\UpperFilters as described here and on this bug.

Alternative devices (other USB sticks and keyboards).

More permissive USB filters.

Disabling device in "Device Manager" before attempting to attach in VirtualBox.

Plugging in USB device in at different times; before starting virtualbox, before starting vm, after starting vm.

Please let me know if there's anything else I can attempt to help debug this issue.

So interestingly today I installed a new standalone USB3.0 card and attempted the same thing and everything worked as expected on the ports connected to that new card.

So this issue only affects the USB3.0 devices connected to the Asus Mobo. Everything else works fine on the Asus ports afaik, so this only seems to be an issue when these ports are used with Virtualbox.

Figured out why my Virtualbox VM's were all saying USB devices were all busy.
Last week I installed a new version of Wire shark that comes with USBPcap.
Turns out Virtualbox and USBpcap don't like each other very much...

Uninstalled USBPcap and my USB pass through on my VM's all started working again.

Figured out why my Virtualbox VM's were all saying USB devices were all busy.
Last week I installed a new version of Wire shark that comes with USBPcap.
Turns out Virtualbox and USBpcap don't like each other very much...

Uninstalled USBPcap and my USB pass through on my VM's all started working again.

VLNinja, you are a genius. This fixed my problem to, uninstalled usbPcap, rebooted and all is well. I wonder if the wonderful folks over at VBox/Oracle could put a check in for this and report it to the user, or at least put it in an FAQ somewhere as something to try if there are USB problems.

Figured out why my Virtualbox VM's were all saying USB devices were all busy.
Last week I installed a new version of Wire shark that comes with USBPcap.
Turns out Virtualbox and USBpcap don't like each other very much...

Uninstalled USBPcap and my USB pass through on my VM's all started working again.