Windows 10: Brave Private window shortcut not working

Description of the issue:
Using Brave Browser on Windows 10 Single Language 64-bit.
Unlike the previous updates the current update of the brave browse stripped off the functionality of Shift+Ctrl+N/ Ctrl+Shift+N which earlier resulted in the opening of a private window. when any brave window is open and the shortcut is executed nothing happens. The already open window doesn’t get affected no update in the console logs or anything.
How can this issue be reproduced?

  1. Open Brave browser (any window private/normal new window)
  2. Now press the shortcut for Private window (Shift+Ctrl+N as given in the customize and control brave menu)
  3. You will encounter no changes to the already opened window nor will a Private window launch up the way its meant to launch.

Expected result:
Launching of a NEW Private window

Brave Version:
Brave is up to date
Version 1.73.104 Chromium: 131.0.6778.204 (Official Build) (64-bit)
Additional Information:
I use a private window almost daily and I use brave for around 4 hours a day everyday from what I observed after the addition of Brave’s new Private Window with TOR this issue initiated though other shortcuts like launching up the TOR Private window work only the shortcut to launch a Normal Private window is bugged

Hopefully the concerned authorities look into this matter and immediate resolution is done

Did this and it works just fine. Have you reassigned those commands to your shortcuts in Brave’s settings? Or using any extensions which might interfere?

Hey So basically I had an app that runs in the background and has ctrl shift n assigned to it as a hotkey by default and I used to close it usually but for the past two days it was in my hidden icons and yeah that ended up interfering here.

I only found out after I was reassembling my desktop and I pressed the shortcut again to create a new folder and even though my shift key ctrl key and n key were working the shortcut was not.
(I simply chatgpt’ed what the issue could be and when it suggested checking an app in the background it struck me the app could be the reason)

Anyhow I wrote this whole explanation so that in future if someone stumbles upon similar problem they can check their background apps and resolve it easily

Thank You for replying to the thread though I appreciate your help and sorry for the inconvenience I may have caused you.

1 Like