Understanding the Windows Boot Process and Boot Configuration
A+ Core 2 · Software Troubleshooting · By Super Admin
Comprehensive guide to the Windows boot process from UEFI/BIOS initialization through kernel loading and user login for troubleshooting boot failures.
BIOS and UEFI Boot Initialization
With the introduction of Windows Vista, the boot process changed from prior operating systems of Windows XP, 2000, and NT 4.0. The current boot process introduced with Windows Vista allows for the adoption of UEFI firmware and continues through Windows 11. In order to troubleshoot a failure to boot, you need to understand the complete boot process, starting with either the BIOS or the UEFI.
Legacy BIOS systems perform a power-on self-test (POST), and then the BIOS bootstrap routine looks at the master boot record (MBR) at the beginning of the disk. The MBR then reads the boot sector on the first primary partition found. This boot sector then instructs the Boot Manager to load. UEFI firmware will perform a similar POST, then the UEFI bootstrap begins by loading drivers for the hardware.
One of the differences is that UEFI can contain drivers that allow it to boot across a network or other nonstandard devices. Just like the legacy BIOS, the UEFI firmware looks at the MBR in the GUID Partition Table (GPT). The GPT defines a globally unique identifier (GUID) that points to a partition containing the Boot Manager. Therefore, UEFI firmware requires a partitioning scheme of GPT and cannot use the standard MBR partitioning scheme.
Critical Boot Files and Their Functions
After control is handed over to the software, several files are used to complete the operating system bootup. The Windows Boot Manager (BOOTMGR) bootstraps the system and starts the loading of an operating system on the computer. The Boot Configuration Data (BCD) holds information about operating systems installed on the computer, such as the location of the operating system files.
The program winload.efi is used to boot Windows and loads the operating system kernel (ntoskrnl.exe). If the system is not starting fresh but resuming a previous session, then winresume.exe is called by BOOTMGR. The Windows OS kernel is the heart of the operating system and is responsible for allowing applications shared access to the hardware through drivers.
The Windows boot log stores a log of boot-time events in ntbtlog.txt, but it is not enabled by default. In addition to the previously listed files, Windows needs a number of files from its system folders (e.g., SYSTEM and SYSTEM32), such as the hardware abstraction layer (hal.dll), the Session Manager (smss.exe), the user session (winlogon.exe), and the security subsystem (lsass.exe).
Complete Boot Sequence Steps
The complete Windows boot process begins with Power On, where the system self-checks and enumerates hardware resources through the POST. After the POST, the UEFI firmware continues to initialize the rest of the hardware components, setting up the CPU, initializing the memory, and detecting connected storage devices. The UEFI firmware also prepares the system environment for the operating system to take over.
Once the hardware initialization is complete, the UEFI firmware hands control over to the Windows Boot Manager (BOOTMGR). The Boot Manager is responsible for managing the boot process and determining which operating system to load, especially if you have multiple operating systems installed. BOOTMGR reads the boot configuration data (BCD) to get a list of boot options for the next step.
The Boot Manager then loads the Windows Boot Loader (winload.efi) from the EFI system partition. The Boot Loader is responsible for loading the Windows kernel and essential drivers needed to start the operating system. If Windows is returning from a hibernated (suspended) state, winresume.exe is responsible for reading the hiberfil.sys file into memory and passes control to the kernel after this file is loaded.
Kernel Initialization and User Login
The Windows Boot Loader initializes the Windows kernel (ntoskrnl.exe), which is the core of the operating system. The kernel is responsible for managing system resources, such as memory, processes, and hardware interactions. This switches the system from real mode to protected mode and enables paging. Protected mode enables the system to address all the available physical memory.
The Windows kernel loads the executive subsystems, which are software components required for the operating system to communicate with the hardware. One of the subsystems is the HAL, which provides a consistent interface for the operating system to interact with the hardware, ensuring compatibility across different hardware platforms. The kernel loads the Session Manager, and the Session Manager (smss.exe) is then started, which initializes system sessions and loads the Registry.
Winlogon.exe loads, and at this point, you are presented with the login screen. After you enter a username and password, you're taken to the Windows desktop. Finally, the Windows Explorer (explorer.exe) process starts, providing the graphical user interface (GUI) for Windows 11. This includes the desktop, taskbar, and Start menu, allowing you to interact with the operating system and launch applications.
Discussion (0)
No discussion on this article yet — be the first to comment.
Please sign in to join the discussion.