Cannot access Sandisk SSD in Windows10 on VMWare Fusion

[Martyin852]

I am using an iMac2017 and VMWare Fusion to host a virtual Windows10 OS.

My goal is to install Windows OS onto a SSD so I can boot directly from the external on my iMac.

Im following this method: How to install Windows 10 "Boot Camp" on a Mac External Drive the EASY way! (2020 edition) - YouTube

I run into problems when I connect my Sandisk Extreme Portable 500G into the iMac.

The windows chime indicates it recognises the disk being connected, however I cannot access it in anyway.

Im not too familiar with windows but after hunting in "This PC" and "Computer Management" I can't see the drive anywhere.

If I change the USB settings on VMWare to 1 or 2, it gives me an error the moment I start the VM.

If I use 3.1 I get no error and a chime telling me it is recognised but still invisible...

Any thoughts are greatly appreciated. Ive been trying several things on this and other forums but no success.

[RickShu]

Hi Martyin852,

This is a known issue and being addressed by development team. Please keep your Fusion up to date, sorry for any inconvenience caused.

Regards,

-Rick

[wila · Accepted solution]

Hi,

FYI, VMware Fusion 11.5.6 is released and it has this item as "fixed" on the release notes.

VMware Fusion 11.5.6 Release Notes

VMware Fusion 11.5.6 Release Notes

                    Last Updated 08/06/2020

Resolved Issues

• Sandisk Extreme SSD device is not recognized in a virtual machineUnable to connect a Sandisk Extreme SSD device to VM because the device is not recognized in the guest operating system. This issue is now resolved.

--

Wil

[Martyin852]

It is working well with the update. Thanks for the quick support!

[ScottR-H]

Then I guess it's been "unfixed" on Fusion 12.1.2 because my SanDisk Extreme SSD isn't recognized on a W10 instance running on that version of Fusion.

[ColoradoMarmot]

If it's thunderbolt and (I think USB 3.2), then that's not virtualized.  USB 3.1 is.

[ScottR-H]

Sigh…. That seems to be the issue. 

Thank you. 

[ColoradoMarmot]

A workaround might be using a 3.1 cable with the drive...it won't impact speed that much, but should force downward compatibility. A 3.1 hub should do the trick too.