Friday, November 7, 2014

windows xp - Keyboard driver corrupted, cannot login. How do I fix without a reinstall?


Okay. So I have Windows XP Professional SP3.


Sometime ago the keyboard randomly stopped working all by itself. The num lock light is switched on at boot up - indicating it works but then it switches off either half way through windows loading or alternatively as soon as I press any button at the login screen.


Googling this indicates I have a corrupted keyboard driver (wooo!)


I have ruled out the following:



  1. The keyboard - it works with various WinPE boot up CDs and with another laptop

  2. The hardware - the USB port the keyboard is plugged into works with the keyboard in a WinPE environment loaded up on the PC, so the problem is not the USB port.


Okay so, is there a way to fix this without reinstalling windows?


NB sadly, the configuration for Remote login is not working - I had as recently as 3 weeks ago attempted to get this working - and I had it accepting a client on another XP netbook that was connecting via an invite token sent by email, but the XP3 pro PC doesn't want to accept connections from Remote Desktop Connection on my Vista laptop (both on same wireless network and connected), my Vista laptop picks up the XP SP3 machine on the network (and can even download shared files over the network) but it doesn't see a remote desktop server it can connect to! Doh.


Any ideas?


PS I obviously have no way to login, the keyboard doesn't function to do it and neither will any other keyboard unless the driver is installed, and to do that I would have to... Login! LOL it doesn't get much worse than this.


Answer



I've fixed my own problem.


I loaded up a WinPE recovery disk that has a GUI interface for moving and copying files, went to C:/System Volume Information


navigated through /_restore{blahblahrandomnumbersguidstuff}/


at which point there were two folders RP1 and RP2, both of them had a _REGISTRY_MACHINE_SYSTEM file and I copied the newest one to c:/windows/system32/config, then renamed the file in there called "system" to "system.oldkeyboardbustedupandstuff" and renamed _REGISTRY_MACHINE_SYSTEM to system. then rebooted. This fixed most of the problems. Although now my DVD drive driver is corrupted. Still, I barely use that and at least I can backup my files now.


No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...