Windows Server Core VM fails to display the cmd prompt

Products

• VMware vSphere ESXi

Issue/Introduction

Symptoms:

• Windows Server Core VM running on hardware version 11 fails to display the cmd prompt.
• Virtual machine console shows black screen and a blinking cursor.
  
  Note: This issue is observed when using vSphere Client and vSphere Web Client.
  
  
• In the vmware.log file, you see entries similar to:
  
  
  
  2016-12-12T21:25:54.326Z| vmx| I120: Tools_SetGuestResolution: Sending rpcMsg = Resolution_Set 1920 993

  2016-12-12T21:25:54.407Z| mks| W110: VNCENCODE 130 failed to allocate VNCBlitDetect

  2016-12-12T21:25:54.407Z| mks| W110: VNCENCODE 130 failed to allocate VNCBackBuffer

  2016-12-12T21:25:54.886Z| vcpu-1| I120: VigorTransport_ServerSendResponse opID=365ad60a-81-90fe seq=789: Completed MKSVMX request.

  2016-12-12T21:25:57.186Z| vmx| I120: VigorTransportProcessClientPayload: opID=3e417f72-73-9112 seq=816: Receiving MKS.SetGuestResolution request.
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
  

Environment

VMware vSphere ESXi 6.0

Resolution

Currently, there is no resolution.

To work around this issue:

1. Click inside the console until minimize or maximize button appears.
2. Click either of the buttons to resize the cmd window.

Additional Information

To be alerted when this document is updated, click the Subscribe to Article link in the Actions box.