Hyper-V Manager can't connect to the host server - WinRM or permission errors

Symptoms

• Hyper-V Manager stuck on 'Connecting to Virtual Machine Management service...' or shows no VMs.
• WinRM/Kerberos errors such as 0x80090311 when connecting.
• VMConnect console fails ('Cannot connect to the virtual machine') from some machines.

Fix it yourself

1. Verify the Hyper-V Virtual Machine Management service (VMMS) is running on the host; restart it if hung.
2. Confirm the connecting user is a member of Hyper-V Administrators (or Administrators) on the host, and Remote Management Users where applicable.
3. Enable remoting on the host: 'Enable-PSRemoting'; for workgroup/cross-domain management also 'Enable-WSManCredSSP -Role server' on the host and '-Role client -DelegateComputer ' on the management machine.
4. On the management machine, add the host to WinRM TrustedHosts: 'Set-Item wsman:localhost\client\trustedhosts <host FQDN/IP>'.
5. Check firewall ports: TCP 2179 must be open for VMConnect console access, and LDAP 389 to domain controllers for authentication; enable the Hyper-V/Remote Management firewall rule groups.
6. Check DNS and Netlogon health - failed domain controller discovery breaks Kerberos for remote management.
7. If the console remains broken, test the same operations via PowerShell (Get-VM against the host) to isolate GUI vs. connectivity.

If that did not help

Attach the exact error, whether PowerShell remoting to the host works, the user's group memberships on the host, WinRM configuration (winrm get winrm/config), and firewall state for ports 2179/5985.