Found a solution here
Run the following: cmd /c “echo off | clip”
You can even make it into a desktop shortcut if the problem keeps happening.
For me the problem was happening only when there was a RDP session open to another machine. After closing RDC, clipboard started working again.
If this is over Remote Desktop (RDP) then ensure that rdpclip.exe is running on the remote machine. You can start it using Win+R and then rdpclip
There’s probably an app that’s “locked” the clipboard. Try and work out what app has done that and close it.
In my case it was a hung Greenshot.
None of the above solutions worked for me. This one however did:
(I am pasting the urls from the browser:) )
Generally, this tool locates an app that is holding the clipboard. For me, it was Xserver.
For you, who knows.
Simple fix: Try to restart your PC. Doesn’t get more simple than that.
As for the possible reasons:
- Bug in an application: It acquired the clipboard and never freed it
- Windows ran out of memory a while ago and is now confused. It’ll probably crash soon (blue screen).
Windows Notepad may be unable to handle excessively large content, or content with special characters. Although Notepad will generally strip out unsupported character set encodings or control characters, it is first and foremost a simple text file editor.
In my case, I had pasted a large amount of code from my development environment, which apparently overwhelmed Notepad. Even running the command to manually clear the clipboard failed. [cmd /c “echo off | clip”]
As per Mathew Lock’s suggestion of an Application that had locked the Windows clipboard, I narrowed down the culprit to that of Notepad. Immediately upon terminating my NOTEPAD process, the lock on Windows Clipboard was freed.
Kill “explorer.exe” process, it was the source of my problem, when I killed itm, copy/paste started working again. Note that you apps bar will disapper, and you will need to execute explorer.exe from taskmgr, New task.
Other option is from free Systernals app “process explorer”, selected explorer.exe , then “Properties”, “Threads” tab, select “Ole32.dll” and then click “kill”.
After killing the thread i was not able to reproduce again the mistake.