Advanced troubleshooting for Windows boot issues

  • Commodity
  • 11 minutes to read

Note

This article is intended for use by support agents and IT professionals. If yous're looking for more general information nearly recovery options, see Recovery options in Windows x.

Summary

There are several reasons why a Windows-based calculator may have problems during startup. To troubleshoot boot problems, offset make up one's mind in which of the post-obit phases the calculator gets stuck:

Phase Boot Process BIOS UEFI
1 PreBoot MBR/PBR (Bootstrap Code) UEFI Firmware
ii Windows Boot Managing director %SystemDrive%\bootmgr \EFI\Microsoft\Boot\bootmgfw.efi
3 Windows Bone Loader %SystemRoot%\system32\winload.exe %SystemRoot%\system32\winload.efi
4 Windows NT OS Kernel %SystemRoot%\system32\ntoskrnl.exe

ane. PreBoot

The PC's firmware initiates a Ability-On Cocky Exam (Mail service) and loads firmware settings. This pre-boot procedure ends when a valid system deejay is detected. Firmware reads the main boot tape (MBR), and so starts Windows Boot Manager.

2. Windows Boot Manager

Windows Boot Managing director finds and starts the Windows loader (Winload.exe) on the Windows kick sectionalization.

3. Windows operating organization loader

Essential drivers required to get-go the Windows kernel are loaded and the kernel starts to run.

4. Windows NT OS Kernel

The kernel loads into memory the system registry hive and additional drivers that are marked as BOOT_START.

The kernel passes control to the session manager procedure (Smss.exe) which initializes the organization session, and loads and starts the devices and drivers that are not marked BOOT_START.

Here is a summary of the kick sequence, what will exist seen on the display, and typical boot problems at that signal in the sequence. Before starting troubleshooting, yous accept to sympathise the outline of the boot process and display status to ensure that the issue is properly identified at the beginning of the date.

thumbnail of boot sequence flowchart.
Click to enlarge

Each phase has a different approach to troubleshooting. This commodity provides troubleshooting techniques for problems that occur during the first three phases.

Annotation

If the calculator repeatedly boots to the recovery options, run the post-obit command at a command prompt to break the cycle:

Bcdedit /prepare {default} recoveryenabled no

If the F8 options don't piece of work, run the post-obit command:

Bcdedit /prepare {default} bootmenupolicy legacy

BIOS phase

To determine whether the system has passed the BIOS phase, follow these steps:

  1. If at that place are any external peripherals connected to the computer, disconnect them.

  2. Check whether the hard disk drive drive low-cal on the physical reckoner is working. If it is not working, this indicates that the startup procedure is stuck at the BIOS phase.

  3. Press the NumLock central to run across whether the indicator low-cal toggles on and off. If it does non, this indicates that the startup process is stuck at BIOS.

    If the system is stuck at the BIOS phase, at that place may be a hardware problem.

Kick loader phase

If the screen is completely black except for a blinking cursor, or if you receive one of the post-obit error codes, this indicates that the boot process is stuck in the Boot Loader phase:

  • Boot Configuration Information (BCD) missing or corrupted
  • Kicking file or MBR corrupted
  • Operating system Missing
  • Boot sector missing or corrupted
  • Bootmgr missing or corrupted
  • Unable to kick due to system hive missing or corrupted

To troubleshoot this problem, use Windows installation media to first the computer, press Shift+F10 for a control prompt, then utilize whatever of the following methods.

Method 1: Startup Repair tool

The Startup Repair tool automatically fixes many common issues. The tool besides lets you quickly diagnose and repair more complex startup problems. When the figurer detects a startup problem, the estimator starts the Startup Repair tool. When the tool starts, it performs diagnostics. These diagnostics include analyzing startup log files to determine the cause of the trouble. When the Startup Repair tool determines the cause, the tool tries to fix the problem automatically.

To do this, follow these steps.

  1. Start the arrangement to the installation media for the installed version of Windows. For more data, see Create installation media for Windows.

  2. On the Install Windows screen, select Next > Repair your reckoner.

  3. On the Choose an option screen, select Troubleshoot.

  4. On the Avant-garde options screen, select Startup Repair.

  5. After Startup Repair, select Shutdown, then turn on your PC to see if Windows can boot properly.

The Startup Repair tool generates a log file to help yous sympathize the startup issues and the repairs that were made. Y'all can find the log file in the post-obit location:

%windir%\System32\LogFiles\Srt\Srttrail.txt

For more information, meet A Stop fault occurs, or the reckoner stops responding when yous endeavor to starting time Windows Vista or Windows seven

Method 2: Repair Kick Codes

To repair kicking codes, run the post-obit command:

              BOOTREC /FIXMBR

To repair the kick sector, run the following command:

              BOOTREC /FIXBOOT

Note

Running BOOTREC together with Fixmbr overwrites only the master boot lawmaking. If the corruption in the MBR affects the sectionalisation table, running Fixmbr may not fix the problem.

Method 3: Gear up BCD errors

If you receive BCD-related errors, follow these steps:

  1. Scan for all the systems that are installed. To practice this, run the following command:

                      Bootrec /ScanOS

  2. Restart the computer to cheque whether the trouble is fixed.

  3. If the problem is not stock-still, run the following commands:

                      bcdedit /export c:\bcdbackup  attrib c:\boot\bcd -r -s -h  ren c:\boot\bcd bcd.quondam  bootrec /rebuildbcd

  4. Restart the system.

Method 4: Replace Bootmgr

If methods 1, two and 3 practice non fix the problem, replace the Bootmgr file from bulldoze C to the Organisation Reserved partition. To do this, follow these steps:

  1. At a command prompt, change the directory to the Organization Reserved sectionalisation.

  2. Run the attrib command to unhide the file:

                      attrib -r -south -h

  3. Navigate to the system bulldoze and run the same command:

                      attrib -r -s -h

  4. Rename the Bootmgr file as Bootmgr.old:

                      ren c:\bootmgr bootmgr.one-time

  5. Navigate to the system drive.

  6. Copy the Bootmgr file, then paste it to the System Reserved partition.

  7. Restart the reckoner.

Method 5: Restore Organization Hive

If Windows cannot load the system registry hive into memory, you must restore the system hive. To practice this, utilise the Windows Recovery Surround or use Emergency Repair Disk (ERD) to copy the files from the C:\Windows\System32\config\RegBack to C:\Windows\System32\config.

If the problem persists, you may want to restore the system country backup to an alternative location, and so think the registry hives to be replaced.

Notation

Starting in Windows 10, version 1803, Windows no longer automatically backs up the organization registry to the RegBack binder.This change is past design, and is intended to help reduce the overall disk footprint size of Windows. To recover a organisation with a corrupt registry hive, Microsoft recommends that you use a system restore point. For more details, check this article

Kernel Phase

If the system gets stuck during the kernel phase, y'all experience multiple symptoms or receive multiple error messages. These include, just are not express to, the following:

  • A Stop error appears afterward the splash screen (Windows Logo screen).

  • Specific fault code is displayed.

    For example, "0x00000C2" , "0x0000007B" , "inaccessible boot device" and so on.

    • Avant-garde troubleshooting for Stop error 7B or Inaccessible_Boot_Device
    • Advanced troubleshooting for Event ID 41 "The system has rebooted without cleanly shutting down start"

  • The screen is stuck at the "spinning wheel" (rolling dots) "system decorated" icon.

  • A blackness screen appears after the splash screen.

To troubleshoot these problems, try the post-obit recovery kicking options one at a time.

Scenario 1: Endeavor to get-go the computer in Rubber mode or Last Known Good Configuration

On the Advanced Kick Options screen, try to beginning the computer in Condom Mode or Safe Fashion with Networking. If either of these options works, use Event Viewer to help identify and diagnose the cause of the boot problem. To view events that are recorded in the event logs, follow these steps:

  1. Use 1 of the following methods to open up Event Viewer:

    • Click Start, point to Administrative Tools, so click Outcome Viewer.

    • Kickoff the Result Viewer snap-in in Microsoft Management Panel (MMC).

  2. In the console tree, expand Event Viewer, and then click the log that you desire to view. For example, click System log or Application log.

  3. In the details pane, double-click the event that you desire to view.

  4. On the Edit bill of fare, click Copy, open a new document in the programme in which you want to paste the event (for example, Microsoft Word), then click Paste.

  5. Use the Up Arrow or Down Arrow key to view the clarification of the previous or next upshot.

Make clean kick

To troubleshoot problems that touch services, do a clean kicking past using System Configuration (msconfig). Select Selective startup to test the services one at a fourth dimension to decide which 1 is causing the trouble. If you cannot find the cause, try including system services. However, in most cases, the problematic service is third-party.

Disable any service that you detect to be faulty, and try to commencement the computer once again by selecting Normal startup.

For detailed instructions, run into How to perform a make clean kicking in Windows.

If the reckoner starts in Disable Driver Signature mode, first the computer in Disable Commuter Signature Enforcement mode, and and so follow the steps that are documented in the post-obit article to make up one's mind which drivers or files require driver signature enforcement: Troubleshooting kicking problem caused by missing commuter signature (x64)

Note

If the estimator is a domain controller, try Directory Services Restore mode (DSRM).

This method is an important step if you see Stop mistake "0xC00002E1" or "0xC00002E2"

Examples

Warning

Serious problems might occur if you lot modify the registry incorrectly by using Registry Editor or by using another method. These issues might require that you reinstall the operating arrangement. Microsoft cannot guarantee that these issues can be solved. Modify the registry at your ain hazard.

Mistake code INACCESSIBLE_BOOT_DEVICE (STOP 0x7B)

To troubleshoot this End error, follow these steps to filter the drivers:

  1. Go to Windows Recovery Environment (WinRE) by putting an ISO disk of the organization in the disk drive. The ISO should be of aforementioned version of Windows or a later on version.

  2. Open up the registry.

  3. Load the system hive, and proper noun it every bit "test."

  4. Nether the following registry subkey, check for lower filter and upper filter items for Not-Microsoft Drivers:

    HKEY_LOCAL_MACHINE\Organisation\ControlSet001\Command\Class

  5. For each third-party commuter that you locate, click the upper or lower filter, and and so delete the value data.

  6. Search through the whole registry for similar items. Process as an appropriate, so unload the registry hive.

  7. Restart the server in Normal mode.

For additional troubleshooting steps, see the post-obit articles:

  • Advanced troubleshooting for Finish error 7B or Inaccessible_Boot_Device

To fix problems that occur afterward you install Windows updates, check for pending updates by using these steps:

  1. Open a Command Prompt window in WinRE.

  2. Run the command:

                      DISM /epitome:C:\ /become-packages

  3. If there are any pending updates, uninstall them by running the post-obit commands:

                      DISM /paradigm:C:\ /remove-packet /packagename: name of the bundle                                  
                      DISM /Image:C:\ /Cleanup-Prototype /RevertPendingActions

    Try to start the computer.

If the computer does not kickoff, follow these steps:

  1. Open up A Command Prompt window in WinRE, and start a text editor, such as Notepad.

  2. Navigate to the system drive, and search for windows\winsxs\pending.xml.

  3. If the Pending.xml file is found, rename the file every bit Pending.xml.erstwhile.

  4. Open the registry, and so load the component hive in HKEY_LOCAL_MACHINE as a examination.

  5. Highlight the loaded examination hive, and then search for the pendingxmlidentifier value.

  6. If the pendingxmlidentifier value exists, delete the value.

  7. Unload the test hive.

  8. Load the arrangement hive, proper name it every bit "examination".

  9. Navigate to the following subkey:

    HKEY_LOCAL_MACHINE\Organization\ControlSet001\Services\TrustedInstaller

  10. Change the Kickoff value from i to four

  11. Unload the hive.

  12. Try to start the computer.

If the Stop mistake occurs late in the startup process, or if the Finish error is still existence generated, you tin can capture a retentivity dump. A good memory dump can assistance decide the root cause of the Terminate error. For details, run into the post-obit articles:

  • Generate a kernel or consummate crash dump

For more information about page file problems in Windows ten or Windows Server 2016, see the following:

  • Introduction to page files

For more information about End errors, see the post-obit Knowledge Base article:

  • Avant-garde troubleshooting for Stop error or blue screen mistake issue

If the dump file shows an error that is related to a commuter (for example, windows\system32\drivers\stcvsm.sys is missing or corrupted), follow these guidelines:

  • Check the functionality that is provided past the driver. If the commuter is a third-party boot driver, make certain that yous sympathise what it does.

  • If the driver is non important and has no dependencies, load the organisation hive, and then disable the commuter.

  • If the end mistake indicates organisation file corruption, run the system file checker in offline mode.

    • To practice this, open WinRE, open up a command prompt, and then run the following command:

                            SFC /Scannow /OffBootDir=C:\ /OffWinDir=C:\Windows

      For more information, see Using Organisation File Checker (SFC) To Fix Problems

    • If in that location is disk corruption, run the check disk command:

                            chkdsk /f /r

    • If the Finish error indicates general registry corruption, or if you believe that new drivers or services were installed, follow these steps:

      1. Kickoff WinRE, and open a Control Prompt window.
      2. Offset a text editor, such as Notepad.
      3. Navigate to C:\Windows\System32\Config.
      4. Rename the all five hives by appending ".quondam" to the proper name.
      5. Copy all the hives from the Regback binder, paste them in the Config folder, and then try to start the calculator in Normal mode.

Annotation

Starting in Windows 10, version 1803, Windows no longer automatically backs up the organisation registry to the RegBack folder.This change is by blueprint, and is intended to help reduce the overall disk footprint size of Windows. To recover a system with a corrupt registry hive, Microsoft recommends that you lot utilise a organisation restore point. For more details, check this article.