As I read the MS instructions, the only reason for the copy is in case you
need the old (bad) registry, such as if the one in the repair area is worse
than the one you now have. Note that the next set of steps is to delete the
registry hives under c:\windows\system32\config. Then, the final set of
steps is to copy those form the repair directory to
c:\windows\system32\config.
You could try deleteing the bad hive without copying it. Remember that a
hive is a file and is the file is truely corrupt, or the pointers to it are
bad, it may not be possible to work with it, even to do a simple command,
like a copy.
In any case be sure that the hive in the repair directory actually exists
before deleting the one in config.
"GvdS" <(E-Mail Removed)> wrote in message
news:91F63647-5117-4225-818E-(E-Mail Removed)...
>I have a Registry File Failure, the registry cannot load the hive
> \SystemRoot\System32\Config\Software.
>
> I found a link to resolve this problem
> (http://support.microsoft.com/kb/307545/en-us).
>
> I have to perform these steps:
>
> 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
>
> This works fine but not for the second one: software. The other files are
> copied just fine, but with the software one I receive: "The file could not
> be
> copied".
>
> I hope someone has a solution for this problem.
>
> Thanks in advance!
Similar Threads
