Upgrade breaks all USB support

[Jason]

Upgrading from 2.2.0 to 2.2.4 renders all USB support inoperable. After a reboot, VirtualBox reports this issue: {{{Failed to access USB subsystem.

Could not find the Host USB proxy service (VERR_FILE_NOT_FOUND). The service might not be installed on the host computer.

Result Code: E_FAIL (0x00004005) Component: Host Interface: IHost {926469ca-9091-42ef-928e-582d78b66c70} Callee: IMachine {13420cbb-175a-4456-85d0-301126dfdec7} }}}

The only way to resolve this is to attempt a repair install (not possible in the normal way, see bug 4206) and reboot. This may need to be done more than once.

Even after the USB sub-system has been recovered, USB functionality is not immediately available. The guest will not list defined USB items (i.e. they have filters) under "Devices/USB Devices" until the item has been attached to the host and the VB drivers installed again. After this the guest will need to be restarted from fresh to have the device work (see bug 3033).

[Frank Mehnert]

This sounds like the VirtualBox USB support was not properly installed. Try to re-install VirtualBox with enabled ​MSI logging.

[Jason]

I have already got USB working by re-installing. I am afraid I did not know about MSI logging when I did this, so I do not have any log files.

The service was installed and working on 2.2.0

[Frank Mehnert]

Is this problem still current with the latest release 3.0.8? You might want to completely uninstall the old version of VirtualBox before you install to the new version.

[Jason]

Sorry this took so long, I have just gone up to 3.0.10 and tried this again; I am please to say that the upgrade has left USB support intact, but USB support is still not fully working.

Upgraded to VBox 3.0.10. Started image, upgraded VBox Additions. Restarted image. Attached USB device with existing filter (SanDisk USB Cruzer Micro) ensuring the VBox image had focus. Windows prompted to install drivers (surely this should have been done at install?). USB device was not connected to VB image, although it did show up in the list under USB devices. Manually selected USB device, got this error: "Failed to attache the USB device SanDisk corporation U3 Cruzer Micro to the virtual machine Ubuntu. USB device 'SanDisk corporation U3 Cruzer Micro' with UUID {id} is busy with a previous request. Please try again later. Details Result Code: E_INVALIDARG (0x80070057) Component: HostUSBDevice Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a} Callee: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}" I should point out that the USB device is not lit and is thus not connected or active. I shut the image down, ejected the device safely and started the image again. Ensuring the VBox image had focus, I reconnected the device. It lit briefly and switched off, the device was not connected to the VBox image. I manually selected the USB device and this time it did connect.

I guess this upgrade bug can be closed. Should I open a new one about the USB connection problems? I'll add to one if it already exists.

[Jason]

I'll retype that as my formatting got ruined.

Upgraded to VBox 3.0.10.
Started image, upgraded VBox Additions.
Restarted image.
Attached USB device with existing filter (SanDisk? USB Cruzer Micro) ensuring the VBox image had focus.
Windows prompted to install drivers (surely this should have been done at install?).
USB device was not connected to VB image, although it did show up in the list under USB devices.
Manually selected USB device, got this error:
    "Failed to attach the USB device SanDisk? corporation U3 Cruzer Micro to the virtual machine Ubuntu.
    USB device 'SanDisk? corporation U3 Cruzer Micro' with UUID {id} is busy with a previous request. Please try again later.
    Details
        Result Code: E_INVALIDARG (0x80070057) Component: HostUSBDevice Interface: IHostUSBDevice {173b4b44-d268-4334-a00d-b6521c9a740a} Callee: IConsole {0a51994b-cbc6-4686-94eb-d4e4023280e2}"
    I should point out that the USB device is not lit and is thus not connected or active.
I shut the image down, ejected the device safely and started the image again. Ensuring the VBox image had focus, I reconnected the device.
It lit briefly and switched off, the device was not connected to the VBox image.
I manually selected the USB device and this time it did connect. 

[Jason]

To add to this:

Unmounted the device within VBox image
Deselected device from drop-down
Device picked up by Windows
Re-selected device in drop down
Device not connected to VBox image, now listed as "Unknown" with not tick beside it.

[Mani]

I get the same problem with Version 3.1.4. I used to get a different error with the USB Drive. So I uninstalled virtual box. Replugged in the USB drive and installed Virtual box 3.1.4. After which I could not start VBOx. I had to unplug the USB drive and work without it. And that is a sore point.

[Frank Mehnert]

Please reopen if still relevant with VBox 4.2.12.