Safe Mode is Windows’ minimal-boot diagnostic state — no third-party drivers, no startup programs, just enough OS to fix things. On ARM laptops it works the same way conceptually, but the paths to reach it differ from the old F8 days, and a few ARM-specific quirks can trip you up.

You need Safe Mode when normal boot fails, when a bad driver causes crashes or black screens, or when you need to remove stubborn software that resists uninstallation while running. This guide covers every reliable way to get there on an ARM laptop, then what to actually do once you are in.

Why this happens

  • No legacy F8 boot menu on ARM UEFI: The old “tap F8 during boot” method relied on legacy BIOS timing. ARM laptops boot UEFI-only with fast startup, so the window for key-based interruption effectively does not exist.
  • Fast Startup skipping the boot menu: Windows Fast Startup hibernates the kernel between boots, which bypasses the normal boot-interrupt points entirely.
  • Bad driver loading at boot: A corrupted graphics, storage, or platform driver can crash the boot process before you ever see the login screen — exactly the situation Safe Mode is designed to escape.
  • Automatic Repair not triggering: Windows should offer recovery options after repeated failed boots, but a damaged recovery environment or boot configuration can suppress it.
  • BitLocker complicating recovery: On encrypted ARM laptops, recovery screens may demand the BitLocker recovery key before letting you into advanced options — without it, you are stuck.
  • Conflicting startup software: Aggressive third-party tools that load at boot can destabilize the system before you can open anything to remove them.
  • Exclusive hardware locks: Some AI-platform drivers take exclusive control of accelerators at boot; a crashed holder can block normal startup — the same exclusive-mode problem seen with NPU app conflicts .

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Enter Safe Mode from Settings (when Windows boots)

If Windows still boots normally, this is the cleanest path — no boot-interruption gymnastics required.

  1. Open Settings > System > Recovery and under Advanced startup, click Restart now and confirm.
  2. The laptop reboots into the blue recovery menu: choose Troubleshoot > Advanced options > Startup Settings, then click Restart.
  3. After the restart, press 4 for Safe Mode, 5 for Safe Mode with Networking (needed if you must download a driver while in Safe Mode), or 6 for Safe Mode with Command Prompt.
  4. Log in — the desktop will say “Safe Mode” in the corners and look low-resolution, which is normal.
  5. To exit Safe Mode later, just restart normally from the Start menu — unless you used msconfig to force it (see Fix 4), a normal restart returns to regular Windows.

Fix 2: Force recovery by interrupting boot (when Windows won’t boot)

When Windows cannot boot, you trigger the recovery environment by interrupting the boot process — three failed boots in a row summons Automatic Repair.

  1. Power on the laptop and wait for the Windows logo or spinning dots to appear.
  2. Press and hold the power button for 5-10 seconds to force a shutdown — do this the moment the logo appears, not after waiting.
  3. Repeat steps 1-2 two more times (three interrupted boots total).
  4. On the fourth boot, let it continue — Windows should enter Automatic Repair, then offer Advanced options.
  5. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then press 4, 5, or 6 for your Safe Mode variant. If Automatic Repair never appears after three interruptions, the boot configuration or WinRE is damaged — see Fix 5.

Fix 3: Use installation media to reach Safe Mode

When the on-disk recovery environment is broken, ARM64 installation media provides an external path to the same recovery tools.

  1. Create ARM64 Windows 11 installation media on a USB drive (see the ARM64 ISO guide if needed).
  2. Boot the laptop from the USB via the boot menu (F12 or your model’s key).
  3. At the Windows Setup screen, click Repair your computer (bottom-left) instead of Install now.
  4. Go to Troubleshoot > Advanced options > Startup Settings > Restart, then select Safe Mode with 4, 5, or 6.
  5. Alternatively, from Troubleshoot > Command Prompt on the media, you can run bcdedit /set {default} safeboot minimal, then exit and continue booting — Windows will enter Safe Mode. Remember to later run bcdedit /deletevalue {default} safeboot from within Safe Mode’s command prompt to undo it.

Fix 4: Force Safe Mode with msconfig (use carefully)

The System Configuration tool can force Safe Mode on every boot — useful when you need repeated Safe Mode sessions, but it will trap you in Safe Mode until you undo it.

  1. In normal Windows, press Win + R, type msconfig, and open the Boot tab.
  2. Check Safe boot and choose Minimal (plain Safe Mode) or Network (with networking), then click OK and restart.
  3. The laptop now boots into Safe Mode every time — do your repairs across as many reboots as needed.
  4. When finished, reopen msconfig in Safe Mode, uncheck Safe boot, click OK, and restart to return to normal Windows.
  5. Warning: if you forget step 4, every boot goes to Safe Mode and it feels like the laptop is broken — this is the most common “Safe Mode won’t turn off” complaint, and the fix is always unchecking that box.

Fix 5: Repair the boot configuration when recovery won’t trigger

If interrupted boots never summon Automatic Repair, the boot configuration data (BCD) or WinRE registration is damaged. Repairing it restores all the recovery paths above.

  1. Boot from ARM64 installation media, choose Repair your computer > Troubleshoot > Command Prompt.
  2. Run bootrec /fixmbr, bootrec /fixboot (if it errors with access denied, that is often normal on UEFI — continue), bootrec /scanos, and bootrec /rebuildbcd, confirming prompts as they appear.
  3. For UEFI systems, you may instead need: bcdboot C:\Windows /s S: /f UEFI (adjust drive letters to match — use diskpart > list vol to identify the EFI partition).
  4. Restart and retry the three-interrupt method from Fix 2 — Automatic Repair should now trigger.
  5. Once in recovery, also run Startup Repair from Troubleshoot > Advanced options before attempting Safe Mode, in case the underlying boot issue is now fixable directly.

Fix 6: What to do once you’re in Safe Mode

Reaching Safe Mode is only half the job. Here is the standard triage order once you are in — the same “most likely culprit first” discipline used when diagnosing slow creative apps .

  1. Remove the suspect driver: Open Device Manager, find the recently updated or yellow-warned device, right-click, and choose Uninstall device (check driver removal) or Roll back driver under Properties > Driver.
  2. Uninstall recent updates: Go to Settings > Windows Update > Update history > Uninstall updates and remove the update that preceded the problem.
  3. Disable startup programs: Open Task Manager > Startup apps and disable everything non-Microsoft, then restart normally to test.
  4. Uninstall the suspect application: In Settings > Apps > Installed apps, remove whatever was installed just before boot problems began — a bad utility or driver-bundled app is a classic cause.
  5. Run system repair: In Safe Mode with Command Prompt (or Terminal as admin), run sfc /scannow followed by DISM /Online /Cleanup-Image /RestoreHealth to fix system file corruption, then restart normally. And if the original problem was performance or streaming-related rather than boot-related — like cloud gaming lag — Safe Mode was the wrong tool; return to normal Windows and troubleshoot the actual symptom.

Closing

Safe Mode on ARM laptops is reached through Settings recovery, triple boot-interruption, or installation media — never F8. Once inside, work the standard triage: bad driver, bad update, bad startup program, corrupt system files. And always undo msconfig’s Safe boot flag when you are done, or every boot will feel broken.

Frequently asked questions

How do I boot an ARM laptop into Safe Mode?
The reliable paths are Settings > System > Recovery > Advanced startup, or interrupting the boot process three times to trigger Automatic Repair. The old F8 key method doesn’t work on modern UEFI ARM systems.
Does Safe Mode work the same on ARM as on x64?
Mostly yes — Safe Mode loads a minimal driver set on both. The differences are in how you get there (no legacy F8 on ARM UEFI) and which drivers load, since ARM uses its own driver stack.
Can I fix driver problems from Safe Mode?
Yes — that’s one of its main uses. In Safe Mode you can uninstall a bad driver, roll back updates, or disable startup programs without the offending software loading and interfering.
What if my laptop won't even reach the login screen?
Interrupt the boot three times in a row (hold power during the Windows logo) to force the recovery environment, then go to Troubleshoot > Advanced options > Startup Settings to reach Safe Mode.