I encountered a c: \ windows \ system32 \ config \ System Fault

Source: Internet
Author: User
Tags administrator password

A computer is a little faulty (the system is Windows 2000). During Processing, I want to clean up the malware in it and use the Windows cleanup assistant to scan and clear it. First, the "cleanup object" is cleared, and there is a prompt in the middle that you need to delete the driver level. If you have done this before, you will be allowed. A blue screen will appear when the system is shut down before restart, and the system will be normal after restart, if there is no problem, we will proceed with the process of "Detachable software", which also requires the driver-level deletion and will continue. Similarly, we will close the blue screen before the restart. If you don't care, continue, the result cannot be started. The progress bar is gone in two steps, and then the black screen, keyboard lights can also be turned off, press the hot boot key can also be restarted, that is, the black screen. I tried the last correct configuration. In safe mode, the screen shows that Windows cannot be started due to the damage or loss of the following files: C: \ winnt \ system32 \ config \ system. The installation disc must be used to start Windows, repair by R. (Note: If it is XP, the prompt path will be c: \ windows \ system32 \ config \ system. Replace winnt in the following path with windows, but the processing method is the same)

First, the memory is suspected. Open the chassis, re-plug the memory, and then start the instance. I had to replace the system file by using the online method.

Start with win PE, back up the system file under c: \ winnt \ system32 \ config \, and copy the system file from c: \ winnt \ repair \ to C: \ winnt \ system32 \ config \, restart, but the result still does not work.

I carefully reviewed the online materials and said that I had to replace the five files under config: the system, software, Sam, security, and default files under \ winnt \ system32 \ config \ are all backed up, and then from C: \ winnt \ repair \ copies five files with the same name to c: \ winnt \ system32 \ config \, and then restarts. This time, I started to enter the desktop, but all the settings (including the original desktop settings) and software installation information were lost. Even though the software files were there, all the information in the registry was lost, completely recovered to the time when the operating system was just installed (even the hardware driver was gone ). Check that a folder is added under c: \ Documents and Settings \. The name is a string added after the original user name. It seems that this is a new configuration.

Because there are financial software on the machine, the re-installation is troublesome, and then back to the PE system, the backup files in addition to the system file four files (software, Sam, security, default) copy back to c: \ winnt \ system32 \ config \ to restore the software content. After this restart, the software installation information was completely returned, and the original desktop was back, but the driver had to be re-installed and the Host Name and IP address had to be re-set. However, this is simple, you can use the software. I really don't understand why it will fail to recover the system file for the first time. Do you need to temporarily accompany other files.

The repair is completed. As for the cause of the fault, it is suspected that the driver-level deletion of the Windows cleanup assistant hurt the system registry when deleting the stubborn file, because it tried to enter the registry of the original Hard Drive System in the PE system, the result is displayed on the blue screen. It seems that the file saved in the registry of the original system is damaged. However, since there were seven uninstalling software at the time, I don't know which one is stubborn. I suspect it is the boboboturbo plug-in. The system should be a file that stores hardware driver information. For other files, Sam is the password. Many people should know about it.

Appendix: How to fix c: \ windows \ system32 \ config \ system on the Internet:

First:

1. This problem is mostly caused by memory quality. Check and replace the memory for testing first.

2. Hard Disk Bad Sectors. Please repair them.

3. If none of the above are true, use the following method:

Restart to dos. If your system is NTFS, DOS support is required. Use the boot disc or maxdos to start to dos,

Copy c: \ windows \ repairs \ ystem c: \ windows \ system32 \ config \ System

But in this way, all your previous settings will be lost. This is the configuration you configured when you started the desktop for the first time. You have to reinstall your driver and settings.

If Windows 2000 is used, the following error occurs: C: \ winnt \ system32 \ config \ system or C: \ winnt \ system32 \ drivers \ NTFS. the sys file is lost. You can use the 2000 system installation disc to enter the installation page and press the r key to fix the problem.

Second:

The following error message is displayed when the instance is started:

Windows cannot be started because the following files are damaged or lost:

C: \ windows \ system32 \ config \ System

In fact, the system file is damaged, causing the system to fail to start normally. The solution is simple. Go to the fault recovery console to fix the problem. The procedure is as follows:

Start the system with the system installation disk, and press the "r" key to select the repair or recovery option to go to the fault recovery console. The system will automatically detect the installed operating system. Enter number 1 to select the operating system to be repaired. Enter the password of the administrator of the local administrator account as required to enter the DOS console interface.

Enter the following command lines in sequence:

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

(Note: The above is to back up the original file)

Copy c: \ windows \ repair \ system c: \ windows \ system32 \ config \ System

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

Original translated from: http://www.stormcn.cn/post/136.html

Today, the loss of c: \ windows \ system32 \ config \ system is solved. This is already a problem that I have encountered many times. Let's record it:
First insert the Windows XP installation disc into the CD-ROM drive and then restart your computer. Start with a CD.
When the "Welcome to installer" Screen appears, press R to start the fault recovery console.
If you are using a dual-boot or multi-boot computer, select the installation to be accessed from the fault recovery console.
Follow the prompts and enter the administrator password. If the administrator password is blank, press Enter.
At the command prompt on the Recovery Console, type the following commands and press enter after each line:
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

Copy c: \ windows \ repair \ system c: \ windows \ system32 \ config \ System
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

Type exit to exit the Recovery Console. The computer restarts.

Original converted from: http://blog.chinaunix.net/space.php? Uid = 609478 & Do = Blog & cuid = 461002

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.