What Does A Startup Repair Do

If y'all have been using Windows throughout its various versions, chances are you know from immediate experience that startup problems with previous version of the Windows operating system occurred pretty regularly. Fortunately, Microsoft has ever provided us with special tools for fixing those problems. For example, in Windows NT we had the Emergency Recovery Utility, in Windows 2000 we had the Recovery Console, in Windows XP we had System Restore, in Windows 7 we had the Startup Repair Tool, and in Windows 8 we had Startup Repair.

Windows 10 comes with a similar tool, besides called Startup Repair. Like its predecessors, Startup Repair is designed to intercede at the get-go hint of an operating system startup problem. When a problem is detected, Startup Repair will launch an automated, diagnostics-based troubleshooter that doesn't require user intervention, and in many cases information technology will resuscitate an unbootable organisation.

If the startup problem is astringent enough to prevent Startup Repair from launching on its own, you lot can launch it from the Windows ten Recovery Bulldoze. In this article, I'll take a look at using Startup Repair from the Recovery Drive. As I do, I'll explain how it works.

Note: In a serial of future articles, I'll continue my exam of the tools on the Recovery Bulldoze and show you in particular how each tool works.

Running Startup Repair

Running Startup Repair from the Recovery Drive is piece of cake. After your system boots from the Recovery Drive and you lot follow the Troubleshoot>Advanced options path through the menu, you'll come across the Avant-garde Options screen shown in Effigy A. Ane the tools plant on this screen is Startup Repair.

Effigy A

The Startup Repair tool is located in the bottom left of the Advanced Options screen.

When you select the Startup Repair option, you'll see the screen shown in Figure B.

Figure B

Your first line of defense when it comes to recovering a Windows 10 system that won't start properly is the Startup Repair tool.

Once you launch it, Startup Repair will begin diagnosing the startup problem, displaying the screen shown in Figure C.

Figure C

In the get-go step of its operation, Startup Repair will diagnose the problem.

During this diagnostic stage, Startup Repair volition scan your organization and analyze the various settings, configuration options, and system files as it looks for corrupt files or botched configuration settings. More specifically, Startup Repair will look for the post-obit problems:

Missing/corrupt/incompatible drivers
Missing/corrupt system files
Missing/decadent kicking configuration settings
Corrupt registry settings
Corrupt disk metadata (main boot record, sectionalization table, or boot sector)
Problematic update installation

If Startup Repair detects any of these types of bug, information technology will automatically attempt to fix them, as shown in Figure D.

Figure D

One time Startup Repair has diagnosed your startup problem, it volition endeavor to repair it.

If Startup Repair can fix the trouble, it will practice so without whatsoever intervention. It volition then restart the organisation and kick unremarkably.

Astringent problems

If Startup Repair can't fix the startup trouble, you'll see a screen like the ane shown in Effigy East. In this situation, Startup Repair will create a log file with more information and provide yous with a way to go dorsum to the Advanced Options screen, where you can select 1 of the other recovery options.

Effigy E

If Startup Repair tin can't repair your organization, it will display this screen.

Earlier you use 1 of the other recovery options, you should investigate the log file and meet what details it provides. The Recovery Drive contains Notepad, so you can use information technology to view the log file. To begin, take notation of the path and filename of the log file. Then click the Advanced Options button. When you render to the Avant-garde Options screen, navigate to the Command Prompt tool.

When the Command Prompt window appears, type the drive letter to change drives. In my instance, the log file is on bulldoze C. Next, apply the CD command to access the folder containing the log file. Finally, type the name of Notepad's executable file, along the name of the log file as a parameter.

This is the prepare of commands you lot would use to admission the log file every bit shown in Figure F:

c:

          cd \Windows\System32\LogFiles\Srt

notepad.exe SrtTrail.txt

Figure F

From the Control Prompt, you lot tin can launch Notepad and open up the log file.

When Notepad appears, you'll see the contents of the SrtTrail.txt log file similar to the one shown in Figure G. If you curlicue to the lesser of the file, y'all will probably find a test that failed, which could exist a practiced lead for further investigation.

Figure Chiliad

The SrtTrail log file contains information you can utilize for further troubleshooting.

If you lot booted the organisation from a USB flash drive, yous tin salvage the file from Notepad to the flash drive, remove the flash drive, take information technology to another PC, and print it. Y'all now have a printed copy of the log file you tin use every bit an assistance to further troubleshooting. After you impress the log file, be certain to return the flash drive to the bilious reckoner.

If you lot booted the organisation from an optical disc, you won't be able to print the file, but you can scroll through information technology and take notation of whatever details y'all call up are crucial.

What'due south your accept?

Using the Startup Repair tool from the Recovery Bulldoze tin can aid you get an ailing Windows 10 organization dorsum to a bootable state. If Recovery Drive tin't set the problem, you can use the log file as an aid for further investigation. Accept you used Windows 10's Startup Repair option? If so, did it get your system dorsum into a bootable state? Share your thoughts in the discussion thread below.