Step 1 — Determine the Failure Type
Before touching any settings or tools, observe exactly what happens when you press the power button.Check for any power activity
Listen for POST beep codes
Note any on-screen error text
BOOTMGR is missing, Operating System not found, or Reboot and Select proper Boot device tell you the firmware found no bootable volume, which points to a different fix path than a splash-screen stall.Step 2 — Power Connection Checks
If the machine shows no signs of life, a loose cable or failed power supply is the most common culprit. Work through each check below before assuming motherboard or hardware failure.Verify the wall outlet and power strip
Inspect the power cable and adapter (laptops)
Reseat internal power connectors (desktops)
Perform a hard reset / drain residual charge
Test the power supply unit (desktops)
Step 3 — Boot Into Safe Mode
If the system reaches the Windows logo but fails before the login screen, Safe Mode loads only the minimum drivers needed to start Windows, helping you isolate whether a third-party driver or service is to blame.Access the Windows Recovery Environment (WinRE)
Navigate to Safe Mode
Evaluate the system in Safe Mode
msconfig to disable non-Microsoft startup services one group at a time.Step 4 — Run Startup Repair
Windows’ built-in Startup Repair automatically scans for and fixes common boot configuration problems.Enter Startup Repair
Allow the repair to complete
Review the Startup Repair log if it fails
Step 5 — Repair the Boot Sector with bootrec
When the MBR, boot sector, or Boot Configuration Data (BCD) is corrupt — common after a failed update, improper shutdown, or disk error —bootrec can rebuild them without reinstalling Windows.
Open a Command Prompt in WinRE
Fix the Master Boot Record
Fix the boot sector
Access is denied on bootrec /fixboot, run bootsect /nt60 SYS first, then retry.Rebuild the BCD store
/scanos lists all Windows installations found on the disk. /rebuildbcd then prompts you to add them to the BCD. Type A to add all found installations.Restart and test
Step 6 — Check the Windows Event Log
If the machine boots but crashes shortly afterward, the Event Log often records the cause before the crash occurs.Open Event Viewer
Review critical and error entries
disk), driver faults (source: Service Control Manager), or file system errors (source: Ntfs).Export findings
Step 7 — Perform a System Restore
If boot problems started after a recent software installation, Windows update, or driver change, System Restore can revert the system to a previous known-good state without affecting personal files.Launch System Restore from WinRE
Choose a restore point
Complete the restore
Common Scenarios & Quick Reference
The accordions below cover the most frequently reported boot error messages and their targeted fixes. Open the one that matches your exact symptoms.'BOOTMGR is missing' error
'BOOTMGR is missing' error
Stuck on motherboard logo / BIOS splash screen
Stuck on motherboard logo / BIOS splash screen
Infinite restart loop after Windows Update
Infinite restart loop after Windows Update
'Inaccessible Boot Device' Blue Screen on startup
'Inaccessible Boot Device' Blue Screen on startup
chkdsk from the WinRE command prompt:Escalation Criteria
Escalate to Tier 2 or a hardware specialist if any of the following apply:- All
bootreccommands succeed but the machine still fails to boot after multiple attempts. chkdskreports unrecoverable bad sectors on the system drive — the drive likely needs replacement.- POST beep codes indicate failed RAM or GPU and reseating/swapping sticks does not resolve the issue.
- The motherboard displays a BIOS error code (Q-Code / POST code) that the manufacturer maps to a fatal hardware fault.
- No restore points exist, Startup Repair fails, and the user’s data has not been backed up — data recovery should precede any reimaging.