System Restore through the command line: an alternative to reinstall Windows.

often to restore functionality of the operating system requires only a couple of simple steps that take just minutes.But instead of saving a lot of time and effort, the user begins the process of reinstalling the system.Accordingly, it pulls the driver installation and all programs.There is even a whole cohort of people whose main occupation of the PC is the reinstallation of Windows.But if you just need to work as quickly as possible and you want to restore your PC?Then this article useful.For Windows developers have provided a convenient tool - Recovery Console.Anyone who does not scare the command line since the PC DOS 7.0, can cope with this task.Just arm yourself with the usual distribution of a series of the Windows 2000 / XP / Vista / 7 - and for the cause.System Restore from a command line will not be easy.Loads from the drive and wait until the distribution stage, when prompted, press "R".Select the installation of the system in which it is necessary to go, and trying to drive the system administrator password;if you do not ask it during the previous installation, it is empty.Consider the typical faults, allows for system recovery via the command line.



1. Damaged malicious software boot sector of the system HDD.

Perhaps one of the simplest problems.Just load the Recovery Console from the distribution package and recruit only 2 console command - fixboot and fixmbr.
Besides often a problem in the absence of ntldr file and ntdetect.com, they must necessarily be.They can be found on the distribution folder i386.Copy them to disk C: \

2. Missing the root C: \ drive file boot.ini

Just run the command key bootcgf rebuild, add discovered operating systems to the file.System Restore through the command line simply elementary.Each user is able to implement advanced this action.

3. Was made to reinstall the system board, and the system after this procedure is not loaded, giving BSOD with code okanchivayuschisya to 7B

If you do not have a convenient tool (say, ERD Commander), you can do a Recovery Console Get the listservices team LISTSVC, and ENABLE command includes system startup services amdide, amdsata, amdxata, atapi, intelide, msahci, pciide.This enables standard drivers and load will allow for the start of the old system based on new equipment.

4. Installing incorrect drivers or services (malware) has led to the inability of the system to boot.

Most often, you can restrict a safe's backup mode and a previous restore point, but it happens when there is a recovery point, and the corresponding service is disabled.Then we go into the recovery console and type the command LISTSVC - a list of all those present in the registry services.Thus, we learn the name of the desired us to faulty drivers.After all, it happens that you can install the device driver is correctly written, and may need to restore the system from the command line.Disable command DISABLE "ServiceName".Keep in mind that malicious software often makes a substitution system driver, such as tcpip.sys or the network card driver (ndis.sys), often without loss of efficiency!Then we must rewrite the root of the C: \ drive, and compare the original file with the size of the impostor.If they do not match, please feel free to substitute with the command "copy" in the directory C: \ windows \ system32 \ drivers.

5. Damaged registry hive file

symptoms of the problem are - you see a black screen where the core of the system reports that the missing or damaged SYSTEM / SOFTWARE.This is probably not a good problem, if there is no backup of the registry.And if the problem affected SOFTWARE, it is necessary to restore all registry entries related to the installation of programs - that is, in fact, re-install the system.A more optimistic scenario - the damaged SYSTEM.Just type in the recovery console command:

cd repair
copy SYSTEM C: \ windows \ system32 \ config

Reboot and wait until the system finds all of the devices.We'll have to manually "show" system, where are the driver files (C: \ windows \ system32 \ drivers).

Here are the main problems and their solutions, if you decide to implement a system restore from the command line.Of course, there are other, more complex problems or a combination thereof, but they can be overcome, the benefit of tools allows.You can also use specialized software Hiren's Boot CD and ERD Commander, has in its arsenal a much larger number of powerful specialized tools, as well as their many clones, but the recovery console - the foundation, which must be able to use the service engineer or an experienced user.After a system restore using the command line gives the result much faster.