Hello everyone

A few days ago I got my brand new laptop but I quickly got disappointed because of this weird capslock button behavior

Once I press it , it seems that irrelevant actions are getting triggered as seen below

The keyboard becomes non-responding after that or the actions performed on each key press are totally random to me! The only way to regain control is using the on-screen keyboard which reveals the lock status as Caps+Alt+Altgr. From this environment, I can press Caps button once again and the keyboard becomes functional again aka it gets unlocked

Any ideas before sending my laptop the the local service department?

I disabled the toggle buttons, removed and re-isntalled the keyboard drivers, even re-installed Windows 11 Pro but no luck. 

Welcome to Lenovo Community evialxg,

I understand that you are experiencing issues with the Caps Lock key on your ThinkBook 13x ITG laptop. Let's start by running the keyboard troubleshooter. To do this, follow these steps: Go to Settings > System > Troubleshoot > Keyboard and click on the "Run the troubleshooter" button.

Additionally, please check that the Caps Lock key is not set to a toggle function. To do this, navigate to Settings > Ease of Access > Keyboard and ensure that the "Toggle Caps Lock on/off with the Caps Lock key" setting is turned off.

Regards,

Hassen_Lenovo

 No keyboard troubleshooter unfortunately

There is an optional firmware update though. Do you recommend to install? I hesitate to do so, cause the first time I did Windows 11 got corrupted and would not start so I had to reinstall it!! 

Hello evialxg,

Corrupt or outdated keyboard drivers can lead to a multitude of issues with keyboard functionality. One common troubleshooting step to address this problem involves uninstalling the keyboard drivers and allowing Windows to automatically reinstall them after a reboot. This process can effectively resolve the problems associated with the keyboard.

How to uninstall drivers from Device Manager - Windows

Regards,

Hassen_Lenovo

Updating the drivers didn't help

Finally and after many many hours of testing I got the solution by disabling the service below and restarting the laptop

Seems like a nasty bug lives in there- please report ..