Recovery Console issues

[PAL]

My girlfriend's laptop is complaining about the C:\windows\system32\config\system file being missing or corrupted. So when I go into the recovery console to follow the official Microsoft KB solution for fixing it (which entails copying the corrupted registry bits to a brand new folder, deleting the originals, and then copying the copies back to the original spot), it says the "file cannot be copied." I'm wondering if this is because the console never asked me for an administrative password (no, I never went into the registry and disabled don't-require-admin-password-for-the-recovery-console option), and thus I don't have access to copy system files.

Everywhere I've looked on the internet, I've found nowhere that addresses what to do if the recovery console doesn't even ask you for admin password. All the console does is ask which OS partition I want to login to, and then it comes up with the C:\WINDOWS\ prompt after I choose it. I've run a chkdsk and fixed some problems, but otherwise I can't see anything wrong. Also, the laptop has XP Home SP2 installed on it, but the only OS disc I could find at my house has XP Pro SP1 on it. Would this make a difference as far as why the console doesn't ask for the admin password? I wouldn't think that it does, since I'm assuming the recovery console itself is the same from one XP build to another.

If all else fails, I guess I could take the HD out, stick it in another machine, back up all the data, reformat, and rebuild the thing, but I really don't want to waste 2 or 3 days fixing it if the MS fix works. And my girlfriend is already getting antsy.

Any suggestions would be appreciated.

Edited August 22, 2007 by PAL

[PAL]

It seems I've fixed the problem. I copied files from the last good restore point into the c:\windows\system32\config\ folder, which let me overwrite the existing files. The corrupt file wouldn't copy because it was unreadable. Laptop booted right up after copying from the restore point.

[Railman5]

Just goes to show.

Basics is the first point of call before devving deep into the inner sanctum.

good bit of advice working from the simplest fix upwards.

[Ponch]

The corrupt file wouldn't copy because it was unreadable.

I had the same problem yesterday on one of our user's desktop (this must be the 6th in about a year). The file was there (about 4.5Meg) and I could move it and copy it back so I don't know what was corrupt to it. I solved it by typing "chkdsk /p" in the recovery console. I wonder why this /p option is not available in normal XP (and then in Bart PE for instance). Maybe it needs some file from the cd, maybe it would make it too easy.