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

Windows key doesn't work when assigning key actions #21874

New Issue
Open
opened 2026-01-31 07:57:10 +00:00 by claunia · 5 comments
claunia commented 2026-01-31 07:57:10 +00:00
Owner
Copy Link

Originally created by @matthewclso on GitHub (Jun 17, 2024).

Windows Terminal version

1.20.11381.0

Windows build number

10.0.22621.3737

Other Software

No response

Steps to reproduce

Go to settings --> actions --> any action and try to set the key combination. Any combination that involves the windows key is not recognized. This is new with a recent version of terminal.

Expected Behavior

Windows key should be allowed in actions key combinations.

Actual Behavior

The key command does not change. It only changes if the windows key is not involved in the input.

Originally created by @matthewclso on GitHub (Jun 17, 2024). ### Windows Terminal version 1.20.11381.0 ### Windows build number 10.0.22621.3737 ### Other Software _No response_ ### Steps to reproduce Go to settings --> actions --> any action and try to set the key combination. Any combination that involves the windows key is not recognized. This is new with a recent version of terminal. ### Expected Behavior Windows key should be allowed in actions key combinations. ### Actual Behavior The key command does not change. It only changes if the windows key is not involved in the input.
claunia added the Help WantedIssue-BugNeeds-Tag-FixArea-SettingsUI labels 2026-01-31 07:57:10 +00:00
claunia commented 2026-01-31 07:57:11 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jun 23, 2024):

My understanding was that this was by design, since the Windows key is meant to be reserved for OS usage. See https://github.com/microsoft/terminal/issues/4329#issuecomment-577926439. But perhaps that policy has changed.

@j4james commented on GitHub (Jun 23, 2024): My understanding was that this was by design, since the Windows key is meant to be reserved for OS usage. See https://github.com/microsoft/terminal/issues/4329#issuecomment-577926439. But perhaps that policy has changed.
claunia commented 2026-01-31 07:57:11 +00:00
Author
Owner
Copy Link

@matthewclso commented on GitHub (Jun 23, 2024):

That makes sense, however I don't know why the feature was removed in a recent release. It had been working for quite a long time, so I don't believe it's a technical limitation.

@matthewclso commented on GitHub (Jun 23, 2024): That makes sense, however I don't know why the feature was removed in a recent release. It had been working for quite a long time, so I don't believe it's a technical limitation.
claunia commented 2026-01-31 07:57:11 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jun 23, 2024):

@matthewclso Sorry, I was mistaken. The policy obviously was changed at some point, and support for the Win key was added in PR #9783. I just checked the version I have installed (1.21.1272.0), and it definitely works for me. Is it possible that you're just trying to use a key combination that is already in use by the OS, or some other apps that's hijacking hotkeys? For example, try an obscure combination like Win+Ctrl+Shift+X.

@j4james commented on GitHub (Jun 23, 2024): @matthewclso Sorry, I was mistaken. The policy obviously was changed at some point, and support for the <kbd>Win</kbd> key was added in PR #9783. I just checked the version I have installed (1.21.1272.0), and it definitely works for me. Is it possible that you're just trying to use a key combination that is already in use by the OS, or some other apps that's hijacking hotkeys? For example, try an obscure combination like <kbd>Win</kbd>+<kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>X</kbd>.
claunia commented 2026-01-31 07:57:12 +00:00
Author
Owner
Copy Link

@matthewclso commented on GitHub (Jun 23, 2024):

Ah, Win+Ctrl+Shift+x does work! But my old combination Win+Ctrl+t doesn't work. Oddly enough, Win+Ctrl+b does work. A few other combinations involving the windows key, even if not paired to a system command, don't work either - might the restrictions for certain key combinations have changed recently?

@matthewclso commented on GitHub (Jun 23, 2024): Ah, `Win`+`Ctrl`+`Shift`+`x` does work! But my old combination `Win`+`Ctrl`+`t` doesn't work. Oddly enough, `Win`+`Ctrl`+`b` does work. A few other combinations involving the windows key, even if not paired to a system command, don't work either - might the restrictions for certain key combinations have changed recently?
claunia commented 2026-01-31 07:57:12 +00:00
Author
Owner
Copy Link

@j4james commented on GitHub (Jun 23, 2024):

might the restrictions for certain key combinations have changed recently?

Yeah, I was thinking the same thing. Possibly an OS upgrade or another app that you have installed, e.g. Microsoft PowerToys? I've just tried your key combination (Win+Ctrl+t) and it works for me, but I'm on Windows 10. I've also tried installing the same version of Windows Terminal as you (1.20.11381.0) and it works there too, so I don't think it's related to the terminal version.

@j4james commented on GitHub (Jun 23, 2024): > might the restrictions for certain key combinations have changed recently? Yeah, I was thinking the same thing. Possibly an OS upgrade or another app that you have installed, e.g. Microsoft PowerToys? I've just tried your key combination (<kbd>Win</kbd>+<kbd>Ctrl</kbd>+<kbd>t</kbd>) and it works for me, but I'm on Windows 10. I've also tried installing the same version of Windows Terminal as you (1.20.11381.0) and it works there too, so I don't think it's related to the terminal version.
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-SettingsUI Help Wanted Issue-Bug Needs-Tag-Fix
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#21874
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?