[Bug] Set-Clipboard leaves ownerless OLE object, stalling RDP clipboard #101676

Activity

1. pablo-munoz-volue commented on Oct 28, 2026

   

   pablo-munoz-volue

   on Oct 28, 2026

   More actions

   Same bug here from the other direction: Claude Code 2.1.312 runs locally (Windows 11, Windows
   Terminal 1.25), and text copied from it pastes empty inside an mstsc session. I narrowed it down
   with a few scripts in plain Windows Terminal, pasting into Notepad in the RDP session each time:

   Clipboard written by	RDP paste
   Windows PowerShell 5.1 Set-Clipboard alone, including the exact text Claude had copied	ok
   two pwsh 7 Set-Clipboard calls back to back	ok
   OSC 52 alone (Windows Terminal writes the clipboard)	ok
   OSC 52, then Windows PowerShell 5.1 Set-Clipboard straight after	empty

   So the OLE object on its own doesn't break RDP for me; the combination does. Claude's copy leaves
   the same clipboard formats as Windows PowerShell 5.1's Set-Clipboard (DataObject, Ole Private Data, plus text), so it looks like Claude Code sends OSC 52 and also runs powershell.exe Set-Clipboard, and rdpclip loses the second write.

   Repro of the failing case:

   $b64 = [Convert]::ToBase64String([Text.Encoding]::UTF8.GetBytes('osc52-first'))
   Write-Host -NoNewline "`e]52;c;$b64`a"
   powershell.exe -NoProfile -Command "Set-Clipboard -Value 'winps-second'"
   # paste inside the RDP session: empty