Windows Startup & Boot problems - Advanced Troubleshooting

Are you an IT admin and need to troubleshoot Windows kicking problems? If the answer is yes, and so in this guide, we will share advanced troubleshooting for Windows ten startup and boot problems. Earlier you begin, we recommend you check out our following postal service:

• Windows 11/10 PC will non boot upward or start

If the basic troubleshooting there does not assistance you, read on!

Windows 11/10 Startup & Kicking problems

Boot Phases of a Windows computer

When you push the power button, the kicking process goes through many phases. Before we go ahead and troubleshoot the issues which occur during the stages, let's first get to know about them, and what happens during the process.

Phase	Boot Procedure	BIOS	UEFI
one	PreBoot	MBR/PBR (Bootstrap Lawmaking)	UEFI Firmware
2	Windows Boot Manager	%SystemDrive%\bootmgr	\EFI\Microsoft\Boot\bootmgfw.efi
iii	Windows OS Loader	%SystemRoot%\system32\winload.exe	%SystemRoot%\system32\winload.efi
four	Windows NT Bone Kernel	%SystemRoot%\system32\ntoskrnl.exe

1]  PreBoot

When y'all hit the power push, the computer firmware starts Mail or Power-On Cocky test and loads firmware settings. It checks if there is a valid disk system to start the next phase. It'due south indicated by an MBR or principal boot tape. The PreBoot process then starts the Windows Boot Director.

two] Windows Boot Manager

The chore of Windows Boot Manager is unproblematic. It loads another plan -Windows Loader, popularly known as Winload.exe. Its located on the Windows Kicking partition.

While it may seem to be a redundant process, the primary reason it exists is to assist you lot boot into the right OS. When you have multiple Bone installed on the aforementioned reckoner, it makes sure to load the right Winload.exe.

3] Windows OS Loader

Windows OS Loader now loads essential drivers to start the Windows kernel. The Kerner finally does the rest of the affair to give you an OS where you lot can piece of work.

4] Windows NT OS Kernel

In the last phase, Windows NT Bone Kernel picks up the organisation Registry hive, and additional drivers mark in the BOOT_START list. Then the control is passed on to the session manager process (Smss.exe). The System Manager in turn initializes the system session and loads up the rest of the hardware and software needed.

Advanced troubleshooting for Windows boot problems

If you are yet wondering why so many phases, then my all-time gauge is that it's intentional. Imagine if it were simply one program, it would have been almost impossible to figure out where exactly the trouble occurred. Let'due south finally start with the troubleshooting.

1] The Computer repeatedly boots to the recovery way

When yous turn on the computer, and it boots into the recovery option every time, we will accept to employ the Bcdedit programme to suspension the loop.

• Click on Troubleshooting > Command Prompt
• Blazon Bcdedit /ready {default} recoveryenabled no and hitting Enter.

If the F8 options (Windows Prophylactic Mode) don't work, set the Rubber Mode to work in legacy mode. Utilise the following controlBcdedit /set {default} bootmenupolicy legacy

ii] Windows stuck with a blank monitor with no activity

BIOS phase is where the system goes from PreBoot to Loading Windows OS. Information technology's just marked as consummate when there is no hardware issue in the organization. So to bank check if it is a hardware consequence:

• Remove external hardware and kick again.
• Check if your hard drive is working. If information technology'southward too silent or there is no blinking LED, it'due south probably dead.
• If you cannot bank check that, press the Num Lock or Caps Lock to check if the indicator light toggles on and off.

3] Windows stuck at a blank monitor with a blinking cursor or an fault message

When you get to run across just a glimmer of an error message, then there is a trouble with the Kick loader phase. The mistake bulletin can include abuse of BCD/MBR boot sector/Bootmgr or missing OS or not being able to boot due to system hive missing or corrupted.

Startup Repair tool

This tool is available under the Advanced Options of Windows Recovery selection. Information technology can diagnose the logs, and fix complex startup problems automatically which does non let the computer boot properly.

1. Create an installation media of the same version of Os installed on the computer.
2. When you attain the Install Windows screen, click on Repair your figurer link.
3. Shutdown after the repair is complete.
4. Next, turn on your PC to see if Windows can kicking properly.

To analyze further, you can have a look at the log generated by the Startup Repair tool. It is located at%windir%\System32\LogFiles\Srt\Srttrail.txt

Repair Kick Codes

If you are stuck with the MBR boot sector error bulletin, run the following in the Command Prompt. You tin can open information technology from Advanced Options of Recovery.

• To repair boot codes, run the following command – BOOTREC /FIXMBR
• To restore the kicking sector, run the following command – BOOTREC /FIXBOOT

BOOTREC can simply fix the Master Boot Record. If there is a trouble with the partitioning table, information technology will non help.

Ready BCD errors

If you lot received BCD-related error, you demand to use the Bootrec command to fix the issue.

1. Execute the Bootrec /ScanOS control to scan for all the existing systems installed on the figurer.
2. Restart, and check if the problem is at that place no more than. If no, then execute with rebuild option, i.e.Bootrec /rebuildbcd

If you receive an output that says Total identified Windows installations: 0,run the post-obit commands:

          bcdedit /consign c:\bcdbackup  attrib c:\\boot\\bcd -h -r –s  ren c:\\boot\\bcd bcd.old  bootrec /rebuildbcd                  

One time the execution is consummate, you lot should receive a success message as Total identified Windows installations: i{D}:\Windows.It will and so enquire "Add together installation to kicking list? Yes/No/All",Enter Y. Reboot and encounter if this Windows boot problems tip resolved the problem.

Supplant Bootmgr

If the above solutions didn't fix the problem, it'south time to replace the Bootmgr file from bulldoze C to the Organisation Reserved sectionalization. To do this, follow these steps:

1. Get to the Command Prompt via Advanced Options.
2. Change the directory to the System Reserved partition and run attrib control attrib-s -h -r.
3. Practice the aforementioned in the organization drive, i.e., where Windows is installed.
4. Rename the Bootmgr file as Bootmgr.old with ren c:\\bootmgr bootmgr.quondam
5. Copy the Bootmgr.Old file to the Organisation Reserved partition.
6. Rename it back to bootmgr.
7. Restart the reckoner.

Restore System Hive

When you receive an error where it says that Windows cannot load the arrangement registry hive into memory, then you must restore it from an alternate backup location.

You can either use the advanced startup or Emergency Repair Disk (ERD) to copy the files from the C:\Windows\System32\config\RegBack to C:\Windows\System32\config. It volition almost, reset the registry to a different fourth dimension where everything was working fine.

4] Mistake during Kernel Phase

Receiving errors at this phase tin exist exhaustive. We already take covered a lot of scenarios in item. Here are a few to get you lot started:

• A Stop mistake appears after the Windows logo splash screen.
• A specific fault lawmaking is displayed.
• The screen is stuck at the spinning wheel or dots
• A black screen appears afterwards the splash screen.

Let us know if this helped you to resolve Windows boot issues.

Source: https://www.thewindowsclub.com/windows-10-startup-boot-problems

Posted by: hunteredwasind.blogspot.com

Share this post