Windows 11 will not boot: choose the next recovery step

1. Record where Windows stops

Photograph the complete error message or stop code. Note:

• the last screen that appears each time;
• whether the PC restarts by itself;
• whether the problem began after an update, driver, power failure or other change;
• whether the failure is identical each time.

Check in UEFI that the SSD is detected consistently. If it disappears, stop Windows repair and protect the data first.

2. Open Windows Recovery Environment

WinRE often opens automatically after several failed boots. You can also boot from official Windows installation media and choose Repair your computer.

Open Troubleshoot → Advanced options.

3. Check BitLocker

BitLocker encrypts the Windows volume. Open the recovery command prompt and check its status before making changes:

manage-bde -status

Expected: you can see which volumes are encrypted and whether the Windows volume is unlocked.

4. Run Startup Repair once

Choose Startup Repair and allow it to complete.

• If Windows starts afterwards, test another restart.
• If exactly the same failure returns, record the result and continue.
• Do not repeat the same failed automatic repair indefinitely.

5. If the problem began after an update, remove the latest quality update

Choose Uninstall Updates → Uninstall latest quality update.

Allow it to finish and restart. Record a changed stop code or later failure point as well.

If the graphical route fails, or the update itself may not have completed, continue with:

Remove a Windows update through WinRE or Windows PE →

6. Use System Restore if a suitable restore point exists

System Restore keeps personal files but can roll back recent applications, drivers, settings and updates.

Review which applications and drivers the restore point affects before confirming.

7. Test Safe Mode

Open Startup Settings, restart and choose Safe Mode.

Windows works in Safe Mode

Back up data first. Then investigate recent drivers, software and security products.

Safe Mode crashes at the same point

Continue with Windows components, early drivers, updates, storage and other hardware.

8. Check the SSD before heavier repair

Watch for:

• volumes that disappear;
• I/O or read errors;
• extremely slow simple reads;
• an SSD that is not detected consistently in UEFI.

Do not automatically run chkdsk /r on a drive that may be physically failing.

9. Identify the offline Windows volume

Offline repair works on the installed copy of Windows while it is not running. Drive letters can change in WinRE and Windows PE, environments used for this work.

diskpart
list volume
exit
dir C:\Windows
dir D:\Windows
dir E:\Windows

Confirm that Windows, Program Files and Users are all present on the chosen volume.

10. Use the result to choose further repair

Choose the route supported by the error, update history and checks so far.

Check Windows components or system files

DISM checks the Windows component store used for repairs; SFC checks protected system files against it. Use this route to investigate damage to those parts of the installation.

Repair Windows offline with DISM and SFC →

Roll back a recent update

If an update completed and the failure began afterwards, check the supported removal options.

Remove a Windows update through WinRE or Windows PE →

Complete an interrupted update

Use this route when logs and package status show that installation did not finish and rollback does not restore a working previous state. The package must match the installed Windows version exactly.

Install a Windows update offline with DISM →

Repair Windows Boot Manager, EFI or BCD

Choose this when Windows Boot Manager is missing or boot configuration is demonstrably wrong. Rebuilding it is not the starting point for a crash after Windows has begun loading.

Repair EFI and BCD with BCDBoot →

Investigate stop code 0xC000021A

This code means a critical Windows process stopped; it does not name the underlying cause.

Investigate 0xC000021A in Windows 11 →

Do not do these blindly

• do not download loose Windows DLLs from random sites;
• do not format the EFI partition as a routine fix;
• do not delete pending.xml, complete update caches or registry values without understanding the state;
• do not change several drivers, packages and boot settings at once;
• do not force an update package that DISM reports as not applicable.

Keep logs and preferably change one thing at a time, so you can tell which action changed the failure.

Need help? Contact Forcys →