VM Guest Clipboard Integration Broken

A VMware, VirtualBox, or Hyper-V guest that suddenly stops sharing clipboard with the host almost never has a Windows-side problem. The cause is missing or outdated guest tools, a one-way direction setting, or a Linux session that is not running the clipboard helper daemon. This guide covers the fix order for each hypervisor, the bidirectional toggle that everyone misses once, and where Win+V stops at the VM boundary.

For the wider remote-session picture, see Citrix and VDI clipboard redirection for the enterprise VDI case, Windows Sandbox has no lasting history for the disposable-VM case, and the general Win+V not working on Windows 11: 9 fixes and Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11 references.

What is in scope

Workstation hypervisors in 2026:

• VMware Workstation Pro (free for personal use since 2024) and VMware Player, with VMware Tools or open-vm-tools inside the guest.
• Oracle VirtualBox with the VirtualBox Guest Additions inside the guest.
• Hyper-V (built into Windows Pro and above), using Enhanced Session Mode for clipboard and drive redirection.

This is the local-VM case, distinct from enterprise VDI. For Citrix, RDSH, AVD, and Horizon, see Citrix and VDI clipboard redirection. For the disposable Windows Sandbox case, see Windows Sandbox has no lasting history.

The shared model

All three hypervisors use the same pattern: a small daemon inside the guest watches the guest clipboard and forwards changes to the host, and the host forwards its clipboard changes back. The host's clipboard is the broker; the guest daemon is the bridge. If the daemon is not running, the bridge is down and clipboard integration silently fails.

For Windows guests, the daemon is installed with VMware Tools or VirtualBox Guest Additions. For Linux guests, the daemon is vmware-user-suid-wrapper (VMware) or VBoxClient --clipboard (VirtualBox), and it must be running in the user's X or Wayland session.

What does not cross the VM boundary

• Win+V history. Windows clipboard history is local to whichever machine opened Win+V. Copy from host to guest carries only the most recent item; the 25-item history stays on the host.
• Pinned items. Pinned Win+V entries stay on the machine they were pinned on.
• Cloud sync. Win+V cloud sync is PC-to-PC and does not extend into a guest VM, even when both are signed into the same Microsoft account.
• Third-party clipboard managers. Ditto, CopyQ, or Edge-Drop running on the host see only the host's clipboard. The guest has its own clipboard, and a manager running inside the guest sees only the guest's clipboard.

VMware Workstation: fix order

VMware Workstation uses two toggles plus a guest-side daemon.

• Install VMware Tools or open-vm-tools in the guest. Without tools, no clipboard integration exists. On Windows guests, install VMware Tools from the VM menu. On Linux guests, install open-vm-tools and open-vm-tools-desktop from the package manager.
• Enable Guest Isolation in VM settings. VM → Settings → Options tab → Guest Isolation. Tick Enable copy and paste. The "Enable drag and drop" toggle is separate and governs file drag only.
• Restart the guest. A running guest does not always pick up the new Guest Isolation setting until it is rebooted.
• On Linux guests, confirm vmware-user is running. A quick check is ps aux | grep vmware-user. If it is not running, the desktop autostart file is missing or the user session did not launch it. Log out and back in, or run vmware-user-suid-wrapper & manually.

VMware's documentation covers the guest isolation toggles in the Workstation Pro admin guide; the policy names there are authoritative.

VirtualBox: fix order

VirtualBox uses a per-VM setting plus the Guest Additions.

• Install Guest Additions in the guest. Devices menu → Insert Guest Additions CD image. On Windows guests, run the installer. On Linux guests, build the kernel modules and install the helpers.
• Set the shared clipboard direction. Devices menu → Shared Clipboard → Bidirectional. The default is Disabled; one-way (Host to Guest or Guest to Host) is also available.
• Set Drag and Drop separately if needed. Devices menu → Drag and Drop → Bidirectional. File drag is independent of the clipboard channel.
• Restart the guest after Guest Additions install. The kernel modules and the VBoxClient helper must load at session start.
• On Linux guests, confirm VBoxClient --clipboard is running. A check is ps aux | grep VBoxClient. If it is not running, the desktop autostart file is missing; run VBoxClient --clipboard & manually to test.

The VirtualBox User Manual documents the Shared Clipboard menu and the Guest Additions requirements.

Hyper-V: Enhanced Session

Hyper-V does not have a separate clipboard daemon. Clipboard flows through RDP when Enhanced Session Mode is on.

• Enable Enhanced Session Mode. Hyper-V Manager → Tools → Hyper-V Settings → Server → Enhanced Session Mode Policy → tick Allow Enhanced Session Mode. Also tick the same under User → Enhanced Session Mode.
• Connect to the VM. When connecting, the Enhanced Session dialog prompts for display resolution and local resources. Tick Clipboard under Local Resources.
• For Linux guests on Hyper-V, use xrdp inside the guest. Hyper-V's Enhanced Session for Linux relies on xrdp to provide the RDP endpoint; without it, Enhanced Session does not work and clipboard falls back to nothing.

If rdpclip.exe hangs inside a Windows guest, the symptom is one-direction-only clipboard. Restart rdpclip.exe in Task Manager, or reconnect the session. See remote desktop copy paste not working for the full RDP sequence.

Linux guest: Wayland versus X11

Linux guests running Wayland do not always expose the clipboard to the VMware or VirtualBox client daemons, because Wayland's clipboard model is different from X11's. The daemons were built for X11 and may miss Wayland clipboard events entirely.

Workarounds:

• Use the X11 session of the desktop environment. Most desktops still offer an X11 session at the login screen. Switch to it for the guest's clipboard integration to work.
• Run wl-clipboard and bridge manually. For setups that must use Wayland, the wl-clipboard package provides wl-copy and wl-paste, and a small script can bridge to the VMware or VirtualBox daemon. This is fragile and rarely worth the trouble.
• Use a shared folder instead. For text snippets, a Hyper-V, VMware, or VirtualBox shared folder plus a small file-watcher script is more reliable than the clipboard channel on Wayland.

Two clipboard managers, one host

Running a clipboard manager on both the host and inside the guest produces the same race condition seen with VDI. Two managers compete for clipboard change notifications, and the user sees duplicate entries or stale content. Run clipboard management on one side only — typically the host, where the user's actual workflow lives.

For more on the conflict pattern, see can you run two clipboard tools at once. Edge-Drop, the Windows clipboard shelf, is one option on the host side. It does not reach into the guest; it sees what the host sees, which is the redirected clipboard.

UAC and integrity mismatches

A Windows guest can hit the same integrity-level mismatch as the host. A non-elevated app and an elevated app cannot exchange clipboard data in all configurations, and the failure is silent. If clipboard works between two non-elevated apps but fails when pasting into an elevated app, integrity level is the cause. Launch the destination app at the same integrity level as the source.

Troubleshooting checklist

• Confirm guest tools are installed and the version matches the host's hypervisor build.
• Confirm the direction setting is Bidirectional, not one-way or disabled.
• On Linux guests, confirm the clipboard daemon (vmware-user or VBoxClient --clipboard) is running in the user session.
• On Wayland Linux guests, switch to X11 or use a shared folder.
• On Hyper-V, confirm Enhanced Session Mode is on at both server and user level, and that the connect dialog has Clipboard ticked.
• If only one direction works on a Windows guest, restart rdpclip.exe or reconnect.
• Confirm the host and guest are not both running clipboard managers that race for notifications.

What to avoid

• Inventing a registry key or config flag. The hypervisor settings documented above are the only ones that exist. A "deep tweak" found on a forum that is not in the official docs is almost certainly wrong or stale.
• Trying to forward Win+V across the VM boundary. Win+V history is local; only the most recent clipboard item crosses.
• Enabling cloud sync as a workaround. Win+V cloud sync is PC-to-PC and does not extend into a guest VM.
• Treating the guest as a clipboard-storage location. Guest state is destroyed when the VM is shut down; nothing in the guest clipboard persists.

Related reading

• Windows Sandbox Has No Lasting History
• Third-Party Antivirus Blocking Clipboard Access
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows

Sources

• Microsoft Support — Using the clipboard on Windows — official statement of the 25-item, 4 MB, text-HTML-bitmap limits and the optional cloud sync that does not extend to VM guests
• VMware Documentation — VMware Workstation Pro — official guide covering Guest Isolation settings and the open-vm-tools package requirements
• VirtualBox Manual — Shared Clipboard — Oracle documentation covering Guest Additions, the Shared Clipboard menu, and the bidirectional toggle
• Microsoft Learn — Use local resources on Hyper-V virtual machine — Hyper-V Enhanced Session Mode documentation, including the Local Resources → Clipboard toggle
• Microsoft Learn — Remote Desktop Services — RDS documentation, relevant because Hyper-V Enhanced Session uses RDP and rdpclip.exe for clipboard

Copy. Stack. Drop.

Transform your clipboard into an interactive edge shelf. Stack, pin, and drag assets into any app with zero friction.

Download for Windows Get from Microsoft Store

How to Install Guide · First 10 Minutes Guide · Drag & Drop Guide · Edge-Drop vs Win+V · Support