Windows 10: My L key doesnt work, yet when I press the fn key it starts spamming L's but holding the fn...

I deep-cleaned my keyboard by taking the keys off and wiping down the inside with a dry qtip. I also hit the keyboard a couple times when I did so. After I finished cleaning it, the l key stopped functioning and instead the fn key began creating l's. Could this be because of the cleaning I did which caused the keyboard to malfunction or could it be a system error? I'm suspecting its because of me smacking it causing it to mess up some part of the keys but I wanna make sure its not something else. I'm using an HK Gaming GK61v2 mechanical keyboard. So far I've tried replugging the keyboard and r

:)

 

FN key always on

If you press “Num Lock" (might also be labeled "Num Lk”) (I’ve also seen it labeled “Pad Lock” for numeric Pad) it turns on the blue keys, and inverts the meaning of the “Fn” key – it’s a way to use that embedded numeric keypad without having to hold down the “Fn” key the entire time. To fix it, just find and press the “Num Lock” or “Pad Lock” key again. (Note, sometimes these keys are themselves “Fn” keys, so you may, or may not, need to also hold down the “Fn” key to get the right function.) Often there is an indicator light associated with the setting.

 

FN key always on

To clarify, I was saying "Accessibility" features maybe be controlled via the BIOS, not the Fn keys. And one of the Accessibility features makes the keys "sticky". This allows folks with some disabilities to press, for example, the Ctrl key, then the Alt key, and then Del in sequence instead of all at once. Same with the Fn key. The sticky feature would let you first press the Fn key, and then the F9 key (for example) and not Fn + F9 at the same time to enable/disable whatever Fn + F9 does with that notebook (it is the touchpad on my Toshiba).

 

New laptop FN keys not working [Solved]

Exactly what I was used to do, pressing the FN key with an F key but that didn't work....
If I press the FN key I get f1 f2 f3 and so on.

It was just the other way around, but I figured it out now.*Smile