USB 3 Drive not recognized on USB 3 port

[wand3r3r]

I'm trying to find a reason and a fix for why my USB 3 drive is not being recognized by my guest OS when it is plugged into the USB3 port. If however I plug it into a USB 2 port the drive automounts and works fine. The device is listed Virtual Box USB Device Filters when plugged into either port.

Windows 7 Host
Ubunutu 16.04 Guest
Virtual Box 5.1.18

[mpack]

Please provide a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[wand3r3r]

The log file is attached.

Code: Select all

00:00:10.924109 xHCI: USB Operational
00:00:10.932784 xHCI: root hub-attached device reset completed with VINF_SUCCESS

[mpack]

The log says that the Ubuntu version is 14.04, not 16.04 as you said in your first post. Can you say which version is correct?

It would also be useful if you could report your Linux guests kernel version.

Is this your USB device? (check IDs on host).

00:05:40.202185 VUSB: Attached '000000000f394610[proxy 1f75:0917]' to port 2
00:06:17.164140 VUSB: Detached '000000000f394610[proxy 1f75:0917]' from port 2
00:06:42.525417 VUSB: Attached '00000000121517e0[proxy 1f75:0917]' to port 2
00:17:52.486155 VUSB: Detached '00000000121517e0[proxy 1f75:0917]' from port 2
00:18:26.989273 VUSB: Attached '00000000121517e0[proxy 1f75:0917]' to port 2

[mpack]

Incidentally, and I'm not sure that it matters, but have you installed xHCI support on your host? Win7 does not have this by default.

[wand3r3r]

I attached and detached the drive then refreshed the log and the following lines appeared in the log.

00:31:52.669710 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_UNSUPPORTED_ARCH fImage=1 fProtect=0x0 fAccess=0x0 cHits=8 \Device\HarddiskVolume1\Program Files\WIDCOMM\Bluetooth Software\BTKeyInd.dll
00:31:52.669795 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\WIDCOMM\Bluetooth Software\btkeyind.dll' (C:\Program Files\WIDCOMM\Bluetooth Software\btkeyind.dll): rcNt=0xc0000190
00:31:57.270493 VUSB: Attached '000000000495ef10[proxy 1f75:0917]' to port 2
00:33:03.149511 VUSB: Detached '000000000495ef10[proxy 1f75:0917]' from port 2
00:33:04.315841 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_UNSUPPORTED_ARCH fImage=1 fProtect=0x0 fAccess=0x0 cHits=16 \Device\HarddiskVolume1\Program Files\WIDCOMM\Bluetooth Software\BTKeyInd.dll
00:33:04.315931 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\WIDCOMM\Bluetooth Software\btkeyind.dll' (C:\Program Files\WIDCOMM\Bluetooth Software\btkeyind.dll): rcNt=0xc0000190

So yes. I believe that is the device as they have the same proxy id.

However that is not what they look like in the windows device properities:
Hardware IDs

USBSTOR\DiskUFD_3.0_Silicon-Power32G1.00
USBSTOR\DiskUFD_3.0_Silicon-Power32G
USBSTOR\DiskUFD_3.0_
USBSTOR\UFD_3.0_Silicon-Power32G1
UFD_3.0_Silicon-Power32G1
USBSTOR\GenDisk
GenDisk

GUID

{4d36e967-e325-11ce-bfc1-08002be10318}

Device Instance Path:

USBSTOR\DISK&VEN_UFD_3.0&PROD_SILICON-POWER32G&REV_1.00\P1601731000000000000000361&0

The Parent property lists:

USB\VID_1F75&PID_0917\P1601731000000000000000361

the VID and PID match the proxy address

Attaching and detaching from the USB2 port gives:

00:51:00.958573 supR3HardenedErrorV: supR3HardenedScreenImage/LdrLoadDll: cached rc=VERR_LDRVI_UNSUPPORTED_ARCH fImage=1 fProtect=0x0 fAccess=0x0 cHits=32 \Device\HarddiskVolume1\Program Files\WIDCOMM\Bluetooth Software\BtMmHook.dll
00:51:00.958768 supR3HardenedErrorV: supR3HardenedMonitor_LdrLoadDll: rejecting 'C:\Program Files\WIDCOMM\Bluetooth Software\btmmhook.dll' (C:\Program Files\WIDCOMM\Bluetooth Software\btmmhook.dll): rcNt=0xc0000190
00:51:05.698370 VUSB: Attached '000000000495ef10[proxy 1f75:0917]' to port 2
00:51:31.861774 VUSB: Detached '000000000495ef10[proxy 1f75:0917]' from port 2

[Perryg]

Your rejected bluetooth software could be the cause of your issue. I would remove it reboot and try again.

[wand3r3r]

Incidentally, and I'm not sure that it matters, but have you installed xHCI support on your host? Win7 does not have this by default.

I believe so. The USB 3.0 eXtensible Host Controller and USB 3.0 Root hub are installed.

[wand3r3r]

Your rejected bluetooth software could be the cause of your issue. I would remove it reboot and try again.

Is there a way to fix the rejection without removing the software? Tell Virtualbox either to accept or ignore the dll?

[Perryg]

Not that I am aware of. If the software is not signed or has an expired certificate it is considered dangerous and should be rejected. They may have an updated driver but you would need to check with them. I would remove it as a test and see what happens. You can always install it again if you need to.

[Perryg]

Some info:
https://file.info/windows/btkeyind_dll.html

[socratis]

Is there a way to fix the rejection without removing the software? Tell VirtualBox either to accept or ignore the dll?

For the 2nd question, as Perryg said, no. But for the 1st part, just to make sure that the situation is clear enough; the software itself (generally speaking) is not the problem.

The problem is that it wants to attach itself to every running process and their parent (no pun intended). That's what's being rejected. So, if there's a setting where you could disable it from either presenting a custom dialog, or another button (like "Send via Bluetooth"), you could solve the problem...

[wand3r3r]

I went ahead an uninstilled the bluetooth software and rebooted.
It was not listed as WIDCOM. But rather Broadcom Bluetooth. It had the same effect. removing the dlls from "Program Files\WIDCOM\Bluetooth Software"
No Bluetooth rejected error but still no Joy on the USB.

00:10:37.445748 VUSB: Attached '000000000505b8d0[proxy 1f75:0917]' to port 2
00:11:03.538091 VUSB: Detached '000000000505b8d0[proxy 1f75:0917]' from port 2
00:11:38.329580 VUSB: Attached '000000000505b8d0[proxy 1f75:0917]' to port 2
00:11:38.873262 VUSB: Detached '000000000505b8d0[proxy 1f75:0917]' from port 2
00:12:42.123125 VUSB: Attached '000000000505b8d0[proxy 1f75:0917]' to port 2
00:12:42.706711 VUSB: Detached '000000000505b8d0[proxy 1f75:0917]' from port 2

I have access to a newer PC that has all USB 3.0 ports. I just tried installing a Virtuabox (with the extension pack) and fresh Ubunbut64 VM. No joy on that system either.

[Perryg]

Not a Windows guy for sure but I believe you need to post another guest log with the software removed and it may not hurt to post the hardening log as well so the Windows gurus can see them..

[michaln]

Are you plugging the device into some kind of a hub? The problem is that you capture the device and it immediately vanishes, as if it were unplugged. It's relatively unlikely that it can be fixed on the VirtualBox side.