How to Boot Into Safe Mode on Windows 11

Hold Shift, click Restart. Troubleshoot, Advanced options, Startup Settings, Restart. Press F4.

That’s the whole thing if your computer still boots. Takes thirty seconds. Most of this article is about what to do when you can’t reach the desktop, because that’s where people actually get stuck.

What Gets Turned Off

Safe Mode replaces your GPU driver — NVIDIA, AMD, whatever you have — with Microsoft’s basic display adapter. That’s why the screen looks terrible and why Safe Mode is the fix when a bad driver update gives you a black screen. Sound goes, printers go, most USB devices beyond mouse and keyboard go, Bluetooth goes, network goes in basic mode.

On the services side: Windows Update, Windows Search, Defender’s real-time protection (mostly), every third-party antivirus, all scheduled tasks, and every startup program. Spotify, Discord, Steam, OneDrive, Teams — none of them load. What’s left is the kernel, storage drivers, the registry, input devices, and a handful of core services.

The diagnostic shortcut I use constantly: problem gone in Safe Mode means whatever caused it got turned off — some driver, service, or startup program. Problem stays in Safe Mode means corrupted system files or hardware. That one piece of logic narrows down most issues I see.

You get three options on the Startup Settings screen. F4 is basic Safe Mode, no network — I use it maybe 70% of the time. Driver conflicts, uninstalling software, System Restore. F5 adds networking, pick this if you need to download a driver or run Malwarebytes (it needs to update definitions before scanning). We use F5 for almost every remote session because AnyDesk needs network. F6 gives you a command prompt instead of the desktop, but honestly everything you’d do in F6 you can do by opening Terminal from normal Safe Mode. I almost never recommend it.

When Windows Won’t Boot

Hold the power button for ten seconds while Windows is trying to start. Everything shuts off. Turn it on again, wait for the logo or spinning dots, hold the power button for ten seconds again. Do this three times. On the third, Windows gives up and drops into recovery — you’ll see “Preparing Automatic Repair” or go straight to “Choose an option.”

Same path from there: Troubleshoot, Advanced options, Startup Settings, Restart, F4 or F5.

If the machine never gets past “Preparing Automatic Repair” and just keeps rebooting — that’s a different problem. You’re stuck in an automatic repair loop and Safe Mode might not even be reachable through the normal interruption method. That guide covers breaking out of the loop first so you can actually get to the Startup Settings screen.

I walked a client through this over the phone once and he’d already done it four times without realizing what was happening. Windows had entered recovery on the fourth restart — blue screen with options — but he panicked and held the power button again, which killed recovery and started the whole cycle over. He just needed to stop pressing buttons and read the screen.

Desktops with a physical reset button on the case — use that instead of the power button for the interruptions, it’s less wear on the PSU. Some Dell and HP machines need four interruptions instead of three before recovery triggers.

msconfig, F8, Getting Stuck

The msconfig method works but has a trap that catches people constantly. Win+R, type msconfig, Boot tab, check “Safe boot,” restart. Your PC boots into Safe Mode. Problem is it stays in Safe Mode on every restart until you go back and uncheck that box. I see this at least once a month — client fixes their issue, restarts normally, panics when Safe Mode loads again. They didn’t break anything. They forgot msconfig.

If you’re stuck and msconfig won’t open, run bcdedit /deletevalue {current} safeboot in an admin Terminal and restart. Clears the flag.

F8 from Windows 7 doesn’t work anymore because UEFI boots too fast — the keypress window is under 200 milliseconds. Same reason getting into BIOS by mashing a key is unreliable now. You can bring it back:

bcdedit /set {default} bootmenupolicy legacy

Adds about 2-3 seconds to every boot because Windows has to pause and wait for a keypress. Fine for technicians, unnecessary for most people. Undo it with bcdedit /set {default} bootmenupolicy standard.

When Safe Mode Is the Wrong Tool

A machine that won’t power on — no fans, no lights — has a power supply or motherboard problem. Safe Mode doesn’t enter the picture because Windows never loads. Same if it turns on but shows no display at all.

The other tell is when Safe Mode has the exact same problem as normal mode. Same blue screen, same freeze. Not a driver or startup program — try SFC and DISM for corrupted system files, or check the drive for hardware failure.

Most common situation though: someone gets into Safe Mode fine but has no idea what to do next. They’re staring at a low-res desktop thinking “now what.” Device Manager for driver conflicts, Event Viewer for crash logs, msconfig for startup isolation — knowing where to look matters more than getting in. If you’re stuck at that point, we can connect through AnyDesk in Safe Mode with Networking and figure it out from there.