Quantcast
Channel: VMware Communities : Discussion List - All Communities
Viewing all articles
Browse latest Browse all 193198

Problem connecting USB-C 3.1 external SSD to a MacBook Pro 2017...

$
0
0

Hi guys,

 

Hoping for some help here, as this is driving me nuts!

 

Environment

     MacBook Pro 2017

     macOS High Sierra 10.13.6

     VMware Fusion 10.1.3

          Windows 10 1083 17134.285

     Generic external USB 3.1 drive enclosure with a Crucial 250GB SSD with a USB-C cable plugged directly into the Mac

 

Issue

Whenever I plug the external enclosure into the Mac, I have it set to prompt me as to which device I wish to connect it to and select the Windows guest. The SSD device connects, with the Windows device connection sound and appears in the Windows Device Manager as a disk drive called "USB Tech SCSI Disk Device". After a few seconds, it then disconnects with the Windows device disconnection sound, but remains visible in Windows Device Manager. It then reconnects and disconnects several times, making the device connect/disconnect noises and eventually stops. At this point the "Standard USB 3.0 eXtensible Host Controller 1.0 (Microsoft" shows an alert in Device Manager and on investigation shows the following error: "Windows has stopped this device because it has reported problems. (Code 43)".

 

The USB device works just fine in macOS.

 

I am able to connect other USB devices to this virtual guest, so the issue is not with the VMware Fusion USB subsystem getting blocked by macOS security and the USB arbitration service is obviously also OK.

 

I have done a complete, manual uninstallation of VMware, logged in as root, so I could get to all the system areas too and then done a clean install of Fusion. With no improvement.

 

Does anybody have an suggestion as to why this device isn't playing nicely and if there is anything I can do to get it working?

 

Cheers,

 

David.


Viewing all articles
Browse latest Browse all 193198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>