app| Error during launch: 11, Virtual machine failed to start. Err 11 = "Unexpected response from VMAuthd"
Purpose
This article describes the permissions necessary to power on a virtual machine. The article also guides you through the troubleshooting steps to correct unexpected virtual machine behavior related to a specific username or configuration settings.
With the exception of the configuration (.vmx ) file for the virtual machine, all virtual machine files and their parent directories have read and write file system permissions.
The configuration (.vmx ) file for the virtual machine has read and execute file system permissions.
The username being used to power on the virtual machine does not have security restrictions in place that limit the file system permissions in steps 1-2.
Note: This can be tested by logging in as a user with Administrator or root permissions and confirming if the virtual machine still does not power on.
If you are using GSX or VMware Server, you are using the VMware Server Console or Machine User Interface (MUI).
Note: Unexpected behavior may result from the use of a Remote Desktop Protocol (RDP) or Terminal Services session to remotely control a virtual machine. This behavior can include failing to power on the virtual machine and seeing a black screen when attempting to view it.
If you are using a Windows version of GSX or VMware Server and the virtual machine powers off every time you log out of the server:
Power down the virtual machine.
Click the entry for the virtual machine from the VMware application window.
Click Edit virtual machine settings.
Click the Options tab.
Click Startup/Shutdown.
Click Local system account in the Run this Virtual Machine As" section.
Click OK.
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.
