Fix for "Clipboard Error. We couldn't copy the content of the clipboard"

This fixed my issue. I had already tried the "Application.CutCopyMode = False" after every Paste or after any Cut that wasn't going to be Pasted, but still would get the Clipboard error every so often in a macro that does A LOT of work. Adding the DoEvents fixed it. And I do use Logitech Options, as do others that use my Excel tools.

For those where the DoEvents isn't enough, maybe add a loop and check the CutCopyMode. If it's not False (it can be False, xlCopy, or xlCut), keep doing a DoEvent (though definitely set a Timeout of some type if you do this). If you go that far, a subroutine is really the only option, so here it is:

Public Sub ClearClipboardIssue(Optional dMaxTime As Double = 2)

    Dim dStart As Double, dTimer As Double

    dStart = Timer

    Do

        Application.CutCopyMode = False

        DoEvents

        If Application.CutCopyMode = False Then Exit Do

        dTimer = Timer

        If dTimer < dStart Then dTimer = dTimer + 86400 ' Watch for WRAP at MIDNIGHT!

        If dTimer - dStart >= dMaxTime Then Exit Do ' Give up and accept the warning. It's 
                                                    '  annoying, but doesn't break anything!

    Loop

End Sub

June 2025 and I'm having the copying error. I uninstalled Logi Options+ that was installed a week ago and no more error message. So annoying.

Since this doesn't happen in the 32-bit version it borders on fraud by Microsoft. They take no responsibility for fixing the bugs in their programs. They let us slog it out in forums with halfassed work arounds. This problm is over a year old. Then again, they've had a problem with the Excel screen refusing to update after locking titles for about 15 or 20 years (not a joke).

Speaking of halfassed work-arounds, instead of a DoEvent, I use a simpler soulution: I build in a defined wait. It's a single line and isn't affected by any load on the processor. I you're tryig to run something else at the same time a Do Loop can bog down.

Application.Wait Now + #12:00:03 AM#    'allow screen to catch up 

That's a 3 second pause. Change the last digits to add/subtract seconds. I started using it when VBA would execute commands before data finished loading ito a file. It's not very useful to tell it to perform a sort on data that's not actually loaded yet. I also use it when I want to temporarily display a message to the user about what the macro is going to do next. It's easy to adjust to determine the abslute minimum time needed to keep your macros from crashing in on themselves.

I had the same problem, very annoying.
I noticed on my computer that Logi Options+ also adds the following parts:

• LogiOptionsPlusExcelAddin
• LogiOptionsPlusPowerPointAddin
• LogiOptionsPlusWordAddin

I'm removing them now and will see if it helps.

I agree with your analysis. I no longer have the problem -reinstalled three updates some time ago, removed the Logitech application, and I don't use One Drive. I think the updates were the key issue. Sorry, I don't remember their names, but when they were uninstalled it worked fine. Of course Microsoft immediately reinstalled them. This occurred three times and somehow the problem went away. So, it may have been the software or the update process. The updates may have assumed that some property existed when it did not.