Fix CLIPBRD_E_CANT_OPEN (0X800401D0) Clipboard Error
The clipboard's stuck—likely a hung process or corrupted data. Quick kill or reboot clears it. Here's the real fix.
Quick Answer for the Impatient
Open Task Manager (Ctrl+Shift+Esc), find rdpclip.exe or clipbrd.exe under Processes, right-click and End Task. If that's missing, kill explorer.exe and restart it (File > Run new task > explorer.exe). That clears the lock 90% of the time.
Why This Happens
I still remember the first time I hit this error—copying a massive Excel table into Outlook, and suddenly nothing worked. The error 0X800401D0 means another process has the clipboard open and didn't let go. Windows only allows one handle to the clipboard at a time. Common culprits:
- Remote Desktop's rdpclip.exe (hang after disconnect)
- A stalled screenshot tool (Snipping Tool, Greenshot, ShareX)
- A buggy script or macro that forgot to call CloseClipboard()
- Corrupted clipboard data (image or text block with weird characters)
This isn't a registry problem or a driver issue—it's a process lock, plain and simple.
Fix 1: Nuke the Locking Process
- Press Ctrl+Shift+Esc to open Task Manager.
- Click More details if you only see a simple list.
- Under the Processes tab, look for:
-rdpclip.exe(if you use Remote Desktop)
-clipbrd.exe(older Windows versions)
- Any screenshot tool or file explorer hang - Right-click it and choose End task.
If you don't see any obvious clipboard processes, kill explorer.exe (that's your desktop and taskbar). Don't panic—it'll restart. After killing it, press Ctrl+Shift+Esc again, click File > Run new task, type explorer.exe, and hit Enter. Your desktop comes back, clipboard lock is gone.
Fix 2: Clear the Clipboard Data Manually
Sometimes the process isn't hung, but the data itself is corrupted. Here's a quick PowerShell one-liner to clear it:
powershell -command "Add-Type -AssemblyName System.Windows.Forms; [System.Windows.Forms.Clipboard]::Clear()"Run that from a command prompt (Win+R, type powershell, paste the command). It forces Windows to flush any bad clipboard content.
If you're on a remote desktop session and this keeps happening, disable clipboard sharing in the RDP client: Show Options > Local Resources > Clipboard (uncheck it). Then reconnect. That stops rdpclip.exe from starting and locking things up.
Alternative: Restart the Clipboard Service (Windows 11 Only)
Windows 11 has a separate clipboard service. If the above doesn't work, try this:
- Press Win+R, type
services.msc, press Enter. - Find Clipboard User Service in the list.
- Right-click it, choose Restart.
This service syncs clipboard across devices if you use clipboard history (Win+V). Stopping it won't break anything—it'll restart automatically.
Prevention Tips
This error is rare once you know the triggers. Here's how to avoid it:
- When using Remote Desktop, always log off properly—don't just close the window. That ensures rdpclip.exe exits cleanly.
- If you use clipboard managers (Ditto, CopyQ, 1Clipboard), update them. Older versions sometimes don't release handles.
- Avoid copying extremely large files or images (over 50 MB) directly to the clipboard. Use file copy instead.
- If you write scripts in AutoIt or AutoHotkey, always pair OpenClipboard() with CloseClipboard(). I've seen scripts hold the clipboard for minutes.
That's it. If none of these work, reboot your machine—it's a nuclear option but kills everything holding the clipboard. The error won't survive a fresh boot.
Was this solution helpful?