Wei-Ning,
Even the error message might be similar/same, your situation might be different from the original post. From the screenshot of the OP, the host is Windows while you have Ubuntu 20.04 LTS.
With 16.2.x the renderer for Linux hosts now uses Vulkan by default instead of OpenGL.
From the vmware.log
2022-03-18T23:50:38.566Z Wa(03) svga The vmx lost its connection to the mksSandbox.
2022-03-18T23:50:38.566Z Wa(03) svga The mksSandbox process may have crashed or hung.
2022-03-18T23:50:38.566Z Wa(03) svga Check the mksSandbox.log and vmware.log for more details.
2022-03-18T23:50:38.566Z Cr(01) svga PANIC: ISBRendererComm: Lost connection to mksSandbox (2713)
From the mksSandbox.log
It looks you have a GTX 1050 mobile GPU but the renderer switched to using the integrated Intel GPU. The Vulkan renderer right now looks for Turing or newer generation for Nvidia GPUs.
2022-03-18T23:48:47.890Z In(05) mks Vulkan Renderer: Available Vulkan devices:
2022-03-18T23:48:47.890Z In(05) mks Vulkan Renderer: Vulkan Device 0:
2022-03-18T23:48:47.890Z In(05) mks Vulkan Renderer: Name= ‘NVIDIA GeForce GTX 1050’
2022-03-18T23:48:47.890Z In(05) mks Vulkan Renderer: Vulkan Device 2:
2022-03-18T23:48:47.890Z In(05) mks Vulkan Renderer: Name: ‘Intel(R) HD Graphics 630 (KBL GT2)’
2022-03-18T23:48:47.890Z In(05) mks Vulkan Renderer: Using device 2 of 3
You can try one of two things. Both options require editing of vmx configuration file of the VM. Shut down the VM and before editing the VM vmx configuration file.
(1) switch to OpenGL
(2) force the Vulkan renderer to use the Pascal-based GTX 1050
For option (1), add the following lines
mks.enableVulkanRenderer = «FALSE»
mks.enableGLRenderer = «TRUE»
For option (2), add the following line
mks.vk.allowUnsupportedDevices = «TRUE»
Options (1) and (2) are mutually exclusive. So you have to the remove the lines of option (1) when you want to try (2) and vice-versa. Instead of deleting the lines you can add a # in front to comment out the dictionary entry.
For both (1) and (2) you could also add
mks.forceDiscreteGPU = «TRUE»
to ensure that the GTX1050 is used instead of the Intel iGPU as the rendering device.
Problem
Today something weird happened on my VMware Workstation 12 Player. I was unable
to run any of my virtual machines(VMs) stored on my computer. When I tried to
run a VM, an error message pop up, saying:
VMware Player cannot connect to the virtual machine.
Make sure you have rights to run the program, access all directories the program
uses, and access all directories for temporary files.
Failed to connect pipe to virtual machine. The
system cannot find the path specified.
If start VMware Workstation Player in administrator mode, the second part of the
error message became:
The vmx process exited prematurely.
Cause
Lots of attempts were performed based on the solutions found on Internet,
including disabling anti-virus software, re-installing VMware Workstation. But
none of the methods worked.
I then checked the Windows event log to see if I could find some useful information
there. Run the Event Viewer, go to Windows Logs — Application. Then I found an
application error record with the following message:
Faulting application name: vmware-vmx.exe, version: 12.5.6.19378, time stamp: 0x591415b1
Faulting module name: gameudp.dll_unloaded, version: 6.0.7.73, time stamp: 0x5917a9d7
Exception code: 0xc0000005
Fault offset: 0x000000000001129b
Faulting process id: 0x1af4
Faulting application start time: 0x01d2dcc9362379ba
Faulting application path: E:Program Files (x86)VMwareVMware Playerx64vmware-vmx.exe
Faulting module path: gameudp.dll
Report Id: 0e182361-bbb6-48d2-90f0-59e7256321c2
Faulting package full name:
Faulting package-relative application ID:
Combined with the previous error message displayed by VMware Workstation, I was
able to determine that the vmware-vmx.exe encountered some errors brought by
gameudp.dll while starting and was terminated.
Solution
Further research about this gameudp.dll indicates that it is not a part of the
original Windows system file and is safe to be removed. So I backed up this file,
then deleted it from C:WindowsSystem32. After that, I restarted VMware Workstation.
This time, the VM successfully started and the problem was solved.
Interestingly, later I restore the gameudp.dll back to its original location. The
VMware Workstation still functioned normally. The actual cause of the problem is
yet to be found and the role of gameudp.dll is still not clear.
Hope this article may help someone who has the same problem as I did!
If when you attempt to power on a VMware virtual machine on your Windows 11 or Windows 10 host machine, and the action fails with the error message The VMware Authorization Service is not running, then this post is intended to help you with the most suitable solutions to the issue.
VMware Workstation cannot connect to the virtual machine
When you encounter this issue, you’ll receive the full error message along the following lines;
VMware Workstation
VMware Workstation cannot connect to the virtual machine. Make sure you have rights to run the program, access all directories the program uses, and access all directories for temporary files.
The VMware Authorization Service is not running.
You’ll encounter this issue mainly due to either of the following reasons;
- The VMware Authorization service is not running.
- The service does not have Administrator rights.
If The VMware Authorization Service is not running on your Windows 11/10 PC, you can try our recommended solutions below in no particular order and see if that helps to resolve the issue.
- Restart PC
- Start the VMware Authorization Service
- Provide Administrator Rights to the VMware Authorization Service
- Repair VMware Workstation
- Contact VMware Support
Let’s take a look at the description of the process involved concerning each of the listed solutions.
1] Restart PC
You can begin troubleshooting to fix The VMware Authorization Service is not running on your Windows 11/10 PC by simply restarting your host machine. This action usually resolves minor issues like this. However, if the issue persists after performing the PC restart you can proceed with the next solution.
2] Start the VMware Authorization Service
To start the VMware Authorization Service or to check whether it is running on your system, do the following:
- Press Windows key + R to invoke the Run dialog.
- In the Run dialog box, type services.msc and hit Enter to open Services.
- In the Services window, scroll and locate the VMware Authorization Service.
- Double-click on the entry to edit its properties.
- In the properties window, click the drop-down on the Startup type and select Automatic.
- Next, click Start button to start the service if the service is already not showing a status of Started.
Note: The VMware Authorization service depends on the Windows Management Instrumentation service. This service must be running as well. If the VMware Authorization service does not start, or starts and then stops, locate and start the Windows Management Instrumentation service.
- Click Apply > OK to save changes.
- Restart PC.
But if the VMware Authorization service is already showing a status of Started and the issue in hand isn’t resolved, then the service does not have Administrator rights. Try the next solution.
3] Provide Administrator Rights to the VMware Authorization Service
To provide Administrator Rights to the VMware Authorization Service on your system, do the following:
- Disable User Account Control (UAC).
- Next, assign administrator rights to the user account that runs the VMware Authorization service on the Windows system.
- Next, uninstall VMware Workstation
- Reboot the host machine.
- On boot, log in as a local administrator (not as a domain administrator).
- Finally, download and reinstall the latest version of VMware Workstation on your PC.
The issue in view should be resolved now. Otherwise try the next solution.
4] Repair VMware Workstation
This solution requires you to perform a repair upgrade to fix the problem. A repair upgrade is a process of installing VMware Workstation over the existing one on your hard disk, using your installation package file. The procedure if successful can repair broken operating system files while preserving your personal files, settings and installed applications.
To perform a repair using the original VMware Workstation installer, do the following:
- Download the VMware Workstation installer.
- Once the installation package file is downloaded, you can start the repair immediately by simply double-clicking the file to mount it.
- In VMware Workstation Setup window, click on Next to continue repairing.
- Click Repair option and wait while the wizard performs the repairing process.
- Once the repair operation is completed, you can click Restart Now to initiate a reboot, or Restart Later if you plan to restart your system later.
On boot, the issue should be resolved. If not, try the next solution.
5] Contact VMware Support
If none of the solutions presented in this post worked for you, you can contact VMware Support at vmware.com/support/services and see what assistance they can provide to resolve the issue.
Hope this helps!
Related post: How to fix VMware Internal Error while powering on.
Why is my VMware not working?
If VMware is not working on your Windows 11/10 host machine, it could be due to a number of reasons. Generally, to fix the issue, you can shut down the virtual machine, then restart your Host Machine. After your host machine reboots, reopen the Workstation. Download and reinstall VMware Workstation. This ensures that you have the most recent version and that any missing or corrupted virtual network settings are replaced/repaired.
Will VMware run on Windows 11/10?
VMware Workstation runs on standard x86-based hardware with 64-bit Intel and AMD processors and on 64-bit Windows or Linux host operating systems. VMware Workstation Pro and Player run on most 64-bit Windows or Linux host operating systems.