Often, to restore the operating system, a couple of simple steps are required, which will take a few minutes. But instead of saving a lot of time and effort, the user begins the process of reinstalling the system. Accordingly, this leads to the installation of drivers and all programs. There is even a whole cohort of people whose main occupation for a PC is to reinstall Windows. And if you just need to work and you need to restore PC performance as quickly as possible? Then this article will come in handy. After all, Windows developers have provided a convenient tool - the recovery console. Anyone who is not afraid of the PC DOS 7.0 command line can handle this task. Just arm yourself with a regular distribution kit from the Windows 2000 / XP / Vista / 7 series - and get to work. System recovery through the command line is not difficult. We boot from the distribution disk and wait for the stage when it will be offered to press the "R" key. We select the installation of the system to which we must go, and drive in the password of the system administrator; if you did not ask it during the previous installation, then it is empty. Consider typical malfunctions that allow you to restore the system through the command line.
1. The boot sector of the system HDD damaged by malware.
Perhaps one of the easiest options for the problem. Just load the recovery console from the distribution kit and type only 2 commands in the console - fixboot and fixmbr.
In addition, often there is a problem in the missing ntldr and ntdetect.com files, they must be mandatory. They can be found on the distribution in the i386 folder. Copy them to the C: \ drive
2. Missing in the root of the drive C: \ boot.ini file
Just run the bootcgf command with the rebuild key, adding the found operating systems to this file. System recovery through the command line is just basic. Each advanced user is able to carry out this action.
3. The system board was reinstalled, and the system after this procedure does not boot, issuing a BSOD with a code ending in 7B
If you don’t have a more convenient tool at hand (say, ERD Commander), you can only get by with the recovery console. We get the list of services with the LISTSVC command, and with the ENABLE command we enable the system start of the services amdide, amdsata, amdxata, atapi, intelide, msahci, pciide. This activates the loading of standard drivers and allows you to start the old system based on new equipment.
4. Installing the incorrect driver or service (malware) has led to the system being unable to boot.
Most often, you can limit yourself to simply safe mode and backup of the previous restore point, but it happens when there is simply no restore point and the corresponding service is disabled. Then you need to go into the recovery console and type the command LISTSVC - a list of all the services present in the registry. Thus, we will find out the name of the faulty driver we need. After all, it happens that you can install an incorrectly written device driver and you may need to restore the system through the command line. Disable the DISABLE command "ServiceName". It should be remembered that often malicious software spoofs a system driver, for example tcpip.sys or a network card driver (ndis.sys), and often without loss of functionality! Then you should rewrite the original file in the root of the C: \ drive and compare it with the size of the impostor. If they do not match, feel free to do the replacement using the "copy" command in the C: \ windows \ system32 \ drivers directory.
5. Corrupted registry hive file
Symptoms of the problem are as follows - you see a black screen where the system kernel reports that SYSTEM / SOFTWARE is missing or damaged. Perhaps this is the worst problem if there is no backup of the registry. Moreover, if the problem affected SOFTWARE, then it is necessary to restore all registry entries relating to the installation of programs - that is, in fact, reinstall the system. A more optimistic scenario is corrupted SYSTEM. Just type the command in the recovery console:
copy SYSTEM C: \ windows \ system32 \ config
We reboot and wait until the system finds all the devices. You have to manually "show" the system where the driver files are located (C: \ windows \ system32 \ drivers).
Here are the main problems and solutions, if you decide to restore the system from the command line. Of course, there are other, more complex problems or their combinations, but they can also be overcome, since the tools allow. You can also use the specialized software Hiren's Boot CD and ERD Commander, which have in their arsenal a lot more powerful specialized utilities, as well as their numerous clones, but the recovery console is the basis that a service engineer or an experienced user should be able to use. Indeed, system recovery using the command line gives a much faster result.