How to start Windows 11 in Safe Mode
Start Windows 11 in Safe Mode from Settings, the sign-in screen, or Windows Recovery Environment, choose the correct Safe Mode option, and use the result to narrow down a Windows problem.
- Updated
- September 17, 2026
- Reading time
- 8 min read
Start Windows 11 in Safe Mode from Settings, the sign-in screen, or Windows Recovery Environment, choose the correct Safe Mode option, and use the result to narrow down a Windows problem. Use the procedure as a controlled diagnostic process and preserve a safe way back.
What Safe Mode does
Safe Mode starts Windows in a limited state using only essential files, services, and drivers. Its main value is diagnostic: compare the same problem in normal Windows and in Safe Mode instead of treating Safe Mode itself as the repair.
If the problem does not reappear in Safe Mode, Microsoft says default settings, basic device drivers, and services can be eliminated as possible causes. That narrows the investigation, but it does not by itself identify the exact startup app, service, driver, or configuration responsible.
Before entering Safe Mode
Save open work before restarting. If device encryption or BitLocker protects the PC, have the recovery key available because Windows Recovery Environment can request it.
Also make sure you know the account password. Microsoft notes that PIN and biometric sign-in options are unavailable when signing in through Safe Mode, so a password is required.
Start Safe Mode from Windows 11 Settings
Use this route when Windows still opens normally and you can reach Settings.
- Open Settings > System > Recovery.
- Under Recovery options, select Restart now next to Advanced startup. Save any unsaved work if Windows prompts you.
- After Windows enters the recovery environment, select Troubleshoot > Advanced options > Startup Settings > Restart.
- When Startup Settings appears, select 4 or press F4 for Safe Mode. Use 5 or F5 only when you specifically need Safe Mode with Networking.
Start Safe Mode from the sign-in screen
Use Shift + Restart when you can reach the Windows sign-in screen but cannot complete an ordinary sign-in or cannot conveniently reach Settings.
- At the sign-in screen, hold the Shift key while selecting Power > Restart.
- In Windows Recovery Environment, select Troubleshoot > Advanced options > Startup Settings > Restart.
- After the PC restarts to Startup Settings, select the Safe Mode option needed for the test.
If Windows cannot start normally
Windows can automatically enter Windows Recovery Environment after repeated startup failures. Microsoft also documents recovery drives and Windows installation media as ways to reach Windows RE when Windows cannot start normally.
Once Windows RE is available, use Troubleshoot > Advanced options > Startup Settings > Restart, then select the appropriate Safe Mode option. Avoid deliberately forcing repeated shutdowns when Windows is actively installing an update or performing a recovery operation.
Choose Safe Mode, Networking, or Command Prompt
Startup Settings provides several boot choices. For ordinary isolation testing, start with standard Safe Mode unless the troubleshooting task specifically requires networking or a command-line-only environment.
- 4 or F4 — Enable Safe Mode: starts Windows in a basic state with a limited set of files and drivers.
- 5 or F5 — Safe Mode with Networking: adds network drivers and services needed for internet or network access.
- 6 or F6 — Safe Mode with Command Prompt: starts Safe Mode with Command Prompt instead of the usual Windows interface.
What the Safe Mode result means
Reproduce the same symptom you observed in normal Windows. Keep the test narrow: open the same Windows component, perform the same sign-in step, or repeat the same action that previously failed.
If the problem disappears in Safe Mode, the result narrows the cause away from the default settings, basic device drivers, and services loaded there. Investigate software, startup items, services, or drivers that differ between normal startup and Safe Mode.
If the same problem remains in Safe Mode, do not assume a startup application is responsible. Preserve that result and continue with evidence appropriate to the symptom, such as system-file, account, storage, display, update, or hardware diagnostics.
Safe Mode is not the same as a clean boot
Microsoft distinguishes Safe Mode from a clean boot. Safe Mode starts Windows with a limited set of files and drivers, while a clean boot gives more control for isolating background software conflicts using essential drivers and startup programs.
A useful sequence is to use Safe Mode as a broad comparison first. If the symptom disappears and the evidence points toward background software, a carefully recorded clean boot can then help isolate the conflicting service or startup program.
If you cannot sign in to Safe Mode
Use the account password rather than expecting Windows Hello PIN, fingerprint, or face recognition. Microsoft states that PIN and biometric options are unavailable for Safe Mode sign-in.
If you do not know the required password or the device is managed by an organization, avoid destructive account or security changes merely to continue troubleshooting. Recover the appropriate credential or contact the administrator responsible for the device.
How to leave Safe Mode
In the normal Startup Settings workflow, restarting the PC is usually enough to return to ordinary Windows. After restart, verify that the Safe Mode label is gone and repeat the original task once under normal startup.
If Windows continues to boot into Safe Mode, Microsoft recommends opening System Configuration and clearing the Safe boot setting.
- Press Windows + R.
- Type msconfig and select OK.
- Open the Boot tab.
- Under Boot options, clear Safe boot.
- Apply the change and restart Windows normally.
Verify what you learned
Record whether the original symptom occurred in normal Windows, standard Safe Mode, or Safe Mode with Networking, and note any exact error that changed. That comparison is the useful output of the test.
Safe Mode should reduce uncertainty. Once the result points toward a narrower cause, return to normal Windows when possible and make one targeted, reversible change at a time rather than applying multiple resets.