WindowsTroubleshootingHow-To

How to Boot Windows Into Safe Mode (All Methods)

TG By The TechFix Guide Editorial Team  ·  Updated  ·  How we check our guides
A laptop on a wooden desk showing a plain blue Windows recovery options screen

Safe Mode starts Windows with the smallest set of drivers and services the operating system needs to reach a desktop. Nothing else loads: no third-party antivirus, no full graphics driver, no cloud sync clients, no startup apps, no print queue. That stripped-down state answers the most useful diagnostic question in Windows repair — is this fault coming from Windows itself, or from something that was installed on top of it? If the problem disappears in Safe Mode, it lives in a driver, a startup program, or a background service. If it survives, Windows or the hardware is the suspect.

This guide covers every reliable way to get there on Windows 10 and 11, which variant to choose, how to get back out, and what to do when the F8 key everyone remembers does nothing.

What Safe Mode loads, and what it leaves behind

In Safe Mode, Windows starts with:

  • Basic display, keyboard, mouse, and storage drivers — enough to draw a desktop and nothing more.
  • Only the services Microsoft marks as essential, each running in its default state.
  • No third-party startup programs, so the notification area is almost empty and the desktop loads in seconds.

What you lose: sound, Bluetooth, the print spooler, multi-monitor spanning, brightness control, and — in the plain variant — all networking. The desktop renders at a low resolution with a stretched aspect ratio, and Windows stamps "Safe Mode" into the corners so there is never any doubt about the state you are in.

The three flavours, and when each one helps

  • Safe Mode — minimum drivers, no network. The right choice for driver conflicts, black screens, and stubborn uninstalls.
  • Safe Mode with Networking — the same bare minimum plus network adapter drivers, DHCP, and DNS, so you can download a replacement driver or a scanner while you work.
  • Safe Mode with Command Prompt — plain Safe Mode, but you land in a command window instead of Explorer. Use it when Explorer itself is the thing crashing.

Method 1: Shift + Restart (works almost everywhere)

This is the fastest route on any machine that still reaches the desktop or the sign-in screen.

  1. Click Start, then the Power icon.
  2. Hold down Shift and click Restart, keeping Shift held until the blue "Choose an option" screen appears. Let go too early and Windows restarts normally, which is the most common reason this method seems to fail.
  3. Choose Troubleshoot > Advanced options > Startup Settings > Restart.
  4. Windows reboots to a numbered list. Press 4 for Safe Mode, 5 for Safe Mode with Networking, or 6 for Safe Mode with Command Prompt.

On many laptops the top-row number keys need Fn held, and the list accepts F4, F5, and F6 on most builds. The menu waits roughly 30 seconds and then boots normally if you press nothing.

The same trick works from the lock screen: click the power icon in the bottom-right corner, then Shift + Restart. Remember that version — it still works when the Start menu is broken.

Method 2: Settings > Recovery

If you would rather click than hold keys, Windows exposes the same menu directly:

  • Windows 11: Settings > System > Recovery, then click Restart now beside Advanced startup.
  • Windows 10: Settings > Update & Security > Recovery, then Restart now under Advanced startup.

From the blue menu, follow Troubleshoot > Advanced options > Startup Settings > Restart as before. Save your work first — this restarts the PC immediately without a second prompt.

Method 3: System Configuration (msconfig)

msconfig does not jump into Safe Mode; it flags the next boot and then you restart into it.

  1. Press Win + R, type msconfig, and press Enter.
  2. Open the Boot tab. Under Boot options, tick Safe boot.
  3. Pick the variant next to it: Minimal for plain Safe Mode, Alternate shell for the command prompt version, or Network for Safe Mode with Networking.
  4. Click OK, then Restart when Windows offers it.

Here is the catch that traps people: Windows does not reliably clear that checkbox for you when the session ends. If you restart and land straight back in Safe Mode, run msconfig again, untick Safe boot, and untick Network as well if it is still selected — a leftover Network tick is the usual cause of a machine that boots into Safe Mode with Networking forever.

Method 4: Interrupt three boots on purpose

When Windows will not start at all, you can trigger its own recovery environment by deliberately failing to boot.

  1. Switch the PC on and wait for the manufacturer logo or the spinning dots.
  2. Hold the power button for five to ten seconds until the machine switches off, before the sign-in screen appears.
  3. Repeat twice more. On the third consecutive failure Windows starts Automatic Repair.
  4. Choose Advanced options > Troubleshoot > Advanced options > Startup Settings > Restart, then press the number for the variant you want.

This route needs nothing but the power button, which is why it is the fallback for a machine stuck in a boot loop or sitting on a black screen. Disabling Windows fast startup makes the interrupted boots register more reliably if the first attempt does not take.

Method 5: Command line with bcdedit

With an administrator command prompt open — including one inside the recovery environment — bcdedit sets the Safe Mode flag directly, without any menus.

  • Plain Safe Mode: bcdedit /set {default} safeboot minimal
  • With networking: bcdedit /set {default} safeboot network
  • Command prompt variant: bcdedit /set {default} safeboot minimal then bcdedit /set {default} safebootalternateshell yes

Restart to apply. To undo, run bcdedit /deletevalue {default} safeboot — and bcdedit /deletevalue {default} safebootalternateshell if you set it. Run bcdedit /enum first on a dual-boot system, because the entry you need may be {current} rather than {default}; picking the wrong identifier sends the wrong installation into Safe Mode.

Method 6: F8, and why it stopped working

F8 is the advice everyone remembers and the one that fails most often. On Windows 7 the boot loader paused long enough to catch a keypress; a modern PC boots from an SSD through UEFI fast boot in a few seconds, and that pause is gone. Shift + F8 was meant to restore it, but it only behaves when fast startup is disabled, UEFI fast boot is off, and the drive is slow enough — a combination most current machines do not meet.

Treat F8 as a bonus rather than a plan: if it happens to work, fine; if not, Shift + Restart from the lock screen takes about twenty seconds.

What to actually fix while you are in Safe Mode

Safe Mode is a diagnostic stop, not a destination. Work through the likely causes, then restart and re-test to see whether the symptom is gone.

  1. Uninstall the suspect software. Go to Settings > Apps > Installed apps, sort by install date, and remove whatever arrived just before the problem started. In Safe Mode the uninstaller cannot be blocked by its own background services.
  2. Roll back a driver. Open Device Manager, expand Display adapters, right-click the adapter, open Properties > Driver tab, and click Roll Back Driver. Display drivers from all three major vendors are a common cause of black screens and random crashes, and rolling back to the previous build is the standard fix.
  3. Scan for malware. Some malware interferes with security tools while Windows runs normally. Our guide to removing malware from a Windows PC covers which free scanners still function in Safe Mode.
  4. Disable startup programs. Use Task Manager > Startup apps (or the Startup tab in msconfig on older builds). Disable everything, restart, then re-enable entries a few at a time until the symptom returns — that is how you identify the culprit instead of guessing.
  5. Remove a bad update. Go to Settings > Windows Update > Update history > Uninstall updates. This is the first move when a PC misbehaves the day after a patch, and our guide to Windows Update failures covers what to do when the rollback will not complete on its own.

Problems people hit inside Safe Mode

  • The PIN is rejected. Safe Mode usually skips Windows Hello, so a fingerprint reader and a PIN will not work — sign in with the account password instead. A Microsoft account may need a connection to validate, which is one reason Safe Mode with Networking suits modern laptops.
  • Keyboard or mouse is dead. Wireless receivers and some USB hubs are not initialised by the minimal driver set. Try another USB port — on a desktop, one on the back panel — and prefer a wired keyboard.
  • Black or flickering screen. That is the basic display driver doing exactly what it is meant to do, and it is the strongest hint that a graphics driver is your problem. Stay put and roll it back.
  • Windows Update refuses to run. By design: the update service does not start in Safe Mode. Patch after you leave it.
  • Stuck on a black screen after choosing Safe Mode. Press Ctrl + Alt + Delete to reach the sign-in screen, or use Method 4 to return to the recovery menu and pick another variant.

Getting back out again

A normal Restart from the Start menu leaves Safe Mode, unless you entered through msconfig or bcdedit, both of which persist their setting across reboots.

  • Via msconfig: run msconfig, untick Safe boot, click OK, and restart.
  • Via bcdedit: run bcdedit /deletevalue {default} safeboot in an administrator command prompt, then restart.

If Windows still boots into Safe Mode after both checks, look for a third-party boot manager or an OEM recovery utility that has set its own flag — those sit outside Windows and are not cleared by either method above.

When Safe Mode will not help

  • Hardware faults. Failing RAM, a dying drive, or an overheating CPU behave exactly the same in Safe Mode, because they sit below the driver layer.
  • Firmware and UEFI problems. These happen before Windows loads, so no Windows mode can diagnose them.
  • Windows will not even reach Safe Mode. Corrupted system files can block it entirely. At that point recovery tools or a fresh install become the practical answer, as covered in our clean install guide.
  • Load-dependent problems. Frame drops and thermal throttling only appear under real workload, so they need normal mode plus monitoring tools.

The short version

Safe Mode answers one question cheaply: is Windows healthy on its own? Reach it with Shift + Restart or the Recovery menu, use it to uninstall, roll back, or disable something, then restart and re-test — and write down what you changed so you know which step actually fixed it. If the symptom survives a clean Safe Mode boot, the fault is in Windows or the hardware, and our blue screen troubleshooting guide is the next stop. Startup slowdowns are the other condition Safe Mode narrows down quickly; our slow-startup walkthrough uses the same Startup apps list. The free utilities on our tools page cover disk health checks and driver cleanup, and the blog index has the rest of the Windows repair series.