starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-09-25 00:15:10 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Rewrite the copy-to-clipboard functionality to use the Win32 functions #21254

New Issue
Closed
opened 2026-01-31 07:37:50 +00:00 by claunia · 9 comments
claunia commented 2026-01-31 07:37:50 +00:00
Owner
Copy Link

Originally created by @dgloverproofpoint on GitHub (Feb 14, 2024).

Windows Terminal version

1.18.10301.0

Windows build number

10.0.19045.3930

Other Software

No response

Steps to reproduce

  1. Select output
  2. [CTRL + C] or [right click] or [CTRL + Shift + P (command palette -> "Copy Text" option]
  3. Neither [CTRL + V] pastes nor does [Win + V] have the selected and presumably copied text in the clipboard

Expected Behavior

Expecting copy from terminal into Windows Clipboard and paste into other programs to work as normal.

Actual Behavior

No text copied to clipboard. I can, at times, get it to continue functionality if I un-snap the Windows Terminal window from fullscreen view but this is only intermittently successful.

This happens whether my shell is ssh'ed to another machine or running locally.

Other programs continue to copy to clipboard and paste to other programs perfectly fine.

Originally created by @dgloverproofpoint on GitHub (Feb 14, 2024). ### Windows Terminal version 1.18.10301.0 ### Windows build number 10.0.19045.3930 ### Other Software _No response_ ### Steps to reproduce 1) Select output 2) [CTRL + C] or [right click] or [CTRL + Shift + P (command palette -> "Copy Text" option] 3) Neither [CTRL + V] pastes nor does [Win + V] have the selected and presumably copied text in the clipboard ### Expected Behavior Expecting copy from terminal into Windows Clipboard and paste into other programs to work as normal. ### Actual Behavior No text copied to clipboard. I can, at times, get it to continue functionality if I un-snap the Windows Terminal window from fullscreen view but this is only intermittently successful. This happens whether my shell is ssh'ed to another machine or running locally. Other programs continue to copy to clipboard and paste to other programs perfectly fine.
claunia added the Issue-TaskNeeds-Tag-FixArea-InteractionProduct-Terminal labels 2026-01-31 07:37:50 +00:00
claunia commented 2026-01-31 07:37:51 +00:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 14, 2024):

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@github-actions[bot] commented on GitHub (Feb 14, 2024): Hi I'm an AI powered bot that finds similar issues based off the issue title. Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you! ### Closed similar issues: - [Copying text from terminal doesn't seem to work on Windows 11 (#11475)](https://github.com/microsoft/terminal/issues/11475), similarity score: 0.81 - [select + enter does not copy selected text into clipboard just as old Terminal (#3179)](https://github.com/microsoft/terminal/issues/3179), similarity score: 0.79 > Note: You can give me feedback by thumbs upping or thumbs downing this comment.
claunia commented 2026-01-31 07:37:51 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Feb 14, 2024):

Maybe we need to rewrite the copy-to-clipboard functionality to use the Win32 functions as well. But 's fairly likely that your machine is having issues right now, like background applications trying to acquire the clipboard lock all the time, etc. May be worth trying to reboot / exiting all background applications, just in case.

@lhecker commented on GitHub (Feb 14, 2024): Maybe we need to rewrite the copy-to-clipboard functionality to use the Win32 functions as well. But 's fairly likely that your machine is having issues right now, like background applications trying to acquire the clipboard lock all the time, etc. May be worth trying to reboot / exiting all background applications, just in case.
claunia commented 2026-01-31 07:37:51 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Feb 14, 2024):

Thanks for filing. Per Leonard's comment above, we'll repurpose this issue to track rewriting the clipboard code to use Win32 functions.

@carlos-zamora commented on GitHub (Feb 14, 2024): Thanks for filing. Per Leonard's comment above, we'll repurpose this issue to track rewriting the clipboard code to use Win32 functions.
claunia commented 2026-01-31 07:37:52 +00:00
Author
Owner
Copy Link

@akantak commented on GitHub (Mar 27, 2024):

Same here on Terminal Windows Version: 1.19.10573.0 and Windows 11 23H2 OS Build 22631.3296.
The copy mechanism from the terminal randomly stops/starts working. It has been happening for a few weeks now.
I would appreciate any workaround (if any known). For now, it is only waiting until it randomly starts working once again.

@akantak commented on GitHub (Mar 27, 2024): Same here on `Terminal Windows Version: 1.19.10573.0` and `Windows 11 23H2 OS Build 22631.3296`. The copy mechanism from the terminal randomly stops/starts working. It has been happening for a few weeks now. I would appreciate any workaround (if any known). For now, it is only waiting until it randomly starts working once again.
claunia commented 2026-01-31 07:37:52 +00:00
Author
Owner
Copy Link

@zadjii commented on GitHub (Mar 11, 2025):

Did we fix this in #17006?

@zadjii commented on GitHub (Mar 11, 2025): Did we fix this in #17006?
claunia commented 2026-01-31 07:37:52 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 11, 2025):

Yes!

@lhecker commented on GitHub (Mar 11, 2025): Yes!
claunia commented 2026-01-31 07:37:52 +00:00
Author
Owner
Copy Link

@Neme12 commented on GitHub (Mar 14, 2025):

Why isn't the WinRT functionality fixed, instead of reverting to a much older API?

@Neme12 commented on GitHub (Mar 14, 2025): Why isn't the WinRT functionality fixed, instead of reverting to a much older API?
claunia commented 2026-01-31 07:37:53 +00:00
Author
Owner
Copy Link

@lhecker commented on GitHub (Mar 14, 2025):

Internally I let its maintainers know about this a long time ago. We don't do anything about this ourselves, because everyone on this team is already booked out with our own work for months on end.

@lhecker commented on GitHub (Mar 14, 2025): Internally I let its maintainers know about this a long time ago. We don't do anything about this ourselves, because everyone on this team is already booked out with our own work for months on end.
claunia commented 2026-01-31 07:37:53 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Mar 14, 2025):

@neme12 in addition to what @lhecker said above, I'll add that switching to the Win32 API is a great way for us to help customers now, even if they are on Windows 10 (which, if the team rewrites the WinRT API, will almost certainly never get the fix!)

Yes, the platform should be fixed. But doing that isn't our only option. 🙂

@DHowett commented on GitHub (Mar 14, 2025): @neme12 in addition to what @lhecker said above, I'll add that switching to the Win32 API is a great way for us to help customers *now*, even if they are on Windows 10 (which, if the team rewrites the WinRT API, will almost certainly never get the fix!) Yes, the platform should be fixed. But doing that isn't our only option. 🙂
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-Interaction Issue-Task Needs-Tag-Fix Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#21254
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?