← Back to Blog

Troubleshooting | Jun 30, 2026 | 9 min read

Win+V Says 'Nothing Here'? How to Fix It

By Mohit Sehrawat

Troubleshooting cover for Win+V Says 'Nothing Here'? How to Fix It
Troubleshooting illustration — Win+V Says 'Nothing Here'? How to Fix It

Win+V opens, but new copies never appear in the history. The history shows the items that were there yesterday, but the URL you just copied is missing. This is a different problem from "Win+V does not open" — the underlying service is running, but new copies are not being recorded. This guide walks through the diagnostic tree for "history works but is not saving new items," covering the 4 MB cap, app exclusions, sync conflicts, and the history database.

For related troubleshooting entries, see Win+V not working on Windows 11: 9 fixes, copy and paste completely dead on Windows 11, and pinned clipboard items disappeared.

Step 1: Confirm the basic mechanism

Before diagnosing, confirm that the basic copy-and-record mechanism is broken. Copy a short text string — "test 1" — from Notepad. Open Win+V. If "test 1" appears, the mechanism works, and the issue is specific to whatever you were copying when you noticed the problem. If "test 1" does not appear, the mechanism is broken and you should proceed to Step 2.

This step isolates "the history is not saving anything" from "the history is not saving this particular item." The two have different causes.

Step 2: Check the 4 MB cap

Windows clipboard history caps each item at 4 MB. Items above the cap are silently dropped — they are not recorded, and no error is shown. The cap applies to the item's serialized size, which for text is the byte count, and for images is the bitmap size.

If the item you were trying to copy was a large screenshot or a long log, the cap is likely the cause. The official Microsoft documentation confirms the 4 MB limit; see Windows clipboard 4 MB cap: what gets dropped for the full discussion.

To verify, copy a small text string ("test 2"). If "test 2" appears in history but the large item does not, the cap is confirmed.

Step 3: Check app exclusions

Windows allows the user to exclude specific apps from clipboard history. Copies from excluded apps are not recorded, even if the app is otherwise functional. The exclusion list is in Settings → System → Clipboard → Exclude apps.

Common excluded apps:

  • Password managers (1Password, Bitwarden, KeePass) — these exclude themselves by default for security.
  • Banking and financial apps.
  • Some enterprise apps configured by IT.

If the app you were copying from is on the exclusion list, that is the cause. Remove it from the list to allow its copies to be recorded.

For the related discussion of what counts as a sensitive format, see what sensitive formats should monitors ignore and password managers and clipboard monitors: who should win.

Step 4: Check cloud sync conflict

If clipboard sync across devices is enabled, the local history can be overwritten by a sync from another device. The symptom is that new local copies appear briefly and then disappear, replaced by items synced from another device on the same Microsoft account.

Steps:

  1. Settings → System → Clipboard → "Sync across your devices."
  2. If sync is on, turn it off temporarily.
  3. Copy "test 3."
  4. Open Win+V. If "test 3" persists with sync off, sync was the cause.

The fix depends on the workflow. For a single-user, single-machine setup, sync should be off; the 25-item local history is sufficient. For a multi-device workflow where the user wants to copy on one machine and paste on another, sync is necessary, but the conflict between local and remote items is a real limitation. For the full discussion, see clipboard history across devices: what Microsoft syncs and automatically sync text I copy: should you turn it on.

Step 5: Restart the Clipboard User Service

The Clipboard User Service (cbdhsvc_*) is the Windows service that records clipboard history. If the service is running but stuck, new copies are not recorded even though the existing history is still visible.

Steps:

  1. Open Task Manager → Services tab.
  2. Find cbdhsvc_*.
  3. Right-click → Restart.
  4. Copy "test 4."
  5. Open Win+V. If "test 4" appears, the service was stuck.

For the command-line equivalent and more detail, see Win+V not working on Windows 11: 9 fixes.

Step 6: Check for two clipboard managers

Two clipboard managers running simultaneously can interfere with each other's recording. The third-party manager may be "consuming" the clipboard event before the Windows history listener sees it, or the two may be fighting over the clipboard sequence number.

Steps:

  1. Quit any third-party clipboard manager (Ditto, CopyQ, ArsClip, etc.) — right-click the tray icon → Exit.
  2. Open Task Manager → Details tab. Confirm no ditto.exe, copyq.exe, etc. are running.
  3. Copy "test 5."
  4. Open Win+V. If "test 5" appears, the third-party manager was interfering.

The fix is to either stop using the third-party manager or to configure it to not interfere with Win+V. Most modern managers have a "coexist with Win+V" option; enable it.

Step 7: Check the history count

Windows clipboard history holds 25 items. If the history is full, new copies push old items out — but the new items should still appear. If the history is at 25 and new items are not appearing, the count is not the cause; proceed to Step 8.

You can check the count by opening Win+V and counting the items. If the count is below 25, this is not the cause.

For the full discussion of the 25-item limit, see Windows clipboard history limit: why only 25 items and can you increase Windows clipboard history past 25.

Step 8: Reset the history database

The clipboard history is stored in a per-user database that can become corrupt. Resetting the database clears all unpinned items and forces the service to rebuild the database from scratch. Pinned items may be preserved or may be lost; back up any pinned items you cannot afford to lose before resetting.

Steps:

  1. Open Settings → System → Clipboard → "Clear clipboard data" → Clear all. This clears the in-memory history.
  2. Open Win+V and confirm it is empty.
  3. Sign out and sign back in.
  4. Copy "test 6."
  5. Open Win+V. If "test 6" appears, the database was corrupt and has been rebuilt.

If the database reset does not help, the issue is at a deeper level — the service is running, the database is fresh, and copies are still not recorded. Continue to Step 9.

Step 9: Test in a clean user profile

If none of the above steps work, the user profile may be corrupt. Create a new local user, sign in, enable clipboard history, and copy "test 7." If "test 7" appears in the new profile's Win+V, the original profile is the problem.

The fix for a corrupt profile is to migrate to a new profile, which is a significant project. For corporate machines, contact IT; they may have a profile-migration tool.

For the full steps, see the equivalent discussion in Win+V not working on Windows 11: 9 fixes.

What actually fixed "Nothing here" for real users

The steps above are the systematic tree. Below are the specific fixes real users reported as working on Microsoft Q&A and support forums in 2024–2026, with the evidence for each. Try them in this order when the generic tree stalls.

Fix A: Suggested Actions off, history off and on again

The single most-endorsed community fix: open Settings → System → Clipboard, turn Suggested actions off, then toggle Clipboard history off and back on. On the main Microsoft Q&A thread for "Win+V not displaying copied text," this answer collected over 180 "helpful" votes across 2024–2025, with multiple "driving me nuts, thank you" confirmations.

Caveat found by users: Suggested actions is not shown in all regions (confirmed missing for UK users, among others). One user forced it to appear by temporarily switching region and language to US. If the toggle is absent on your machine, skip to Fix B — its absence is a regional SKU difference, not a deeper breakage.

Fix B: Delete the Clipboard store folders

Close history, show hidden files, and delete the contents of C:\Users\<you>\AppData\Local\Microsoft\Windows\Clipboard (two folders inside), then reopen with Win+V. Multiple users report history resuming immediately after the folders rebuild. This is the manual version of the Step 8 database reset for cases where Settings → Clear does not reach the corrupt store.

Fix C: Check the Clipboard User Service in services.msc

Open services.msc and confirm Clipboard User Service_<suffix> exists and is running. If the service entry itself is missing from the list, that matches the "after a Windows update" breakage pattern users reported following cumulative updates (including the September 2024 24H2 preview KB5043178 wave, where Snipping Tool images also stopped landing in history). A missing service is an OS-level fault: run sfc /scannow, then install the latest cumulative update — several users report history returning on its own after the next patch (e.g., December 2024 reports of spontaneous recovery).

Fix D: Remove a stale clipboard policy (registry)

If history also shows as grayed out or managed, an old policy may be forcing it off. From an elevated Command Prompt, reg delete HKLM\SOFTWARE\Policies\Microsoft\Windows\System /v AllowClipboardHistory /f (and the corresponding AllowCrossDeviceClipboardHistory value for sync), then restart. This matches the Winhelponline August 2026 repair sequence for empty-history cases.

App-specific issues

Some apps do not place content on the clipboard in the formats that Windows history records. Windows history records text, HTML, and bitmap; apps that place only private formats (some legacy apps, some games) will not appear in history even though the copy worked.

Common apps with this behaviour:

  • Some terminal emulators that place only CF_TEXT in a private format.
  • Some games that place screenshots in a private format.
  • Some remote-desktop clients that place only remote-private formats.

The fix is to copy via a different path — for example, paste the item into Notepad first, then copy from Notepad, which places the content in a format Windows history records.

Honest positioning

Edge-Drop, the Windows hover-activated clipboard shelf, is a separate tool from Windows clipboard history and does not interfere with it. The shelf uses its own clipboard poll and its own storage; if Windows history is not saving new items, the shelf's history may still be saving them (and vice versa). The shelf is not a replacement for Windows history — it is a complementary tool. The right fix for broken Windows history is to fix Windows, not to switch to a third-party manager. For the honest comparison, see edge-drop vs Windows clipboard history (Win+V).

A short summary

StepCauseTime
1Confirm mechanism with a small text copy30 seconds
24 MB cap on large items1 minute
3App exclusion list1 minute
4Cloud sync conflict2 minutes
5Clipboard User Service stuck1 minute
6Third-party manager conflict1 minute
7History count (rarely the cause)30 seconds
8Reset history database5 minutes
9Clean user profile test10 minutes

Work through in order. Stop at the first step that resolves the issue.

Related reading

Sources

Mohit Sehrawat
Written by Mohit Sehrawat · Author & Software Tester

Mohit Sehrawat is a B.Tech Computer Science Engineering student with a focus on software testing, bug detection, and product quality. He is interested in exploring applications, identifying issues, and improving the overall user experience through thorough testing.

GitHub · LinkedIn

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

Free · Lightweight · Privacy First
Find us on CodeHype