Repaired XP using recovery Console -No USB help!?

Calx

Active Member
Reaction score
200
Location
Birmingham, UK
Following yesterday brainfreeze, I have patted myself on the back as I have managed to repair a Dell desktop using recovery Console. with the following error " XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"

Used GeGeeks guide and copied the system, sam, security over.

Can now boot into windows but no keyboard or mouse.
I can boot into safemode but still the same no Keyboard or mouse.
I have gone back into recovery console (keyboard works) and checked that the usb drivers are present in the system32 folder but at a loss of what to try next.

(I know this is probably all simple stuff to you, but I tend to reinstall rather than repair, but the lady wants her data so this is a good learning experience for me).

Any ideas please?
 
Sometimes, dell machines, will only recognise a dell keyboard.
This, plus I have seen Dells with PS/2 ports that are picky about using USB keyboard and mouse. Have you got any PS/2 keyboard to hand? Different brand USB keyboard?

Is the hard drive okay (given the original problem)? Just because files (e.g., USB drivers) are in a file listing, doesn't mean that they are readable/not corrupt.

Edit: sorry, crossed with @Cadishead Computers reply.
 
It must be, if its working with bios.

Is it usb only.. Ie no Ps2 ports?
No ps2 :(

This, plus I have seen Dells with PS/2 ports that are picky about using USB keyboard and mouse. Have you got any PS/2 keyboard to hand? Different brand USB keyboard?

Is the hard drive okay (given the original problem)? Just because files (e.g., USB drivers) are in a file listing, doesn't mean that they are readable/not corrupt.

Edit: sorry, crossed with @Cadishead Computers reply.
I'll try a scan from recovery console see if it helps. Ta :)
 
Russian roulette with the USB ports. By that I mean shut it down and move the keyboard to another port. Fire it up, if it doesn't work, shut it down, try the next port and repeat. You're trying to find the port the kb was previous using. Typically if you find that particular port, almost any USB kb will work.

This issue is USB drivers are installed and assigned to a particular USB port for that device. Thus if you move a USB device around you'll see Windows pop back up saying it's loading device drivers, although that device has been previously plugged into another USB port. Drivers are loaded from the registry and Windows won't detect and install new drivers until you log in, SO you need to guess what port the previous driver was assigned to by moving the keyboard around :)

I noticed you didn't move the full hive (or maybe you did and didn't mention the other files) which might be another issue. I try to keep the hive files mated or in this case go and see if you can move over the components file from that set you used.

Lastly scan that drive. Although registry files can corrupt like this for a number of reasons, typically when we see this error the hard drive has bad sectors. Not always but typically.
 
Russian roulette with the USB ports. By that I mean shut it down and move the keyboard to another port. Fire it up, if it doesn't work, shut it down, try the next port and repeat. You're trying to find the port the kb was previous using. Typically if you find that particular port, almost any USB kb will work.

This issue is USB drivers are installed and assigned to a particular USB port for that device. Thus if you move a USB device around you'll see Windows pop back up saying it's loading device drivers, although that device has been previously plugged into another USB port. Drivers are loaded from the registry and Windows won't detect and install new drivers until you log in, SO you need to guess what port the previous driver was assigned to by moving the keyboard around :)

I noticed you didn't move the full hive (or maybe you did and didn't mention the other files) which might be another issue. I try to keep the hive files mated or in this case go and see if you can move over the components file from that set you used.

Lastly scan that drive. Although registry files can corrupt like this for a number of reasons, typically when we see this error the hard drive has bad sectors. Not always but typically.
This was the process I did
md tmpcopy c:\windows\system32\config\system c:\windows\tmp\system.bakcopy c:\windows\system32\config\software c:\windows\tmp\software.bakcopy c:\windows\system32\config\sam c:\windows\tmp\sam.bakcopy c:\windows\system32\config\security c:\windows\tmp\security.bakcopy c:\windows\system32\config\default c:\windows\tmp\default.bakdelete c:\windows\system32\config\systemdelete c:\windows\system32\config\softwaredelete c:\windows\system32\config\samdelete c:\windows\system32\config\securitydelete c:\windows\system32\config\defaultcopy c:\windows\repair\system c:\windows\system32\config\systemcopy c:\windows\repair\software c:\windows\system32\config\softwarecopy c:\windows\repair\sam c:\windows\system32\config\samcopy c:\windows\repair\security c:\windows\system32\config\securitycopy c:\windows\repair\default c:\windows\system32\config\default

I did a chkdsk from recovery console and it found and fixed errors.
I have tried each usb port in turn.
I'm searching my cupboard of doom for any dell usb accessories.

I tried plugging in my usb memory stick and that didn't load up either so wonder if it is a USB driver issue, but don't know how to rectify that outside of windows.

Thanks for all your help so far guys. :)
 
... but the lady wants her data ...

Lots of good ideas on how to handle the driver issues. But in the end, if you can't get the kb/mouse to work, then at least retrieve the lady's data and then you can consider a re-install (or, preferably, get her to replace the XP box).

Either boot up a live CD or remove the HD and access via another PC. Once you can access the data, use Fabs (or do it manually) to copy the lady's data.
 
To make sure you're not facing a hardware issue, just boot with a Hirens and run Windows XP mode to see if that your USB ports work correctly. It is also much easier to use for backing up and restoring hive files than the command prompt :)
 
Let me see if I got this.......

Keyboard works in recovery console, but not when booted to OS.

Can you run a previous restore point from the recovery console?

By the way, you had mentioned your client WANTS her data.

Did you clone the drive for a worse case scenario?

Rule #1.....Save the data first, then proceed.
 
I initially plugged it into my machine to attempt to get the data off to start with, but it wanted to initialise the disk. So I stopped there and tried to repair it inside its own box.
I tried to access it again from my PC and still wants to initialise the disk..
Somethings not right...

I've booted into Mini Windows using HironsCD and the mouse works. So no hardware issue.
I've managed to copy the data off onto a stick using Hirons --- first time I've used it - its great!

Any idea if I can use Hirons to "reset" the usb drivers in windows?
 
Can you get some form of remote session into the PC? Say RDP? If you can, then you'll be able to use the host machines keyboard and mouse, then run updates etc. I'd delete the USB drivers from device manage, and then reboot and let it sit for about 5 minutes while it trys to find the drivers from Windows Update.

Before deleting drivers though, have you run SFC /Scannow?

Andy
 
Between that and the initial "XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM" it is almost certain the drive is failing.

......By the way, you had mentioned your client WANTS her data.

Did you clone the drive for a worse case scenario?

Rule #1.....Save the data first, then proceed.

If your clients data is important, you probably should stop and get a sector level image before its too late. If the drive is failing, the last thing you want to do is to something like attempting a file system repair.
 
Between that and the initial "XP could not start because the following file is missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM" it is almost certain the drive is failing.

Yea I think so... I am doing a repair install and its just hanging.
I've got her data, so I'll see if I can sell her a new system rather than a new hard drive.
 
Yea I think so... I am doing a repair install and its just hanging.
I've got her data, so I'll see if I can sell her a new system rather than a new hard drive.
If this is still running XP, explain to her why she needs a new system. Spending more money on this, sounds like your throwing it away.
 
Back
Top