VM Clipboard Sharing Broken on Hyper-V? Let’s Fix It

1. Enhanced Session Mode Isn’t Enabled (The One That Gets 9 Out of 10 People)

I know it’s infuriating when you copy a command from your host, switch to the VM, and nothing happens. You press Ctrl+V again. You check the clipboard viewer. Still empty. The culprit, more often than not: Enhanced Session Mode is disabled on the host.

Here’s the thing — Hyper-V’s basic clipboard sharing does not work without Enhanced Session Mode. It’s not a bug, it’s by design. The basic VMConnection window only passes clipboard data when the session is enhanced. And on a fresh Windows Server 2022 or Windows 11 Pro install, that setting is often turned off by default.

Let’s fix it:

1. Close any open VM connections.
2. Open Hyper-V Manager on the host.
3. In the right-hand pane, click Hyper-V Settings.
4. Under Server, select Enhanced Session Mode Policy.
5. Check Allow enhanced session mode.
6. Click OK.

That’s it for the host side. Now, when you connect to a VM, the window will prompt you with a session options dialog. Click Show Options, then Local Resources. Make sure Clipboard is checked. If it isn’t, tick it. Hit Connect.

If you see the prompt and clipboard is already checked, but copying still doesn’t work, move to the next cause. But for most people, this single checkbox is the whole story.

2. The VM’s Guest Services Service Is Stuck or Disabled

Sometimes you enable Enhanced Session Mode, check clipboard in the RDP settings, and it still won’t paste. You start asking yourself whether the VM is just stubborn. In those cases, I’ve found the Hyper-V Guest Services service inside the VM itself needs a kick.

This service runs on the guest OS and handles clipboard, file copy, and other integration features. If it’s set to Manual and hasn’t started, or if it crashed after a Windows Update, you’ll get the black hole clipboard effect.

Here’s what to do inside the VM:

1. Log into the VM (if you can type — use the Type Clipboard or just reboot if you’re locked out).
2. Press Win + R, type services.msc, hit Enter.
3. Scroll down to Hyper-V Guest Services.
4. Right-click it, select Properties.
5. Set Startup type to Automatic.
6. If the service isn’t running, click Start.
7. Click OK.

While you’re in Services, also check Hyper-V Data Exchange Service and Hyper-V Heartbeat Service. Set those to Automatic as well. I’ve seen a chain reaction where one of those failing causes the Guest Services to hang.

After starting the service, close the VM connection and reconnect via Enhanced Session. If clipboard starts working, you’re done. If not, reboot the VM and try again. Sometimes the service needs a clean start.

3. The RDP Clipboard Redirection Is Blocked by Group Policy

This one trips up IT admins who’ve locked down their VMs with Group Policy. You can have Enhanced Session Mode enabled, Guest Services running, and clipboard still won’t pass. That’s when I start checking the RDP policies.

There’s a specific policy: Do not allow Clipboard redirection. If it’s set to Enabled, the VM will silently ignore all clipboard requests from the host. The VM’s RDP stack is basically saying “nope” to your paste.

To check and fix it:

1. Inside the VM, press Win + R, type gpedit.msc, hit Enter.
2. Navigate to Computer Configuration > Administrative Templates > Windows Components > Remote Desktop Services > Remote Desktop Session Host > Device and Resource Redirection.
3. Double-click Do not allow Clipboard redirection.
4. Set it to Not Configured or Disabled.
5. Click OK and close the editor.

If the VM is joined to a domain and you see Enabled with a note that it’s enforced by a domain GPO, you’ll need to contact your domain admin. They can create a GPO that sets this policy to Disabled and link it to the OU where the VM lives. Yes, it’s a pain, but it’s the only clean fix.

Once the policy is changed, run gpupdate /force in a command prompt (admin) inside the VM, then reconnect. Clipboard should work now.

Quick-Reference Summary Table

One last tip I always give: if clipboard sharing is still broken after all three fixes, try copying a single line of plain text from the host. Sometimes rich text or images trigger a weird formatting conflict. But honestly, 95% of the time it’s one of these three. You’ve got this.