[Solved] Failed to attach USB device... busy with previous request
Posted: 4. Dec 2017, 07:00
Host: Windows Version 10.0.16299 Build 16299
Virtualbox 5.2.2 with extension pack
Guest: MSEdge Win10 and Kali Linux (kind of irrelevant, I believe it is a host problem)
USB NIC: Realtek 8812au; Alfa AWUS036ACH
This seems to be a problem with my windows host but I have no idea why. I get the following error: Things I have tried:
- enabled USB 2.0, created a filter with the device attached with guest down, then booted the guest
- deleted upper filters using regedit
- tried different USB ports
- disabled the NIC on the host
- removed the NIC from the host
- uninstalled Vbox and reinstalled as admin
Something that I noticed is that when I remove the NIC, it still shows under the USB tab. I know that VBox on my mac automatically removes the NIC from the USB menu when I disconnect the NIC, but on Windows 10 it still remains. I am not sure why it does that. Screenshot for reference: I believe is has something to do with Win10 host. Maybe there's a service that is using it but I have no idea what or why since I already disabled and even removed the device from my host.
I do not have wireshark installed on my host so the USBPS thing doesn't apply.
Any help is greatly appreciated!
Virtualbox 5.2.2 with extension pack
Guest: MSEdge Win10 and Kali Linux (kind of irrelevant, I believe it is a host problem)
USB NIC: Realtek 8812au; Alfa AWUS036ACH
This seems to be a problem with my windows host but I have no idea why. I get the following error: Things I have tried:
- enabled USB 2.0, created a filter with the device attached with guest down, then booted the guest
- deleted upper filters using regedit
- tried different USB ports
- disabled the NIC on the host
- removed the NIC from the host
- uninstalled Vbox and reinstalled as admin
Something that I noticed is that when I remove the NIC, it still shows under the USB tab. I know that VBox on my mac automatically removes the NIC from the USB menu when I disconnect the NIC, but on Windows 10 it still remains. I am not sure why it does that. Screenshot for reference: I believe is has something to do with Win10 host. Maybe there's a service that is using it but I have no idea what or why since I already disabled and even removed the device from my host.
I do not have wireshark installed on my host so the USBPS thing doesn't apply.
Any help is greatly appreciated!