Article ID : 307545 cannot find file specified

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

In the recovery console window, I typed:

md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\.....
etc, then

delete c:\windows\system32\config\system
delete c:\w....etc

when I try to copy the files back

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

I get a message saying 'the system cannot find the file specified. Any
ideas? I am working off of the CD-ROM
 
Julia said:
In the recovery console window, I typed:

md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\.....
etc, then

delete c:\windows\system32\config\system
delete c:\w....etc

when I try to copy the files back

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

I get a message saying 'the system cannot find the file specified. Any
ideas? I am working off of the CD-ROM
Click to expand...

Is there a reason that you did not execute the replace command like this:

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

By the way, it is very dangerous to be doing things like this to registry
hives. If you have logged off the computer without restoring the registry,
your computer will not boot.
You will then need to consult the article in Help & Support about how to
recover from a corrupt or missing registry.
Jim
 
Jim said:
Is there a reason that you did not execute the replace command like this:

copy c:\windows\tmp\system.bak c:\windows\system32\config\system
Click to expand...

That would just take the broken system hive and return it to the config
folder. Julia needs to replace the broken hive with the one that was
created when Windows was installed.

By the way, it is very dangerous to be doing things like this to registry
hives. If you have logged off the computer without restoring the registry,
your computer will not boot.
Click to expand...

If Julia is in the Recovery Console executing these commands her
computer is already not booting.

You will then need to consult the article in Help & Support about how to
recover from a corrupt or missing registry.
Click to expand...

She has/is already doing that, her subject header mentions KB307545

John
 
Julia said:
In the recovery console window, I typed:

md tmp
copy c:\windows\system32\config\system c:\windows\tmp\system.bak
copy c:\windows\.....
etc, then

delete c:\windows\system32\config\system
delete c:\w....etc

when I try to copy the files back

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

I get a message saying 'the system cannot find the file specified. Any
ideas? I am working off of the CD-ROM
Click to expand...

If you cannot copy the file then you possibly have disk or file system
corruption. Can you copy the other files? If yes, and if the system
hive (from the Repair folder) is the only one that you can't copy then
you can try copying the system.bak hive from the same repair folder to
the config folder, making sure to rename it SYSTEM (without the .bak or
any other extension).

If you cannot copy the file you will probably have to run a chkdsk /r on
the disk, you can run it from the Recovery Console. Be warned that
there is always a risk of data loss when you run chkdsk. Chkdsk can
take a long time to run, do not interrupt chkdsk while it is doing its
work! If you have important files on the disk it may be advisable to
mount the disk to another Windows XP or Windows 2000 installation and
see if you can salvage your files before running chkdsk.

If you really cannot copy the system hive even after running chkdsk,
then you can mount the disk to another Windows 2000/XP computer and
dispense with Steps 1 and 3 altogether, the object of the exercise in
KB307545 is to copy the registry files in the Snapshot folder to the
Config folder. From the Snapshot folder copy the files:


• _REGISTRY_USER_.DEFAULT
• _REGISTRY_MACHINE_SECURITY
• _REGISTRY_MACHINE_SOFTWARE
• _REGISTRY_MACHINE_SYSTEM
• _REGISTRY_MACHINE_SAM

to the System32\config folder directly, making sure to rename them as
follows:

Rename _REGISTRY_USER_.DEFAULT to DEFAULT
• Rename _REGISTRY_MACHINE_SECURITY to SECURITY
• Rename _REGISTRY_MACHINE_SOFTWARE to SOFTWARE
• Rename _REGISTRY_MACHINE_SYSTEM to SYSTEM
• Rename _REGISTRY_MACHINE_SAM to SAM

These will in fact replace the present DEFAULT, SECURITY, SOFTWARE,
SYSTEM, and SAM files in the Config folder.

Once that is done, return the disk to the computer and if it boots
proceed to Step 4 as instructed in the article. To repair this you may
have no choice but to run chkdsk on the drive, if you do you may find
that the Snapshot files are not in the expected System Volume
Information folder, if that is the case look for FOUND.xxx folders in
the root of the drive, the Snapshot files may get dumped in there, they
may or may not be usable, you will only know by trial.

Good luck,

John
 
Back
Top