Keyboard "ghosting" after driver update has disabled my computer.

Hello all, again.

Two day ago I was notified by my computer to update the BIOS and Chipset drivers. I did so and upon restart the numpad "4" is behaving as though it's being continually pushed by an invisible hand. With Num Lock on it types "4" nonstop anywhere typing is allowed. With Num Lock off it acts as the directional button so if I try to type any word the "cursor" keeps jumping back one space at a time so the words become jumbled. This has also affected anything which can be controlled by that button (so, for example, when I go to Device Manager and I see a list of devices I can't expand anything in the tree because it's like I'm pushing the back button non stop.

This is not a physical keyboard problem because it doesn't happen in safe mode. System Restore says it can't restore the computer back to before I installed the drivers. I was able to make it stop once for about 4-5 minutes by disabling the touchpad while a USB mouse is detected. I have no idea what the connection is, but I read somewhere that I should try that. Re-enabling and disabling no longer affects this at all. Also, Bitdefender says my system is clean, but I don't suspect it could be an infection anyway because I haven't downloaded anything or clicked any links or anything around that time. It was working perfectly up to the point my computer restarted with the new drivers.

This "little" problem has surprisingly disabled my computer as there is very little I can do that won't be interfered with by this issue (imagine trying to type while someone is pushing the left arrow key non stop). I'm currently using my daughter's Chromebook to write this.
Help would be greatly appreciated.

Thanks in advance.

well surprisingly you say it doesnt behave the same in safe mode because this sound exactly how keyboards break . so that rolled out we are left to believe this is a software issue , in such case you need to apply monk like patience and uninstall / delete / reinstall all HID , USB devices and ports , if it persists then you are most probably infected by a malicious code that your antivirus isnt aware of where in such case i'd suggest disabling all startup apps and browser plugins and start enabling them one at the time to see which one causes such behavior .
If this all sounds silly then just reset your windows .

It doesn't sound silly, just daunting. Going in to the device manager to uninstall those things would indeed require monk like patience since I'd be fighting the "ghost" every step of the way. OK, so uninstall all HID, USB devices and ports. Do they all reinstall on their own at startup?

Is it not possible to roll back somehow the drivers that I updated?

Another question: is it possible to disable just that key input, or the entire numpad, to make fixing this problem easier? It's very difficult to do anything at all while this is happening, and other trying to diagnose and fix the problem, I also need to have full functionality of my computer back so I can do things like work and pay my bills. If I could just disable that one key, or the entire numpad it would make things so much easier.

I've noticed several people have been posting about similar problems, but there isn't much being offered in help. I've solved my issue and I just wanted to share what and how in case this helps anybody else. I know very little about this stuff so don't bother asking me what the connection might be.

So, in my case it wasn't a keyboard problem at all. For some reason updating the BIOS and Chipset drivers somehow screwed up something called Tobii Eye Tracking (which came preinstalled with my system). I noticed that when Tobii would randomly crash the problem would stop, so tested it and found that indeed closing down or otherwise disabling Tobii would stop this erratic behavior. My best guess is that it was detecting my eye movement (as it is supposed to) and inputting the keyboard command to move left in all text field or other areas. Again, I have no idea how this works or why the driver updates caused this behavior with Tobii (if there even is a connection at all), but this has solved (or at least identified) my problem.