CLIPBRD_E_CANT_SET (0x800401D2): Fix Clipboard Fails

1. A Broken Clipboard Viewer Chain (Most Common)

I know this error is infuriating—you're in the middle of something, hit Ctrl+C, and get CLIPBRD_E_CANT_SET (0x800401D2). Nine times out of ten, the culprit is a misbehaving clipboard viewer. Some app—usually a clipboard manager like Ditto, ClipClip, or even an old adobe app—has registered itself in the clipboard viewer chain and then crashed or hung. Windows can't talk to it, so it hands you the error.

The fix is blunt but fast: force-kill the clipboard process and restart it. Here's what to do:

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Look for Clipboard User Service or ClipSvc under the Processes tab.
3. Right-click and choose End Task. If you don't see it, also kill any third-party clipboard tools you recognize (Ditto, Clipdiary, etc.).
4. Press Win+R, type clipbrd (but that's old—actually use clip from cmd) or simply restart your clipboard manager.

The real fix is to restart the clipboard service cleanly. Open Command Prompt as admin and run:

taskkill /f /im clipboardsvc.exe
start clipboardsvc.exe

If that doesn't exist on your system (Windows 10 20H2 and later use a different service), just run:

cmd /c echo off | clip

That clears the clipboard and resets the viewer chain. I've seen this fix the error immediately on everything from Windows 10 22H2 to Windows 11 23H2.

One real-world trigger: I see this constantly when someone uses both Ditto and Microsoft PowerToys with clipboard history enabled. The two managers fight over the chain. If that's you, disable one. Go to Settings > System > Clipboard and turn off Clipboard history if you prefer your third-party tool, or uninstall the third-party toy and keep Windows' built-in one.

2. RDP Clipboard Redirection Collision

Second most common cause: you're connected to a remote machine via Remote Desktop (RDP) and the clipboard redirection gets tangled. This is especially common when you copy large files or rich text between sessions. The RDP clipboard channel gets stuck in a half-open state, and any SetClipboard call returns 0x800401D2.

The fix is to restart the RDP clipboard channel without disconnecting. On the remote machine, open Task Manager, find rdpclip.exe, right-click it, and choose End Task. Then immediately restart it by pressing Win+R, typing rdpclip, and hitting Enter.

This reinitializes the clipboard bridge between local and remote. I've had to do this three or four times in a day when moving large Excel tables across RDP sessions—it's annoying but works every time.

If you see the error repeatedly during RDP sessions, consider limiting clipboard size. Go to the RDP client settings (mstsc.exe), under Local Resources > Clipboard, try disabling clipboard redirection entirely, then re-enabling it after the session starts. That forces a fresh negotiation.

3. Corrupted Clipboard History Files

Less common, but I've seen it on Windows 10 machines that have clipboard history enabled for months without clearing. Windows stores clipboard history in a local database under:

%LocalAppData%\Microsoft\Windows\Clipboard

If that database gets corrupted (power loss, disk errors, bad permission changes), the clipboard service can't write new entries and throws 0x800401D2.

Fix: clear the clipboard history database. Go to Settings > System > Clipboard and turn off Clipboard history. Then delete the entire Clipboard folder in File Explorer (the path above). Restart the clipboard service by running:

net stop clipboardsvc
net start clipboardsvc

(On older builds, use ClipSvc instead of clipboardsvc.)

Then re-enable clipboard history. The database is recreated fresh, and the error usually vanishes. I recommend doing this cleaning every few months if you use clipboard history heavily—saves you from hitting this wall later.

Quick-Reference Summary Table

Try these in order—you'll almost never need to go past step one. If none of these work, check for antivirus software that monitors clipboard access (some aggressive settings in Norton or McAfee can block clipboard writes). Disable clipboard scanning temporarily to test.