Page 1 of 1

The dreaded USB captured, but not attached.

Posted: 4. Aug 2020, 02:17
by MikeC7
So my situation is as follows. I have a laptop (Host) running Windows 10 64bit, and I'm attempting to run a Windows 7 32bit as my Guest. The host machine only has USB 3.0 ports, but installing the extension pack and guest additions has not affected the outcome. I uninstalled everything, and reinstalled as Admin. I did not reinstall the extension pack as I will not be using any of its features. I've already confirmed the absence of the Upperfilter entry in the registry. In my attempts of troubleshooting, I did notice that there is no VirtualBox USB entry in the device manager, nor does the driver files exist in the system32 driver folder, and attempting to install the filter driver manually by right click>>install results in a message the operation was a success. Any USB device I attempt to use has the same outcome.

Code: Select all

VBoxManage -version
6.1.12r139181

VBoxManage list extpacks
Extension Packs: 0

Code: Select all

VBoxManage list usbhost
Host USB Devices:

UUID:               39fde908-496c-46e1-a58d-4c5d3bd57c1d
VendorId:           0x8087 (8087)
ProductId:          0x0a2b (0A2B)
Revision:           0.16 (0016)
Port:               7
USB version/speed:  2/Full
Manufacturer:       Intel Corp.
Address:            {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}\0000
Current State:      Busy

UUID:               7145159a-22fa-4aaf-a170-08f7104dc738
VendorId:           0x5986 (5986)
ProductId:          0x054c (054C)
Revision:           49.7 (4907)
Port:               6
USB version/speed:  2/High
Manufacturer:       Acer, Inc
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0004
Current State:      Busy

UUID:               29410922-e777-429e-ad21-6bf5d7a4bbb0
VendorId:           0x1199 (1199)
ProductId:          0x9071 (9071)
Revision:           0.6 (0006)
Port:               2
USB version/speed:  2/High
Manufacturer:       Sierra Wireless, Inc.
Address:            {36fc9e60-c465-11cf-8056-444553540000}\0005
Current State:      Busy

UUID:               73cc2a00-260d-49d4-aa7f-d3f28734055d
VendorId:           0x0a5d (0A5D)
ProductId:          0x2010 (2010)
Revision:           4.0 (0400)
Port:               1
USB version/speed:  1/Full
Manufacturer:       Diatrend Corp.
Current State:      Available

UUID:               6544a26c-cc5f-42f3-b6b7-f39fb23941c7
VendorId:           0x056a (056A)
ProductId:          0x5018 (5018)
Revision:           0.84 (0084)
Port:               5
USB version/speed:  2/Full
Manufacturer:       Wacom Co., Ltd
Address:            {745a17a0-74d3-11d0-b6fe-00a0c90f57da}\0000
Current State:      Busy

Code: Select all

VBoxManage list usbfilters
Global USB Device Filters:

<none>

Code: Select all

VBoxManage showvminfo Maint
Name:                        Maint
Groups:                      /
Guest OS:                    Windows 7 (32-bit)
UUID:                        e1162465-f7ed-48af-ac98-40f942f5adb7
Config file:                 C:\.VirtualBox\Maint\Maint.vbox
Snapshot folder:             C:\.VirtualBox\Maint\Snapshots
Log folder:                  C:\.VirtualBox\Maint\Logs
Hardware UUID:               e1162465-f7ed-48af-ac98-40f942f5adb7
Memory size                  3072MB
Page Fusion:                 disabled
VRAM size:                   256MB
CPU exec cap:                100%
HPET:                        disabled
CPUProfile:                  host
Chipset:                     piix3
Firmware:                    BIOS
Number of CPUs:              1
PAE:                         enabled
Long Mode:                   disabled
Triple Fault Reset:          disabled
APIC:                        enabled
X2APIC:                      disabled
Nested VT-x/AMD-V:           disabled
CPUID Portability Level:     0
CPUID overrides:             None
Boot menu mode:              message and menu
Boot Device 1:               Floppy
Boot Device 2:               DVD
Boot Device 3:               HardDisk
Boot Device 4:               Not Assigned
ACPI:                        enabled
IOAPIC:                      disabled
BIOS APIC mode:              APIC
Time offset:                 0ms
RTC:                         local time
Hardware Virtualization:     enabled
Nested Paging:               enabled
Large Pages:                 enabled
VT-x VPID:                   enabled
VT-x Unrestricted Exec.:     enabled
Paravirt. Provider:          Default
Effective Paravirt. Prov.:   HyperV
State:                       powered off (since 2020-08-03T21:22:51.000000000)
Graphics Controller:         VBoxSVGA
Monitor count:               1
3D Acceleration:             enabled
2D Video Acceleration:       disabled
Teleporter Enabled:          disabled
Teleporter Port:             0
Teleporter Address:
Teleporter Password:
Tracing Enabled:             disabled
Allow Tracing to Access VM:  disabled
Tracing Configuration:
Autostart Enabled:           disabled
Autostart Delay:             0
Default Frontend:
VM process priority:         default
Storage Controller Name (0):            SATA
Storage Controller Type (0):            IntelAhci
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0):  30
Storage Controller Port Count (0):      3
Storage Controller Bootable (0):        on
SATA (0, 0): C:\.VirtualBox\Maint\Maint.vdi (UUID: ab0219f9-8d21-4485-a06a-5d415b9e500a)
SATA (1, 0): C:\Program Files\Oracle\VirtualBox\VBoxGuestAdditions.iso (UUID: b6bf607a-83c9-4a70-9dfc-d12c4e6fd3e2)
NIC 1:                       MAC: 080027A8C84D, Attachment: Bridged Interface 'Intel(R) Ethernet Connection (4) I219-LM', Cable connected: on, Trace: off (file: none), Type: 82540EM, Reported speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth group: none
NIC 2:                       disabled
NIC 3:                       disabled
NIC 4:                       disabled
NIC 5:                       disabled
NIC 6:                       disabled
NIC 7:                       disabled
NIC 8:                       disabled
Pointing Device:             USB Tablet
Keyboard Device:             PS/2 Keyboard
UART 1:                      I/O base: 0x03f8, IRQ: 4, attached to device 'COM1', 16550A
UART 2:                      disabled
UART 3:                      disabled
UART 4:                      disabled
LPT 1:                       disabled
LPT 2:                       disabled
Audio:                       enabled (Driver: DSOUND, Controller: HDA, Codec: STAC9221)
Audio playback:              enabled
Audio capture:               disabled
Clipboard Mode:              disabled
Drag and drop Mode:          HostToGuest
VRDE:                        disabled
OHCI USB:                    enabled
EHCI USB:                    disabled
xHCI USB:                    disabled

USB Device Filters:

Index:                       0
Active:                      yes
Name:                        Diatrend Corp.  [0400]
VendorId:                    0a5d
ProductId:                   2010
Revision:                    0400
Manufacturer:
Product:
Remote:                      0
Serial Number:

Bandwidth groups:  <none>

Shared folders:<none>

Capturing:                   not active
Capture audio:               not active
Capture screens:             0
Capture file:                C:\.VirtualBox\Maint\Maint.webm
Capture dimensions:          1024x768
Capture rate:                512kbps
Capture FPS:                 25kbps
Capture options:

Guest:

Configured memory balloon size: 0MB

Re: The dreaded USB captured, but not attached.

Posted: 4. Aug 2020, 03:29
by scottgus1
MikeC7 wrote: did not reinstall the extension pack as I will not be using any of its features.
Might want to reconsider, as the EP provides USB 2 and 3. Very few devices are USB 1 anymore.

Your provision of USB diagnostic info shows you have probably seen USB basics and troubleshooting. That tutorial also says that Windows 7 needs drivers for USB 3. There's a nuance about what to do if your host PC only has USB 3 ports, I don't remember it right off. But put the EP back on and the USB 3 drivers in 7, and try again.

Re: The dreaded USB captured, but not attached.

Posted: 4. Aug 2020, 03:53
by MikeC7
When I installed the extension pack, I installed the Intel USB3 drivers in my guest, and selected the 3.0 controller in VirtualBox's USB settings menu. There was no change. I can't use the extension pack legally since this will be used in a commercial environment. This vm is mainly for connecting to legacy equipment that lack a 64 bit driver and are no longer supported by the manufacturer.

Re: The dreaded USB captured, but not attached.

Posted: 6. Aug 2020, 23:54
by MikeC7
So, any clue as to why I wouldn't be seeing virtualbox's USB controller appearing in the host's device manager?

Re: The dreaded USB captured, but not attached.

Posted: 7. Aug 2020, 00:03
by scottgus1
The Virtualbox host USB 'controller' only appears when a USB device has successfully passed into a guest. You won't see it if no USB devices are being captured.

If I recall correctly it is possible to turn off the USB drivers in the installer. Try running the installer again, use right-click-Run-As-Administrator, even if you already have admin privileges.

Also, 3rd-party Antivirus may have blocked the drivers automatically or questioned them and received a pebcak response to the AV question. Try disabling 3rd-party AV during the install.

Re: The dreaded USB captured, but not attached.

Posted: 2. Sep 2020, 21:25
by MikeC7
Hate to necro a post like this, but I have not solved my issue. After losing my sanity to Bitlocker for a week, I managed to get Driver Enforcement turned off. I uninstalled and reinstalled Virtual Box, making sure to run the installer as Admin. VBoxUSB is still missing from the System32\drivers folder. The VM still shows Captured but not Attached. I used pnputil from an admin command prompt to manually install VBoxUSB.inf, and still no change. As far as virus protection, only Windows Defender is on. I'm trying to turn it off to see if that helps.

Re: The dreaded USB captured, but not attached.

Posted: 3. Sep 2020, 01:21
by scottgus1
MikeC7 wrote:Hate to necro a post like this,
Not a problem, this one is still yours.
MikeC7 wrote:VBoxUSB is still missing from the System32\drivers folder.
I checked my two Windows 10 hosts and founr VboxUSB.sys and VboxUSBmon.sys in the System32 folder.

So either there is something really unusual going on in your computer or the USB option in the Virtualbox installer was turned off.

In the even you had the USB option turned on, you might want to enable MSI installer logging (web-search this), then try the installer again. The MSI log may explain why USB is not being loaded.

Note that with no Extension Pack you will be limited to USB 1 and the glacial data rates appertaining thereto.

Re: The dreaded USB captured, but not attached.

Posted: 14. Oct 2020, 17:05
by TehBoss
I have found that when this issue is repeated for either a specific device, all devices, or all VMs; that the issue is not with the VM but with the Host machine, and more specifically the VirtualBox installation. In every instance, an uninstall/reboot/reinstall of VirtualBox on the Host machine (including the Extension Pack) restores the USB Passthrough functionality. Occasionally a repair will work, but not always. Based on the behavior I've seen, it appears that the VirtualBox software loses the driver for the device in question. I'm not certain how this happens or where to repair it.

On Windows 10 under Devices and Printers, when you attempt to connect the device an error occurs under the hardware section of the properties. A warning symbol appears stating something about the driver under the device status.

I have not had a non-Windows Host that this has occurred on in order to verify that this solution works, but I suspect that it does.

Re: The dreaded USB captured, but not attached.

Posted: 18. Nov 2020, 00:49
by fablege
Could this be related to the issue at viewtopic.php?f=6&t=99443 ? I also have that issue and have not been able to get to root cause.