How do I fix Windows 10 startup problems?
Skip to main content This browser is no longer supported. Show
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Advanced troubleshooting for Windows boot problems
In this articleTry our Virtual Agent - It can help you quickly identify and fix common Windows boot issues. Note This article is intended for use by support agents and IT professionals. If you're looking for more general information about recovery options, see Recovery options in Windows 10. Applies to: Windows 10 SummaryThere are several reasons why a Windows-based computer may have problems during startup. To troubleshoot boot problems, first determine in which of the following phases the computer gets stuck:
Here's a summary of the boot sequence, what will be seen on the display, and typical boot problems at that point in the sequence. Before you start troubleshooting, you have to understand the outline of the boot process and display status to ensure that the issue is properly identified at the beginning of the engagement. Select the thumbnail to view it larger.
Each phase has a different approach to troubleshooting. This article provides troubleshooting techniques for problems that occur during the first three phases. Note If the computer repeatedly boots to the recovery options, run the following command at a command prompt to break the cycle:
If the F8 options don't work, run the following command:
BIOS phaseTo determine whether the system has passed the BIOS phase, follow these steps:
Boot loader phaseIf the screen is black except for a blinking cursor, or if you receive one of the following error codes, this status indicates that the boot process is stuck in the Boot Loader phase:
To troubleshoot this problem, use Windows installation media to start the computer, press Shift+F10 for a command prompt, and then use any of the following methods. Method 1: Startup repair toolThe Startup Repair tool automatically fixes many common problems. The tool also lets you quickly diagnose and repair more complex startup problems. When the computer detects a startup problem, the computer 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 problem. When the Startup Repair tool determines the cause, the tool tries to fix the problem automatically. To do this task of invoking the Startup Repair tool, follow these steps.
The Startup Repair tool generates a log file to help you understand the startup problems and the repairs that were made. You can find the log file in the following location: %windir%\System32\LogFiles\Srt\Srttrail.txt For more information, see Troubleshoot blue screen errors. Method 2: Repair boot codesTo repair boot codes, run the following command:
To repair the boot sector, run the following command:
Note Running Method 3: Fix BCD errorsIf you receive BCD-related errors, follow these steps:
Method 4: Replace BootmgrIf methods 1, 2 and 3 don't fix the problem, replace the Bootmgr file from drive C to the System Reserved partition. To do this replacement, follow these steps:
Method 5: Restore system hiveIf Windows can't load the system registry hive into memory, you must restore the system hive. To do this step, use the Windows Recovery Environment or use the Emergency Repair Disk (ERD) to copy the files from the C:\Windows\System32\config\RegBack directory to C:\Windows\System32\config. If the problem persists, you may want to restore the system state backup to an alternative location, and then retrieve the registry hives to be replaced. Kernel phaseIf the system gets stuck during the kernel phase, you experience multiple symptoms or receive multiple error messages. These error messages include, but aren't limited to, the following examples:
To troubleshoot these problems, try the following recovery boot options one at a time. Scenario 1: Try to start the computer in Safe mode or Last Known Good ConfigurationOn the Advanced Boot Options screen, try to start the computer in Safe Mode or Safe Mode 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:
Clean bootTo troubleshoot problems that affect services, do a clean boot by using System Configuration ( Disable any service that you find to be faulty, and try to start the computer again by selecting Normal startup. For detailed instructions, see How to perform a clean boot in Windows. If the computer starts in Disable Driver Signature mode, start the computer in Disable Driver Signature Enforcement mode, and then follow the steps that are documented in the following article to determine which drivers or files require driver signature enforcement: Troubleshooting boot problem caused by missing driver signature (x64) Note If the computer is a domain controller, try Directory Services Restore mode (DSRM). This method is an important step if you encounter Stop error "0xC00002E1" or "0xC00002E2" ExamplesWarning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall the operating system. Microsoft can't guarantee that these problems can be solved. Modify the registry at your own risk.
To troubleshoot this Stop error, follow these steps to filter the drivers:
For more troubleshooting steps, see Advanced troubleshooting for Stop error 7B or Inaccessible_Boot_Device. To fix problems that occur after you install Windows updates, check for pending updates by using these steps:
If the computer doesn't start, follow these steps:
If the Stop error occurs late in the startup process, or if the Stop error is still being generated, you can capture a memory dump. A good memory dump can help determine the root cause of the Stop error. For more information, see Generate a kernel or complete crash dump. For more information about page file problems in Windows 10 or Windows Server 2016, see Introduction to page files. For more information about Stop errors, see Advanced troubleshooting for Stop error or blue screen error issue. Sometimes the dump file shows an error that's related to a driver. For example, windows\system32\drivers\stcvsm.sys is missing or corrupted. In this instance, follow these guidelines:
Additional resourcesAdditional resourcesIn this articleWhat are the 4 ways to fix Windows 10 startup?Four of the top approaches for solving Windows 10 boot problems are launching the Startup Repair tool, repairing the Master Boot Record (MBR), scanning the system for corrupt or missing files, and running the Deployment Image Servicing and Management (DISM) tool.
How to repair Windows 10 startup using command prompt?In the System Recovery Options dialog box, click Command Prompt. Type Bootrec.exe, and then press Enter.. bcdedit /export C:\BCD_Backup.. cd boot.. attrib bcd -s -h -r.. ren c:\boot\bcd bcd. old.. bootrec /RebuildBcd.. How to repair Windows 10 from BIOS?When using a USB drive, make sure to set up your BIOS to boot from the USB drive. After booting into setup, choose the Repair Computer option > Troubleshoot > Advanced Options > Command Prompt. If you are using a recovery drive, click Troubleshoot > Advanced Options > Command Prompt.
|