In the ideal case, when you turn on a Windows-based computer based on a family of kernels that still run with NT, the system boots up normally. If the download is completed successfully, the standard Windows shell Explorer starts automatically (in the process manager explorer.exe).
But sometimes, as a result of some phenomena, the boot process may be disrupted, which will lead to damage to the operating system and inability to work. The most common causes of the problem: power failure and malware, third-party user actions. Restoring the registry to its normal state is exactly what can quickly help in this case.
There are different “levels” of system damage. If the screen saver stage is over and the Explorer shell color is displayed (Desktop), and then loading does not occur, then you can limit yourself to the rollback procedure to the previous state of the system. To do this, when loading, press the F8 key on the top of the keyboard, which initiates a menu in which you must select the "Safe Mode" item . In the "All Programs" menu, select "Standard", then "Utilities", the "System Restore" item (rstrui.exe). Select any system restore point to the date of the ill-fated failure and reboot. If you are lucky and the reason is really in the registry, which happens quite often, the system boots as a result of these actions.
There are fatal crashes when loading does not occur at all. Typical symptoms are a blue screen during the boot phase or a black screen indicating that the system cannot load part of the registry. No problem. A couple of magical passes - and the system works again! But here, like any business, there are also subtleties. After all, the cause of fatal failures can be not only software conflicts, but also hardware problems (damaged RAM memory modules or the motherboard). Before attempting to fix the system, they should be checked. To do this, open the case and make sure that the capacitors on the motherboard are in order. Then try to boot with one, then with another RAM module. If there is only one module, then replace it with a new one; if this is not possible, test the working memory with memtest86 utility (can be found on the wonderful collection for PC resuscitation procedures - Hiren's Boot CD).
None of this helped? Then the problem is really in the registry. We try an elementary trick with loading the last working state, including restoring the registry, or rather, a small part of it (one of the items on the F8 menu). Did not help? Then we proceed to the "reinforced concrete" option - we do the registry recovery. To access the file system, use the recovery console. We take the disk with the Windows distribution, wait for all the drivers to load, and press the R key. Exit to the recovery console. Then we replace the damaged "registry hive" with the copy command, indicating the path to C: \ WINDOWS \ REPAIR \ REST_CUSTER_NAME, and the destination path will be C: \ WINDOWS \ SYSTEM32 \ CONFIG
This is enough to boot the system in its original form. In the simplest case, work on this will be completed, if SYSTEM is damaged, you will only need to manually show the system the path to the device drivers. Most often, this can serve as a temporary measure only until that happy moment, until you gain the right to read the System Volume Information directory, where the system’s snapshot is stored, which allows you to restore the registry (restore points).
To gain access, go to the "Control Panel", there we look for the "Folder Options" icon. We remove the checkboxes "hide protected system files", do not forget about the checkbox "use simple shared folder access". We go to the C: drive and look at the coveted "System Volume Information". In the properties of the folder, go to the tab under the name "security" and do the operation of adding the current user to the list. Accessed.
We go into the System Volume Information and into the whole tree of subdirectories. We are looking for RP (Recovery Point, recovery point) as fresh as possible date, go to the Snapshot subdirectory. Copy the registry hive we need of the form _REGISTRY_MACHINE_SOFTWARE to C: \ WINDOWS \ REPAIR. We load the recovery console and use the copy command to copy the registry hive from C: \ WINDOWS \ REPAIR to C: \ WINDOWS \ SYSTEM32] CONFIG. A few seconds after the restart, everything works again! Registry recovery done. A feature of WiNDOWS Vista and Seven versions is the location of the registry backup files in the C: \ WINDOWS \ SYSTEM32 \ CONFIG \ REGBACK directory, which simplifies the above algorithm to one action (moving the registry hive file from the Regback folder to the C: \ Windows directory vital for the operating system \ System32 \ Config. Thus, restoring the Windows 7 registry is simple.