CloseClipboard Failed 0X800401D4: Why It Sticks and How to Fix It

The 30-Second Fix: Empty the Clipboard

What's actually happening here is that a process grabbed the clipboard handle and never let go. The simplest way to force it free is to copy something tiny — that requests a new clipboard open/close cycle.

1. Open Notepad.
2. Type a single space.
3. Press Ctrl+A then Ctrl+C to copy it.
4. Close Notepad — don't save.

That's it. In 9 out of 10 cases, this forces Windows to close the old handle and open a fresh one. The error goes away immediately. If it doesn't, move to the next fix.

The 5-Minute Fix: Kill the Hung Process

If the space trick didn't work, something has a real lock on the clipboard. Common culprits: Office apps (especially Outlook or Excel with large copied ranges), virtual machine software (VMware, VirtualBox), or clipboard managers like Ditto or ClipClip.

Step 1: Find what's holding the clipboard

1. Press Ctrl+Shift+Esc to open Task Manager.
2. Look under Processes for any app that's hung or using high CPU:
• explorer.exe — if Explorer itself is stuck, you'll need to restart it (see below).
• outlook.exe, winword.exe, excel.exe — Office apps are notorious for not releasing clipboard handles after a big copy.
• vmware.exe, vboxsvc.exe — VM shared clipboard integration often causes this.
• Any clipboard manager you installed.

Step 2: Kill the offender

Right-click the hung process and select End task. Then run the Notepad space trick again. The error should clear.

Step 3: Restart Explorer (if needed)

If no obvious app is listed, the culprit might be explorer.exe. Don't end it directly — that'll crash your desktop. Instead:

1. In Task Manager, find Windows Explorer under Processes.
2. Right-click it and choose Restart.
3. Your taskbar will disappear for a second, then come back. That's normal.
4. Try the Notepad space trick again.

The 15+ Minute Fix: Reset Clipboard via Command Line

If none of the above worked, the clipboard system service itself might be corrupted or stuck. The reason step 3 works is because we're killing and restarting the underlying RDP clipboard service — yes, it also handles local clipboard operations.

1. Open Command Prompt as Administrator (right-click Start, choose Terminal (Admin)).
2. Run this to stop the clipboard service:

net stop rdpclip

3. If the service was running, it'll stop. If it wasn't, you'll get an error — that's fine, move on.
4. Now restart it:

net start rdpclip

5. Alternatively, you can do both in one go:

net stop rdpclip && net start rdpclip

6. Close the terminal and try copying a space from Notepad again.

This resets the entire clipboard stack. I've seen this fix errors that persisted through reboots. The reason is that rdpclip manages clipboard synchronization — when it glitches, it holds the handle open. Restarting it forces a clean state.

If It Still Fails: Reboot and Disable Clipboard History

Yes, a full reboot always works. But let's also make sure this doesn't come back. Windows 10 and 11 have a built-in clipboard history feature (Win+V). It's a fantastic feature, but it also increases the chance of handle leaks. If you see this error frequently:

1. Open Settings (Win+I).
2. Go to System > Clipboard.
3. Turn off Clipboard history.
4. Also turn off Sync across devices if it's on.

That reduces the load on the clipboard system. I leave history off on my own machines for this reason — the feature is nice but the tradeoff isn't worth it if you're a developer who copies large text blocks all day.

What the Error Code Actually Means

0X800401D4 maps to CLIPBRD_E_CANT_CLOSE. The Windows clipboard API works like this: an app calls OpenClipboard() to get exclusive access, does its work, then calls CloseClipboard() to release it. If the second call fails, it means the handle was already closed or, more commonly, another thread still holds it. The error is almost never a hardware issue — it's always a software lock contention problem.

One real-world scenario: You copy a 50MB Excel range, switch to PowerPoint, paste, and then try to copy something else. The Excel process hasn't released the clipboard yet. Error 0X800401D4 appears. The Notepad space trick works because it forces a new copy operation that triggers a proper close.