yet another corrupted reg file question.

[Tony Bad]

Hello, I am using the MS instructions on "How to recover from a corrupted
registry that prevents Windows XP from starting" and am getting hung up when I
get to this point in the instructions:

copy c:\windows\repair\system c:\windows\system32\config\system

This started with a "missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
warning and an otherwise blank screen. Searching usenet I came to conclusion
that I needed to follow these instructions, but while I was able to get thru all
this:

md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default


When I get to:

copy c:\windows\repair\system c:\windows\system32\config\system

I get a "The system cannot find the file specified" warning.

Please help...I don't know where to go from here or how to back track if that is
what I should do.

I would sincerely appreciate any advice.

 

[Tony Bad]

Hello, I am using the MS instructions on "How to recover from a corrupted
registry that prevents Windows XP from starting" and am getting hung up when I
get to this point in the instructions:

copy c:\windows\repair\system c:\windows\system32\config\system

This started with a "missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM"
warning and an otherwise blank screen. Searching usenet I came to conclusion
that I needed to follow these instructions, but while I was able to get thru all
this:

md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\system32\config\software c:\windows\tmp\software.bak
copy c:\windows\system32\config\sam c:\windows\tmp\sam.bak
copy c:\windows\system32\config\security c:\windows\tmp\security.bak
copy c:\windows\system32\config\default c:\windows\tmp\default.bak

delete c:\windows\system32\config\system
delete c:\windows\system32\config\software
delete c:\windows\system32\config\sam
delete c:\windows\system32\config\security
delete c:\windows\system32\config\default


When I get to:

copy c:\windows\repair\system c:\windows\system32\config\system

I get a "The system cannot find the file specified" warning.

Please help...I don't know where to go from here or how to back track if that is
what I should do.

I would sincerely appreciate any advice.

Just to add to prior message, while entering:

copy c:\windows\repair\system c:\windows\system32\config\system

results in a "The system cannot find the file specified" warning, the steps that
follow (listed below) all were copied without incident...

copy c:\windows\repair\software c:\windows\system32\config\software
copy c:\windows\repair\sam c:\windows\system32\config\sam
copy c:\windows\repair\security c:\windows\system32\config\security
copy c:\windows\repair\default c:\windows\system32\config\default

 

[Bert Kinney]

Hi Tony,

Why not use System Restore? This will also restore the registry.

How to restore the operating system to a previous state in Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306084

How to start the System Restore tool at a command prompt in Windows XP:
http://support.microsoft.com/kb/304449

 

[Tony Bad]

Hi Tony,

Why not use System Restore? This will also restore the registry.

How to restore the operating system to a previous state in Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306084

How to start the System Restore tool at a command prompt in Windows XP:
http://support.microsoft.com/kb/304449

I will give that a try.

I had been told to start in safe-mode, and hit return to last useable form (or
words to that effect), but when I did so I got the same missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM warning.

I will try the instructions from the link you indicated.

As you probably guessed, I am a bit lost...so I sincerely appreciate your
advice!

Tony

 

[Tony Bad]

Hi Tony,

Why not use System Restore? This will also restore the registry.

How to restore the operating system to a previous state in Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306084

How to start the System Restore tool at a command prompt in Windows XP:
http://support.microsoft.com/kb/304449

Tried to follow instructions from second link, however, when I use F8 to get to
safe mode, and then try to get to "Safe Mode with a command prompt", I get the
same warning about missing or corrupt: \WINDOWS\SYSTEM32\CONFIG\SYSTEM message.

Oh nuts...thought I was getting somewhere.

 

[Bert Kinney]

With the lack of success in what you have tried so far I
would suggest doing a Repair Install.

I found these steps posted by Rick Rogers. It simplifies
the procedure in the article below. I would suggest reading
the article first before proceeding.

1. Insert the Windows XP CD into your computer's CD-ROM
drive or DVD-ROM drive.
2. Restart your computer. If you have to, change the BIOS
settings to start from
the CD-ROM drive or DVD-ROM drive, and then restart your
computer again.
3. At the "Welcome to Setup" page, press ENTER.
4. Press F8 to accept the Licensing Agreement.
5. Use the arrow keys to select the installation of Windows XP
that you want to repair, and then press R to start the automatic
repair process.
6. When Setup is completed, activate Windows XP.

Note that you will need your Product Key for this procedure,
so have it handy before you begin.

How to perform an in-place upgrade (reinstallation) of Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;315341

 

[Malke]

Tried to follow instructions from second link, however, when I use F8
to get to safe mode, and then try to get to "Safe Mode with a command
prompt", I get the same warning about missing or corrupt:
\WINDOWS\SYSTEM32\CONFIG\SYSTEM message.

Oh nuts...thought I was getting somewhere.

Very often the errors you are experiencing indicate failing hardware. It
would be best to a) rescue any data from that drive you need; b) test
the drive with a diagnostic from the drive mftr.; c) if the drive is
good, test the RAM. Please post back if you need help with any of those
suggestions.

Malke

 

[Tony Bad]

With the lack of success in what you have tried so far I
would suggest doing a Repair Install.

I found these steps posted by Rick Rogers. It simplifies
the procedure in the article below. I would suggest reading
the article first before proceeding.

1. Insert the Windows XP CD into your computer's CD-ROM
drive or DVD-ROM drive.
2. Restart your computer. If you have to, change the BIOS
settings to start from
the CD-ROM drive or DVD-ROM drive, and then restart your
computer again.
3. At the "Welcome to Setup" page, press ENTER.
4. Press F8 to accept the Licensing Agreement.
5. Use the arrow keys to select the installation of Windows XP
that you want to repair, and then press R to start the automatic
repair process.
6. When Setup is completed, activate Windows XP.

Note that you will need your Product Key for this procedure,
so have it handy before you begin.

How to perform an in-place upgrade (reinstallation) of Windows XP:
http://support.microsoft.com/default.aspx?scid=kb;en-us;315341

Thanks again...I really appreciate you taking the time to respond.

As I said, I was using the guidelines from here...

http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;307545

and all worked well, except I would get a "cannot find specific file" message
when trying to execute this command:

copy c:\windows\repair\system c:\windows\system32\config\system

In reading other posts on the same subject, I noted a few which indicated I
should use

copy c:\windows\repair\system.bak c:\windows\system32\config\system (note added
*.bak after 1st system) in place of command that wasn't working.

I did so, and then continued with instructions as per MS...all seems okay...for
now.

I would like to understand why this happened and what steps I can take to
prevent any future occurrences. Any additional advice inn that area would be
most appreciated.

Thanks again for your advice, patience, and assistance.

Tony

 

[Tony Bad]

Very often the errors you are experiencing indicate failing hardware. It
would be best to a) rescue any data from that drive you need; b) test
the drive with a diagnostic from the drive mftr.; c) if the drive is
good, test the RAM. Please post back if you need help with any of those
suggestions.

Malke
--
MS MVP - Windows Shell/User
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"

As noted above, I have things working again...for now...but your opinion gives
me cause for concern.

I am pretty good at backing up data...actually just did so yesterday, so that
wasn't a big concern when faced with today's issue....but the other
possibilities are certainly something to worry about. How does one test the
drive and/or test RAM?

Thanks, Tony

 

[Bert Kinney]

Glad to see you have the system up and running.

What it looks like happened was there was no file by the name of
"System" in the C:\WINDOWS\repair folder. So when you used the
following command it could not find the file.

copy c:\windows\repair\system c:\windows\system32\config\system


And when you used this command it found the System.bak file, copied
it to the c:\windows\system32\config\ folder and renamed it to System

copy c:\windows\repair\system.bak c:\windows\system32\config\system

You should check the repair folder and make sure it's there now.

I would suggest a full virus scan with up to date virus software.

Then do a search any installed SpyWare/malware/adware:
Ad-aware is a free multi spyware removal utility that scans
your memory, registry and hard drives for known spyware
components and lets you remove them safely. After installing
Ad-Aware make sure to run the update feature before scanning.
http://www.lavasoftusa.com/ For large amounts of installed
spyware and such, it may be necessary to run Ad-Aware several
times to clear them all.

Here are a couple more removal tools that should also be run.
CWShredder: http://aumha.org/freeware/freeware.php#cwshred

Spybot: http://www.safer-networking.org/

SpywareBlaster:
http://www.wilderssecurity.net/spywareblaster.html
SpywareBlaster doesn't scan and clean for spyware – it
prevents it from ever being installed. SpywareBlaster is
a non memory resident utility. It works by setting a "kill bit"
for the CLSIDs of spyware ActiveX controls, it prevents the
installation of any of them from a webpage.

 

[Malke]

As noted above, I have things working again...for now...but your
opinion gives me cause for concern.

I am pretty good at backing up data...actually just did so yesterday,
so that wasn't a big concern when faced with today's issue....but the
other possibilities are certainly something to worry about. How does
one test the drive and/or test RAM?

Thanks, Tony

To test the drive, go to the drive mftr.'s website where they will have
a diagnostic utility to download. Usually you will make a bootable
floppy from that. Boot with it and do a thorough test. If you get drive
errors, replace the drive.

To test RAM, I like Memtest86 from www.memtest86.com. You can download
the precompiled Windows binary and make a bootable floppy or download
the .iso to make a bootable cd-r if you have third-party burning
software (XP's built-in burning feature won't do that). Either way,
boot with the media you made. The test will run immediately. Allow it
to run for a few hours, unless you get errors right away. If you get
errors, replace the RAM.

Malke

 

[Tony Bad]

I'll get right on the spyware clean-up!

As for the file in my repair folder..."system.bak" is there, but not
"system"...not sure what to make of that?

Thanks again...we'll see what happens!

Tony

Glad to see you have the system up and running.

What it looks like happened was there was no file by the name of
"System" in the C:\WINDOWS\repair folder. So when you used the
following command it could not find the file.

copy c:\windows\repair\system c:\windows\system32\config\system


And when you used this command it found the System.bak file, copied
it to the c:\windows\system32\config\ folder and renamed it to System

copy c:\windows\repair\system.bak c:\windows\system32\config\system

You should check the repair folder and make sure it's there now.

I would suggest a full virus scan with up to date virus software.

Then do a search any installed SpyWare/malware/adware:
Ad-aware is a free multi spyware removal utility that scans
your memory, registry and hard drives for known spyware
components and lets you remove them safely. After installing
Ad-Aware make sure to run the update feature before scanning.
http://www.lavasoftusa.com/ For large amounts of installed
spyware and such, it may be necessary to run Ad-Aware several
times to clear them all.

Here are a couple more removal tools that should also be run.
CWShredder: http://aumha.org/freeware/freeware.php#cwshred

Spybot: http://www.safer-networking.org/

SpywareBlaster:
http://www.wilderssecurity.net/spywareblaster.html
SpywareBlaster doesn't scan and clean for spyware - it
prevents it from ever being installed. SpywareBlaster is
a non memory resident utility. It works by setting a "kill bit"
for the CLSIDs of spyware ActiveX controls, it prevents the
installation of any of them from a webpage.

--
Regards,
Bert Kinney [MS-MVP DTS]
http://dts-l.org/

Thanks again...I really appreciate you taking the time to respond.

As I said, I was using the guidelines from here...

http://support.microsoft.com/default.aspx?Product=winxp&scid=kb;en-us;307545

and all worked well, except I would get a "cannot find specific file"
message
when trying to execute this command:

copy c:\windows\repair\system c:\windows\system32\config\system

In reading other posts on the same subject, I noted a few which indicated
I
should use

copy c:\windows\repair\system.bak c:\windows\system32\config\system (note
added
*.bak after 1st system) in place of command that wasn't working.

I did so, and then continued with instructions as per MS...all seems
okay...for
now.

I would like to understand why this happened and what steps I can take to
prevent any future occurrences. Any additional advice inn that area would
be
most appreciated.

Thanks again for your advice, patience, and assistance.

Tony

 

[DanS]

As noted above, I have things working again...for now...but your
opinion gives me cause for concern.

I am pretty good at backing up data...actually just did so yesterday,
so that wasn't a big concern when faced with today's issue....but the
other possibilities are certainly something to worry about. How does
one test the drive and/or test RAM?

Thanks, Tony

for a fairly decent RAM testing software, do a google search on: memt86

it does some fairly deep testing of RAM modules.