Emergency recovery of damaged Windows system (1)

1, the last configuration

Windows2000 or later operating system, each time after successful startup, the system registry will be automatically backed up, once we find that the Windows system can not start normally this time, it is mostly The last time we made a wrong operation on the system or made a wrong installation of some software, it destroyed the relevant settings of the system registry. At this point, we can try to restart the computer system with the last successful startup configuration: just press the F8 function key in time to restart the system, call up the system boot menu, and then select "last correct. Configure the project, so that the Windows system may start up normally.

2, repair system files

If some of the core files of Windows system are accidentally damaged
, then even if you use "last configuration", Windows system is very It is difficult to guarantee that it will start normally. If the Windows system only has a small number of system files damaged, then we may wish to use the built-in SFC scan repair command of Windows system to try to repair the damaged system files. Once the repair is successful, the Windows system starts again. Will return to normal. When repairing damaged system files, just click the "Start" /"Run" command, in the pop-up system run dialog box, enter the string command "sfc/scannow", click the Enter key, the command program It will search and scan the system files at every corner of the system. Once the system file is found to be incorrect or the system file is damaged, it will automatically pop up a prompt interface, asking us to insert the installation CD of Windows system to extract from it. A normal system file replaces an abnormal system file to achieve the purpose of repairing system files. If the system repair operation is successful, I believe that when we restart the computer system, we will not see any abnormality.

3, log out the current user

If the damaged part of the Windows system is only due to the installation of inappropriate software, or the software is not properly set up, then we can usually Through the "logout of the current user" method, first aid to the damaged Windows system, because the impact of the software on the system settings can only be limited to the currently logged in users, once the system is not working properly in the current user state, we can Log out of the current user and log in to the system as another user, so that Windows can generally resume normal operation.

Before logging out of the current user and switching to other users to log in to the system, we need to open the control panel window of the system, then double-click the "User Account" item, and then click "Add" in the interface. Button to re-create a new login account, set a suitable access password for the account, and set the corresponding account as super administrator.

After logging in to the Windows system with another account, some important data saved in the current user directory may not be accessible. Therefore, before logging out the user, we need to open the system explorer window. Find the user directory corresponding to the current account. For example, if the current login system account is aaaa, the default account directory of the system should be “C:\\Windows\\DocumentsandSettings\\aaaa”, and all important data under the directory should be backed up to In a partition directory other than the system partition.

After doing the above preparations, we can now execute the "Start" /"Logout aaaa" command in turn to log out the current login account, and then log in to Windows with the account just created. System; after successfully logging into the Windows system with the new account, we restore the important data backed up to the new user directory corresponding to the current account, so that the damaged Windows system can restore the previous normal running state.

4, re-registering DLL files

Windows systems are sometimes subject to frequent damage, mainly because many applications often share calls to some DLL files, once some applications are automatically used After uninstalling, the DLL files called by these applications are often deleted, so that when the Windows system or other applications in the system call the shared DLL files again, the error will naturally occur. .