Since this is an OEM system and we are unable to use KB 307545's method, if
possible you may install the hard drive of the problematic system into
another computer with Windows XP which can start normally as a slave disk
and then refer to one of the following methods:
Method 1 Backup the data and then reinstall the system
========================
I noticed that when you tried to copy the files during Recovery Console,
you get a error saying access denied. If you would like to reinstall the
problematic system, you may copy the data from the slave disk after you
install the hard drive into another computer. If you are prompted "Access
is denied" error when you try to copy the data, you may refer to the
following Kb article:
How to take ownership of a file or folder in Windows XP
http://support.microsoft.com/kb/308421
After the backup, you may install the hard drive back to the original
computer and then format and reinstall the system.
Method 2 Try to restore the corrupted registry file
========================
If you would like to restore the registry file rather than reinstall the
system, you may refer to the following steps after you install the hard
drive into another computer:
1. Start Windows Explorer.
2. On the Tools menu, click Folder options.
3. Click the View tab.
4. Under Hidden files and folders, click to select Show hidden files and
folders, and then click to clear the Hide protected operating system files
(Recommended) check box.
5. Click Yes when the dialog box that confirms that you want to display
these files appears.
6. Click the system partition of the problematic slave disk, usually this
partition contains a Windows folder and other system folders such as
Documents and Settings, I assume the drive is D:. Please note do not click
the system partition of the primary disk, such as C:\.
Note: It is very important to select the correct drive before you continue
the following steps.
7. Open the D:\System Volume Information folder in above partition. This
folder is unavailable and appears dimmed because it is set as a
super-hidden folder.
Note: This folder contains one or more _restore {GUID} folders such as
"_restore{87BD3667-3246-476B-923F-F86E30B3E7F8}".
Note: You may receive the following error message:
D:\System Volume Information is not accessible. Access is denied.
If you receive this message, see the following Microsoft Knowledge Base
article to gain access to this folder and continue with the procedure:
How to gain access to the System Volume Information folder
http://support.microsoft.com/kb/309531
8. Open a folder that was not created at the current time. You may have to
click Details on the View menu to see when these folders were created.
There may be one or more folders starting with "RPx under this folder.
These are restore points.
9. Open one of these folders to locate a Snapshot subfolder. The following
path is an example of a folder path to the Snapshot folder:
D:\System Volume
Information\_restore{D86480E3-73EF-47BC-A0EB-A81BE6EE3ED8}\RP1\Snapshot
10. From the Snapshot folder, copy the following files to the
D:\Windows\Tmp folder:
_REGISTRY_USER_.DEFAULT
_REGISTRY_MACHINE_SECURITY
_REGISTRY_MACHINE_SOFTWARE
_REGISTRY_MACHINE_SYSTEM
_REGISTRY_MACHINE_SAM
11. Rename the files in the D:\Windows\Tmp folder 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
12. Copy above files from D:\Windows\Tmp folder to
D:\Windows\System32\Config folder to overwrite the corrupted file and other
registry files.
Note: Even though just the SYSTEM file is corrupted, please do not replace
the SYSTEM file only. When we replace the registry file, we recommend
replacing all the hives at the same time to avoid any potential mismatched
issue.
13. Install the problematic hard drive back into the original computer and
then try to boot the system.
14. If the issue persists, you may repeat above steps but select another
older restore point and then test it again. If this still fails, please
refer to KB 822705 to check other reasons.
For more information about the above steps, I recommend you may carefully
read KB 307545 again.
Hope this helps! Please try the suggestions above and let me know the
results at your earliest convenience. I look forward to hearing from you
soon.
!!