Windows 10 reached EOS (end of support) on October 14, 2025. For more information, see this article.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Sidebar ChatBot shortcut stopped working after resetting PC

  • 1 reply
  • 0 have this problem
  • Last reply by TyDraniu

more options

I've been extensively relying on the `Ctrl+Alt+X` shortcut to spin up the selected chatbot in the sidebar, but ever since I reset my pc (complete reset, cloud download of windows, clear all apps and files) and re-installed firefox, the keyboard shortcut isn't working for me anymore.

I installed firefox with chocolatey, upon noticing that the shortcut had stopped working, I tried to downgrade to v145, which didn't help either. So an uninstall and re-install later (this time manually downloading the installer exe), `Ctrl+Alt+X` still doesn't work. Although hovering over the chatbot's icon in the sidebar shows the shortcut in the tooltip.

More info: `choco uninstall firefox` created a backup of "Old Firefox Data" or something similar, could that have somehow persisted the malfunction across installs?

Any help would be appreciated! System: Windows 10 Pro Firefox: 146

I've been extensively relying on the `Ctrl+Alt+X` shortcut to spin up the selected chatbot in the sidebar, but ever since I reset my pc (complete reset, cloud download of windows, clear all apps and files) and re-installed firefox, the keyboard shortcut isn't working for me anymore. I installed firefox with chocolatey, upon noticing that the shortcut had stopped working, I tried to downgrade to v145, which didn't help either. So an uninstall and re-install later (this time manually downloading the installer exe), `Ctrl+Alt+X` still doesn't work. Although hovering over the chatbot's icon in the sidebar shows the shortcut in the tooltip. More info: `choco uninstall firefox` created a backup of "Old Firefox Data" or something similar, could that have somehow persisted the malfunction across installs? Any help would be appreciated! '''System''': Windows 10 Pro '''Firefox''': 146

All Replies (1)

more options

This issue may be due to the keyboard layout as described in bug 1953245. Are you able to change the keyboard layout to US as a test?

Ask a question

You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.