virtualbox.org

I have a hard disk that uses USB UAS and is connected via USB 3.1 to my system. Since installing VirtualBox 6.1.34 every time I connect the device while a [Windows based e.g. 10/11] VM is running in background the device is totally screwed:

Windows is only able to detect the USB controller, but not the actual drive. Afterwards also other USB 2.0+ devices don't work anymore (only my USB mouse still works) and new USB device are no longer found.
Unmounting don't work anymore (tries to unmount the device without result for hours), Windows host shutdown does not work anymore (you have use the reset switch because it never completes the shutdown process.

If no VM is running everything works as expected.

So it seems like the USB driver Virtualbox screws up the USB support of my Windows 10 host system while VMs are running.

Host: Windows 10 21H2 64bit Home - Intel Core i5 10400 on Z490 chipset
Guest: Windows 10 or 11 with guest tools installed.
VirtualBox: Version 6.1.34 r150636
USB device: SATA disk connected to an ASMedia ASM235

Provide a VM log file. Make sure the VM is fully shut down, then right click it in the manager UI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.

You seem to be describing the symptoms of an overly broad USB filter.

Thanks for your reply, I have added a log that demonstrates the problem, but I don't think the log files will be helpful. When I looked into it there wasn't anything related to USB at the time when I activated the USB drive (max 10 minutes before VM shutdown).

As the problem occurs with multiple VMs I don't think that USB filter (which should be a VM property).
The first VM I encountered the problem has only rule for passing a simple smartcard reader to the guest system.
I checked VBoxSVC.log and found: There are no other USB devices forwarded to the guest OS.
The second VM is a plain Windows 11 VM without any additional USB configuration (no devices forwarded).