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

Ctrl+Shift+C Not working to copy text #7366

New Issue
Closed
opened 2026-01-31 01:02:04 +00:00 by claunia · 13 comments
claunia commented 2026-01-31 01:02:04 +00:00
Owner
Copy Link

Originally created by @danstur on GitHub (Apr 10, 2020).

For some reason I can't use Ctrl+Shift+C on a new Windows Terminal installation with the default bindings (nothing changed in profiles.json). Ctrl+Insert works fine.

I tried to explicitly add { "command": "copy", "keys": "ctrl+shift+c" } in profiles.json but that didn't help either.

Environment

Windows build number: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0
Windows Terminal version (if applicable): 0.10.781.0

Steps to reproduce

  1. Open Windows Terminal.
  2. Select text and press Ctrl+Shift+C.

Expected behavior

The text is put into the clipboard.

Actual behavior

Nothing happens.

Originally created by @danstur on GitHub (Apr 10, 2020). For some reason I can't use Ctrl+Shift+C on a new Windows Terminal installation with the default bindings (nothing changed in profiles.json). Ctrl+Insert works fine. I tried to explicitly add `{ "command": "copy", "keys": "ctrl+shift+c" }` in profiles.json but that didn't help either. # Environment ```none Windows build number: 10.0.18363.0 Microsoft Windows NT 10.0.18363.0 Windows Terminal version (if applicable): 0.10.781.0 ``` # Steps to reproduce 1. Open Windows Terminal. 2. Select text and press Ctrl+Shift+C. # Expected behavior The text is put into the clipboard. # Actual behavior Nothing happens.
claunia added the Needs-TriageNeeds-Tag-FixNeeds-AttentionProduct-Terminal labels 2026-01-31 01:02:05 +00:00
claunia commented 2026-01-31 01:02:05 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 10, 2020):

What is your keyboard layout?

@DHowett-MSFT commented on GitHub (Apr 10, 2020): What is your keyboard layout?
claunia commented 2026-01-31 01:02:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 10, 2020):

Where are you trying to paste the text?

Does the text appear in the "cloud clipboard" (press Win+v)

Does copying from other applications and pasting into the Terminal work?

Do you have any clipboard manager style applications installed?

@zadjii-msft commented on GitHub (Apr 10, 2020): Where are you trying to paste the text? Does the text appear in the "cloud clipboard" (press <kbd>Win+v</kbd>) Does copying from other applications and pasting _into_ the Terminal work? Do you have any clipboard manager style applications installed?
claunia commented 2026-01-31 01:02:06 +00:00
Author
Owner
Copy Link

@danstur commented on GitHub (Apr 10, 2020):

@DHowett-MSFT English (with Austrian locale settings) with US Qwerty and German QWERTZ keyboard layouts. I tried with both without success.
Edit: I also tried an English (United States locale settings) keyboard option without any changes. Although the locale settings are rather complicated, so I might've missed something. It's definitely not a standard setup so this could definitely be the cause. Any settings in particular I should check, or an option to give you a nice programmatic output?

@zadjii-msft I tried notepad and the terminal itself. I can paste things from the clipboard into the terminal with ctrl+v without problems.
There's nothing in the cloud clipboard.
This is a new windows installation and I haven't installed any clipboard manager style applications - at least intentionally. Apart from the AMD chipset and GPU drivers, the realtek audio drivers and VS2019 I've installed everything I can think of via chocolatey. I added the list from choco list -lo at the end.

What's noticeable if I use ctrl+insert to copy the selection is removed, while using ctrl+shift+c the selection stays as-is. I tried cmd, the old PowerShell 5 and PowerShell Core 7 with the same behavior in all of them, so I think we can exclude PowerShell profiles as well

If I'm using the default PowerShell core shell (i.e. just open pwsh.exe) copying things via Ctrl+C works just fine.

choco list -lo

7zip.install 19.0
chocolatey 0.10.15
chocolatey-core.extension 1.3.5.1
chocolatey-misc-helpers.extension 0.0.3.1
chocolatey-windowsupdate.extension 1.0.4
coretemp 1.15.1.20190411
cpu-z.install 1.91
discord.install 0.0.306
DotNet4.5.2 4.5.2.20140902
dotnetcore-sdk 3.1.201
furmark 1.21.1.0
git.install 2.26.0
goggalaxy 1.2.67.58
gpg4win-vanilla 2.3.4.20191021
gpu-z 2.30.0
hearthstone-deck-tracker 1.1.6
hwinfo 6.20
hwinfo.install 6.24
irfanview 4.54
KB2533623 1.0.4
KB2919355 1.0.20160915
KB2919442 1.0.20160915
KB2999226 1.0.20181019
KB3033929 1.0.5
KB3035131 1.0.3
KB3118401 1.0.4
kdiff3 0.9.98
nodejs.install 13.12.0
notepadplusplus.install 7.8.5
openvpn 2.4.7
powershell-core 7.0.0
prime95 29.4
pwsh 7.0.0
spotify 1.1.29.592
steam 3.0.1.20190215
treesizefree 4.4.1.1
vcredist140 14.24.28127.4
vcredist2015 14.0.24215.20170201
vscode.install 1.43.2
@danstur commented on GitHub (Apr 10, 2020): @DHowett-MSFT English (with Austrian locale settings) with US Qwerty and German QWERTZ keyboard layouts. I tried with both without success. Edit: I also tried an English (United States locale settings) keyboard option without any changes. Although the locale settings are rather complicated, so I might've missed something. It's definitely not a standard setup so this could definitely be the cause. Any settings in particular I should check, or an option to give you a nice programmatic output? @zadjii-msft I tried notepad and the terminal itself. I can paste things from the clipboard into the terminal with ctrl+v without problems. There's nothing in the cloud clipboard. This is a new windows installation and I haven't installed any clipboard manager style applications - at least intentionally. Apart from the AMD chipset and GPU drivers, the realtek audio drivers and VS2019 I've installed everything I can think of via chocolatey. I added the list from choco list -lo at the end. What's noticeable if I use ctrl+insert to copy the selection is removed, while using ctrl+shift+c the selection stays as-is. I tried cmd, the old PowerShell 5 and PowerShell Core 7 with the same behavior in all of them, so I think we can exclude PowerShell profiles as well If I'm using the default PowerShell core shell (i.e. just open pwsh.exe) copying things via Ctrl+C works just fine. `choco list -lo` ``` 7zip.install 19.0 chocolatey 0.10.15 chocolatey-core.extension 1.3.5.1 chocolatey-misc-helpers.extension 0.0.3.1 chocolatey-windowsupdate.extension 1.0.4 coretemp 1.15.1.20190411 cpu-z.install 1.91 discord.install 0.0.306 DotNet4.5.2 4.5.2.20140902 dotnetcore-sdk 3.1.201 furmark 1.21.1.0 git.install 2.26.0 goggalaxy 1.2.67.58 gpg4win-vanilla 2.3.4.20191021 gpu-z 2.30.0 hearthstone-deck-tracker 1.1.6 hwinfo 6.20 hwinfo.install 6.24 irfanview 4.54 KB2533623 1.0.4 KB2919355 1.0.20160915 KB2919442 1.0.20160915 KB2999226 1.0.20181019 KB3033929 1.0.5 KB3035131 1.0.3 KB3118401 1.0.4 kdiff3 0.9.98 nodejs.install 13.12.0 notepadplusplus.install 7.8.5 openvpn 2.4.7 powershell-core 7.0.0 prime95 29.4 pwsh 7.0.0 spotify 1.1.29.592 steam 3.0.1.20190215 treesizefree 4.4.1.1 vcredist140 14.24.28127.4 vcredist2015 14.0.24215.20170201 vscode.install 1.43.2 ```
claunia commented 2026-01-31 01:02:06 +00:00
Author
Owner
Copy Link

@myusrn commented on GitHub (Apr 10, 2020):

why are the defaults copy = ctrl+shift+c and paste = ctrl+shift+v to begin with vs the ctrl+c and ctrl+v standard used everywhere else in windows?

@myusrn commented on GitHub (Apr 10, 2020): why are the defaults copy = ctrl+shift+c and paste = ctrl+shift+v to begin with vs the ctrl+c and ctrl+v standard used everywhere else in windows?
claunia commented 2026-01-31 01:02:06 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Apr 10, 2020):

@myusrn this has been discussed in a bunch of other threads, and is not worth on-topic for @danstur's bug report.

@DHowett-MSFT commented on GitHub (Apr 10, 2020): @myusrn this has been discussed in a bunch of other threads, and is not worth on-topic for @danstur's bug report.
claunia commented 2026-01-31 01:02:06 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 10, 2020):

What's noticeable if I use ctrl+insert to copy the selection is removed, while using ctrl+shift+c the selection stays as-is. I tried cmd, the old PowerShell 5 and PowerShell Core 7 with the same behavior in all of them, so I think we can exclude PowerShell profiles as well

That's certainly peculiar.

Could you share you whole profiles.json file? Maybe there's some peculiar combo of settings that's causing this? Because by all accounts, Ctrl+Shift+C should be working for you 🤔

@zadjii-msft commented on GitHub (Apr 10, 2020): > What's noticeable if I use ctrl+insert to copy the selection is removed, while using ctrl+shift+c the selection stays as-is. I tried cmd, the old PowerShell 5 and PowerShell Core 7 with the same behavior in all of them, so I think we can exclude PowerShell profiles as well That's certainly peculiar. Could you share you whole `profiles.json` file? Maybe there's some peculiar combo of settings that's causing this? Because by all accounts, Ctrl+Shift+C should be working for you 🤔
claunia commented 2026-01-31 01:02:06 +00:00
Author
Owner
Copy Link

@danstur commented on GitHub (Apr 10, 2020):

@zadjii-msft Certainly. The path is C:\Users\<UserName>\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\profiles.json I opened it via the GUI (but just to be save that there's not a problem here somehow). The file is as follows:


// To view the default settings, hold "alt" while clicking on the "Settings" button.
// For documentation on these settings, see: https://aka.ms/terminal-documentation

{
    "$schema": "https://aka.ms/terminal-profiles-schema",

    "defaultProfile": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",

    "profiles":
    {
        "defaults":
        {
            // Put settings here that you want to apply to all profiles
        },
        "list":
        [
            {
                "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}",
                "hidden": false,
                "name": "PowerShell",
                "source": "Windows.Terminal.PowershellCore"            },
            {
                // Make changes here to the powershell.exe profile
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false
            },
            {
                // Make changes here to the cmd.exe profile
                "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}",
                "name": "cmd",
                "commandline": "cmd.exe",
                "hidden": false
            },
            {
                "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}",
                "hidden": false,
                "name": "Azure Cloud Shell",
                "source": "Windows.Terminal.Azure"
            }
        ]
    },

    // Add custom color schemes to this array
    "schemes": [],

    // Add any keybinding overrides to this array.
    // To unbind a default keybinding, set the command to "unbound"
    "keybindings": [
	]
}
@danstur commented on GitHub (Apr 10, 2020): @zadjii-msft Certainly. The path is `C:\Users\<UserName>\AppData\Local\Packages\Microsoft.WindowsTerminal_8wekyb3d8bbwe\LocalState\profiles.json` I opened it via the GUI (but just to be save that there's not a problem here somehow). The file is as follows: ``` // To view the default settings, hold "alt" while clicking on the "Settings" button. // For documentation on these settings, see: https://aka.ms/terminal-documentation { "$schema": "https://aka.ms/terminal-profiles-schema", "defaultProfile": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "profiles": { "defaults": { // Put settings here that you want to apply to all profiles }, "list": [ { "guid": "{574e775e-4f2a-5b96-ac1e-a2962a402336}", "hidden": false, "name": "PowerShell", "source": "Windows.Terminal.PowershellCore" }, { // Make changes here to the powershell.exe profile "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}", "name": "Windows PowerShell", "commandline": "powershell.exe", "hidden": false }, { // Make changes here to the cmd.exe profile "guid": "{0caa0dad-35be-5f56-a8ff-afceeeaa6101}", "name": "cmd", "commandline": "cmd.exe", "hidden": false }, { "guid": "{b453ae62-4e3d-5e58-b989-0a998ec441b8}", "hidden": false, "name": "Azure Cloud Shell", "source": "Windows.Terminal.Azure" } ] }, // Add custom color schemes to this array "schemes": [], // Add any keybinding overrides to this array. // To unbind a default keybinding, set the command to "unbound" "keybindings": [ ] } ```
claunia commented 2026-01-31 01:02:07 +00:00
Author
Owner
Copy Link

@danstur commented on GitHub (Apr 10, 2020):

@zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things.

Sorry to take your time, most certainly a user error.

Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?)

@danstur commented on GitHub (Apr 10, 2020): @zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things. Sorry to take your time, most certainly a user error. Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?)
claunia commented 2026-01-31 01:02:07 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 10, 2020):

Hey no problem at all! I'm glad you were able to figure it out, and I'm especially happy that you decided to post your findings once you figured it out ☺️

@zadjii-msft commented on GitHub (Apr 10, 2020): Hey no problem at all! I'm glad you were able to figure it out, and I'm especially happy that you decided to post your findings once you figured it out ☺️
claunia commented 2026-01-31 01:02:07 +00:00
Author
Owner
Copy Link

@onuryurdupak commented on GitHub (Jun 29, 2020):

@zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things.

Sorry to take your time, most certainly a user error.

Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?)

Bless you. It would have been very hard to pinpoint (the very same issue) if it wasn't for your edit. :)

@onuryurdupak commented on GitHub (Jun 29, 2020): > @zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things. > > Sorry to take your time, most certainly a user error. > > Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?) Bless you. It would have been very hard to pinpoint (the very same issue) if it wasn't for your edit. :)
claunia commented 2026-01-31 01:02:07 +00:00
Author
Owner
Copy Link

@vinayak19th commented on GitHub (Apr 30, 2024):

@zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things.

Sorry to take your time, most certainly a user error.

Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?)

Thanks. This fixed my error too. I use an Nvidia GPU and the iGPU on my CPU installed adrenaline software

@vinayak19th commented on GitHub (Apr 30, 2024): > @zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things. > > Sorry to take your time, most certainly a user error. > > Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?) Thanks. This fixed my error too. I use an Nvidia GPU and the iGPU on my CPU installed adrenaline software
claunia commented 2026-01-31 01:02:07 +00:00
Author
Owner
Copy Link

@giggio commented on GitHub (Apr 30, 2024):

@zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things.

Sorry to take your time, most certainly a user error.

Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?)

Thank you!
Same thing here, it was the "AMD Software: Adrenaline Edition" in my case.
For anyone having the problem: click on the gear icon on the top right for settings, then go to the Hotkeys menu, and disable all hotkeys, or the "Toggle camera" option. I disabled it all.

@giggio commented on GitHub (Apr 30, 2024): > @zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things. > > Sorry to take your time, most certainly a user error. > > Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?) Thank you! Same thing here, it was the "AMD Software: Adrenaline Edition" in my case. For anyone having the problem: click on the gear icon on the top right for settings, then go to the Hotkeys menu, and disable all hotkeys, or the "Toggle camera" option. I disabled it all.
claunia commented 2026-01-31 01:02:07 +00:00
Author
Owner
Copy Link

@Letus252 commented on GitHub (Aug 4, 2024):

@zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things.

Sorry to take your time, most certainly a user error.

Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?)

Same problem for me, thanks for providing fix.

@Letus252 commented on GitHub (Aug 4, 2024): > @zadjii-msft I created a sample WPF app to see if I could reproduce the error and lo-and-behold I have the same problem there. So I guess some helpful program decided to register a global hotkey. I love those things. > > Sorry to take your time, most certainly a user error. > > Edit: For anyone else having the same problem: It was the Radeon GPU driver that decided to helpfully enable a dozen global hotkeys without mentioning that anywhere. (It's always the awful drivers isn't it?) Same problem for me, thanks for providing fix.
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 Needs-Attention Needs-Tag-Fix Needs-Triage 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#7366
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?