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

1. Are you part of a group?  Or is this a personal PC (asked because of the MMC involvement).

I am part of AD, local admin of my machine due to my admin work.

2.Do you have 'special' software running?  Anything you've installed to do stuff for you in the background?  

Define special.......visual studio, custom programming environments, manage engine.

3.The clipboard object being used is trying to SetData, which is different than SetText, it suggests there is a lot more data?, an image?, a something that ISN'T text.  Does anything come to mind?

more than i can count.

4. Before leaving tonight, reboot into safe mode. It would be a good indicator if it's Windows System related or external poking in dependent on whether the clipboard is still an issue the next morning.

That is a nice idea, though if it gives me 24 hours more of working then it may not trigger........i will try it see what the mileage is.

5. Something that had a large effect for me, but I haven't heard you mention, was clipboard history. 

I did this upon hearing someone else had luck with it, no luck for me. i still had the issue.

6. The underlying issue seems touch a lot of places.  Tomorrow morning when you get in, repeat the steps below:

concat

nice idea, i will do that, see what info comes up. i have had the "the clipboard is in use" in excel error a long time before the rest of my machine started having problems with it, usually that was fixed by copying something many times and it started to work.

i will give the excel issue a run through hopefully that will bring something up.

Manage Engine... that's piqued my interest, at least for your case. It strikes me as odd that ManageEngine interacts with the mmc (Windows Microsoft Management Console) and that's the module that's touching the SetDataObject in the Forms namespace when you crash. If you follow it, the MMC is tossing the error via the clip, but it's happening by way of SnapIn; ManangeEngine offers SnapIns as a service to load into the MMC... I think we're on to something.

It makes me feel like the problem is deep in the clipboard, not the item that Kim and I have disabled. If I was forced to guess, I would say that Kim and I are sharing the same solution because we have some similarity in peripherals (bluetooth, etc.); I'd guess the CDP is interacting with the clipboard in a way THE clipboard is not expecting, or isn't protected from, in the same way your MMC is interacting with by instruction of the SnapIn; something in the clipboard is open.

I'd put all the other testing back for a night and only disable ManageEngine. I'd bet there's a Service/Process that's kickin' a thread into gear to load some SnapIn, and that SnapIn triggers MMC, which is using the faulty part of the clipboard, and *POOF* ...

My three-cents...

I cannot confirm if manage engine is using the MMC or was the issue etc,

My only interaction today with the MMC was when viewing the EVENT VIEWER.

I tried to copy the error that happened over night (while my copy and paste was already broken) and the MMC crashed with the error logs that i posted above.

Manage engine itself didn't directly create the crash, my copying the event while copy and paste was broken, created the crash.

If that makes sense.

Okay, you're moving along, I noted a few things while you 'spoke'.

** Note: Items in [square brackets] are keystrokes (e.g. [command], [esc], [ctrl+alt+del]). Items in brackets and surrounded by quotes should be typed as seen.

1. It's good that hibernate and/or sleep are left out of the picture while Microsoft (we) diagnose the problem.
2. Are you part of a group? Or is this a personal PC (asked because of the MMC involvement).
3. Do you have 'special' software running? Anything you've installed to do stuff for you in the background? The clipboard object being used is trying to SetData, which is different than SetText, it suggests there is a lot more data?, an image?, a something that ISN'T text. Does anything come to mind?
4. Before leaving tonight, reboot into safe mode. It would be a good indicator if it's Windows System related or external poking in dependent on whether the clipboard is still an issue the next morning.
5. Something that had a large effect for me, but I haven't heard you mention, was clipboard history. Kim & I have ours off. Can you verify the same? [Win+V]
6. The underlying issue seems touch a lot of places. Tomorrow morning when you get in, repeat the steps below:
   1. Open Excel
      1. Type into at least three cells, going up, and going across (e.g. A1, A2, B1)
   2. Open REGULAR NOTEPAD. It must be the boring version of notepad (due to it's simplicity)
      • Copy the text from Excel into Notepad a ridiculous amount of times. You WANT the error. It has to be 'pickable'.
      • Did you get the 'Can't paste between applications yet'? Once you get it, do it ten more times!
   3. Open the Event Viewer => Applications => Windows Logs => Refresh SORTED BY TIME AND DATE
      1. If you sort by anything else, we'll be tracking stuff all the way back to your last clear.

What do you got?

So did it, came in this morning, cant copy and paste.

loaded excel, tried to copy some text and it popped up....."cannot paste into other apps" BRILLIANT!!! LETS GET TESTING!

there is absolutely NOTHING in the event viewer that is related.

NOTHING.

i have hammered copy and paste umpteen times and nothing.

the event viewer doesn't even know excel exists.

i cleared my logs and tried again....NOTHING. GRRRRR

Interesting. When you say related, what do you mean? Were there errors but seemingly off-base? Or was it clean of errors? I ask only because I wouldn't have guessed that my clipboard function was related to my IoT, but as it turns out... Just a thought.

Maybe, in my case, it was the CDP that wasn't protected well? Maybe the dev team at Microsoft has everything caught and clean... maybe break it?

You said you had VS, make a junk programs with a dumb GUI to copy/paste, just use the same namespace; it's the same object. In this case, you'd not only get the ability to remove error protection, to see what's really happening, but maybe even catch it (try).