Clipboard problems (can not copy/paste) in Windows 11

Anonymous
2023-11-27T07:08:13+00:00

Clipboard stops to working in random time during the working day. Can't copy/paste, clipboard manager is empty. No any special actions done before this: it just stops to work in regular routine. I just have to restart Windows and hope to work for a next few hours.

It's make me crazy to restart my computer few times a day. I have complicated environment with VM's, Docker, IDE, SSH Terminals and should restart it JUST BECAUSE SUDDENLY I HAVE NO CLIPBOARD.

HOW IT'S EVEN POSSIBLE TO BREAK THE CLIPBOARD??? I CAN'T BELIEVE IT'S NOT JOKE

Windows 11 is broken! Please fix it!

I know here a lot of people with same issue. Please comment: let's make this problem visible to MS.

Please no generic advises about restart explorer, dism/sfc, troubleshooting and reinstalling my OS.

All of this was tried many times and doesn't solve this deep Windows bug.

My system information:

Windows 11 22H2 (x64), build 22621.2715, all the updates installed (Nov 2023)

Ryzen 7 5800H, 32 Gb RAM

•

UPDATES:

SOLUTION #1 (JUNE 2024): confirmed and tested

As I noticed before, clipboard issue was always after my computer was left for some time switched on. During this my screensaver was shown and SOME BACKGROUND TASKS performed. This caused the issue 100% of time! I was trying to find and disable background tasks - but it doesn't help.

So, here's my solution: don't let PC to get idle. I've installed Caffeinated utility and keep my PC always awake, even when I'm go out for a few hours or night. AND IT WORKS! For 1 month already no more Clipboard Problem, no any restart! So I recommend to try this method.

SOLUTION #2 (doubtful: works for some)

Discovered by Glen Decker, instructions by Kim-LarryPapp

I hope it can help shine a light. You can follow the steps below. Some things to note, I've placed keystrokes in square brackets to indicate the keyboard touches, and the 'WIN' key refers to the Windows Key on the keyboard. (e.g. [ctrl+alt+del])

  • [Win + R] to open the Run Window
  • [services.msc] => [enter]
  • Click the 'Name' column heading to be sure the items are listed in alphabetical, A to Z.
  • Scroll down to find the item listed 'Connected Devices Platform Service' (Служба платформы подключенных устройств)
  • Double-Click the item to open the properties window.
  • Change the 'Start-up Type' in the drop-down to 'Disabled'. Mine was set to 'Automatic (Delayed)'.
  • Reboot

UPDATE FROM SEPTEMBER 2024:

From the moment I discovered solution #1 I have no issues with clipboard at all - for 3 months in a row!

Just using Caffeinated utility or PowerToys Awake - yes, not fix, but stable workaround. At least I can do my job while Microsoft ignores this issue.

Windows for home | Windows 11 | Performance and system failures

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments

191 answers

Sort by: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2024-08-22T08:23:34+00:00

    unfortunately installing formatting a machine, installing windows 10 then upgrading to 11 is going to be prohibitive for most.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2024-08-22T12:43:36+00:00

    Understood, I was lucky since mine was a new P/C and most of my files were not transferred yet. I passed the info on to the Level 3 team so they had something to work with and recreate in the lab. I also saw a few posts that people using Windows 10 had the same problem with copy and paste. Hopefully the Microsoft team will fixthe problem. My calls have stopped with Level 3 since my problem is fixed and has not returned. Keeping fingers crossed. Thanks Dean for all your valuable input in these post's.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2024-08-22T12:55:34+00:00

    To add, while I agree with Dean in the 'bang your head on desk' nature of re-formatting and starting over, in the end, it was the only thing that fixed it for me.

    I've been following here for a bit, have used some of the info and contributed where I could. Unfortunately, and fortunately at the same time, what solved my problem was the 'System Restore' to it's original setting (Lenovo). I kept my files, but everything else re-installed itself. From that point on, the graphics card and the clipboard issues have been eliminated; I'm working normally.

    Some of the programs were a trick to re-install and get working on Windows 11 (I'm talking to you VB6), but in the end, it was worth it. Mathematically, I was working around the problem for 2 or more hours a day. Compared to the three days of re-installing and setting up, it feels like the juice was worth the squeeze.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2024-08-22T13:10:27+00:00

    To add, while I agree with Dean in the 'bang your head on desk' nature of re-formatting and starting over, in the end, it was the only thing that fixed it for me.

    I've been following here for a bit, have used some of the info and contributed where I could. Unfortunately, and fortunately at the same time, what solved my problem was the 'System Restore' to it's original setting (Lenovo). I kept my files, but everything else re-installed itself. From that point on, the graphics card and the clipboard issues have been eliminated; I'm working normally.

    Some of the programs were a trick to re-install and get working on Windows 11 (I'm talking to you VB6), but in the end, it was worth it. Mathematically, I was working around the problem for 2 or more hours a day. Compared to the three days of re-installing and setting up, it feels like the juice was worth the squeeze.

    Roll the format and reinstall everything across an organisation with a few hundred machines...... :/

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2024-08-22T13:52:33+00:00

    Duly noted fine Sir, duly noted. ;)

    Was this answer helpful?

    0 comments