Copy from
Client Hyper-V "Cannot Connect to Virtual Machine
Solution from Taylor Brown
If not we should enable some additional logging if possible to see what is going on.
- Shutdown any running VM’s
- Close all of the Hyper-V UI
- Stop the VMMS service (net stop vmms)
- Enable Analytic logging for the VMMS and Worker Process (see below)
- Enable UI Tracing for Hyper-V Manager and VMConnect (see below)
- Start the VMMS service (net start vmms)
- Open Hyper-V Manger
- Restart the VM
- Attempt to connect (try two or three times)
- Gather Logs (see below)
- Disable Tracing (see below)
- Open the Event Viewer
- From the menu bar select View -> Show Analytic and Debug Logs
- Navigate to the Hyper-V logs and Enable the Analytic Channels
Applications and Services Logs
MicrosoftWindows
Hyper-V-VMMS
AnalyticRight Click -> Enable (yes if a pop up asks about enabling the logs)
Hyper-V-Worker
AnalyticRight Click -> Enable (yes if a pop up asks about enabling the logs)
Enabling UI Tracing
- Create a new text file named “VMClientTrace.config” in the "%appdata%\Microsoft\Windows\Hyper-V\Client\1.0\” folder
- Copy the following XML text into that file:
- The Analytic logs will be in the analytic folder (you often have to refresh or select another source then analytic again to see them)
- The UI trace Logs will be in %temp% (sometime back one directory i.e. %temp% = “C:\Users\taylorb\AppData\Local\Temp\2” for me but the logs are at “C:\Users\taylorb\AppData\Local\Temp”
- To disable Analytic Tracing just right click on the analytic sources and select disable (same as enabling)
- To disable UI tracing just delete the “%appdata%\Microsoft\Windows\Hyper-V\Client\1.0\VMClientTrace.config” file.
