Keyboard not recognized

I have upgraded my PC with a fast SSD and installed Windows 10. Since then, when I boot my PC and see the windows account password login page, my keyboard (USB wired) is not active. I have to use the Windows "virtual keyboard" to enter my password. Then, when my desktop shows up, it becomes active. This only happens when I boot my PC from power off. If I restart it, there is no issue.
Jean-Christophe GALLANDKorea R&D DirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Scott CSenior EngineerCommented:
1.  Try a different USB port.  If you have a USB 2.0 port try that one.

2.  Go into the BIOS and see if there is a USB compatibility setting.

3.  Try a different keyboard.  What kind of keyboard are you working with?  Is it  a plain "generic" keyboard or a gaming keyboard?
JohnBusiness Consultant (Owner)Commented:
I would also try a new keyboard as suggested.

Also, since this was an operating system upgrade, run System File Checker. Open cmd.exe with Run as Administrator and run SFC  /SCANNOW twice. Close out, shut down, start up and test.
Gerwin Jansen, EE MVETopic Advisor Commented:
Can you try unplugging and plugging in the keyboard when you have the logon screen?
Is this a fresh Windows 10 install? Did you use the same keyboard during installation?
Do the leds work on the keyboard, providing the keyboard has any?
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Turn off fast startup and retry. See instructions here:
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
Hello all,
Thanks for your contributions.
Here is an update
- changing usb port when PC is shut off does not help
- SFC procedure helped a couple of times but then the isse came again
I will test the other options
- switch usb port at logon page
- turn off fast startup
- test another keyboard
Stay tuned
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
- turn off fast startup : solved the issue but resulted in a lot of Blue Screens Of Death when I booted the PC. Errors were of various kinds (pool caller...). Had to cancel this change to go back to a stable OS
Very weird, should not influence stability. Please check your RAM using memtest, I suspect it's faulty.
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
My RAM is ok
What is very strange is that if I reboot, no problem: the keyboard is recognized. But if I switch on and back off, the keyboard is not detected (until I reach my desktop) and I have to use the virtual keyboard
Ok, we turn off fast startup whenever we deploy software, never bluescreens, on the whole network. That's why I suspect the RAM being faulty. Tests like memtest are not reliable. I use those since 15 years and from time to time they declared faulty ram to be ok. Exchange the RAM just for a test.
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
Just bought them...And not crap (Patriot!)
That's no reason. All brands have errors and out of the box failures.
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
Also if my RAM was faulty, I would detect other symptoms occasionally. But my PC works just fine, except this issue
One module is enough for a test.
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
I tested them...They are just fine...sorry! This may be stupid but I got the issue when I replaced my old HD by a fast SSD (Samsung) and upgraded from W7 to W10. After I installed my SSD, the startup was much ,much, much faster than before. Then I installed W10 and the problem arose. Would this information help? Would there be an issue with the startup beeing too fast and not loading the driver fast enough to to get my keyboard to work? I am not an expert so sorry if this is nonsense...
Do what you like, but if you ask for sound advice, I can only repeat: memory testing is not reliable. That does not mean it has to be the problem, but to rule out memory as the cause for your bluescreens, you HAVE to exchange it. I know, if you don't have a spare RAM module, you will not like this idea, but that's how it is.
The keyboard problem has to do with drivers not working correctly after resuming from kernel hibernation, which is what fast startup puts your machine into (not applicable in general, but seems to apply to your machine and drivers). No fast startup=no kernel hibernation->drivers work as expected because the get loaded freshly.
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
Ok so if you don't trust me please at least understand my constraints. You carry on suggesting I should replace my RAM to do a test. So what should I do? Should I spend another $100 to buy new RAMs? And what if the problem is still there? I have just spent money to buy new Patriot RAM chips, I don't want to spend more. Whereas I trust your expertise please understand my situation. If the only solution is to buy new chips, I will just stick with the virtual keyboard. But if my RAMs are so defective, you still have not answered my question: then why is it that my PC is just perfectly fine once I have my desktyop? do defective RAMs focus on login page only?
I do understand, of course. If you don't happen to have a RAM module lying around, you'll want to go another route, understandably. So let's do this: you should be able to name the bluescreen reasons by starting nirsoft bluescreenview on your system. Take a look at this picture: - the info needed in that case would be "driver irql not less or equal" and the driver file, "tcpip.sys", only that. Provide those for all dumps that bluescreenview finds.
Jean-Christophe GALLANDKorea R&D DirectorAuthor Commented:
Thank you. But you know what, I don't think we need it.... This morning I decided to grab a wipe and clean my keyboard.  I was at the login screen so I thought this would not hurt because this damned keyboard would remain inactive, like always... I wiped over all the buttons in one gesture and ... all the became active. I just happened to push the "num/lock" button which enabled the keypad to work...Crazy...So the problem only relies on the fact that this "num/lock" button is off by default when I switch my pc on. I don't have any LED on my keyboard that could have alerted me. This also explains why I had no issue when I restared my PC: meanwhile I had manually activated the keypad and it stays active on reboot..Oh well... I guess the last thing to do to fix this is to find a way to get the keypad automatically on when the PC boots. I assume there should be a setting in the BIOS screen to do this..
Oh :)
I think this registry key here is responsible (applies to newer OS, too).
The last thing to fix now are your bluescreens which indicate there's something wrong, but if you don't want to, I could understand that, since you can avoid those easily.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 10

From novice to tech pro — start learning today.