Windwos 10 - keyboards stopped working over the weekend
I have a laptop (dell XPS 12 convertible) and a desktop (Dell 9020) which are running Windows 10. Both keyboards stopped working over the weekend. The 9020 desktop is the one I am currently using and I was able to get the keyboard working again after several reboots, a hardware diagnostic, an attempted boot to USB Ubuntu distro (which for some reason never came up). I am not sure what happened. The laptop and desktop on screen keyboard seems to work fine even when the USB keyboard is not working.
On the Desktop, I tried to determine when it stops working. The keyboard works fine until after I put the password into the login screen and then after a few seconds the caps lock/num lock keys stop working. I tried toggling caps lock on and off until it got stuck on and would respond. I did the same with the Num Lock key. The mouse still works and the keyboard and mouse still receive power from the computer.
I tried moving the keyboard USB connection to the computer to a different USB port and it still did not work. I left it in that port for a couple of reboots. The keyboard eventually came back, although I am not sure why. Does anybody have any insight into this?
On the Desktop, I tried to determine when it stops working. The keyboard works fine until after I put the password into the login screen and then after a few seconds the caps lock/num lock keys stop working. I tried toggling caps lock on and off until it got stuck on and would respond. I did the same with the Num Lock key. The mouse still works and the keyboard and mouse still receive power from the computer.
I tried moving the keyboard USB connection to the computer to a different USB port and it still did not work. I left it in that port for a couple of reboots. The keyboard eventually came back, although I am not sure why. Does anybody have any insight into this?
Geez... you might want to try making a voodoo doll for each keyboard and poke them with needles.
A couple of questions:
1. When was the last time Windows 10 updated?
2. Have you checked the System log for errors?
3. Has there been a BSOD?
4. What anti-virus are you using and when was the last time it updated and ran?
A couple of questions:
1. When was the last time Windows 10 updated?
2. Have you checked the System log for errors?
3. Has there been a BSOD?
4. What anti-virus are you using and when was the last time it updated and ran?
I haven't installed any new software. I wasn't even at work over the weekend. I do have Panda USB vaccine installed on the Desktop, but that has been active for at least 1/2 a year if not more (and it is not installed on the laptop). I will look into the system/event logs.
If you don't see anything funky in the event logs, get rid of the Panda and any other AV that isn't active.
Go download the free version of Malware Bytes:
https://www.malwarebytes.org/dl-confirm/
Do a full scan and see what it comes up with.
Go download the free version of Malware Bytes:
https://www.malwarebytes.org/dl-confirm/
Do a full scan and see what it comes up with.
I am checking the logs. Any suggestion as to what to look for? I see errors trying to connect to another computer, Mbamchameleon information alerts (failed to obtain file name information). I get an error around login time that says: WUDFPf (part of UMDF) did not load yet. After it does, Windows will start the device again.
And then I get another error: The driver \Driver\WUDFRd failed to load for the device ROOT\PARAGONBLOCKDEVICE\00
And I'm not sure what this is: The server {7006698D-2974-4091-A424-8
And this one is just plain troubling and I'm not sure I like it: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-1
and APPID
{316CDED5-E4AE-4B15-9113-7
to the user CA\zucker SID (S-1-5-21-902742264-372434
(numbers have been changed a little).
And then I get another error: The driver \Driver\WUDFRd failed to load for the device ROOT\PARAGONBLOCKDEVICE\00
And I'm not sure what this is: The server {7006698D-2974-4091-A424-8
And this one is just plain troubling and I'm not sure I like it: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID
{C2F03A33-21F5-47FA-B4BB-1
and APPID
{316CDED5-E4AE-4B15-9113-7
to the user CA\zucker SID (S-1-5-21-902742264-372434
(numbers have been changed a little).
I'm not sure DCOM would be an issue since we're not talking about any kind of distributed app, but you can use DCOMCNFG.EXE to troubleshoot for DCOM errors.
The Paragon error - are you using Parition Manager?
That last error is a little worrisome.
Did you run an AV scan?
The Paragon error - are you using Parition Manager?
That last error is a little worrisome.
Did you run an AV scan?
Look for all events at the exact time the keyboard gives up in the system log and in application and services Logs - Microsoft-Windows-Kernel-P
What you quoted so far will not be the problem.
What you quoted so far will not be the problem.
I found one interesting entry. It seems to say I have a cordless desktop keyboard, when I have a cordless mouse and a wired keyboard. It is a HitmanPro.Alert event from over a month ago:
Platform 10.0.10586/x64 06_3c
Keyboard name 2.4GHz Cordless Desktop
Hardware ID HID\VID_046D&PID_C52A&REV_
It also says it is trying to obtain a DHCP address, while we use static addresses and no DHCP server is defined.
Platform 10.0.10586/x64 06_3c
Keyboard name 2.4GHz Cordless Desktop
Hardware ID HID\VID_046D&PID_C52A&REV_
It also says it is trying to obtain a DHCP address, while we use static addresses and no DHCP server is defined.
I have Paragon Hard Disk Manager 14. I still have Paragon Partition Manager, but have not used it in several years.
I ran a scan and nothing showed up. Did this right after I regained use of the keyboard.
I should mention that, and this may explain some problems, we are in transition from static IP addressing to DHCP. Although it has not happened yet, our computers are about to be migrated to our new parent company's domain with managed SEP and restrictive GPOs. So far I have not been able to wrest any assurances of some control over my own OU. We have HIPAA compliance to worry about on top of everything else.
I ran a scan and nothing showed up. Did this right after I regained use of the keyboard.
I should mention that, and this may explain some problems, we are in transition from static IP addressing to DHCP. Although it has not happened yet, our computers are about to be migrated to our new parent company's domain with managed SEP and restrictive GPOs. So far I have not been able to wrest any assurances of some control over my own OU. We have HIPAA compliance to worry about on top of everything else.
I currently use the Paid version of MBAM Pro and BD Antiransomware.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Filter keys don't turn off the keyboard, please explain what settings you used, your screenshot doesn't explain that.
If you have hitmanpro.alert installed this is the keyboard issue. They released a patch or update and it has disabled the keyboard after a reboot. You will have to login to safe mode or connect to the computer remotely to uninstall- wait for a stable release.
But if HitmanPro.alert is the problem, how come my keyboard is now working? Also my laptop doesn't have HitmanPro.Alert. the only things that they have in common are that they run Windows10, Malwarebytes Pro, Office 2010 Adobe acrobat Pro, some remote software, and cryptoprevent.
Auto-updating of hitman pro solved it?
Might not be related to your issue with the laptops-we just became aware of our issue yesterday, and it has multiplied through my users that have HitmanPro. alert. I personally installed the latest version download(31?) which upgraded my current version which was 2.4-rebooted and my KB was locked. We did find that if you uninstall old version and re-install new it did work for 1 user. We are waiting for a stable build, un-installing all versions
Another interesting tidbit about HitmanPro.Alert, surfright was acquired over a year ago by Sophos. They are putting out a new product called Crytoguard, based on HitmanPro.Alert. It is being introduced next week, but just got off a webinar where they had some info.
Although all the input was appreciated, it turned out to be an easy solution I should have figured out earlier, but just didn't apply the filter keys off setting when I first tried it, but closed the dialog instead.
Look into the event logs for clues. For example in the system log, but also in Microsoft-Windows-Kernel-P