Unable to Connect to VM via Hyper-V Manager – Remote Video Error

Francois P 20 Reputation points
2025-08-04T12:24:13.2133333+00:00

Hello everyone,

I'm experiencing an issue with my Hyper-V setup and I'm hoping someone might be able to help or share insights.

I have a Windows Server Core 2025 machine hosting Hyper-V. It's located on a remote network, which I access from my Windows 10 PC through a VPN connection. From my PC, I'm able to connect to the server using Remote Desktop, SSH, and Hyper-V Manager without any problems.

User's image

The issue arises when I try to launch a virtual machine. I create and start the VM using Hyper-V Manager. The small preview thumbnail appears in the lower corner, indicating the VM is running. However, I’m unable to connect to the VM directly. I receive an error message saying that "remote video has been interrupted" (or similar wording).

User's image

User's image

I've tried multiple solutions found across various forums, but nothing has worked so far.

Do you have any ideas or hypotheses?

Windows for business | Windows Client for IT Pros | Storage high availability | Virtualization and Hyper-V
0 comments No comments
{count} votes

Accepted answer
  1. Henry Mai 2,375 Reputation points Independent Advisor
    2025-08-05T09:06:27.9766667+00:00

    Hello Francois, I am Henry and I want to share my insights about your issue.

    The error "Video remoting was disconnected" means your client successfully told the host to start the VM, but when it tried to establish the separate video stream on port 2179, that connection failed. This points to a connectivity or authentication failure. The connection request from your client PC is being blocked before it can be fully processed by the Hyper-V service (VMMS).

    The most common blockers are:

    • The Firewall: Blocks the connection on the required port (TCP 2179).
    • Authentication Failure: Your credentials can't be passed correctly to the service (the "double-hop" problem), so the service rejects the connection.

    Before proceeding with troubleshooting, could you please open Event Viewer and check the Hyper-V-VMMS log to see if any error entries appear?

    Here's what I recommend for troubleshooting:

    You'll need to run these commands on the Server Core host, either through an SSH session or a remote PowerShell session (Enter-PSSession).

    Step 1: Enable the Firewall Rule on the Host Server

    1. Check the existing rule: Get-NetFirewallRule -DisplayName "Hyper-V (VMMS-In)"
    2. Enable the rule for all profiles to ensure it's not a firewall issue:

    Enable-NetFirewallRule -DisplayName "Hyper-V (VMMS-In)"

    Set-NetFirewallRule -DisplayName "Hyper-V (VMMS-In)" -Profile Any

    After running this, try connecting to the VM console again.

    Step 2: Remotely connecting to a VM console requires your credentials to be passed from the host to the VM service, a "double-hop" that is blocked by default. Enabling CredSSP fixes this.

    1. On your Windows 10 Client PC (run in an Administrator PowerShell): Enable-WSManCredSSP -Role Client -DelegateComputer "Your-HyperV-Host-Name"

    (Replace Your-HyperV-Host-Name with the actual name of your server).

    1. On your Windows Server Core Host (run in PowerShell): Enable-WSManCredSSP -Role Server

    After enabling it on both machines, try connecting to the VM console again.

    Step 3: Ensure your user account is a member of the local Hyper-V Administrators group on the host server.

    On your Windows Server Core Host, run this command in PowerShell to add your user: Add-LocalGroupMember -Group "Hyper-V Administrators" -Member "YourDomain\YourUser"

    (Replace YourDomain\YourUser with your actual username).

    You may need to close and reopen Hyper-V Manager for the new permissions to apply. Hope one of these works for you.

    2 people found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.