Is It Windows or the App? Test the Clipboard Itself

When paste stops working, the first instinct is often to blame the clipboard manager — Win+V, Ditto, CopyQ, or an edge shelf like Edge-Drop. That instinct is usually wrong. The Windows clipboard is a system service, and most paste failures are app-level, shortcut-level, or input-method-level, not clipboard-service-level. This guide gives a five-minute test that isolates the OS clipboard from everything around it. If the test passes, the manager is innocent; if it fails, the manager is the last thing to look at.

For neighbouring topics, see Win+V not working on Windows 11: 9 fixes, language packs that steal Win+V, Win+V Says 'Nothing Here'? How to Fix Clipboard History on Windows 11, and safe mode and a clean boot for clipboard bugs. The aim of this article is to be the first diagnostic you run, before any of those deeper fixes.

Why an OS-level test matters

The Windows clipboard has several layers, and each can fail independently:

A failure in any one layer can look like "the clipboard is broken." The test below checks layer one (the service) directly, bypassing history, managers, and most app handlers. If layer one is healthy, the search narrows to the upper layers.

Test 1: the Notepad text round-trip

This is the canonical test. Notepad ships with Windows, has no clipboard integrations of its own, and uses the OS clipboard directly.

1. Open Notepad (Win+R, type notepad, press Enter).
2. Type a unique string — for example, clipboard-test-2026-08-19.
3. Select all (Ctrl+A).
4. Copy (Ctrl+C).
5. Open a second Notepad window.
6. Paste (Ctrl+V).

Expected: the unique string appears in the second window, identical to what was typed.

If the paste is empty, garbled, or contains a previous clipboard entry, the OS clipboard is not healthy and the rest of this guide applies. If the paste is clean, the OS clipboard is fine and the issue is in a higher layer.

Test 2: the image round-trip

Text and images travel different clipboard formats. A service can break one and not the other, so test both.

1. Open Snipping Tool (Win+Shift+S), capture a small region of the screen.
2. Open Paint (mspaint from the Run dialog).
3. Paste (Ctrl+V).

Expected: the captured snip appears in Paint.

If text works (Test 1) but images do not, the bitmap format is not arriving on the clipboard. This often points to an antivirus or a screen-capture blocker. If neither works, the clipboard service itself is the suspect.

Test 3: the file copy round-trip

Files use the HDROP clipboard format, which is separate from text and bitmap. Win+V history does not store files as first-class cards — only text, HTML, and bitmap — but the live clipboard does carry files.

1. In Explorer, select a small file (a .txt is fine).
2. Press Ctrl+C.
3. Navigate to a different folder.
4. Press Ctrl+V.

Expected: a copy of the file appears in the destination folder.

If file copy fails but text and image work, the issue is with Explorer or with the file's permissions, not with the clipboard service itself.

Test 4: PowerShell Get-Clipboard and Set-Clipboard

For a more authoritative answer, use PowerShell's built-in cmdlets. These talk directly to the clipboard API.

Set-Clipboard -Value "os-clipboard-probe-001"
Get-Clipboard

Expected output: os-clipboard-probe-001.

If Get-Clipboard returns empty or returns a stale value, the OS clipboard is not responding to API calls. The official PowerShell documentation for Get-Clipboard and Set-Clipboard covers the parameters in detail.

A second probe using clip.exe, which pipes stdin to the clipboard:

echo probe-002 | clip

Then in PowerShell:

Get-Clipboard

Expected: probe-002. If clip.exe writes successfully but Set-Clipboard does not (or vice versa), one of the two APIs is being blocked — a classic antivirus behaviour.

Test 5: confirm the clipboard service is running

The clipboard is hosted by the cbdhsvc_* user service, which runs under each user's session. To check its state:

1. Open Task Manager → Services tab.
2. Search for cbdhsvc_* (the suffix is a per-user GUID).
3. Confirm the status is Running.

If it is stopped, restarting Explorer usually restarts the service. If not, see how to restart the clipboard user service and Explorer.exe restart to unstick copy-paste.

Test 6: confirm Win+V is enabled

A separate question from "is the clipboard service healthy" is "is clipboard history turned on." Win+V history is off by default. Check at Settings → System → Clipboard → Clipboard history. If it is off, no amount of testing will reveal history cards because there are none. The 25-item cap, the 4 MB per-item limit, and the text/HTML/bitmap formats only apply once history is enabled.

For the full settings walkthrough, see Windows clipboard settings, line by line.

Reading the results

The table below maps test results to the likely failing layer:

Most "clipboard is broken" reports land in the first row. The OS clipboard is fine; the failure is in a specific app, in a third-party manager, or in the Win+V shortcut chain.

What to do if the OS clipboard is genuinely broken

If Tests 1, 2, and 4 all fail, the OS clipboard service is the problem. The recovery sequence, in order:

1. Restart Explorer from Task Manager.
2. Restart the clipboard user service (see the linked guide).
3. Run sfc /scannow from an elevated command prompt to repair system files.
4. Run DISM /Online /Cleanup-Image /RestoreHealth to repair the component store.
5. Boot into Safe Mode and re-run Tests 1, 2, and 4. If they pass in Safe Mode, a third-party driver or service is the cause.
6. Do a clean boot to bisect the offending service.

For steps 5 and 6, see safe mode and a clean boot for clipboard bugs. Only after the clean boot fails to identify a culprit should a Windows reset be considered — and even then, almost never for clipboard issues alone. See when to reset Windows because paste is haunted.

App-level false alarms to rule out first

Before pronouncing the OS clipboard broken, rule out the common app-level causes that mimic a clipboard failure:

• Paste is greyed out in a password field. This is by design. See why paste fails in password fields.
• Paste works in Notepad but not Word. Often the Office clipboard intercepting. See paste works in Notepad but not in Word.
• Paste works in Word but not in a browser. Browser paste policies, not the OS. See paste works in Word but not in a browser.
• Cannot paste into an admin window. UAC blocking cross-integrity paste. See cannot paste into an admin window.
• Right-click paste is missing in a terminal. Windows Terminal's right-click is configurable. See mouse right-click paste missing.

Each of these is an app, session, or integrity-level problem, not an OS clipboard problem. The Notepad round-trip in Test 1 will pass in every one of these cases, which is the point of running it first.

A five-minute clipboard health check

The full check, condensed:

1. Notepad text round-trip (Test 1) — 60 seconds.
2. Snip-and-Paint image round-trip (Test 2) — 90 seconds.
3. PowerShell Set-Clipboard / Get-Clipboard probe (Test 4) — 60 seconds.
4. Check cbdhsvc_* is running (Test 5) — 30 seconds.
5. Check Settings → System → Clipboard → Clipboard history is On (Test 6) — 30 seconds.

If all five pass, the OS clipboard is healthy. The remaining investigation is app-specific, manager-specific, or shortcut-specific — and the rest of the C12 troubleshooting cluster picks up from there.

Related reading

• Safe Mode and a Clean Boot for Clipboard Bugs
• When to Reset Windows Because Paste Is Haunted
• 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 Win+V history toggle
• Microsoft Learn — Get-Clipboard — official PowerShell cmdlet that reads the current clipboard contents, used in Test 4
• Microsoft Learn — Set-Clipboard — official PowerShell cmdlet that writes to the clipboard, used in Test 4
• Microsoft Learn — clip command — official documentation for clip.exe, the command-line tool that pipes stdin to the clipboard
• Microsoft Learn — Clipboard reference — official Win32 clipboard API reference, describing the formats and services that the OS clipboard exposes

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