Bad Keyboard drivers???

[Athlongamer]

I recently d/led some new drivers for my MX Duo because it was acting extremely weird (keyboard and mouse) I knew it wasn't dead batteries but i changed all of them out anyway.

So i installed the new drivers thinking they would do something but now when i restart my system the login window comes up and i try to type in my password but it won't let you hit any buttons.

It's like its not responding but my wireless reciever is lighting up and everything.

I was just wondering if there is a way to get into windows to change the drivers without hitting a button LOL

OH YEA.......when i do hit any button on my keyborad my mouse stops responding.....so it's impossible to login.

I've also tried switching out keyboards and mice......but it does the exact same thing.

I've tried safe mode and you still have to login...IDK what to do.....i really don't want to have to reboot my computer. I would lose SOOO much stuff.

Can anyone help?

Thanks, Jordan

 

[BadThad]

The problem persists when you plug in a different PS/2 keyboard and a PS/2 mouse? If so, make sure the PS/2 port is working by going into your BIOS when you start the PC.

 

[Athlongamer]

Yeah i can get into bios and everything, it only locks up as soon as i hit a key but only when windows is actually loaded. So in bios everything works fine. The problem persists on all keyboards and mice, i've switched them out like 6 times and it does the same exact thing for them all.........I'm pretty sure it cuz of the drivers, if i could just get away to change the PS2 drivers back to the old ones i think i'll be fine

 

[neit]

If you have set it up for an admin user, try to remotely login to the pc. Perhaps you can get in there and roll back to a previous version.

 

[Smilin]

You've likely introduced a goofy registry setting (i8042prt disabled or somethign), or you've swapped out your keyboard driver (.sys file) with a bad one. With a little troubleshooting you can correct one or both of these problems.

First, try a last known good. Since you've been unable to logon, lastknowngood should still be preserved.

If this doesn't work, boot with your XP CD and go to recovery console.

Try first:
do a listsvc to see what drivers are running.
If you see any drivers related to that duo running, set them to disabled with the "disable" command.
See if i8042prt is set to run, if not turn it on. The start type on it should be "system"

If you don't see anything goofy in the above, do this:
find out what the .sys file is for that keyboard driver. Navigate to windows\system32\drivers and rename the version that's in there to *.backup. Get an older version of the driver and drop the .sys file in it's place and rename it if necessary to the correct name.

If the above doesn't apply (like there is no driver for the keyboard for instance), do this:
In recovery console, navigate to windows\system32\config.
rename software and system to software.bad and system.bad
navigate to:
c:\system volume information\_restore { ugly guid } \ (most recent RP) \ snapshot
copy _REGISTRY_MACHINE_SYSTEM and _REGISTRY_MACHINE_SOFTWARE to your windows\system32\config folder and rename them to system and software respectively.
Reboot.

If all of the above doesn't work, boot to recovery console, use listsvc and disable to kill any 3rd party keyboard drivers you're using, then perform a repair/inplace upgrade with your Windows CD.

a repair is done by booting to CD, hitting enter to setup, then hitting R when it detects your install.

IMPORTANT: The good news is a repair preserves all existing apps and data. The bad news is it will also preserve any goofy 3rd party software used by that keyboard. Killing any 3rd party keyboard drivers from recovery console is important. When you are all done, the normal Microsoft driver, i8042prt.sys should be the one that's left running.


Good Luck, I hope this made sense. (and I hope a last known good is all you need )

 

[Athlongamer]

I'm gunna try the last know good confiuration........lol i'm ashamed to admit that i didn't that would work so i didn't even try......guess it would hurt. Hopefully thats all i need to do, but i have a bad feelling that it won't be. If not then i'll just kill the 3rd party driver and do a repair. Hopefully that will work.

I'll give you guys an update later tonight.

Thanks for the help, Jordan

 

[BadThad]

Originally posted by: Smilin
You've likely introduced a goofy registry setting (i8042prt disabled or somethign), or you've swapped out your keyboard driver (.sys file) with a bad one. With a little troubleshooting you can correct one or both of these problems.

First, try a last known good. Since you've been unable to logon, lastknowngood should still be preserved.

If this doesn't work, boot with your XP CD and go to recovery console.

Try first:
do a listsvc to see what drivers are running.
If you see any drivers related to that duo running, set them to disabled with the "disable" command.
See if i8042prt is set to run, if not turn it on. The start type on it should be "system"

If you don't see anything goofy in the above, do this:
find out what the .sys file is for that keyboard driver. Navigate to windows\system32\drivers and rename the version that's in there to *.backup. Get an older version of the driver and drop the .sys file in it's place and rename it if necessary to the correct name.

If the above doesn't apply (like there is no driver for the keyboard for instance), do this:
In recovery console, navigate to windows\system32\config.
rename software and system to software.bad and system.bad
navigate to:
c:\system volume information\_restore { ugly guid } \ (most recent RP) \ snapshot
copy _REGISTRY_MACHINE_SYSTEM and _REGISTRY_MACHINE_SOFTWARE to your windows\system32\config folder and rename them to system and software respectively.
Reboot.

If all of the above doesn't work, boot to recovery console, use listsvc and disable to kill any 3rd party keyboard drivers you're using, then perform a repair/inplace upgrade with your Windows CD.

a repair is done by booting to CD, hitting enter to setup, then hitting R when it detects your install.

IMPORTANT: The good news is a repair preserves all existing apps and data. The bad news is it will also preserve any goofy 3rd party software used by that keyboard. Killing any 3rd party keyboard drivers from recovery console is important. When you are all done, the normal Microsoft driver, i8042prt.sys should be the one that's left running.


Good Luck, I hope this made sense. (and I hope a last known good is all you need )

Awesome! :thumbsup:

 

[Athlongamer]

Well i fixed it...........it was actually the restart in Last Known Good Configuration that worked.......I feel stupid as mess........but thanks for the help. That was some great advice and thanks for the time to post it

Jordan

 

[Smilin]

Right on! Glad you're working.

Yeah, last known good only covers (most of) HKLM\System so in the whole spectrum of stuff that can go wrong it's rare a lastknowngood will fix anything. Looks like it applied here.

I cannot encourage you enough to always be sure your system restore is turned on. It would have saved the day here too.

 

[BadThad]

Originally posted by: Smilin
Right on! Glad you're working.

Yeah, last known good only covers (most of) HKLM\System so in the whole spectrum of stuff that can go wrong it's rare a lastknowngood will fix anything. Looks like it applied here.

I cannot encourage you enough to always be sure your system restore is turned on. It would have saved the day here too.

Very nice job smilin!

 

[Beanz0r]

I'm glad I found this thread. The exact same situation just happened to me when I (down)upgraded to a Logitech Cordless Desktop MX(3100) I uninstalled the iTouch software that came with my MX Duo, and after it forced me to restart, I lost ALL keyboard and mouse support. The Last Known Good thing worked for me. Thanks.