I, too, am only able to log onto a user account that is not password protected and type using this virtual KB, due to the EXACT thing you have described. I have spent the last 20 hours trying to find some answers, as well as trying to get people to understand that you CAN'T uninstall, install, or do any of the normal troubleshooting steps that requires admin account when you can't log onto an admin account cuz you don't have a keyboard!! I can't find any info on this, so feel free to correct me if need be, but i think we've got a case of the flu, and not a mild one, either. My kb driver in device mgr has sprouted a new driver file, ekomox51.sys. This is NOTa windows, nor a signed driver, and it changed even the display text, as well as the driver info to russian. I am a tech, but i know just enough about code to get me into trouble. I opened the file to view, and the english parts say this: (paraphrased) initialize, blah,blah, IO DELETE DEVICE, I/O CREATE DEVICE, ATTATCH DEVICE, CALL DRIVER, PO START NEXT POWER IRP, WRITE...NTOSKRNL.exe (uh-oh), EX RELEASE FAST MUTEX, ACQUIRE FAST MUTEX HAL.DLL SYS\PBOTKBD.DBG KBD.SYS Go figure; i thought the cold war ended... my virus defs are current, use a firewall, shut down nov 15, started up nov 16 in hacker hell. it won't allow live-update or online v scan. no error msg, just does nothing. i havent been able to find any new alerts; In checking recent norton logs, the 15th of nov, crash day, norton scan deleted two trojans: one named PWSteal.trojan, found in c:\windows\system32\drivers\KBFLTR.SYS. Since it looks like there may be tenacles attached to the ntoskrnl as well as other critical system files, i'll continue to type using my mouse. i'm off to the registry...i can't let this ruskie get the best of me. if anyone has any answers, please reply. if you think i'm chasing non-existant demons, let me know, i might even agree with you. |