Sorry for the late response! Will you please enable debug mode from vm > settings > options > advanced > Gather debugging information to "Full", and attach all vmware*.log and mksSandbox*.log, as wel...
See more...
Sorry for the late response! Will you please enable debug mode from vm > settings > options > advanced > Gather debugging information to "Full", and attach all vmware*.log and mksSandbox*.log, as well as the vmware-vmx-debug.dmp file (all from the VM directory)? And also, can you give it a try if disabling 3D can workaround the issue? Please disable 3D from vm settings > hardware > display > uncheck Accelerate 3D graphics?
So from vmware.log, this VM is not shut down, instead, vmware-vmx process crashed. I think the VM does not have to run in background for it to crash. You might leave the VM running with VMware Workst...
See more...
So from vmware.log, this VM is not shut down, instead, vmware-vmx process crashed. I think the VM does not have to run in background for it to crash. You might leave the VM running with VMware Workstation UI for some time, it might crash too. From the log, the VM is Windows 2000. Does that mean any VM in your environment will crash after running some time?
Will you please enable debug mode from vm > settings > options > advanced > Gather debugging information to "Full", and attach the vmware.log when the VM shuts down?
Yes, we are definitely working on this issue and we have made good progress internally. But I am not supposed to tell about the detailed time. Sorry about that. For USB headset, plugging to USB 2.0 p...
See more...
Yes, we are definitely working on this issue and we have made good progress internally. But I am not supposed to tell about the detailed time. Sorry about that. For USB headset, plugging to USB 2.0 port and using USB 2.0 controller for the VM is also a workaround.
The event viewer complains about VMware Workstation Server which is a service to run shared VM. I suppose your VM is a local VM instead of a shared VM. So this might be two different things. When yo...
See more...
The event viewer complains about VMware Workstation Server which is a service to run shared VM. I suppose your VM is a local VM instead of a shared VM. So this might be two different things. When you find the VM is shut down, if you open the VM, is the VM in power-off state or suspend state? If the VM is in suspend state, it might be caused that you guest OS goes to sleep when inactive for some time. Anyway, we will try if we can reproduce the issue locally.
This is a known issue. Please plug the USB devices to USB 2.0 port on physical machines, and change USB controller to USB 2.0 from vm > settings > USB controller. Then connect your USB device to the ...
See more...
This is a known issue. Please plug the USB devices to USB 2.0 port on physical machines, and change USB controller to USB 2.0 from vm > settings > USB controller. Then connect your USB device to the VM and try again. Let me know if it works for you.
Hi russtanner I cannot open the thread you posted. It says "The message you are trying to access is not available.". Maybe it is due to the new community?
When you remove the rule files, did you close VMware Workstation? Please also attach C:\Windows\Temp\vmware-SYSTEM\vmware-usbarb-*.log files when reproducing the issue. Thanks!
Hello, Sorry you ran into the installation issues. Will you please try "VMware-Workstation -*.exe -r" to repair the Workstation installation? The VMware-Workstation-*.exe is the installation f...
See more...
Hello, Sorry you ran into the installation issues. Will you please try "VMware-Workstation -*.exe -r" to repair the Workstation installation? The VMware-Workstation-*.exe is the installation file you downloaded. After that please reboot host and run the installer again. Let me know if it works for you.
Hi user_0110, In your VM, from task manager, are there two "vmtoolsd" processes running? For your tools.conf file, I think you need to add [logging] at beginning of the file.
Hi, Will you please enable tools log in your guest operating system as below? 1. Create a folder maybe on your desktop in your guest os to store the tools log. Let 's say C:\users\${USER}\d...
See more...
Hi, Will you please enable tools log in your guest operating system as below? 1. Create a folder maybe on your desktop in your guest os to store the tools log. Let 's say C:\users\${USER}\desktop\toolsLog. 2. Added below line in your C:\ProgramData\VMware\VMware Tools\tools.conf (Create the file if not exist) in your guest os [logging] log = true # Enable tools service logging to a file. vmtoolsd.level = debug vmtoolsd.handler = file vmtoolsd.data = C:/users/${USER}/desktop/toolsLog/vmtoolsd.${USER}.log # Enable 'vmsvc' service logging to a file. vmsvc.level = debug vmsvc.handler = file vmsvc.data = C:/users/${USER}/desktop/toolsLog/vmsvc.log # Enable 'dndcp' service logging to a file. dndcp.level = debug dndcp.handler = file dndcp.data = C:/users/${USER}/desktop/toolsLog/dndcp.log # Enable new "vmusr" service logging to a file. vmusr.level = debug vmusr.handler = file vmusr.data = C:/users/${USER}/desktop/toolsLog/vmusr.${USER}.log 3. restart the guest and reproduce the issue 4. Send us the logs in C:/users/${USER}/desktop/toolsLog
For the old tools issue, we are still investigating it. From logs provided by GT500org, the installed indeed skipped to replace the tools iso fies (windows.iso, linux.iso, etc from WS installatio...
See more...
For the old tools issue, we are still investigating it. From logs provided by GT500org, the installed indeed skipped to replace the tools iso fies (windows.iso, linux.iso, etc from WS installation directory) because it detects that those iso files were modified. Can somebody let us know if you ever maybe used CDS to update those iso files? Thanks a lot!
Vmware Tools 11.1.5 is the correct version in Workstation 16.0. And DX11 is supported on Linux host with NVIDIA GPU. Please see VMware Workstation 16 Pro Release Notes
We are aware of this issue and has an internal bug to track it. You can try to add below line to the VM 's .vmx file as a workaround: cpuid.7.edx = "----:----:----:----:----:----:---0:----"
