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

Default quake terminal keybinding is no longer working. #17197

New Issue
Closed
opened 2026-01-31 05:35:05 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 05:35:05 +00:00
Owner
Copy Link

Originally created by @H4M5TER on GitHub (Apr 8, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19044.1620

Other Software

No response

Steps to reproduce

I was using the default keybinding [win+`] for quake terminal and felt good with it.
But it's no longer working.
Current shortcut became win+sc(41) and can't be change to other keys including win.
So this might be a problem with the way windows treat its reserved win keybindings.

Recent windows update log:

0407: KB5011543 （03 cumulative）
0405: KB4023057 （04）
0318: KB5011487 （03 cumulative）
0310: KB4023057 （03）
0310: KB5012418 （.net core）
0310: KB5012416 （.net）
0310: KB890830  （msrt）

The problem happened not earlier than March.

Expected Behavior

No response

Actual Behavior

As above.
Maybe use another default keybinding for quake terminal.
But I'd like the [win+`] one, any idea?

Originally created by @H4M5TER on GitHub (Apr 8, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19044.1620 ### Other Software _No response_ ### Steps to reproduce I was using the default keybinding [win+\`] for quake terminal and felt good with it. But it's no longer working. Current shortcut became `win+sc(41)` and can't be change to other keys including `win`. So this might be a problem with the way windows treat its reserved win keybindings. Recent windows update log: ``` 0407: KB5011543 （03 cumulative） 0405: KB4023057 （04） 0318: KB5011487 （03 cumulative） 0310: KB4023057 （03） 0310: KB5012418 （.net core） 0310: KB5012416 （.net） 0310: KB890830 （msrt） ``` The problem happened not earlier than March. ### Expected Behavior _No response_ ### Actual Behavior As above. Maybe use another default keybinding for quake terminal. But I'd like the [win+`] one, any idea?
claunia commented 2026-01-31 05:35:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2022):

Hmm. Only reason I can think of that this wouldn't work is if something else stole the hotkey first. My guesses would be that maybe there's a Terminal window running as Admin somewhere? Or I think there was some PowerToy that bound itself to Win+` in the past. Any of those apply here? Unfortunately, there's no way for the Terminal to know who already registered that hotkey.

You may have a good point that Win+key can't be set in the SUI, probably mainly because almost all Win+key shortcuts were already reserved by the OS. You should be able to set it in the settings.json file by hand though.

@zadjii-msft commented on GitHub (Apr 13, 2022): Hmm. Only reason I can think of that this wouldn't work is if something else stole the hotkey first. My guesses would be that maybe there's a Terminal window running as Admin somewhere? Or I think there was some PowerToy that bound itself to <kbd>Win+`</kbd> in the past. Any of those apply here? Unfortunately, there's no way for the Terminal to know _who_ already registered that hotkey. You may have a good point that <kbd>Win+key</kbd> can't be set in the SUI, probably mainly because almost all <kbd>Win+key</kbd> shortcuts were already reserved by the OS. You should be able to set it in the `settings.json` file by hand though.
claunia commented 2026-01-31 05:35:09 +00:00
Author
Owner
Copy Link

@H4M5TER commented on GitHub (Apr 13, 2022):

more information

The shortcut (with Win key) of my Ditto (a clipboard) stoped not working either (it worked now), so I assumed that it's a Win key related problem.
They are both UWP (idk if this correct) from Microsoft Store but I don't have another software support keybinding with Win.
I had tried changing the keybinding in the json file but it not worked.
I looked through the PowerToys settings and found nothing.
BTW if there are any tools to find the registered hotkey?

the problem disappeared

It's weird that the problem disappeared but I didn't change anything.
Maybe I disabled the wt -w _quake startup task? But it worked before and I don't think it would be relate with Ditto.
I had reboot before (with a Windows update) but the problem remained.
It still displayed as win+sc(41) instead of `win+`` and I can change it into others with Win key.
Should I close this now?

@H4M5TER commented on GitHub (Apr 13, 2022): ### more information The shortcut (with Win key) of my Ditto (a clipboard) stoped not working either (it worked now), so I assumed that it's a Win key related problem. They are both UWP (idk if this correct) from Microsoft Store but I don't have another software support keybinding with Win. I had tried changing the keybinding in the json file but it not worked. I looked through the [PowerToys](https://github.com/microsoft/PowerToys) settings and found nothing. BTW if there are any tools to find the registered hotkey? ### the problem disappeared It's weird that the problem disappeared but I didn't change anything. Maybe I disabled the `wt -w _quake` startup task? But it worked before and I don't think it would be relate with Ditto. I had reboot before (with a Windows update) but the problem remained. It still displayed as `win+sc(41)` instead of `win+\`` and I can change it into others with Win key. Should I close this now?
claunia commented 2026-01-31 05:35:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 13, 2022):

Yea, we should probably close it out. These kinds of bugs do often go away with a reboot - not really helpful for us getting to the root cause, but definitely and easy enough workaround.

I'll close this out, thanks for the follow up!

@zadjii-msft commented on GitHub (Apr 13, 2022): Yea, we should probably close it out. These kinds of bugs do often go away with a reboot - not really helpful for us getting to the root cause, but definitely and easy enough workaround. I'll close this out, thanks for the follow up!
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 Issue-Bug Needs-Attention Needs-Tag-Fix Needs-Triage Resolution-No-Repro
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#17197
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?