Boot & Startup Issues

Windows 11 Troubleshooting & Administration

Chapter 9 · Boot & Startup Issues

Chapter 4's own warn-box named this chapter directly as the destination for recovering from a bad Registry edit under HKLM\SYSTEM. GRUB & Multibooting 6 already covered Windows Boot Manager from GRUB's own side, including a real, well-documented gotcha this chapter closes the loop on from the Windows side.

Windows Boot Manager & the BCD Store

Windows's own first-stage bootloader is bootmgr, reading configuration from the Boot Configuration Data (BCD) store — the modern replacement for the old boot.ini file. GRUB & Multibooting 6 covered exactly how this coexists with GRUB in a dual-boot setup: either GRUB becomes the primary bootloader and chainloads to Windows Boot Manager, or Windows Boot Manager itself is configured to chainload to GRUB — the same chainloading mechanism that course covered generally, applied specifically to Windows's own bootloader here.

Closing the loop on GRUB & Multibooting 6's own gotcha

That chapter named "the classic Windows-Update-breaks-GRUB gotcha" directly — from the Windows side, this happens because a Windows feature update can overwrite the boot entry in the EFI System Partition, silently removing whatever chainload configuration previously handed control to GRUB. Windows isn't being deliberately hostile to a dual-boot setup; it's simply re-asserting its own boot entry as part of a normal update, with no awareness that a second bootloader's own entry existed at all.

WinRE — Windows Recovery Environment

WinRE launches automatically after three consecutive failed boot attempts, or can be reached deliberately via Shift+Restart from the sign-in screen or Start menu, or by booting from install media. Its Advanced options offer Startup Repair, System Restore, System Image Recovery, a Command Prompt, Uninstall Updates, and Startup Settings (the gateway to Safe Mode).

WinRE tool	Best for
Startup Repair	An automated first attempt — common boot-configuration problems, though not everything
System Restore	Reverting system files, installed programs, and Registry state to an earlier restore point — not personal files
Uninstall Updates	A recent quality or feature update specifically identified as the cause
Safe Mode (via Startup Settings)	Isolating whether a third-party driver or startup program, rather than core Windows, is responsible
Command Prompt	Manual intervention — running SFC/DISM (Chapter 7) or direct file operations when nothing automated works

Safe Mode — Minimal Drivers, Minimal Services

Safe Mode starts Windows with only the essential drivers and services running, deliberately excluding most third-party software. If a problem disappears in Safe Mode, that's real, useful evidence — pointing at a specific driver or startup program rather than a core Windows fault. Safe Mode with Networking adds network drivers for anything requiring internet access to fix; Safe Mode with Command Prompt boots directly to a command line instead of the desktop, for situations where the graphical shell itself is the problem.

System Restore — Chapter 4's Own Discipline, at Whole-System Scale

A restore point captures system files, installed programs, and Registry state at a specific moment — deliberately not personal files, which are unaffected by a restore. This is the exact same "capture a known-good state before risking a change" principle Chapter 4 taught for a single Registry key's own export, just applied at the scale of the entire system rather than one key.

Reading a BSOD

A modern Windows 11 Blue Screen shows a QR code (linking to Microsoft's own troubleshooting page for that specific error) and a Stop Code — a specific, named identifier like CRITICAL_PROCESS_DIED or DRIVER_IRQL_NOT_LESS_OR_EQUAL. This is the same pattern this course has already named twice: an Event ID (Chapter 2) and a Device Manager error Code (Chapter 7) are both specific, lookupable identifiers rather than vague free text — a Stop Code is the third instance of that same troubleshooting pattern, this time for the single most severe class of Windows failure.

Build a recovery drive before it's needed

Settings > System > Recovery offers "Create a recovery drive" — a bootable USB with WinRE's own tools, worth building in advance rather than discovering, mid-crisis, that the recovery partition on the affected machine is itself damaged or inaccessible.

Hands-On Exercises

Exercise 1

A dual-boot machine that previously showed a GRUB menu now boots straight into Windows with no GRUB option at all, right after a Windows feature update. Using this chapter's own warn-box and GRUB & Multibooting 6, explain what most likely happened.

📄 View solution

Exercise 2

A problem disappears entirely when booted into Safe Mode. Explain what this actually proves, and what it doesn't yet tell you about the specific cause.

📄 View solution

Exercise 3

Explain why a BSOD's Stop Code is described as the same kind of troubleshooting anchor as an Event ID or a Device Manager error code, rather than something entirely new to this chapter.

📄 View solution

Chapter 9 Quick Reference

Windows Boot Manager (bootmgr) + the BCD store — Windows's own first-stage bootloader, chainloading with GRUB per GRUB & Multibooting 6
A Windows feature update can silently overwrite the EFI boot entry, removing a GRUB chainload configuration — closing that course's own named gotcha
WinRE — Startup Repair, System Restore, Uninstall Updates, Safe Mode, Command Prompt
Safe Mode disappearing symptoms point at a driver/startup program, not core Windows — but doesn't identify which one alone
System Restore — Chapter 4's export-before-editing discipline, applied at whole-system scale, excluding personal files
A BSOD Stop Code is the same lookupable-identifier pattern as an Event ID (Ch.2) or Device Manager Code (Ch.7)
Next chapter: Capstone — Diagnosing a Real Multi-Symptom Windows Issue