Troubleshooting playbook · Reviewed 2026-10-23
Windows startup recovery playbook
A low-risk decision path for Windows that will not start, loops into recovery, or reaches a blank sign-in path.
When to use this
Use this when Windows cannot reach a stable desktop. It prioritizes preserving data and identifying the failure boundary before reset or reinstall.
Protect data and access first
- Do not reset or reinstall before checking whether BitLocker recovery is required.
- Avoid repeated forced shutdowns when storage errors or a recent firmware change may be involved.
Before you change anything
- Keep the device on AC power.
- Photograph any exact stop code or recovery message.
- Have the BitLocker recovery key available if device encryption is enabled.
Decision path
Identify the last stable point
Note whether Windows reaches the sign-in screen, Safe Mode, or only Windows Recovery Environment.
Check: You can name the last point where normal startup worked.
Remove only new external variables
Disconnect nonessential USB devices and recent docks; leave keyboard, display and power connected.
Check: The symptom is tested once with a minimal peripheral set.
Use Startup Repair once
From Windows Recovery, run Startup Repair and record its result rather than repeating it several times.
Check: Windows either reaches a stable desktop or returns a specific repair result.
Choose the next branch
Use Safe Mode for a driver or startup-app change; use the linked stop-code guide for a BSOD; investigate disk health before reset.
Check: The next action matches observed evidence, not a guess.
Stop and escalate when
- A BitLocker key is requested but unavailable.
- The drive is not detected in firmware or recovery.
- The device powers off, smells hot, or shows physical damage.