Windows 11 Won’t Start: A Safe Troubleshooting Guide

Safest troubleshooting order

If Windows 11 won't start, do not reinstall Windows first. Work out the last stage the PC reliably reaches: no power, firmware (BIOS/UEFI) screen, Windows logo, recovery, or sign-in. That stage tells you whether the problem is power, the boot drive, the boot configuration, a driver or update, or Windows itself.

Work through these actions in order, and retest after each change.

1. Unplug all USB devices, docks and extra drives, then restart.
2. Force Windows Recovery to open and run Startup Repair.
3. Try Safe Mode and undo the last change (update, driver, software).
4. Use System Restore or uninstall the latest update.
5. If the drive is not detected or makes noises, stop and protect your data before any repair.
6. Only then consider advanced commands, Reset this PC (Keep my files), or a clean install.

Record the exact error before changing anything

If a blue screen showed a stop code, or the screen showed an error such as 0xc000000e, write it down or photograph it before making changes. Use another phone or computer to look up the code, and compare the advice with the symptoms you observe.

Identify where startup stops

Write down the last thing you see. This single observation prevents most unnecessary repairs.

Tip: Repeat the failure once without changing anything. If the PC stops at a different stage each time, suspect hardware, power, storage or memory instead of corrupted Windows.

Remove simple external causes

A connected device can change the boot order or stall hardware initialization. This costs nothing and fixes more cases than people expect.

1. Shut the PC down fully (hold the power button about 10 seconds).
2. Disconnect USB drives, SD cards, docks, printers, external displays and any extra internal drives you can safely remove.
3. On a laptop, connect the original charger. Check the charging light behaves normally.
4. On a desktop, check the power cable, PSU switch and monitor cable. Try a different display cable or port.
5. Power on again.

Open Windows Recovery Environment (WinRE)

Windows Recovery Environment is where Startup Repair, System Restore, Safe Mode and Command Prompt live. If it does not appear automatically, use one of the methods below.

Open recovery by interrupting startup

On most PCs, two interrupted startup attempts are enough for Windows to offer Automatic Repair. Do not use forced shutdowns while firmware is updating or while a recovery operation is visibly running.

1. Power on the PC and wait for the Windows logo (or the manufacturer logo) to appear.
2. Hold the power button until the PC turns off.
3. Repeat the interruption once, for two interrupted starts in total.
4. Start the PC a third time. If Automatic Repair appears, choose Advanced options.

Open recovery from the sign-in screen

At the sign-in screen, hold Shift while selecting Power → Restart. Then choose Troubleshoot → Advanced options.

Open recovery from Windows installation media

Use this method if WinRE will not open or appears damaged. Create official Windows installation media on another working PC first.

1. On another PC, create Windows installation media with Microsoft's Media Creation Tool.
2. Boot the affected PC from the USB using the boot-menu key shown by the manufacturer; common keys include F12, F9, Esc or F10.
3. Choose the language and other preferences, then select Repair your computer → Troubleshoot → Advanced options.

Choose a recovery tool in WinRE

Open Troubleshoot → Advanced options and choose the tool that best matches the failure stage. If BitLocker is enabled, Windows may request its recovery key before allowing access to some recovery options.

• Startup Repair: start here to let Windows diagnose common startup problems.
• System Restore: rolls system files and settings back to a restore point when one exists; personal files are not normally removed.
• Uninstall Updates: remove a recently installed quality or feature update when the timing suggests it caused the failure.
• Startup Settings: use this to reach Safe Mode.
• Command Prompt: use only for the advanced checks below, after confirming the correct drive letter.

If Startup Repair cannot repair Windows

Do not keep rerunning Startup Repair without reviewing the result. Check its log at C:\Windows\System32\Logfiles\Srt\SrtTrail.txt; the Windows drive letter can be different inside recovery. Use that information to choose the next diagnostic step.

Safe Mode and recent changes

Safe Mode loads a minimal set of drivers and services. If Windows starts there, the basic boot path works and the suspect becomes software, a driver, or an update.

To open Safe Mode from recovery, choose Troubleshoot → Advanced options → Startup Settings → Restart.

1. After the PC restarts, press 4 for Safe Mode or 5 for Safe Mode with Networking.

• Undo the most recent change first: a graphics or storage driver, antivirus or security suite, system utility, or Windows update.
• Change one thing at a time and restart between changes. Changing several items at once hides the cause.
• Check Settings → Windows Update → Update history → Uninstall updates for something installed just before the problem started.
• Open Device Manager and look for warning icons. For unidentified devices, use the hardware ID rather than downloading a random driver.
• If the desktop is slow only after sign-in, disable recent startup apps in Task Manager → Startup apps.

If Safe Mode also fails

If Safe Mode also fails, the cause is more likely to involve storage, system files, memory or hardware than a normal startup app. Continue with the boot-drive and hardware checks below.

Boot drive not found or boot error codes

If you see No bootable device, Operating system not found, or a blue recovery screen with an error code, check these in order.

Check firmware (BIOS/UEFI)

Open firmware setup (commonly Del, F2, F10, F12 or Esc right after power on).

• Is the SSD/HDD listed? If the drive is not detected at all, Windows cannot be the primary problem. Reseat the drive (see the hardware checks below) or test it in another machine or enclosure.
• Boot order: make sure Windows Boot Manager or your internal drive is first, not a USB device or network boot.
• Storage mode (SATA/AHCI/RAID/Intel VMD): if a BIOS update or reset changed this, Windows can fail with INACCESSIBLE_BOOT_DEVICE. Return it to the mode it had before. Do not flip it randomly: note what it was before you touch it.
• UEFI vs Legacy/CSM and Secure Boot: a Windows 11 install on a GPT disk expects UEFI. Switching to Legacy/CSM can make a working install unbootable.
• Date and time: a dead CMOS battery can reset settings and cause odd boot behavior.

Common boot error codes

Advanced checks from Command Prompt (only if comfortable)

These checks are for readers comfortable with recovery tools. Drive letters in WinRE often differ from normal Windows. If the drive is encrypted, have the BitLocker recovery key available. If the drive is disappearing, clicking, or reporting repeated I/O errors, stop and protect the data instead of running repair commands.

Use DiskPart only to list volumes at this stage. Do not delete, format, clean, or change partitions.

diskpart
list volume
exit
dir C:\

• Try dir D:\, dir E:\ or another letter until you find the volume containing the Windows and Users folders. Substitute that detected drive letter for C: in the examples below.

Check system files offline

After identifying the correct Windows volume, run the offline System File Checker command below. Replace C: with the drive letter that actually contains the Windows folder in WinRE.

sfc /scannow /offbootdir=C:\ /offwindir=C:\Windows

Check the file system

Do not run file-system scans on a drive that is clicking, repeatedly disappearing, or showing repeated storage errors. Prioritize data recovery first. On a drive that is not showing those warning signs, use the correct Windows volume letter in this command.

chkdsk C: /f

Rebuild boot records

Only continue if the internal drive is detected and you have confirmed the Windows installation and boot configuration are the likely issue. These commands change boot configuration; stop if the output does not match the expected Windows installation.

bootrec /scanos
bootrec /rebuildbcd

Refresh UEFI boot files if Bootrec reports “Access is denied”

On a UEFI system, bootrec /fixboot can return “Access is denied”. The following is an advanced alternative, not a step to run blindly: identify the correct disk and the small FAT32 EFI System partition first. Never assume the Windows disk is disk 0. Replace <disk-number>, <efi-partition-number>, and <WindowsDrive> with the values you confirmed. Selecting the wrong partition can make the system unbootable.

diskpart
list disk
select disk <disk-number>
list partition
select partition <efi-partition-number>
assign letter=S
exit
bcdboot <WindowsDrive>:\Windows /s S: /f UEFI

Undo pending update actions (advanced)

If a pending Windows update is preventing startup, this DISM command may help. Replace C:\ with the root of the offline Windows volume you identified. Do not run it against an uncertain drive letter.

dism /image:C:\ /cleanup-image /revertpendingactions

BitLocker recovery screen

A blue screen asking for a BitLocker recovery key is not a Windows failure. It means the PC detected a change (BIOS update, firmware reset, hardware change, boot order, or a motherboard or TPM change) and is protecting your data.

This is one of the most common startup surprises on newer Windows 11 PCs.

• Find the key at aka.ms/myrecoverykey by signing in with the Microsoft account used on that PC, from another device.
• Work or school PCs: the key is usually held by your IT administrator.
• The key can also be saved in a file, USB stick or printout from when encryption was enabled.
• Do not reset, reinstall or wipe the drive just because the prompt appeared. Without the key, encrypted data is not recoverable.
• After you unlock the PC, make sure the key is backed up to your account so it never blocks you again.

Boot loop and Automatic Repair failed

A restart loop means Windows is failing before startup completes. Common leads to investigate include, in order:

• A recent Windows update or driver.
• A failing or disconnected storage drive.
• Damaged system files or boot configuration.
• Unstable memory (RAM) or overheating.
• A power-supply or battery fault.

Troubleshoot a boot loop in order

Work through one recovery option at a time and restart between attempts.

1. Open recovery and try Uninstall Updates → latest quality update, then the latest feature update if relevant.
2. Try System Restore if a suitable restore point exists.
3. Try Safe Mode and undo the most recent driver, update or application change.
4. Use the offline SFC and boot-repair commands above only after confirming the correct Windows volume.
5. Test the drive, memory, power and thermals if software recovery does not resolve the loop.

If the stopping point changes between attempts

If the loop happens at different points each time, treat that variability as a hardware warning. Prioritize storage, memory, power and temperature checks instead of repeatedly applying Windows repairs.

Blue screen during startup

If the screen shows a stop code such as CRITICAL_PROCESS_DIED, INACCESSIBLE_BOOT_DEVICE, KERNEL_DATA_INPAGE_ERROR or MEMORY_MANAGEMENT, photograph it. Many codes are generic, so the pattern matters more than a single code:

Use the stop code lookup on another device, but verify it against what you observe rather than trusting one line of advice.

• Storage-related codes (such as KERNEL_DATA_INPAGE_ERROR and INACCESSIBLE_BOOT_DEVICE) point toward the drive, cable or storage driver.
• Memory-related codes point toward RAM, XMP/EXPO overclock settings or an unstable motherboard.
• Different codes on every crash strongly suggest hardware instability.

Black screen, with or without a cursor

Try these checks in order; after each one, see whether the display returns or the PC responds.

1. Press Ctrl + Win + Shift + B to restart the graphics driver; this sometimes restores the display.
2. Press Win + P and cycle through display modes in case output is going to a disconnected screen.
3. Press Ctrl + Alt + Del to check whether Windows responds.
4. Disconnect extra monitors, reseat the HDMI/DisplayPort cable, and try another port.
5. On a desktop with a graphics card, connect the monitor to the card rather than the motherboard. If hardware was recently changed, test another output.
6. If Windows can reach recovery, boot to Safe Mode and roll back or reinstall the graphics driver.

When a black screen points beyond Windows

If the PC shows a black screen and a firmware screen never appears, the display path or motherboard is the problem rather than Windows.

No power or no display

If nothing happens at all:

• Laptop: hold the power button for 30 to 60 seconds with the charger and (if removable) battery disconnected, then reconnect the charger only and try again. Test with a known-good charger of the correct wattage.
• Desktop: check the PSU switch, wall socket, power cable and front-panel connectors. Try powering with only one RAM stick and no extra drives.
• Listen for fans, beeps or LED codes. Motherboard LED and beep codes are in your manufacturer's manual, and they are more reliable than guessing.
• Any swelling, burning smell, heat or damage to a laptop battery means stop and have it inspected. Do not keep charging a swollen battery.

Bench checks: what to test when Windows is not the problem

This is where a hardware workflow beats a reinstall. If the failure stage points away from Windows, test the parts:

1. Reseat memory. Power off, disconnect power, remove the RAM, clean the contacts with care, and reseat firmly. Try one stick at a time in different slots. Faulty RAM is a classic cause of random stopping points and varied blue screens.
2. Test the drive elsewhere. Put the SSD/HDD in a USB enclosure or another PC. If it is not detected, or it appears and then disappears, the drive or its connection is the issue.
3. Reset firmware settings. Load BIOS defaults, or clear the CMOS (remove the coin cell battery for a few minutes on desktops, or use the manufacturer's method). Remember to restore the original storage mode if it differs.
4. Check temperatures and fans. Overheating can cause shutdowns during boot or a loop at the logo.
5. Swap known-good parts. Power supply, charger, RAM and display cable are the cheapest parts to rule out.
6. Look for physical damage. Liquid residue, corrosion, bent connectors and a loose M.2 screw are common on laptops.

When to stop and protect your data

Stop repairing and prioritize a backup or professional recovery assessment if any of these warning signs appear:

• The drive clicks, grinds or beeps.
• The drive keeps vanishing from firmware or recovery.
• You see repeated storage or I/O errors.
• The PC becomes extremely slow, or file copies keep failing.
• Recovery cannot see the Windows drive at all.

Copy files from a drive that appears healthy

Only attempt this DIY route if the drive is not making unusual noises, disappearing, or showing repeated errors. Connect it to a working computer with an enclosure or adapter that matches its interface (SATA or NVMe M.2).

1. Power off the PC and disconnect power before removing the drive.
2. Remove the drive and connect it to a working PC using a matching USB enclosure or adapter.
3. Copy important folders such as Documents, Desktop, Pictures and browser data to a different disk. Do not copy files onto the suspect drive.
4. If BitLocker encryption is enabled, unlock the drive with its recovery key before copying files.

When to use a professional data-recovery lab

Use a professional data-recovery service if the drive makes noises, has been exposed to liquid or heat, repeatedly disconnects, or contains irreplaceable data. Repeated power-on and repair attempts can reduce the chance of recovering data from a failing drive.

Reset this PC is not a data-recovery tool

Reset this PC → Keep my files is less destructive than a clean install, but it is still a major change and can affect apps and settings. Back up first when possible, and do not expect a reset to fix a hardware fault.

Repair, reset or replace: how to decide

TWW diagnosis: the stage is the clue

The most useful clue is not the error message by itself. It is the last stage the machine reaches reliably.

• Reaches firmware but not the Windows logo → focus on boot storage and boot configuration.
• Reaches Windows Recovery but crashes loading the desktop → drivers, updates, system files or hardware instability.
• Stopping point changes between attempts → hardware, power, storage or memory.