Windows Lock Screen disables keyboard | Razer Insider
Skip to main content
Question

Windows Lock Screen disables keyboard

  • August 1, 2025
  • 3 replies
  • 116 views

bestAeroBlueplace071

If I lock my screen with WINKY+L my BlackWidow V4 keyboard is disabled and cannot log back in. I can sometimes type just one letter of password and then keyboard is totally unresponsive. I can use the On Screen keyboard, or plug in another keyboard in to complete password in order to log back in. Also while in the lock screen the RBG color changes (I use a static color) which  seems to indicate a software issue with Synapse. Also noteworthy just upgraded to Windows 11 Pro from Windows 10.

 

3 Replies

  • Insider Mini
  • September 8, 2025

Hi, I’m having the exact same problem on mine as well. Previously I experienced a similar issue with my Cynosa and now with my Blackwidow V4. I suspect it is due to Synapse too. My problem started a few weeks ago. It had been fine before that. Any updates? Does your problem persist?


FiszPL
Vanguard
Forum|alt.badge.img+1
  • VANGUARD
  • September 8, 2025

Synapse version?

Note that Chroma settings are not stored on the keyboard internal memory, so every time when you lock the screen it’ll go with default chroma setting. But on the other side it’s somewhat stupid, because Synapse services are still running in background - and should take care of the RGB.


  • Insider Mini
  • September 8, 2025

Synapse version?

Version 4.0.86.2508271151

The issue probably started a few patches ago for me, not sure (assuming it’s been a few weeks).

It has definitely something to do with the lock-screen disabling Synapse. Somehow basic keyboard functions are blocked alongside RGB and that might be causing the issue. A few months back, I had an issue where lights were completely disabled/stuck after unlocking the screen, now this. For a couple of years I had a problem where RGB got stuck as faint light and keys became sticky (with a different Razer keyboard as well). These previous two seem to have been solved but the issue persists as this new one. The culprits are the same though: lock-screen and Synapse. Oddly enough, it never ever happened to my Basilisk v2 and v3 mice.