CmdPal: if you assign a hotkey to a top-level command, then uninstall that extension, we still eat that hotkey

[rozsazoltan]

Microsoft PowerToys version

0.97.1

Installation method

PowerToys auto-update

Area(s) with issue?

Command Palette

Steps to reproduce

It works fine until I start PowerToys. It also works fine until I enable the Command Palette.

So, as soon as I start PowerToys and turn on the Command Palette, CtrlW immediately stops working properly. If I disable the Command Palette, it immediately starts working again, without needing a restart.

✔️ Expected Behavior

That is curious. Could you create an issue on the repo and upload your logs? We shouldn't be watching any keybind you didn't assign. source

It only reserves the key combinations used in PowerToys when handling keystrokes. I set CtrlSpace for the Command Palette. I didn't assign CtrlW to anything else, but the screenshot below clearly shows that the Command Panel is swallowing the keystroke.

❌ Actual Behavior

I use the CtrlW keybind quite a lot in applications. However, if I enable the Command Palette, then CtrlW becomes invalid globally in every application and they are unable to capture the keystroke. If I disable the Command Palette, it works again.

For the Command Palette, I set the CtrlSpace keybind; I don't see any other keybinds configured for it.

The issue persists even if I disable all extensions in Command Palette.

• https://github.com/ITachiLab/hotkey-detective

c:\Program Files\WindowsApps\Microsoft.CommandPalette_0.8.10263.0_x64__8wekyb3d8bbwe\Microsoft.CmdPal.UI.exe

I've only experienced an issue with the CtrlW keybinding. For example, I often use it in Total Commander to close tabs, and I'm already used to it, so I wouldn't like to change that key combination because of this.

I wrote latest as the version number, but the problem has existed for a long time already, ever since the Command Palette was introduced.

• Shortcut conflicts not found

I thought about uploading some kind of log file as well if necessary, but I’m not really familiar with how and where the Command Palette creates its logs.

Additional Information

Windows 11 Pro

• CtrlW worked with PowerToys for a long time. Unfortunately, I didn't notice the issue immediately. After I adjusted my settings in PowerToys and introduced the Command Palette, I initially thought the problem was related to Windows.

❯ dotnet --list-runtimes
Microsoft.NETCore.App 8.0.23 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 8.0.23 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

System language: HUN / ENG

• At first I thought the issue was related to the language, so I removed HUN and then ENG, but removing either of them did not result in any improvement.
• I always use HUN as the typing language; I'm already used to the keyboard layout. As for the display language, I believe it doesn't affect the program's behavior, does it?

Other Software

Anything that uses CtrlW, for example closing a Notepad tab, a Total Commander panel, a file explorer tab, or a browser tab. This is a pretty global keybind, so I'm reluctant to change it. Opening the panel with CtrlT works perfectly.

[jiripolasek]

Hi,
could you please upload the logs? I would also like to ask for your configuration file:
%localappdata%\Packages\Microsoft.CommandPalette_8wekyb3d8bbwe\LocalState\settings.json

/bugreport

[microsoft-github-policy-service]

Hi there!

We need a bit more information to really debug this issue. Can you add a "Report Bug" zip file here? You right click on our system tray icon and just go to report bug. Then drag the zipfile from your desktop onto the GitHub comment box in this issue. Thanks!

[rozsazoltan]

Bingo.

{
  "CommandHotkeys": [
    {
      "CommandId": "DavideGiacometti.EdgeFavoritesForCmdPal_vmjk9v3vswc4e!App!PG-SP-ID12936294450445468815",
      "Hotkey": {
        "win": false,
        "ctrl": true,
        "alt": false,
        "shift": false,
        "code": 87,
        "key": ""
      }
    },
  ]
}

I couldn't associate the error with anything because, naturally, I didn't expect an error. So I couldn't remember which actions led me to encounter it. I reviewed the requested JSON file before uploading, searching for code 87 (for W). I didn't find this file earlier. A previously installed but later removed Command Palette plugin had assigned a hotkey, which apparently wasn't removed when the plugin was deleted.

Tip

Reminder: if you encounter another hotkey issue, the solution is to open the following file:

%localappdata%\Packages\Microsoft.CommandPalette_8wekyb3d8bbwe\LocalState\settings.json

Then, in the CommandHotkeys array, locate the blocked key and assess whether it should be there. If it's being intercepted without reason, delete it, and the hotkey monitoring will immediately work correctly.

Thanks, @jiripolasek, for the quick response!