1 2 3 Previous Next 36 Replies Latest reply on Mar 15, 2020 11:54 AM by crok13 Go to original post
      • 15. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
        nihilinterit Lurker

        I had this exact same issue, tried everything, and finally stumbled upon a truly unlikely solution on another forum:

         

        Simply reinstall VMware Workstation, but UNCHECK the Enhanced Keyboard Driver option.

         

        Everything works perfect now, but some serious debugging seems warranted for the enhanced keyboard driver.

        • 16. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
          vmgeroplayer Lurker

          Having the same issue on Windows 10 Professional 1903 on two different systems (Workstation / Laptop). Everything worked fine before 1903 upgrade so this seems to be a 1903-related issue. All USB 2.0 or 3.0 devices freeze the VM, respectively. Cannot even shutdown the guest, have to kill the entire VMWare Player 14 from task manager.

          Tried to install an update but no updates available. This is really annoying!!!

          • 17. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
            fletchmeister Lurker

            I wouldnt hold your breath waiting for an update for v14. It seems pretty clear to me now that VMware expects you to upgrade to v15 for this to be fixed. I have been testing out VirtualBox again and have to say that it has no problems with 1903 and their corporate licenses are way cheaper per seat. The downside is their minimum order is a bit steep but still not that bad.

            • 18. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
              vmgeroplayer Lurker

              Thanks. That's correct. I also updated to Player 15 and performed an update of the VMWare Linux Guest Tools. Works like a rock now.

              My player 14 license has become garbage...

              • 19. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                Eric1975 Lurker

                I also have the same issue on V15.5.1.  When I connect a USB to the VM, it just freezes up and can not close it without killing the task through Task Manager.

                 

                I have another Laptop with V15.1 on it and this problem does not exist on that one and it use to work on this computer prior to the update.

                 

                Attached is the LOG file that shows (the device in RED is the one I connected):

                 

                2020-01-27T16:17:19.230-05:00| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 7 USB devices

                2020-01-27T16:17:19.230-05:00| vmx| I125: USB: Found device [name:ASUSTek\ 802.11ac\ NIC vid:0b05 pid:184c path:1/0/0/3 speed:high family:vendor instanceId:USB\\VID_0B05&PID_184C\\123456 serialnum:123456 arbRuntimeKey:1 version:3]

                2020-01-27T16:17:19.230-05:00| vmx| I125: USB: Found device [name:Siemens\ SIMATIC\ PC\ Adapter\ USB vid:0908 pid:0004 path:1/0/0/6 speed:full family:vendor virtPath:usb:2 instanceId:USB\\VID_0E0F&PID_0001\\6ES7_972-0CB20-0XA0 serialnum:6ES7_972-0CB20-0XA0 arbRuntimeKey:2 ownerdisplay:Siemens\ Step7\ MicroWin\ -\ Windows\ 10\ Pro\ x64 version:3], connected to usb:1 port 0.

                2020-01-27T16:17:19.230-05:00| vmx| I125: USB: Found device [name:Acer\ Integrated\ Camera vid:5986 pid:2113 path:1/0/0/8 speed:high family:video instanceId:USB\\VID_5986&PID_2113\\5&3DED37A&0&8 arbRuntimeKey:3 version:3]

                2020-01-27T16:17:19.230-05:00| vmx| I125: USB: Found device [name:Synaptics\ WBDI vid:06cb pid:009a path:1/0/0/9 speed:full family:vendor instanceId:USB\\VID_06CB&PID_009A\\3E60A407C640 serialnum:3E60A407C640 arbRuntimeKey:4 version:3]

                2020-01-27T16:17:19.230-05:00| vmx| I125: USB: Found device [name:Acer\ Integrated\ IR\ Camera vid:5986 pid:211a path:1/0/0/12 speed:high family:video instanceId:USB\\VID_5986&PID_211A\\5&3DED37A&0&12 arbRuntimeKey:5 version:3]

                2020-01-27T16:17:19.230-05:00| vmx| I125: USB: Found device [name:Intel(R)\ Wireless\ Bluetooth(R) vid:8087 pid:0aaa path:1/0/0/14 speed:full family:hid,wireless,bluetooth instanceId:USB\\VID_8087&PID_0AAA\\5&3DED37A&0&14 arbRuntimeKey:6 version:3]

                2020-01-27T16:17:19.230-05:00| vmx| I125: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth deviceType:virtual-bluetooth info:0000001 version:3]

                2020-01-27T16:17:40.549-05:00| mouse| W115: Poll timeout: Something may be hung... ungrabbing

                • 20. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                  hotvooboy Novice
                  VMware Employees

                  Thank you very much for reporting this issue and for your analysis!

                  Looks like the device you mentioned is not a common usb device and we will do investigation.

                  • 21. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                    bevanweiss Novice

                    I'm seeing exactly the same behaviour as @Eric1975when I run 15.5.1 build-15018445 under Windows 10 x64 (1909).  I can plug the Siemens MPI Adapter into the computer and everything is fine, but if I assign it to a VM then that VM locks up, and is not able to be interacted with, including Guest Power Off / Restart.

                    This has been the case on two VMs, one a Windows 10 x64, and the other a Windows XP x86.  Both have previously worked fine with this adaptor.

                     

                    I have since uninstalled 15.5.1 build-15018445 and installed 15.1.0 build-13591040.  Unfortunately the situation happened whilst I was on-site in front of a client... so not the nicest situation to be in.

                     

                    I haven't yet tried to update to 15.5.0 to see if the issue is within this build also, but may try this tomorrow if I find time.

                    I did try to lower the USB Support version within the VM settings (setting it down to USB 1.1).  This did not resolve the situation, and the lockups still occurred.

                    I did not try to remove the Enhanced Keyboard support, as I believe this requires a reinstall, so it was a more likely fix to revert versions at the time.

                     

                    I'm a bit worried if there is special treatment for different USB devices within the VMware handling.  That seems incredibly prone to these kind of 'weird' bugs, which would also only affect a limited population and so may not get the fix criticality that we would require of them.  As it stands we will be unable to upgrade VMware versions until this issue is resolved.

                    • 22. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                      hotvooboy Novice
                      VMware Employees

                      Hi,

                       

                      Thank you for posting this issue in community.

                      Sorry for the inconvenience caused with WS 15.5.1. We have created  internal bug to track it and will do more investigation.

                      • 23. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                        ivivanov Expert
                        VMware Employees

                        Hi Eric,

                         

                        Thanks for your report.

                         

                        As there is nothing in the log file that gives a clue to what the problem might be, and since this issue is not reproducible in-house, can you please share some additional information in order to proceed further with the investigation?

                         

                        1. Can you confirm the VMware Workstation build number that you are using, the Windows OS version and the guest OS version?

                        2. Can you try the workaround mentioned in https://communities.vmware.com/message/2882908#2882908 (uninstall and re-install VMware Workstation with unchecking Enhanced Keyboard Driver) and confirm whether this fixes the issue for you?

                        3. Can you collect a live dump from the vmx process? In order to do it there are several steps to perform:

                             a) close VMware Workstation and open the virtual machine .vmx file in a text editor and add the following line to it:

                                        vmx.buildType = "debug"

                             b) open VMware Workstation, power on the VM and reproduce the hang

                             c) download the ProcDump utility from https://docs.microsoft.com/en-us/sysinternals/downloads/procdump and extract the archive to a temporary folder

                             d) open an Administrative Command Prompt, navigate to the temporary folder where ProcDump was extracted and run the following command:

                                       procdump64 /ma vmware-vmx-debug

                                 Wait for procdump to complete - it should generate a .dmp file in the current directory.

                             e) Compress the .dmp file and send it to me for further analysis (maybe as a private message).

                         

                        Regards,

                        Ivan

                        • 24. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                          Matt_1 Lurker

                          Hi,

                           

                          I have the exact same issue as you. Did you manage to find a solution?

                           

                           

                          Cheers

                          • 25. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                            bevanweiss Novice

                            Hi Ivan,

                             

                            I've just reproduced the issue with the SIMATIC adapter (which is likely similar to other issues with USB devices).

                            It appears that the bug was introduced between 15.1.0 build-13591040 and 15.5.0 build-14665864.

                            It crashed when the keyboard driver was not installed, so this is not related.

                             

                            I turned on USB Verbose debugging as the VM was starting up in the 15.1.0 release... and there is a lot more USBIO 'noise' in the logs of the 15.5.0 test.  So I think perhaps the USB Verbose logging only activates when the VM is first started up.  So I'll retest under 15.1.0 to get logging with the verbose USB definitely 'active'.

                             

                            I've obtained the ProcDump also, with a dump file of 6686MB.  I'll 7zip it down which should give us something more manageable.

                             

                            I'll include some of the 15.5.0 log here, since it might be obvious from it..

                             

                            2020-02-13T16:37:55.916+11:00| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 7 USB devices

                            2020-02-13T16:37:55.916+11:00| vmx| I125: USB: Found device [name:Western\ Digital\ Elements\ 1048 vid:1058 pid:1048 path:1/0/1/1 speed:super family:storage,storage-bulk instanceId:USB\\VID_1058&PID_1048\\575834314139335330323030 serialnum:575834314139335330323030 arbRuntimeKey:5 version:3]

                            2020-02-13T16:37:55.916+11:00| vmx| I125: USB: Found device [name:Siemens\ SIMATIC\ PC\ Adapter\ USB vid:0908 pid:0004 path:1/0/0/2 speed:full family:vendor instanceId:USB\\VID_0E0F&PID_0001\\6ES7_972-0CB20-0XA0 serialnum:6ES7_972-0CB20-0XA0 arbRuntimeKey:7 version:3]

                            2020-02-13T16:37:55.916+11:00| vmx| I125: USB: Found device [name:Microdia\ Integrated_Webcam_HD vid:0c45 pid:6717 path:1/0/0/11 speed:high family:video instanceId:USB\\VID_0C45&PID_6717\\5&2C784537&0&11 arbRuntimeKey:3 version:3]

                            2020-02-13T16:37:55.917+11:00| vmx| I125: USB: Found device [name:Qualcomm\ QCA61x4A\ Bluetooth vid:0cf3 pid:e007 path:1/0/0/14 speed:full family:wireless,bluetooth instanceId:USB\\VID_0CF3&PID_E007\\5&2C784537&0&14 arbRuntimeKey:4 version:3]

                            2020-02-13T16:37:55.917+11:00| vmx| I125: USB: Found device [name:Action\ Star\ HID\ to\ SPI\ Device vid:0835 pid:2a06 path:1/0/0/4/1/0 speed:full family:hid instanceId:USB\\VID_0835&PID_2A06\\0123456789ABCDEF serialnum:0123456789ABCDEF arbRuntimeKey:2 version:3]

                            2020-02-13T16:37:55.917+11:00| vmx| I125: USB: Found device [name:DisplayLink\ USB-C\ Hybrid\ UHD\ Video\ Dock vid:17e9 pid:6000 path:1/0/1/5/2 speed:super family:vendor,other,audio,comm instanceId:USB\\VID_17E9&PID_6000\\000100117202082 serialnum:000100117202082 arbRuntimeKey:6 version:3]

                            2020-02-13T16:37:55.917+11:00| vmx| I125: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth deviceType:virtual-bluetooth info:0000001 version:3]

                            2020-02-13T16:37:59.155+11:00| vmx| I125: USBGA: device 1000000709080004 arrived

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USBGA: Autoconnecting new device

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Connecting device desc:name:Siemens\ SIMATIC\ PC\ Adapter\ USB vid:0908 pid:0004 path:1/0/0/2 speed:full family:vendor instanceId:USB\\VID_0E0F&PID_0001\\6ES7_972-0CB20-0XA0 serialnum:6ES7_972-0CB20-0XA0 arbRuntimeKey:7 version:3 id:0x1000000709080004

                            2020-02-13T16:37:59.156+11:00| vmx| I125: Policy_GetUSBDevAccess: checking usb devices at policy path: /vm/#_VMX/mvm/policyState/val/policySet/usbDevices/#

                            2020-02-13T16:37:59.156+11:00| vmx| I125: Policy_GetUSBDevAccess: allowConnect = YES

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USBG: Created 1000000709080004

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USBGW: Disabling USB 3.0 streams

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USBIO: Up dev=2 'usb:1' endpt=81 stream=0 datalen=1 numPackets=0 status=0 0

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USBIO:  000: 02                                              .              

                            2020-02-13T16:37:59.156+11:00| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 7 USB devices

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Found device [name:Western\ Digital\ Elements\ 1048 vid:1058 pid:1048 path:1/0/1/1 speed:super family:storage,storage-bulk instanceId:USB\\VID_1058&PID_1048\\575834314139335330323030 serialnum:575834314139335330323030 arbRuntimeKey:5 version:3]

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Found device [name:Siemens\ SIMATIC\ PC\ Adapter\ USB vid:0908 pid:0004 path:1/0/0/2 speed:full family:vendor virtPath:usb:2 instanceId:USB\\VID_0E0F&PID_0001\\6ES7_972-0CB20-0XA0 serialnum:6ES7_972-0CB20-0XA0 arbRuntimeKey:7 version:3], connected to usb:1 port 0.

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Found device [name:Microdia\ Integrated_Webcam_HD vid:0c45 pid:6717 path:1/0/0/11 speed:high family:video instanceId:USB\\VID_0C45&PID_6717\\5&2C784537&0&11 arbRuntimeKey:3 version:3]

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Found device [name:Qualcomm\ QCA61x4A\ Bluetooth vid:0cf3 pid:e007 path:1/0/0/14 speed:full family:wireless,bluetooth instanceId:USB\\VID_0CF3&PID_E007\\5&2C784537&0&14 arbRuntimeKey:4 version:3]

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Found device [name:Action\ Star\ HID\ to\ SPI\ Device vid:0835 pid:2a06 path:1/0/0/4/1/0 speed:full family:hid instanceId:USB\\VID_0835&PID_2A06\\0123456789ABCDEF serialnum:0123456789ABCDEF arbRuntimeKey:2 version:3]

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Found device [name:DisplayLink\ USB-C\ Hybrid\ UHD\ Video\ Dock vid:17e9 pid:6000 path:1/0/1/5/2 speed:super family:vendor,other,audio,comm instanceId:USB\\VID_17E9&PID_6000\\000100117202082 serialnum:000100117202082 arbRuntimeKey:6 version:3]

                            2020-02-13T16:37:59.156+11:00| vmx| I125: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth deviceType:virtual-bluetooth info:0000001 version:3]

                            2020-02-13T16:37:59.157+11:00| vmx| I125: VUsbUpdateVigorFieldsAndAutoconnect: New set of 7 USB devices

                            2020-02-13T16:37:59.157+11:00| vmx| I125: USB: Found device [name:Western\ Digital\ Elements\ 1048 vid:1058 pid:1048 path:1/0/1/1 speed:super family:storage,storage-bulk instanceId:USB\\VID_1058&PID_1048\\575834314139335330323030 serialnum:575834314139335330323030 arbRuntimeKey:5 version:3]

                            2020-02-13T16:37:59.157+11:00| vmx| I125: USB: Found device [name:Siemens\ SIMATIC\ PC\ Adapter\ USB vid:0908 pid:0004 path:1/0/0/2 speed:full family:vendor virtPath:usb:2 instanceId:USB\\VID_0E0F&PID_0001\\6ES7_972-0CB20-0XA0 serialnum:6ES7_972-0CB20-0XA0 arbRuntimeKey:7 ownerdisplay:Siemens\ TIA ownertarget:vmware-vmx:C:\\VMWare\\VM_W10_Siemens\ V1.0\\Win\ 10\ x64.vmx version:3], connected to usb:1 port 0.

                            2020-02-13T16:37:59.157+11:00| vmx| I125: USB: Found device [name:Microdia\ Integrated_Webcam_HD vid:0c45 pid:6717 path:1/0/0/11 speed:high family:video instanceId:USB\\VID_0C45&PID_6717\\5&2C784537&0&11 arbRuntimeKey:3 version:3]

                            2020-02-13T16:37:59.157+11:00| vmx| I125: USB: Found device [name:Qualcomm\ QCA61x4A\ Bluetooth vid:0cf3 pid:e007 path:1/0/0/14 speed:full family:wireless,bluetooth instanceId:USB\\VID_0CF3&PID_E007\\5&2C784537&0&14 arbRuntimeKey:4 version:3]

                            2020-02-13T16:37:59.157+11:00| vmx| I125: USB: Found device [name:Action\ Star\ HID\ to\ SPI\ Device vid:0835 pid:2a06 path:1/0/0/4/1/0 speed:full family:hid instanceId:USB\\VID_0835&PID_2A06\\0123456789ABCDEF serialnum:0123456789ABCDEF arbRuntimeKey:2 version:3]

                            2020-02-13T16:37:59.157+11:00| vmx| I125: USB: Found device [name:DisplayLink\ USB-C\ Hybrid\ UHD\ Video\ Dock vid:17e9 pid:6000 path:1/0/1/5/2 speed:super family:vendor,other,audio,comm instanceId:USB\\VID_17E9&PID_6000\\000100117202082 serialnum:000100117202082 arbRuntimeKey:6 version:3]

                            2020-02-13T16:37:59.157+11:00| vmx| I125: USB: Found device [name:Virtual\ Bluetooth\ Adapter vid:0e0f pid:0008 speed:full family:wireless,bluetooth deviceType:virtual-bluetooth info:0000001 version:3]

                            2020-02-13T16:37:59.184+11:00| vmx| I125: USBIO: Up dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

                            2020-02-13T16:37:59.184+11:00| vmx| I125: USBIO:  000: 00 00 e1 32 28 54 00 00                         ...2(T..       

                            2020-02-13T16:37:59.188+11:00| vmx| I125: USBIO: Down dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

                            2020-02-13T16:37:59.189+11:00| vmx| I125: USBIO: Class 0x00(wValue=0x0000, wIndex=0x0001)

                            2020-02-13T16:37:59.189+11:00| vmx| I125: USBIO: Down dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.189+11:00| vmx| I125: USBIO:  000: a3 00 00 00 01 00 04 00                         ........       

                            2020-02-13T16:37:59.189+11:00| vmx| I125: USBIO: Up dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.189+11:00| vmx| I125: USBIO:  000: a3 00 00 00 01 00 04 00                         ........       

                            2020-02-13T16:37:59.189+11:00| vmx| I125: USBIO:  000: 01 01 01 00                                     ....           

                            2020-02-13T16:37:59.190+11:00| vmx| I125: USBIO: Class 0x00(wValue=0x0000, wIndex=0x0002)

                            2020-02-13T16:37:59.190+11:00| vmx| I125: USBIO: Down dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.190+11:00| vmx| I125: USBIO:  000: a3 00 00 00 02 00 04 00                         ........       

                            2020-02-13T16:37:59.190+11:00| vmx| I125: USBIO: Up dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.190+11:00| vmx| I125: USBIO:  000: a3 00 00 00 02 00 04 00                         ........       

                            2020-02-13T16:37:59.190+11:00| vmx| I125: USBIO:  000: 00 01 00 00                                     ....           

                            2020-02-13T16:37:59.192+11:00| vmx| I125: USBIO: Class 0x00(wValue=0x0000, wIndex=0x0003)

                            2020-02-13T16:37:59.192+11:00| vmx| I125: USBIO: Down dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.192+11:00| vmx| I125: USBIO:  000: a3 00 00 00 03 00 04 00                         ........       

                            2020-02-13T16:37:59.192+11:00| vmx| I125: USBIO: Up dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.192+11:00| vmx| I125: USBIO:  000: a3 00 00 00 03 00 04 00                         ........       

                            2020-02-13T16:37:59.192+11:00| vmx| I125: USBIO:  000: 00 01 00 00                                     ....           

                            2020-02-13T16:37:59.193+11:00| vmx| I125: USBIO: ClearFeature(feature=1, device=0)

                            2020-02-13T16:37:59.193+11:00| vmx| I125: USBIO: Down dev=2 'usb:1' endpt=0 stream=0 datalen=0 numPackets=0 status=0 0

                            2020-02-13T16:37:59.193+11:00| vmx| I125: USBIO:  000: 00 01 01 00 00 00 00 00                         ........       

                            2020-02-13T16:37:59.193+11:00| vmx| I125: USBIO: Up dev=2 'usb:1' endpt=0 stream=0 datalen=0 numPackets=0 status=0 0

                            2020-02-13T16:37:59.193+11:00| vmx| I125: USBIO:  000: 00 01 01 00 00 00 00 00                         ........       

                            2020-02-13T16:37:59.195+11:00| vmx| I125: USBIO: Class 0x00(wValue=0x0000, wIndex=0x0004)

                            2020-02-13T16:37:59.195+11:00| vmx| I125: USBIO: Down dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.195+11:00| vmx| I125: USBIO:  000: a3 00 00 00 04 00 04 00                         ........       

                            2020-02-13T16:37:59.195+11:00| vmx| I125: USBIO: Up dev=2 'usb:1' endpt=0 stream=0 datalen=4 numPackets=0 status=0 0

                            2020-02-13T16:37:59.195+11:00| vmx| I125: USBIO:  000: a3 00 00 00 04 00 04 00                         ........       

                            2020-02-13T16:37:59.195+11:00| vmx| I125: USBIO:  000: 00 01 00 00                                     ....           

                            ... lots more of these...

                            2020-02-13T16:37:59.796+11:00| vmx| I125: USBIO: Down dev=1 'usb:0' endpt=81 stream=0 datalen=8 numPackets=0 status=0 0

                            2020-02-13T16:37:59.796+11:00| vmx| I125: USBIO: GetDescriptor(config, 0)

                            2020-02-13T16:37:59.797+11:00| vmx| I125: USBIO: Down dev=3 'usb:2' endpt=0 stream=0 datalen=255 numPackets=0 status=0 0

                            2020-02-13T16:37:59.797+11:00| vmx| I125: USBIO:  000: 80 06 00 02 00 00 ff 00                         ........       

                            2020-02-13T16:38:19.714+11:00| mouse| W115: Poll timeout: Something may be hung... ungrabbing

                            2020-02-13T16:38:19.714+11:00| mouse| I125: MKS: Release starting (Poll timeout)

                            2020-02-13T16:38:19.714+11:00| mouse| I125: MKSGrab: Resetting grab...MKSGrab: MKS release: start, unlocked, nesting 0

                            2020-02-13T16:38:19.716+11:00| mouse| I125: MKSGrab: MKS release: end, unlocked, nesting 0

                            2020-02-13T16:38:19.716+11:00| mouse| I125: MKS: Release finished (Poll timeout)

                            • 26. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                              bevanweiss Novice

                              ivivanov I re-ran the USB verbose logging on the 15.1.0 release, and confirmed that it does indeed only become active if the VM itself is restarted.  I think that there should perhaps be a simple message box that warns of this when ticking the box for Verbose USB Logging if the VM is already running that says something like 'Verbose USB logging will only take affect on the next start of the Virtual Machine, the current session will not have Verbose USB logging applied'.

                               

                              I'll direct message you a link to the process dump.

                              • 27. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                                bevanweiss Novice

                                ivivanov ok it seems I can't send direct messages.

                                 

                                The process dump is 7zipped, and can be found at the link below

                                https://drive.google.com/open?id=1YM8A4DfXQcReVXAYyMc7BciMF3ewnohE

                                 

                                Hopefully that provides some additional information which can resolve the issue.

                                Logs are attached also.  This shows the same VM, starting up from shutdown.  Once it's started, then I plug in the USB, and attach it to the VM.

                                In 15.1.0 it didn't crash, so I then proceeded to remove the USB device before shutting down the VM again.

                                In 15.5.0 (without Enhanced keyboard driver installed), I plugged in the USB, things were still ok, then I assigned it to the VM, and things locked up.

                                 

                                Hopefully it helps.

                                • 28. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                                  hotvooboy Novice
                                  VMware Employees

                                  Thanks for your information. we've received the logs and dump files.

                                  • 29. Re: USB Device Causing VM's to Freeze - Cannot Kill vmware-vmx.exe
                                    ivivanov Expert
                                    VMware Employees

                                    Hi Eric and bevanweiss,

                                     

                                    Thanks for your support and for providing the additional details. Based on the new information I was able to root cause the issue - the code entered an endless loop while trying to process some unexpected data sent by the device. Yes, this issue is device-specific, but likely there are multiple devices that can expose this behavior.

                                     

                                    I am currently investigating the potential options for a fix.