VirtualBox USB installation issue on Win 7 64 bit host

[Royaltyrant]

Hello,

I was running VirtualBox 3.0.8 (same problem with 3.0.6 and now with 3.0.10) on a Windows 7 Ultimate 64 bit host (German edition, though the forum-posts show the same problem for users of English editions too). Just upgraded from Vista Ultimate 64 bit (German edition too) where all was ok. Hardware is a Core 2 Quad Intel CPU (Q8300) with 2,53 GHz and 8 GB RAM. I´m using a guest with Win 7 RC 32 bit (no 64 Bit RC available). The guest has 2 GB RAM. At first (then still with VBox 3.0.6, which I had been running under Vista 64 Bit, due to frequent bluescreens in the guest with VBox 3.0.8) everything seemed ok after upgrading the host to Win 7. The VM was starting normal and there were no warnings, etc. When I experienced some bad performance of USB-Gear in the guest (i.e. a Philips Speechmike Pro, LFH 6274) after upgrading from Vista to Win 7 I tried upgrading VBox to 3.0.8. While the VM still starts and runs normally, all USB support for the VM is gone. Changing back to VBox 3.0.6 didn´t help. After installing VBox and starting the VM, the host tries to install "VirtualBox USB" driver but is not succesfull. The host displays a message saying that the driversoftware was not installed, added by "VirtualBox USB Device unplugged". Remember: I´m from Germany an I have a German edition of Windows so the messagetext is my translation; the exact message may differ on nongerman editions of Windows, but the meaning is translated correctly.

Uninstalling and reinstalling VBox did not help (either with 3.0.6 or 3.0.8; I tried it repeatedly). Uninstalling "VirtualBox USB" from the device manager does not help either. Originally "VirtualBox USB" was not even shown in the device manager, even with "show hidden devices" selected, since the host sees it as a disconnected device. I had to add the system variable devmgr_show_nonpresent_devices=1, before it was shown as a greyed out device, which then could be deleted. Needless to say, that I did boot my computer after each attempt to install / uninstall VBox, or USB-Drivers.

I tried VBox 3.0.10, build 54097 (PUEL), when I became aware it had become available today (that was around 10:00 am German local time (GMT +1), but to no avail. It´s still exactly the same story: Wben the VM starts for the first time after installation of VirtualBox, the host shows the usual message, that it has detected a new USB device and is installing devicedriversoftware for it. Then - while the VM is still starting) the host displays a notification, that the devicedriversoftware could not be installed and states, that the device "VirtualBox USB" had been unplugged. After that, the "VirtualBox USB" device is nevertheless shown in the devicemanager as a hidden (but seamingly installed) device (at least, when the proper systemvariables have been set), but no USB support is available for the VM. Mind: the VirtualBox GUI shows USB support as available (at least it is possible to enable USB support, including USB 2, and set a filter for USB devices), but the "VirtualBox USB" device in the host devicemanager remains hidden and greyed out and the VM can not access USB devices on the host. When I try to force access by checking a USB device in the devices menu (my translation again) I just get a message, that the device is busy, due to a previous request (probably the filter from the GUI, still trying to connect the device to the VM). Starting the VM without filter does not help either. It´s just, that in this case on the first try to activate a USB device there happens nothing (including no checkmark in the list of USB devices available on the host) and on every following try I get the "busy" notification. In the devicemanager of the guest none of the USB devices of the host are present.

On further attempts to start a VM, VirtualBox (or probably Win 7) does not again try to install the devicedriversoftware. Further if I try to force a detection for new hardware in the devicemanager of the host it does not see the - running - VM as a new device, even if I manually delete the greyed out "hidden" VirtualBox USB device first. For a new installation attempt of the VirtualBox USB driversoftware to happen I have to uninstall VirtualBox, manually delete the "VirutalBox USB" device in the devicemanager of the host and then reinstall VirtualBox.

Is there a solution????????????????? I really need my VBox USB back.

[Royaltyrant]

VBox.log of VM startup with VBox 3.0.10

[Michel Jung]

Same problem here, my version is German, too.

• Windows 7 x64 (Upgraded from Vista)
• Virtualbox 3.0.10

[Michel Jung]

It works when disabling USB 2.0 support

[Royaltyrant]

1. I tried a clean install of Win 7 to make sure it´s no problem resulting from the upgrade from Vista. But the problem is still there, even on a freshly installed Win 7.

2. I will try disabling USB 2.0 support, as advised by Michael Jung and report back. Anyway I will need USB 2.0 support back, since I use software which needs it.

[Royaltyrant]

I have now tried to use VirtualBox USB without USB 2.0 support enabled. The VM starts and USB (1.1) support is available; it is possible to check USB devices for the VM in the devices menu. However when I try to use USB (for example my usb mike) the VM freezes. The VirtualBox main window on the host is affected too. Only possibility is to close both windows (Sun VirtualBox window and VM-Window) with the task manager. After that the host (i.e. explorer.exe) is affected too and has to be restarted. Mostly normal reboot of the host fails. I have to use the power button to cut off power supply. I tried it several times now. It seems, that even USB 1 support is VERY limited.

Any other suggestions?

[Michel Jung]

I think this needs a higher priority as it is a broken but important feature.

[Royaltyrant]

Replying to Michel Jung:

I think this needs a higher priority as it is a broken but important feature.

Sorry, I´m still new to bugtracker: HOW can I change the tickets priority. I found nothing. Give me a hint and I will upgrade the priority.

[Frank Mehnert]

You can't change the priority, only we can and this is by intension. You can be assured that we are investigating.

[Royaltyrant]

Update: Same Problem with 3.0.12.

[michl]

I have the same problem using USB devices under Win 7 Prof. engl. 64 bit (build 7600) as a host.

Updated today VirtualBox (v 3.0.12 r54655), My guest: win xp 32bit prof. SP 3, Guest Additions installed.

It didn't worked with enabled nor disabled USB 2 support. The error message was as discribed above "VirtualBox USB; Device unplugged" after the installation of a device was canceled in the host.

[skullster]

I have the same problem. Windows 7 Ultimate 64 bit host Windows xp pro sp3 guest. Just updated to 3.0.12 from 3.0.10 the usb devices are listed when I manually click to select one (Epson cx6600 printer the VM crashed and restarted it self. Now its stuck on "windows is starting up" Forced a reset - VM hung following clicking the reset button on the "do you really want to reset" dialog. VBox unresposive - VM screen now greyed out. Forced to close Vbox down via task manager. Vbox GUI not responding. Windows 7 collecting info about the problem. Cancelled after 20 mins! Virtual box hammering the cpu still (quad core 9400) using 75% of core one by the looks of it. Cancelled again in task manager. Then CPU went to 100% all cores. System became unresponsive and could not be soft restarted. Had to manually power down the whole system. On reboot Virtual box would not run intiially then ran at second request. I will attatch the log. It seems USB is a major problem in 64bit hosts and no one iseems interested in fixing it :-(

[skullster]

Restart, crash and full system lockup following adding a usb device.

[Royaltyrant]

Update: The Problem persists with VBox 3.1.0

Is there really no way to write a working USB driver for 64 bit systems?

[skullster]

This is all very annoying! I moved from VMware workstation 6 to VirtualBox to support the product then having used it successfully on Vista 32 bit I moved to Windows 7 64 bit to give access to more memory for virtual machines. Now I find one of Virtual Box's key components does not work properly on 64 bt and seems to have been like that for many versions. Either fix the issue or stop making a 64bit version that you cannot properly support.

[Frank Mehnert]

Calm down. You don't support VirtualBox by just installing it and shouting. An objective comment that it still does not work for you is sufficient. Support for non-paying users is always on a best effort basis. And yes, we are working on a solution.

[skullster]

Ah Frank my appologies for the outburst. I am sure all of us who have the issue and have added a bug will appreciate your comment and the re-prioitisation. If there is anything we can do to assist please leave a note. Thanks for your assistance.

[michaln]

For problems with host lockups, please always note whether the VM was using software or hardware virtualization.

[skullster]

In my case VT-x/AMD-V hardware virtualisation was enabled

[Tony Andrews]

I just noticed something that you may find interesting, related to this issue.

While using my Ubuntu guest OS on VB 3.1.0, I noticed that under the Devices>Floppy Device menu that my usb media card reader, the mass storage device that I am having problems capturing, is listed and can be mounted and accessed in the guest OS as a floppy drive.

Now, this would be a great work-around if I only needed to access the FAT partition on my SD cards, but I also have an ext3 partition on the cards that I need access to. My primary use for the card reader is to mount SD cards through the Ubuntu guest, and use g-parted to format and repartition ext partitions. Mounting through Floppy Device does not allow this scenario.

Also, I believe that the root of the problem may be the AMD USB filter driver that I had installed for my MB. It was not allowing VB to capture the USB device. When I removed that driver, VB could finally see the reader and install the driver.

Unfortunately, without the AMD driver Windows BSODs as soon as VB loads the VB USB driver. Here is the BSOD error, summarized:

A clock interrupt was not received on a secondary processor within an allocated time

STOP: 0x00000101 (0x0000000000000061, 0x0000000000000000, 0xfffff880009e7180, 0x0000000000000001

[Jupp Maifeld]

Hallo

It seamed to be not only a win 7, 64 bit problem. I have the same problem as described above with win 7 (Home Premium), 32 bit and VB 3.1.r55467.

[Donald Skinner]

I am experiencing a similar problem on my Toshiba laptop, running Win7 64bit host with WinXP 32bit as guest, when I connect my scanner via USB. Sometimes the freeze in the guest is immediate, progressing to the Vbox GUI, and then to the host system. CPU on the host is at 100%.

At other times, the guest starts fine, and the scanner software seems to start fine, but eventually bogs down, and the familiar freeze sequence repeats. Again CPU use on host is 100%.

On the host, even a forced shutdown window seldom works. I have to either hold the power button down, or, if I can get to the taskmanager, I can end the wininit service which leads to a blue screen with memory dump.

I had less serious issues with Vista 64bit, but there I would often get screen corruption with USB, and a system freeze. With Vista I was using the latest 3.0 version. Any suggestions how I may assist with diagnosis?

[Donald Skinner]

Further to my previous post, my machine does not support hardware virtualization, even though the GUI says it is enabled. I "disabled" it from the command line so it showed disabled in the GUI, but the problem still occurred as above.

[Donald Skinner]

And further to my 2 posts above...

I had another WinXP guest machine that was experiencing the same problem. In the end the problem produced a corruption in the guest OS. The disk is still readable, but won't boot, and a repair installation keeps failing when it attempts to install networking. It can be hard to get log files if the lockup is too complete, but I am attaching one of the last log files from my first WinXP guest.

[Donald Skinner]

WinXP 32bit on a Win7 64bit host

[crazy]

I have the same problems ==> I'm running win7 64bit as host and windows vista, windows XP as guest machines ... The virtual box version is also 3.1. Reinstalling was also not successful ...

[Ken]

I'm running win7 64 bit as the host and winxp sp3 as a guest. Host machine is an amd dual core opteron with an nforce chipset. I can get the usb drivers to load and at least for a printer it will actually work but the system becomes unstable and will usually lockup with the only way out being the reset button or a power down. I have diabled usb 2.0 support in both the host bios and the vbox settings which was the only way I could get usb to work at all. I have had a couple of BSOD's but that was with usb 2.0 enabled.

[Sander van Leeuwen]

All the reports about hangs and crashes with USB on 64 bits Windows hosts should have been added to #5237. (fix available)

[skullster]

Hi In that case can all the notes here be ported across to #5237? It may help in the fix in 3.1.1 and we would all like to help.

[Sander van Leeuwen]

Test build link posted in #5237.

[Royaltyrant]

#5237 - unfortunately - is not really helpfull. The "fix" there seems to be reverting to 3.0.6. First reverting to an outdated version of vbox is at most a temporary solution. Second - as posted in the original bug report above, the problem with the usb-driver ob a 64 bit host is the same with 3.0.6.

Lets hope somebody will come up with a working driver soon. Until then VMWare Player will have to suffice.

[Sander van Leeuwen]

Royaltyrant: Reread my comment. All the other posters in your ticket are talking about host crashes; not about the problem you describe.

I can't reproduce your problem with Windows 7 x64.

[skullster]

Sandervl73: Part of my issue was a crash in the guest following the hosts inabilty to load the Vbox drivers. So it sounds like Royaltyrant has the same problem but he is getting further than me. Is there anytthing we can do to assist with his problem - provide more info or test a beta?

[Sander van Leeuwen]

skullster: just try the test build please. The bug manifested itself in many ways; from crashing user processes to BSODs and even host reboots.

[skullster]

Sandervl73: Happy to do this - Downloading now I'll report back tomorrow.

[skullster]

Sandervl73: Downloaded 3.1.1r55893 and installed it. When trying to setup the USB printer as before The host says the driver was installed but the printer dwas not added to the guest. When trying to add it again I get an error saying Failed to atatch th usb device Epson usb2.0 MFP to the virtual machine. USB deveice (blah uid etc etc) is busy with a previous request. Please try again later and the following detail :

Result Code: E_INVALIDARG (0x80070057) Component: HostUSBDevice Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a} Callee: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}

This time the gues does not crash and neither does the host. So we are getting somewhere. However the USB devices still cannot be atatched to the virtual machine.

Guest shutdown and logfile atached here for your information.

[skullster]

Test attaching usb printer to xp guest from win7 64bit host.

[skullster]

UPDATE:

Virtual machine restarted and still no crash on host so definate improvement over 3.1.0. Still the same error trying to attach the printer though :-(

Trid another usb device (USB webcam) same problem - device busy with previous request but still no guest or host crash :-)

[Donald Skinner]

Replying to renniks:

I am experiencing a similar problem on my Toshiba laptop, running Win7 64bit host with WinXP 32bit as guest, when I connect my scanner via USB. Sometimes the freeze in the guest is immediate, progressing to the Vbox GUI, and then to the host system. CPU on the host is at 100%.

At other times, the guest starts fine, and the scanner software seems to start fine, but eventually bogs down, and the familiar freeze sequence repeats. Again CPU use on host is 100%.

On the host, even a forced shutdown window seldom works. I have to either hold the power button down, or, if I can get to the taskmanager, I can end the wininit service which leads to a blue screen with memory dump.

I had less serious issues with Vista 64bit, but there I would often get screen corruption with USB, and a system freeze. With Vista I was using the latest 3.0 version. Any suggestions how I may assist with diagnosis?

Apologies. Cancel my "screen corruption" comment, which was a different USB problem unrelated to VBox.

[Donald Skinner]

Replying to sandervl73:

skullster: just try the test build please. The bug manifested itself in many ways; from crashing user processes to BSODs and even host reboots.

Also happy to try the test build and report back tonight.

[Donald Skinner]

Replying to sandervl73:

skullster: just try the test build please. The bug manifested itself in many ways; from crashing user processes to BSODs and even host reboots.

Nice work sandervl73! My test went off very smoothly. USB scanner recognized normally, test scans functioned normally, image files showed up normally. No slowdowns or crashes on host or guest.

The only thing I noticed (and this was also true of earlier versions) is that after exiting the guest and then the VBox gui, my USB scanner was no longer recognized. Device manager displayed an "unknown device". A scan for hardware changes produced recognition, however. This is *not* a major issue for me.

On the whole, so far as I'm concerned: success. I will post a log file.

[Donald Skinner]

Testing USB scanner with test build

[Donald Skinner]

This is the actual full scanner test. Previous attachment was a 2nd and minor test.

[flaker]

Replying to renniks:

Replying to sandervl73:

skullster: just try the test build please. The bug manifested itself in many ways; from crashing user processes to BSODs and even host reboots.

Nice work sandervl73! My test went off very smoothly. USB scanner recognized normally, test scans functioned normally, image files showed up normally. No slowdowns or crashes on host or guest.

The only thing I noticed (and this was also true of earlier versions) is that after exiting the guest and then the VBox gui, my USB scanner was no longer recognized. Device manager displayed an "unknown device". A scan for hardware changes produced recognition, however. This is *not* a major issue for me.

On the whole, so far as I'm concerned: success. I will post a log file.

In my case, just adding empty filters seems to work, otherwise the usb device is hanging there forever, not in my host not in my guest.

[skullster]

Has anyone experienced the USB device problem in host type Windows 2008 server? I am running a VB server on Win2k8 32 bit and want to move the host to 64 bit to use the 16gb RAM the server has installed but use USB drives for backups and other usb devices such as flash drives.

[skullster]

Windows 7 ultimate host - Windows xp 32 bit guest

Update - installed 3.1.2r56127. A change had occurred. When the USB device (Epson 6600cx) is captured in the guest (guest says the usb device is busy) Wndows 7 says its found a new device (I guess this should be the Vbox usb device) it fails to install it. In the client the device state is now shown as captured. But the printer cannot be used If the usb device is clicked from Devices > USB devices in the client a pop up message gives the old failed to attach the USB device Epson USB2.0 Blah blah into the virtual machine XP accounts.

USB device Epson blah blah with uuid 9e7as15b-10b2-482a-a626-cd0a62a5ea3c is busy with a previous request please try later.

However there are no crashed of either the ghost or the guest. Getting closer to a solution by the looks of it. Attaching latest log file

[skullster]

Latest usb capture test log

[skullster]

Update

Now installed 3.1.4 r57640 issue still the same. Windows 7 cannot install the VirtualBox USN driver and fails. USB devices are busy in VirtualBox when trying to attach. Those manually added in via settings cause previous error messages.

Any word on this issue its all been very quiet here.

[skullster]

Searching through the open Bugs I cannot see anywhere that this bug has been fixed. I suppose as the ticket is still open its work in progress but could someone give us an update please?

[dokov]

In new version 3.2.0 issue is still actual.

USB doesn't work with windows 7 64 bit host and windows XP sp3 guest.

USB is not monitored nor is it updated. When attemted to capture an USB device it silently fails and on the secdond capture attempt fails with attached error. The logs show no trace of the event.

[Donald Skinner]

Replying to flaker:

In my case, just adding empty filters seems to work, otherwise the usb device is hanging there forever, not in my host not in my guest.

It's been a while since I've checked in here, but also in my case, adding an empty usb filter works well. I have to specifically select it from the Vbox GUI once the guest is running, but then it comes up as the device that is attached and all works very normally. Upon exiting the guest, control of the device returns to the host with no problems. Mind you, I'm still using version 3.1.4r57640. I'll upgrade, and then post again.

[skullster]

I can also confirm that using 3.2.0 r61806 that adding a blank USB filter allows the 64bit windows host to pass over usb devices. Perhaps on creation of a guest from a 64bit host a blank filter should be automatically created to save other users trawling for the solution.

[Chuck]

I can confirm that adding a blank usb filter works for me in 3.2.6 r63112. I have Windows 7 Enterprise 64-bit host with Windows 7 Professional 64-bit guest and have never been able to get USB capture working - usually locks up the guest machine and then takes down the VirtualBox GUI. I had tried creating a filter specific to my USB Device (a Microsoft OAK USB Telephone) and that failed. Applying skullster's fix of a blank USB filter - deleted all my other USB filters as well, this worked flawlessly. This definitely needs to be documented as a workaround/fix

[Lutz Weidhase]

Since upgrading to Win 7 / 64bit I have the same problem. No USB-device works in the gast. This evening, I disabled the UAC (for germans like me: Benutzerkontensteuerung) in Win 7 and now it works. But this can't be the solution, only a workaround. The solution have to provide the developers of Virtualbox...

Kind regards Taste

[ddn]

i got USB issues too. its going from long long versions ago i started using USB passthrough at VB 3.1.x and same thing on last 3.2.8 build: summary: first USB device insertion to guest always fails in host vboxusbflt driver installation. I i reboot host system completely and process again - all fine (vbox driver succeess installs) So for any new USB device that i want to passthrought to guest VM i must reboot host after first usb use.

HOST windows 7 64bit with 8 gigs of RAM, CPU = Interl q6600 with VT-X enabled. GUEST - any! from windows xp to windows 2008R2.

[aftyde]

Config - Win 7 professional 64 bit running r64453 Have tried everything - even following the instructions... :) Reinstalled, reinstalled guest tools - nothing works. USB is clearly broken and completely non-functional.

VMware on the other hand works just fine. Any chance of this feature working - I'd have to move back to VMware? Seems like the problem has been around for over a year. How is it possible that USB support can be completely and utterly broken for a year?

Cheers, Arthur...

[Dominik]

Hi !

Just want to let you know that I have exact the same problem. Host is win7 64Bit Ultimate. Guest is Win7 32 Bit with installed guest tools.

I can´t get only one device running within the VM.

Is there any solution to come in the near feature?

Greetz Dominik

[someguy]

just to let people know what fixed the issue for me:

host: win7 64bit, oracle vm virtualbox 3.2.10 r66523

guest: winxp sp3 b2600, guest-addons installed, vt-x on

disconnect usb-device, reboot host, create new blank usb-filter in virtualbox, start guest, reconnect usb-device. (works for synchronisation of an iphone via itunes 10.0.1.22)

[skullster]

Windows 7 64bit ultimate host Windows XP pro 32 bit guest - Running 3.2.10r66523 the USB issue remains. The blank filter works for one device but it still messes up if you want to remove that device form the VM to use on the host. The non captured devices in the list all show as busy and selecting them causes an error installing drivers on the hoist. This really is a pain. Are there any plans to fix this issue?

[4am]

Replying to skullster:

Sandervl73: Downloaded 3.1.1r55893 and installed it. When trying to setup the USB printer as before The host says the driver was installed but the printer dwas not added to the guest. When trying to add it again I get an error saying Failed to atatch th usb device Epson usb2.0 MFP to the virtual machine. USB deveice (blah uid etc etc) is busy with a previous request. Please try again later and the following detail :

Result Code: E_INVALIDARG (0x80070057) Component: HostUSBDevice Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a} Callee: IConsole {6375231a-c17c-464b-92cb-ae9e128d71c3}

This time the gues does not crash and neither does the host. So we are getting somewhere. However the USB devices still cannot be atatched to the virtual machine.

Guest shutdown and logfile atached here for your information.

We're on 4.0.2 here and getting the same thing. I need USB for my APC BackUPS (small server). Is this ever going to be fixed?!?

Result Code: 
E_INVALIDARG (0x80070057)
Component: 
HostUSBDevice
Interface: 
IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: 
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}

[ptar]

Same problem here on a Win7 64-bit host with 64-Bit-Kubuntu or 32-Bit-Win XP guests (using Virtualbox 4.0.2 + extpack)
The Virtualbox manager doesn't even recognize changes due to attached/removed USB devices. It seems to read them on start and then they're fixed (and useless). The host system has USB 3 devices on-board, but the devices tried to attach where USB 2 at the USB 2 sockets. Does that matter somehow?

A Virtualbox 4 on a Kubuntu 64-Bit host (without USB 3) has no problems with USB devices.

[jeff]

The following fixed the issue for me. (Note: I have 2.0 turned off and a blank filter, I don't know if that helps or not)

0. Shutdown any instances of VirtualBox and any other processes related.
   
1. Disconnect the device that you are using from your host machine.
   
2. Start your VirtualBox Guest machine.
   
3. Wait for the machine to boot up completely.
   
4. You may have to install the VirtualBox USB drivers, right click on the USB icon or select from the dropdown device list, this should start the process. I am not sure on this step since I did not need to do this when I figured out the fix.
   
5. Now connect the USB device to your host machine.
   
6. For me the connection was already made under the USB devices, but you may also have to select the USB device.
   

Mostly taken from here: ​http://forums.virtualbox.org/viewtopic.php?f=3&t=19656

[4am]

@moosen - I've tried that, same settings (2.0 off and blank filter), shut down VBox completely, unplug device, restart guest, plug in device. It never shows up in the USB menu or the Devices menu.

I'm having the issue where devices are read at start-up and then never read again it seems - I can plug in and unplug devices and they never change in the Devices menu. Selecting one results in the error message:

Failed to attach the USB device Unknown Device to the virtual machine The-VMs-Name

Result Code: 
E_INVALIDARG (0x80070057)
Component: 
HostUSBDevice
Interface: 
IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a}
Callee: 
IConsole {515e8e8d-f932-4d8e-9f32-79a52aead882}

[netsrac]

Same problem here. Newest Version 4.0.4, disabling USB 2.0 support doesn't work. When will there at long last a solution??

[Brandon]

Ditto. Just d/l'd VB today, installed Win7 64bit as guest OS. No USB connectivity. I am trying 'moosen's advice now to see if it does the trick.

Likewise I don't appear to be able to utilize Serial ports either. I have enabled them and set them to 'Host Device' - 'COM1' as path, and I get nothing in the guest OS's device manager showing that it has some COM ports.

Replying to netsrac:

Same problem here. Newest Version 4.0.4, disabling USB 2.0 support doesn't work. When will there at long last a solution??

[skullster]

This seems to still be an issue in the latest 4.0.10 r72479

Are there really no fixes??

[Frank Mehnert]

There are. Have a look at the ​Beta of VirtualBox 4.1. Beta 1 already contains fixes, Beta 2 (out soon) will contain an additional ​fix.

[skullster]

YAY! With v 4.1.0 and associated extension pack usb 2 works at last on Windows 7 46bit ultimate. Well done! Use printer detected and can be associated and de-associated as can usb drives no problems so far.

[Daniel]

Unfortunately, 4.1.0 didn't solve the issue for me. I can no longer mount some USB devices.

Host: Win7 Pro 64bit (De)
Guest: Win XP SP3 (De)

However, USB mass storage devices (such as usb sticks) can be mounted, but a usb scanner as well as a usb printer can no longer be mounted. The disappointing thing is that these devices worked properly a few weeks ago. I was running 4.0.8 then, but I'm not sure if it's related to the VB version, I rather suspect that it might be related to some other usb device driver installations on the host system (i was installing a new system from scratch during the last weeks).

The mentioned trick above from 'someguy' with the blank filter worked exactly once for me; after the next boot of the guest system the usb devices could not be mounted again. However, they are still in the usb devices menu, but when I try to mount them I get the well known error

Failed to attach the USB device Unknown Device to the virtual machine MyVM.

USB device 'Canon CanoScan' with UUID {...} is busy with a previous request.

E_INVALIDARG (0x80070057)
...

Any help on this is much appreciated.

[misha]

Unfortunately we are unable to reproduce the problem here. I can give you a link to the instrumented build that contains verbose logging for USB subsytem so you can collect the log and post it back to me for analysis so we can detect the problem.
If you are willing to test it, please drop me a mail at mikhail dot sennikovsky at oracle dot com I'll then post you a link to the test build with instructions on how to collect the log.

[Daniel]

misha, thanks for your quick reply. I'm on travel next weeks and I won't have a chance to do something, but I'll gladly test more and send you the log files when I'm back. I sent you a mail right before. Thanks.

[John Silver, Esq.]

Hello,

I have the same problem (host: Windows 7 Enterprise 64 bit (version 6.1.7600), guest: Windows XP SP2, VB: 4.1.6 r74713). Under the guest system I'm whorking with application which uses special USB hardware.

Earlier my host's OS was Windows XP SP2 32 bit, and I had no problems with attaching the mentioned hardware, but my PC was replaced with new one and now I cannot attach the USB device: the VB reports the following error: "Failed to attach the USB device Unknown device xxxx:yyyy to the virtual machine zzz. USB device <'unknown'> with UUID {nnn} is busy with a previous request. Please try again later".

I tried to connect/disconnect USB hadware before/after booting host/guest OSes in different combinations, but it has no effect.

[Steve]

I have the same issues:

1. VBox 4.1.6 r74713
   
2. Host - Win7, 64b (Dell Latitude E6250
   
3. Guest - Ubuntu 11.10, 64b
   
4. Checking the usb2 features does not seem to have any effect
   
5. Having an empty filter does not seem to have any effect
   

Most all my USB devices work. However I'm developing on a TI Blaze Android development platform and one of the USB devices does not work.

• The device serial-over-USB port always works.
  
• - It gets captured and works always.
  
• - Windows is able to assign drivers to this whenever captured by guest or left for the host.
  
• - ">sudo lsusb" always finds this in the guest.
  

• This second port in 'normal' mode has a separate USB port that works also.
  
• - Captured by the device, shows up with lsusb
  
• - When left for the host, the windows driver works.
  

• The second port in 'fastboot' mode,
  
• - When left for the host works and finds the driver.
  
• - When assigned to the guest, it lists it as being captured (the checkbox is checked.)
  
• - HOWEVER it does not show up with ">sudo lsusb"
  
• - *If* I uncheck the box, then windows complains that it cannot assign a driver. E.g. if I give it back to the host, the host now no longer recognizes it.
  
• - - I try to manually assign a driver to it from VBox, and Win7 will neither accept the device nor filter drivers.
  
• - - If I try to capture it back by VBox, then I get the familiar message that it is busy.
  

There are two things that are particularly strange to me.

• 1. When more or less working (i.e. windows host finds the correct VBox driver and its captured by VBox) why does lsusb not find it? What intermediate state can it be in?
  
• 2. When going back to windows, why is the device now unknown?
  

Anyway, I supply this information in the hopes that it may help someone (and possibly myself.)

[GK64]

Same issue. Win7 64 bit Ultimate, latest VirtualBox. Bug open for 3 years and counting? I'm working through Oracle Jdeveloper ADF Mobile but can't even deploy to a Nexus 7 tablet for testing. Moving on to non-oracle software...

[cnaaa2013]

Replying to GK64:

Same issue. Win7 64 bit Ultimate, latest VirtualBox. Bug open for 3 years and counting? I'm working through Oracle Jdeveloper ADF Mobile but can't even deploy to a Nexus 7 tablet for testing. Moving on to non-oracle software.

Virtualbox doesn't support USB3.0 controllers by now. I have a notebook with Win7 64bit ultimate and USB3.0 and I disabled USB3.0 function in BIOS setting. Then it works fine with my usb2.0 storage.

[T Kamizi]

Hi everyone, I have had the same problem and I tried with two different USB 3.0 devices. The thing is, I think that was the problem, because when I changed to USB 2.0 it worked immediately (although you need to have the USB 2.0 support enabled before booting your VM).

So if nothing else works for your USB 3.0, try a USB 2.0 device instead! :)

PS. All my USB ports in my laptop are USB 3.0...

[aeichner]

Please reopen if still relevant with a recent version of VirtualBox.