VMware Communities
woolie161
Contributor
Contributor

VMWare Pro 15 Stalls when External USB is connected to Host

Hi All,

      I'm not sure if I'm in the right place to ask this question, so please redirect me if required.

I am running WMWare Pro 15.5 and on my old computer with OS = Win 7 I had no problems when I attached an external USB Drive to either the host or the guest.

I have since purchased a new Laptop, Lenovo Legion with OS = Win 10 Pro Build 1809.  My issue is every time I attach a USB Drive the computer stalls (temporary freeze) for up to 10 minutes when VMWare is running.  If VMWare is not running, there is no issue with external USB Drives.  I have multiple VM's with different operating systems and all are affected.  I have tried configuring USB options to only connect to the Host (my perfered selection) Ask before connecting etc.  I have also tried changing the USB compatibility from 3.0, to 2.0 and 1.1 without resolving the issue.

The difference between my old laptop and new laptop

Old:  OS = Win7 16GB Ram  1 only 1TB HDD,  but only had USB 2 ports

New: OS = Win10 Build 1809 16GB Ram 1only 256GB SSD (where VMWare Pro 15.5 is loaded) and 1 only 1TB HDD where the different Virtual Machine files reside) only has USB 3 ports.

Can anybody suggest some suggestions that will allow me to connect an External USB to the Host machine whilst running a Virtual Machine with freezing the computer for a long time.  If I am patient enough, the system will recover and everything works as it should.

Thank you.

Woolie161

30 Replies
woolie161
Contributor
Contributor

Hello Bonnie201110141,   I have completed the tasks as requested and the log files are attached.

The External USB Drive was connected at              04:29:00 (24Hr Time)

Windows Explorer / Virtual Machine "un-froze" at    04:39:55

                                                                   Time Frozen = 55 Seconds

Once again I appreciate your help and persistance.

Woolie 161

Reply
0 Kudos
bonnie201110141
VMware Employee
VMware Employee

Thanks for your quick response! And sorry for having you try this and that.

We are still investigating this issue. Will you please give it another try?

I attached a zip file which contains two vmware-vmx-debug.exe binary and one vc runtime debug dll.

0. copy vcruntime140d.dll to C:\Program Files (x86)\VMware\VMware Workstation\x64\

1. Please replace C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx-debug.exe with vmware-vmx-debug_0.exe (please rename it to the correct name). Let us know if the problem persists. Logs are not needed for this try.

2. Replace the C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx-debug.exe with vmware-vmx-debug_1.exe (please also change the name to the correct one). Then do the followings:

1). Stop service VMwareHostd. Make sure it is kept stopped before the final step.

2). add

vmx.buildType=debug

loglevel.user.main = 10

loglevel.user.vigor = 10

loglevel.user.usb = 10

to the VM's .vmx config file.

3). Boot VM via administrator account with command

"C:\Program Files (x86)\VMware\VMware Workstation\x64\vmware-vmx-debug.exe" "-x" "-s" "vmx.stdio.keep=TRUE" "-#" "product=1;name=VMware Workstation;version=15.5.0;buildnumber=14665864;licensename=VMware Workstation;licenseversion=15.0+;" "D:\_VirtualMachines\Rockwell_V32_Win7x64\Rockwell_V32_Win7x64.vmx"

3). Plug in the device, and record the exact device plug in time and the time of freeze stop.

4). After reproduced, please return the usbarb and vmware.log together.

Reply
0 Kudos
woolie161
Contributor
Contributor

Hello Bonnie201110141,

        I have attempted to comply with your last request.  I have pasted the new ".dll" file and I have coppied / renamed the Debug_0 file into the VMWare Workstation config file.

I booted the VM using the standard GUI.  Following is the result

Debug_0.exe         The External USB was connected at 13:57:00 (24Hr Time)

                               Windows explorer "Un-Froze"     at 13:58:12

                                                             Total Time  1 Minute 12 Seconds

I then pasted / renamed the Debug_1 file into the Config file, but when I tried to start the VM from the Command Prompt, an error message was received.  I have attached a screen grab, showing the error message.

I think I have followed the test procedure as per your instruction, so I am unsure if it is your "Debug_1.exe" code causing the error or something I have done.

In saying that, I have since manage to start the VM using the original "Debug" file and your other file "Debug_0"

Thank you for your continued interest with this issue.

Woolie 161

Reply
0 Kudos
GeorgeGa
VMware Employee
VMware Employee

Hi woolie161,

Could you please try debug_0.exe with the steps for debug_1.exe and return the logs if issue persisted? No need to collect logs if not reproduced. Thanks.

Reply
0 Kudos
woolie161
Contributor
Contributor

Hi GeorgeGa,

            It must be something I'm doing.  I replaced the original "debug.exe" with "Debug_0.exe" and now when I try to start using command prompt the same error is reported as when I tried "Debud_1.exe".  If I restore the original "Debug.exe" the VM will start as normal.  I have even downloaded the ".zip" file supplied and attempted to start the VM with both the "Debug_0 & Debug_1"

files with the same error about not finding the "ucrtbased.dll" file.  see attached screen grab.

Reply
0 Kudos
GeorgeGa
VMware Employee
VMware Employee

Thanks woolie161.

The issue is hard to debug without opening verbose debug log level from vmx side. Unfortunately we could not deliver binaries compiled with debug log level opened according to company policy. Till now, all logs show no suspicious clue in vmx. Since the issue is specific to one env, we couldn't do more without the env. As the last try, you could uninstall other softwares to make the env clean and try again. Some conflicts may exist between ws and others.

We are also letting UI engineers check the logs. If still no more clues, we would stop working on this issue unless the laptop could be ship to us. Very sorry for that.

Reply
0 Kudos
haiweiz
VMware Employee
VMware Employee

Hi, woolie161:

Thanks your support, most likely this issue is caused by some locks, would you mind try to collect the crash dump for us to continue?

After you reproduce this issue, during the UI and VMX hang, open task manager, go to "details" tab, find the vmware-vmx and vmware process, right click the process name (vmware-vmx and vmware), select "create dump file". The generated dump file locate %temp%\vmware.dmp and %temp%\vmware-vmx.dmp.

Please upload them to us for next step.

Thanks.

Reply
0 Kudos
nkaufman
Enthusiast
Enthusiast

Didn't want to contaminate this thread and hence have just been watching.

Now that you seem to be giving up, I thought I'd let you know that I've been experiencing something similar, see my post mentioned below

WS15.5 VM crashes on resume

Thanks

Reply
0 Kudos
nkaufman
Enthusiast
Enthusiast

OP - Can you check what option is selected under

VM - > Manage -> Change Hardware Compatability

Click on Next on First Screen and in the first dropdown select 15.5 and then you can select the options that suit you such as 'Clone first' and then apply.

After having done that, my VM BSOD from resume has disappeared ever since, though it has been only a few days but not ONE BSOD.

Reply
0 Kudos
woolie161
Contributor
Contributor

Hello nkaufman,

          Thanks for taking an interest.  I have sort of given up.  I know it is a big question for support to correct remotely and I appreciate the time and effort that they offered.

Currently the compatibility is set to "Workstation 15.x" as I don't have an option to enter "15.5".  I also have the USB option set to "Connect to Host" but I have tried all 3 USB options with no success.

My issue seems to be related to Windows 10 as I tried inserting a USB Thumb drive on my old Win 7 Laptop with no issues.  I am reluctant to update Win 10 to the latest version due to issues with some of the industrial software I run.

Again thanks for making contact and if I find a solution I'll definitely Woolie

Reply
0 Kudos
nkaufman
Enthusiast
Enthusiast

Completely forgot to update this thread.

It worked for a few days but I've been getting a BSOD now again though less frequently..

Such a shame that VMWare cannot even research this issue further...

Reply
0 Kudos