I'm having this frustrating issue on my Lenovo LOQ 15 laptop that's running the latest version of Windows 11. Whenever I try to interact with the lockscreen, whether by clicking the mouse or pressing a key, the screen flashes and then reloads back to the lockscreen. It's really annoying! The keyboard and mouse are functional in the BIOS, the Novo Menu, and even in Windows recovery, but as soon as the lockscreen shows up, any kind of input just causes this weird flashing cycle.
I did mess around with the WudfRd registry key before this started happening, but I didn't install any new software or updates right before the lockscreen issue began.
Here's what I've tried so far: I booted from a Windows 11 USB and accessed the Command Prompt in recovery mode. I ran the sfc /scannow command, which did find and repair some corrupted files, and then I tried the offline SFC as well, which found no integrity violations. I also attempted Startup Repair, but that didn't fix anything. I haven't gotten any specific error codes, just the annoying flashing on the lockscreen when I attempt to use the keyboard or mouse. I've shared a video of the issue for clarity.
I'm looking for guidance on how to fix this lockscreen issue without losing my personal files. Are there any registry or driver fixes that I can apply from recovery?
2 Answers
Before anything else, make sure you have backups of your important data in case things go pear-shaped. Since you've already done some troubleshooting, consider resetting the registry settings back to default as a next step. If that doesn't help, you could also try reinstalling the graphics drivers, but ensure you have the correct versions based on your setup.
You might want to check if your laptop has two GPUs. Windows 11 has been known to have issues with dual graphics setups, often requiring older drivers or some tweaks for power management to work properly. It could be that the changes you made with the WudfRd key messed up the graphics settings.
I do have an integrated GPU and a dedicated 4060 mobile. This issue only started happening after I fiddled with the WudfRd settings this morning.