Quick self-help emergency Windows recovery disk (3)

Example 2: Repair security mode

Some viruses will clear the registry [HKEY_LOCAL_MACHINE\\SYSTEM\\ControlSet001\\Control\\SafeBoot] key value, resulting in the original system can not Enter safe mode. For example, the 8749 virus has this "efficacy". At this point, you can restore by exporting the key value corresponding to the emergency system registry. After entering the emergency system, start the registry editor, expand the above key value and export it to “saft.reg”, and then enter the original system to import “saft.reg”. You can fix the security mode.

Example 3: Extracting important system files

Since the emergency system and the original system file are completely consistent, when the original system encounters a failure that cannot be started due to the loss of important system files, just enter the emergency system to extract. The corresponding file can be. For example, in the previous period, Norton accidentally killed "lsasrv.dll" and "netapi32.dll" in the system directory, which caused the blue screen to fail to enter after the original system was restarted. At this time, just enter the emergency system, start the command prompt and execute the following commands to solve the problem. The operation of the emergency system is obviously more convenient than the faulty console:

Copy d:\\windows\\system32\\lsasrv.dll c:\\windows\\system32\\

Copy d:\\windows\\system32\\lsasrv.dll c:\\windows\\system32\\dllcache

Copy d:\\windows\\system32\ etapi32.dll c :\\windows\\system32\\

Copy d:\\windows\\system32\ etapi32.dll c:\\windows\\system32\\dllcache

Dong Master Tip:

Emergency System can It is said that the original system system file backup location, if it is similar to Ntldr and other important system boot files are lost, this will lead to boot can not start, of course, can not enter the emergency system. At this time, we can use DOS boot disk to enter DOS, copy the file from D disk to C:\\. The structure and location of the two system files are identical.

Example 4: Synchronous Update System

We know that the GHO image created by NTFS partition cannot be edited. Therefore, when the original system installs new software or upgrades the system patch, we can only re-create the image. Synchronization Update. In fact, the emergency system produced above is the source of dynamic update of the original system. It is obviously more convenient to edit and update the emergency system than to re-image. For example, for users who use NTFS on the C drive, if you need to recover the system if you encounter a failure, just start GHOST under DOS, perform the "partition to partition" clone, and restore the emergency system partition to partition 1 to quickly update the original system, because Usually we have updated the emergency system virus database and system patches, and the original system is easily resurrected after recovery (Figure 5).

Figure 5