1] PreBoot: POST or Power-On Self-Test loads firmware settings. It checks for a valid disk system, and if the system is good to go for the next phase. If the computer has a valid MBR, i.e., Master Boot Record, the boot process moves further and loads Windows Boot Manager.

2] Windows Boot Manager: This step determines if you have multiple OS installed on your computer. If yes, then it offers a menu with the names of the OSs. When you select the OS, it will load the right program, i.e., Winload.exe to boot you into the correct OS.

3] Windows OS Loader: Like its name, WinLoad.exe loads important drivers to kick start the Windows Kernel. The kernel uses the drivers to talk to the hardware and do rest of the things required for the boot process to continue.

4] Windows NT OS Kernel: This is the last stage that picks up the Registry settings, additional drivers, etc. Once that has been read, the control is taken by the system manager process. It loads up the UI, the rest of the hardware and software. That’s when you finally get to see your Windows 10 Login screen.

When you run Windows 10 on a computer that supports Unified Extensible Firmware Interface (UEFI), Trusted Boot protects your computer from the moment you power it on. When the computer starts, it first finds the operating system bootloader. Computers without Secured Boot simply run whatever bootloader is on the PC’s hard drive. When a computer equipped with UEFI starts, it first verifies that the firmware is digitally signed. If Secure Boot is enabled, the firmware examines the bootloader’s digital signature to verify that it is intact hasn’t been modified. You can read more on how to secure the Windows 10 Boot Process.

Do remember that lot of things happen even after you log in, but that’s all post-boot process scenarios. Do note that there is much more to Windows 10 Boot process than we explained here – we only explained the basics!

Windows 10 — Boot Process

What is the Detailed Phases, Steps and sub-steps of the Windows 10 Boot Process ?

«http://blogs.msdn.com/b/b8/archive/2011/09/22/protecting-the-pre-os-environment-with-uefi.aspx» is an old article from 2011, that is similar to what I’m looking for.

Gives a general Idea, but how does Windows 10 compare to Windows 7,8,8.1?

I’m specifically looking at a traditional Desktop computer for best comparison.

From what I can tell, several of the boot decisions are made at the UEFI level, well before the kernel loads (ntoskrnl.exe in previous versions) And the boot process decision is no longer at the registry, it’s at an earlier phase (Secure boot.). Looking for details/info on these types of things.

Replies (4) 

Thank you for posting in Microsoft Community.

As the your post you have already accumulated articles on the comparison of different boot processes and have come to an conclusion, for which we at Microsoft Community appreciate you for your interest.

Certainly, we would be mainly focusing in provided/assisting any kind of help with Windows 10.

Thanks and Regards

1 person found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

3 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Mr. Ahmed (And Microsoft Community),

Sir, so what is the detailed boot process, what stages and files specifically are used?

Every Version of Windows has had changes to the boot process. Is there an article or read that spells out stage by stage, and file by file, of the traditional «normal» boot process for Windows 10? I know that we have several versions of windows 10 (Including the IoT version.) so can I read about the other boot sequence options if they are different?

It’s safe to assume, I hope, that Windows 10 it has:
POST stage -> Boot Loader/UEFI stage/TPM stage -> Kernel loading -> Windows Login -> Post Login stage. .

If you have a useful link please reply. (This is probably already solved by now.)

5 people found this reply helpful

Was this reply helpful?

Sorry this didn’t help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

Boot Process: A lot more then what you thought

The boot process is something that happens every time you turn your computer on. You don’t really see it, because it happens so fast. You press the power button come back a few minutes later and Windows XP, or Windows Vista, or whatever Operating System you use is all loaded.

However, what really happens when you press the power button and turn your computer on? This process is called the boot process and this article will help you understand the process of turning on your computer. The following is a list of what typically happens in a pc, but it will differ depending on your bios and manufacturer.

The first step your computer does when you press the power button, is to turn the Computer Power Supply on. Once a ‘Power Good’ signal is sent to the motherboard, the CPU then (understanding that the power supply is stable) looks for the ROM bios.

The CPU looks to the ROM bios for the first instruction, and the first instruction is to run the POST (Power-On-Self-Test).

The POST first checks the bios and then tests the CMOS RAM. If there is no problems with this then POST continues to check the CPU, hardware devices such as the Video Card, the secondary storage devices such as the Hard Drive, Floppy Drives, Zip Drive or CD/DVD Drives.

If there are any errors found then an error message is displayed on screen or a number of beeps are heard. These beeps are known as POST beep codes. The reason the computer sometimes uses beep codes instead of displaying an error message is because the video card has not yet been initiated or there may be an error with the card.

Next the bios finds the video card and runs the video card’s bios. This usually is the first thing that modern machines display on the screen. After that the computer looks at the other devices and runs their bios’ if they have one.

The bios then displays the system configuration.

During the display more tests are conducted including the test that shows your computer testing the memory. If there are any problems found from now on they will be displayed in a text message on the screen.

After that the bios searches for something that it can boot from. This can be set in the CMOS under boot sequence. It can be set to the A: Drive (Floppy) C: (Hard Drive, Primary Partition) D: (CD/DVD Drive) or others such as the USB drive or network card (depending on the bios).

Once the target boot device has been selected the bios will search for the Master Boot Record (MBR). If it is searching for a hard drive it looks at cylinder 0, head 0, sector 1.

Once a valid volume boot sector is found the bios has done its job and hands over control to the Operating System that completes the booting process. It will also conduct a few hardware tests.

If no valid boot record is found the computer will display an error such as the following:

Non-System Disk or disk error

Replace and press any key when ready

If a valid boot record is found but it cannot read the Master Boot Record then the computer will display a message such as:

Disk boot failure, insert system disk and press enter

This concludes this article on the boot process that happens to your computer when you press that power button. Were you surprised at how much work the computer has to do when it starts? It surprised me when I first heard about it.

Boot and UEFI

NoteВ В Some information in this section may apply only to WindowsВ 10 Mobile and certain processor architectures.

A device running WindowsВ 10 has several requirements for booting into the OS. After the device’s firmware initializes all the hardware, the device needs to ensure that there is enough power to boot. Afterwards, the device needs to ensure that the device is booting into the appropriate OS depending on if the user wants to perform an update or a restore on the device, or if the user wants to boot the device into the main OS.

To accommodate each of these scenarios, the WindowsВ 10 boot process uses the following components:

Firmware boot loaders provided by the SoC vendor.

UEFI (Unified Extensible Firmware Interface) environment provided by the SoC vendor.

Windows Boot Manager provided by Microsoft.

This topic provides an overview of the boot process, and it describes the SoC firmware boot loaders, UEFI, and Windows Boot Manager in more detail.

Overview of the boot process

When a WindowsВ 10 device is turned on, it goes through the following high-level process:

The device is powered on and runs the SoC-specific firmware boot loaders, which initialize the hardware on the device and provide emergency flashing functionality.

The firmware boot loaders boot the UEFI environment and hands over control to UEFI applications written by the SoC vendor, Microsoft, and OEMs. These applications can utilize UEFI drivers and services.

The UEFI environment launches the Windows Boot Manager, which determines whether to boot to FFU flashing or device reset mode, to the update OS, or to the main OS.

The following diagram illustrates this process at a high level.

Following are additional details about some of the components in this diagram:

The update OS is a minimal OS environment provided by Microsoft. This OS is used specifically for installing updates.

FFU flashing mode refers to a UEFI application that flashes an OS image to device storage. Microsoft provides a UEFI flashing application which can be used in non-manufacturing scenarios. OEMs can also implement their own UEFI flashing application.

SoC firmware boot loaders

The SoC firmware boot loaders initialize the minimal set of hardware required for the device to run. The SoC firmware boot loaders are designed to finish as fast as possible, and nothing is drawn to the screen while they are running. After the SoC firmware boot loaders finish, the device is booted into the UEFI environment.

The SoC firmware boot loaders also contain an emergency flashing capability that allows devices to be flashed when the boot environment is not stable and FFU-based flashing using the Microsoft-provided flashing tool is not possible. Emergency flashing requires tools specific to the SoC. For more information, contact the SoC vendor.

WindowsВ 10 utilizes the Unified Extensible Firmware Interface (UEFI) to support the handoff of system control from the SoC firmware boot loader to the OS. The UEFI environment is a minimal boot OS upon which devices are booted and the WindowsВ 10 OS runs. For more information, see UEFI in Windows.

Understanding the Windows Boot Manager

The Windows Boot Manager is a Microsoft-provided UEFI application that sets up the boot environment. Inside the boot environment, individual boot applications started by the Boot Manager provide functionality for all customer-facing scenarios before the device boots.

ImportantВ В All components inside the boot environment are provided by Microsoft and cannot be modified, replaced, or omitted by OEMs.

Boot applications implement functionality for the following scenarios:

Charging the device battery before boot.

Capturing and saving offline crash dumps (developer builds only).

Flashing the device with a new image.

Resetting the device.

Updating the device.

Booting the device to the main OS.

The following diagram illustrates some of the key portions of the process that the Boot Manager follows after it is launched by the UEFI environment.

The following steps describe this process in more detail:

After the UEFI environment launches the Boot Manager, the Boot Manager initializes boot libraries, reads the boot configuration database to determine which boot applications to run and in which order to run them. The Boot Manager launches boot applications sequentially, and each application exits back to the Boot Manager after finishing.

Boot libraries are libraries of functions that extend upon existing UEFI functionality, and are designed to be used within the boot environment. Only boot applications, which are launched by the Boot Manager, have access to the boot libraries.

The Boot Manager first captures any reserved hardware button combinations that are pressed by the user.

In non-retail OS images, the Boot Manager next runs an offline crash dump boot application which allows the device to capture a snapshot of physical memory from the previous OS session. When the device resets abnormally, the previous OS session’s memory is preserved across the reset. When this happens, the offline crash dump application will save that memory and turn it into an offline crash dump file, which can be transferred off the device and analyzed. If the device did not reset abnormally in the previous OS session, the offline crash dump application exits immediately.

Вам также может понравиться

Windows или Linux: Что лучше выбрать?

Есть много причин выбирать между Windows и Linux, но

Файл владелец изменить linux

Команда Chown в Linux Chown Command in Linux (File

Установка шлюза по умолчанию linux

Настройка сети вручную Содержание Краткое описание

Чем разбить диск для linux

ИТ База знаний Курс по Asterisk Полезно — Узнать IP —