Thanks for the reply.
I tried reinstall VMWare (referred to this tutorial: VMware Knowledge Base ). Still not working.
The VM machine can detect my usb devices, but just 1 sec later, windows disconnected my device. Very weird but thank you still.
I have a feeling this is a new issue. I just encountered this situation myself, and I didn't know this was a problem before.
MacOS Catalina 10.15.3
VMware 11.5.1 (15018442)
Windows 10 32-bit
I recently used Windows to run Western Digital Data LifeGuard, to run diagnostics on some external hard disks.
The hard disks are connected by an OWC USB 3 Gen 1 (aka 5 Gbps) dual-drive dock.
About two weeks ago, I was able to use this dock in Win10 to run disk diagnostics.
About 2 days ago, I installed the latest MacOS update that recently became available.
Tonight, I received another WD disk, and so I put it in the OWC drive dock with Win10 to run diagnostics.
Mysteriously, I received an error message from VMware about how "this device couldn't be connected through its preferred mechanism" or something to that effect.
I then started googling the message, which is how I found the support topic mentioned up-thread. That's when I discovered VMware Fusion had a toggle in the Advanced USB settings to enable USB 3 support. When I checked my settings, the Win10 VM was set for USB 2 support. I've never changed that setting before. Also, the dock has always been connected to the Mac with a USB 3 cable... no changes there. So, in the period of about two weeks, I was able to use the USB 3 drive dock successfully in Win10, and suddenly I'm receiving error messages.
I'm inclined to say that the recent MacOS update might have had something to do with it?
Mac is a Thunderbolt 3 but for usb I think it's a Gen 2 port (type-c).
I tried both Samsung T3 and T5 external SSD (type-c Gen 2). And these SSDs also come with usb-c to USB 3.0 cable. So I tried the 3.0 port and the the same problem occurred.
Furthermore, I tried a Seagate external Hdd and an external thunderbolt 2 (I use an Apple thunderbolt 3 adapter) with USB 3.0 port, no luck.
I think it may be VMware's driver problem?
I didn't have this information but only the sound played in Windows vm.
And yeah, my system version is the newest 10.15.3.
4 people found this helpful
Can you try to add an option into vmx file and see if it helps?
1. Power off the VM
2. Right click the VM from VM Library
3. Press 'Option' Key from keyboard and hold it
4. Choose 'Open Config File in Editor'
5. Add a new line with the string usb.generic.keepStreamsEnabled = "FALSE"
6. Save and close the file, power on the VM
Perfect, it works!
I'll mark my question as resolved. But I think it's a vm usb bug or need drive support issue right?
Thanks a lot!
Ps. did some search, looks like it disabled the usb device as UAS.
And one more thing.
I used to create external usb devices as physical vmdk by vmware-rawdiskCreator.
Looks like vmware cannot boot from the physical drive. I saw error message like:
Operation not permitted
Cannot open the disk '<vm_path>.vmwarevm/Virtual Disk.vmdk' or one of the snapshot disks it depends on.
Module 'Disk' power on failed.
Failed to start the virtual machine
I'm sure that device is not used by OS(ejectable) and doesn't have any snapshot for the vm. Is this also related to usb issue?
I've discovered that adding this line also fixes the "me too" issue that I posted to this thread! The drive dock is now visible.
Good to know.
Problem solved for:
"Operation not permitted"
Allow "com.vmware.DiskHelper" in "Full disk access" of System Preferences - Security
This did indeed 'fix' similar issue for me, though I've previously used the same drive on a win 10 fusion VM before without issue, so what's changed?