Clipboard Only Works After You Paste? How to Fix It

A stuck clipboard is one of the most frustrating Windows problems because the symptom looks random. The user copies something, switches apps, tries to paste, and gets the previous content — or nothing. Then they paste once into Notepad, copy again, and suddenly everything works. The pattern is the clue: an app opened the clipboard, held onto it, and only released it after a paste completed. The clipboard was not broken; it was locked.

This guide walks through how to identify the app holding the clipboard, how to release the lock without rebooting, and how to prevent the problem from recurring. For related failures, see Win+Shift+S does nothing for the case where capture fails entirely, two clipboard managers fighting each other for the case where two tools are stepping on each other, and the broader Win+V not working on Windows 11: 9 fixes and clipboard history not saving items for related symptoms.

What "stuck until you paste" actually means

The Windows clipboard is a global resource. When an app calls OpenClipboard, it gets exclusive access until it calls CloseClipboard. If the app forgets to close — or hangs while the clipboard is open — no other app can write to or read from the clipboard until the lock is released.

The classic symptom is:

1. Copy text in app A.
2. Switch to app B and try to paste. You get the previous clipboard content (from before step 1), or nothing.
3. Paste the stale content somewhere — into Notepad, into a chat window, anywhere.
4. Try copying again. Now it works.

What happened at step 3 is that the paste completed whatever the holding app was waiting for, and the holding app released the clipboard. After release, new copies land normally.

This pattern is more common than it sounds. It is the cause of "Windows clipboard stops working every few hours" reports on machines that have a clipboard manager, a remote desktop client, or a screen capture tool running.

The classic culprits

A handful of app categories are responsible for most stuck-clipboard reports in 2026:

• Remote desktop clients — mstsc.exe (RDP), Citrix Workspace, VMware Horizon. These hold the clipboard open during redirection negotiations.
• Screen capture tools — ShareX, Snagit, Snipping Tool when it crashes mid-capture.
• Clipboard managers with their own listeners — Ditto, CopyQ, ClipboardFusion, third-party tools running alongside Win+V.
• Office add-ins and Adobe plugins — particularly Outlook add-ins that monitor the clipboard for "smart paste" features.
• Antivirus suites with clipboard monitoring — Kaspersky, Bitdefender, and others scan clipboard text for sensitive patterns. A stuck scan holds the clipboard.

If any of these are running, they are the first suspects.

Quick fix: paste into Notepad, then copy again

The fastest recovery is to paste the stale content anywhere — Notepad is convenient because it accepts plain text and does not lock the clipboard — and then immediately copy the new content. The paste triggers the holding app to release the clipboard, and the new copy lands.

This works for one-off stalls. It does not fix the underlying problem. If the stall recurs, move to the next layer.

Layer 1: identify the app holding the clipboard

Windows does not have a clean UI for "which app has the clipboard open right now." The reliable diagnostic is to use the GetClipboardOwner Win32 call, which returns the window handle of the app that currently has the clipboard open. Several free tools wrap this:

• Clipboard Viewer utilities — small tools that show the current clipboard owner. Some are open-source on GitHub.
• Process Explorer — Sysinternals tool that can show which process has certain kernel handles, though clipboard handles are not directly visible.

The simpler approach is binary-search close. Close suspect apps one at a time and re-test the clipboard after each close. When the clipboard starts working again, the most recently closed app was the culprit.

For most users, the binary-search approach is faster than installing a diagnostic tool.

Layer 2: restart the Clipboard User Service

Windows 11 has a user-level service called cbdhsvc (the Clipboard User Service, displayed as Clipboard User Service in services.msc). This service hosts the clipboard history infrastructure. When the service is misbehaving — typically because it has a stale handle from a previous app — restarting it can release the lock.

To restart the service:

1. Press Win+R, type services.msc, press Enter.
2. In the list, find Clipboard User Service. Note that there may be a per-user suffix like Clipboard User Service_12345.
3. Right-click and choose Restart. If Restart is greyed out, choose Stop and then Start.

After restart, test the clipboard. If it works, the lock was held by the service itself rather than by a user app.

For a deeper walkthrough, see how to restart the clipboard user service.

Layer 3: restart explorer.exe

If restarting the Clipboard User Service does not help, the next step is to restart explorer.exe. The Windows shell holds a clipboard viewer registration, and a stuck shell can hold the clipboard open indirectly.

To restart explorer.exe safely:

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Find Windows Explorer in the Processes list.
3. Right-click and choose Restart. The taskbar and desktop will briefly disappear and return.

This is the classic "turn it off and on again" for the Windows shell. It is more invasive than restarting a service but less invasive than rebooting. For the full breakdown of when this helps and when it is cargo cult, see explorer.exe restart to unstick copy-paste.

Layer 4: rule out a second clipboard manager

Two clipboard managers running at the same time is a common cause of stuck clipboards. Win+V is itself a clipboard manager; running Ditto, CopyQ, or ClipboardFusion alongside Win+V means two listeners are competing for the same clipboard events, and one of them can hold the clipboard open while the other tries to write.

The fix is to disable one. Either:

• Turn off Win+V history in Settings → System → Clipboard → Clipboard history.
• Or exit the third-party clipboard manager from its tray icon.

For the wider problem of running two tools at once, see two clipboard managers fighting each other and can you run two clipboard tools at once.

Layer 5: rule out a remote desktop or VDI client

Remote desktop clients are notorious for holding the clipboard open during redirection. If a remote session is connected — RDP, Citrix, VMware Horizon, Parallels — the local clipboard is being mirrored to the remote session, and a slow or stalled connection can leave the clipboard in a half-open state.

To test:

1. Disconnect the remote session.
2. Try copying and pasting locally.

If the clipboard works after disconnecting, the remote client is the culprit. The fix is usually to update the client to the latest version, or to disable clipboard redirection for that session. For RDP specifically, see remote desktop copy paste not working and RDP files paste but text does not (or the reverse). For Citrix and other VDI, see Citrix and VDI clipboard redirection.

Layer 6: check for an antivirus clipboard scan

Some antivirus suites scan clipboard text for sensitive patterns (credit card numbers, passwords, etc.) and hold the clipboard open while the scan runs. A scan that hangs — typically because of a definition update clash or a slow disk — leaves the clipboard locked.

To test:

1. Temporarily disable clipboard scanning in the antivirus settings (the option is usually called Clipboard protection, Clipboard scanning, or similar).
2. Test the clipboard.

If the clipboard works with clipboard scanning disabled, the antivirus is the culprit. The fix is usually to update the antivirus definitions and reboot, or to whitelist the apps the user copies from most often.

For more on this, see third-party antivirus blocking clipboard access.

Prevention

Once the immediate problem is solved, a few habits prevent recurrence:

• Run only one clipboard manager at a time. Win+V or a third-party tool, not both.
• Keep remote desktop clients updated. RDP client updates are bundled with Windows Update; Citrix and VMware clients update through their own channels.
• Keep antivirus definitions current. Stuck scans are often caused by definition corruption.
• Reboot weekly. A weekly reboot clears accumulated clipboard handles and is the cheapest preventive maintenance available.

When to give up and reboot

If layers 1 through 6 do not restore the clipboard, the practical answer is to reboot. Rebooting clears all clipboard handles, restarts all services, and re-initializes the shell. It is the catch-all that solves the stubborn cases.

The goal of this guide is not to avoid rebooting entirely. It is to identify the underlying cause so that the problem does not recur after the reboot. A reboot without diagnosis is a temporary fix; a reboot with diagnosis is a permanent one.

Related reading

• Two Clipboard Managers Fighting Each Other
• Clipboard History Grayed Out by Organization
• Win+V Not Working on Windows 11: 9 Fixes
• Best Free Clipboard Manager for Windows

Sources

• Microsoft Support — Using the clipboard on Windows — official description of clipboard history and how the clipboard interacts with apps
• Microsoft Learn — OpenClipboard function — Win32 API documentation that explains the exclusive-lock model the clipboard uses
• Microsoft Learn — GetClipboardOwner function — Win32 API that returns the window handle of the app currently holding the clipboard
• Microsoft Learn — Clipboard User Service — Windows application management documentation that covers the cbdhsvc user service
• Sysinternals — Process Explorer — Microsoft Sysinternals tool for inspecting which process holds which handle

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