USB storage devices no longer connect to guest after December cumulative update

[ReeferSales]

Trying to create an image using Acronis Home 2017.  This has worked without issue since Workstation 12.  Updated my Win 10 Pro - 1709 host and guest with the December cumulative update and since then I have not been able to connect a USB HD.  Can still connect ISOs.

Anyone else seen this?

I even reformatted to see if that would resolve the issue and I am still not able to connect to any of my VMs after a fresh install of WS 14.1.0 build-7370693.

[voidp]

Win10 Workstation USB won't work

My USB Drive is not detected by VMware Workstation...

[Susie201110141]

Could you upload your vm-support log from "Help"->"Support"->"Collect Support Data" ?

[ReeferSales]

Support logs attached.

What I have tried so far:

- Reinstalled tools

- reinstalled WS

- Reformatted host

- tried multiple USB drives

- changed USB compatibility from 3.0 to 2.0 and back again.

- ensured the USB Arb service was running

- downgraded and then upgraded compatibility from 14-12-14

The VM is stored on a server and I am running it over the network.

The drive is a 2TB USB 3 Seagate external drive.

The issue is with all VMs and the guest doesn't seem to matter as I was trying to connect the drive to the VM while booted to an Acronis bootable ISO so it doesn't look like Tools is the issue.

[ReeferSales]

Thanks for the suggestions.  I saw those in my search but neither is applicable to my situation.

[ReeferSales]

Anyone have any ideas?

[bonnie201110141]

From vmware.log, I see that Seagate device is connected to guest.

2017-12-27T11:56:46.657-05:00| vmx| I125: USB: Found device [name:Seagate\ RSS\ USB\ Attached\ SCSI\ (UAS)\ Mass\ Storage\ Device vid:0bc2 pid:ab24 path:1/0/1/1 speed:super family:storage,storage-bulk instanceId:USB\\VID_0BC2&PID_AB24\\MSFT30NA9DACLY serialnum:MSFT30NA9DACLY arbRuntimeKey:5 version:3]

2017-12-27T11:56:46.657-05:00| vmx| I125: USB: Autoconnecting device "Seagate RSS USB Attached SCSI (UAS) Mass Storage Device" matching pattern [path:1/0/1/1 autoclean:1] prefer usb_xhci

2017-12-27T11:56:46.657-05:00| vmx| I125: USB: Connecting device desc:name:Seagate\ RSS\ USB\ Attached\ SCSI\ (UAS)\ Mass\ Storage\ Device vid:0bc2 pid:ab24 path:1/0/1/1 speed:super family:storage,storage-bulk autoclean:1 instanceId:USB\\VID_0BC2&PID_AB24\\MSFT30NA9DACLY serialnum:MSFT30NA9DACLY arbRuntimeKey:5 version:3 id:0x100000050bc2ab24

2017-12-27T11:56:46.657-05:00| vmx| I125: Policy_GetUSBDevAccess: checking usb devices at policy path: /vm/#_VMX/mvm/policyState/val/policySet/usbDevices/#

2017-12-27T11:56:46.657-05:00| vmx| I125: Policy_GetUSBDevAccess: allowConnect = YES

2017-12-27T11:56:46.657-05:00| vmx| I125: MsgHint: msg.usb.generic.stopDevice

2017-12-27T11:56:46.657-05:00| vmx| I125+ A USB device is about to be unplugged from the host and connected to this virtual machine. It will first be stopped to enable safe removal. With some devices, the host may display the message "The device can now safely be removed."

2017-12-27T11:56:46.657-05:00| vmx| I125+ ---------------------------------------

2017-12-27T11:56:49.748-05:00| vmx| I125: USBG: Created 100000050bc2ab24

So your issue is that the device does not show up in Windows Explorer in Windows guest?

[VBAdmin]

Hi, Did you ever figure out a solution to this painful issue?

[continuum]

... not sure what you have in mind ... - lets see where it leads us ...

So please assume that in a few days you get the reply "YES" - what is your next move then ?

Ulli