How to Start Windows 11 in Safe Mode

Goal: Safe Mode starts Windows with a reduced set of drivers and services so you can determine whether a problem is caused by normal startup software, a driver, or another component loaded in a full Windows session. This guide shows the supported ways to enter Safe Mode, what the different variants mean, how to diagnose problems methodically, and how to avoid configuring the PC to loop into Safe Mode.

Quick steps

If Windows still opens, go to Settings > System > Recovery > Advanced startup and choose Restart now.
In Windows Recovery Environment, choose Troubleshoot > Advanced options > Startup Settings > Restart.
Choose Safe Mode, Safe Mode with Networking, or Safe Mode with Command Prompt according to the test you need.
Reproduce the original problem without making several changes at once.
Restart normally after testing.

Expected result: Windows reaches a reduced diagnostic session and a normal restart returns the PC to standard mode.

What you need before you start

Your Windows account password. Some sign-in methods may behave differently in Safe Mode.
Your BitLocker recovery key if the device is encrypted and recovery asks for it.
A note of the original symptom and the most recent driver, application, or update change.
Network access only if your test genuinely requires Safe Mode with Networking.

Real-world illustration — How to Start Windows 11 in Safe Mode

Why Safe Mode is useful

If a crash, black screen, or application problem disappears in Safe Mode, the reduced startup environment becomes evidence: something loaded in the normal session may be involved. It is not automatic proof that “Windows is fine,” but it helps narrow the search. Conversely, if the same failure occurs in Safe Mode, investigate system files, hardware, storage, or lower-level drivers instead of focusing only on startup apps.

Enter Safe Mode from a working Windows desktop

Open Settings > System > Recovery. Under Advanced startup, select Restart now. Windows opens the recovery environment. Choose Troubleshoot > Advanced options > Startup Settings > Restart, then select the required Safe Mode option.

Choose the right variant

Safe Mode: best default for isolating startup software and many driver issues.
Safe Mode with Networking: adds network components. Use it only when you need network access because it expands the set of loaded components.
Safe Mode with Command Prompt: intended for command-line diagnostics when the normal graphical shell is not useful.

When Windows cannot reach the desktop

Use Windows Recovery Environment rather than repeatedly forcing random shutdowns. Windows may open recovery automatically after failed starts, or you can boot from official Windows installation/recovery media and choose repair options. Once in Windows RE, use the same Startup Settings path.

Diagnose rather than “fix everything”

Before changing anything, write down whether the symptom occurs in Safe Mode. Then test one category at a time: startup applications, a recently installed driver, a newly added peripheral, or a specific third-party service. A clean diagnosis is more valuable than disabling many components simultaneously and not knowing which one mattered.

The following PowerShell command is read-only and lists common Windows startup entries. Run it in a normal PowerShell session or Safe Mode with the required shell available. No administrator rights are required for the query itself.

Get-CimInstance Win32_StartupCommand |
  Select-Object Name, Command, Location, User

Review the names and paths for recently installed software. Do not delete startup entries blindly. Prefer disabling a suspected startup application through Settings or Task Manager so that rollback is simple.

Exit Safe Mode

If you entered through Startup Settings, a normal restart usually returns to standard Windows automatically. Avoid old tutorials that tell you to permanently force Safe Mode through boot configuration unless you have a specific reason and understand how to undo it. A misconfigured persistent Safe Mode setting can make users believe the PC is “stuck.”

How to verify that the test is meaningful

Record whether the original symptom happens in Safe Mode.
Repeat the same action under normal Windows after making exactly one reversible change.
If disabling one startup app fixes the problem, re-enable unrelated items so the test remains specific.
Check Event Viewer or Reliability Monitor for a matching driver or application failure if the symptom is intermittent.

Common problems and fixes

No Internet in Safe Mode: you probably selected plain Safe Mode. Use Networking only if needed.
PIN sign-in does not behave as expected: use the account password when required.
BitLocker recovery appears: enter the legitimate recovery key associated with the device.
The problem disappears in Safe Mode: focus on startup software, third-party services, recent drivers, and shell extensions.
The problem remains: broaden the investigation to system files, storage, firmware, and hardware.

Safety and precautions

Do not uninstall several drivers or applications at once; you lose the ability to identify the cause.
Do not permanently disable security services merely because Safe Mode behaves differently.
Back up important data before deeper recovery work if the symptom includes disk errors or repeated boot failures.

Frequently asked questions

Does Safe Mode delete anything?

No. Starting Safe Mode is a diagnostic boot mode. Data loss would come from changes you choose to make while troubleshooting, not from entering the mode itself.

Should I use Safe Mode with Networking?

Use it only when your diagnostic task needs network access. Plain Safe Mode provides a smaller environment and is usually the better first comparison.

What if Windows will not boot at all?

Use Windows Recovery Environment and Startup Settings. If recovery itself fails, move to Microsoft’s documented startup-repair and recovery options.

Safe Mode decision tree

If Windows starts normally but crashes only after login, Safe Mode is useful for separating core Windows components from third-party startup software, drivers, and services. If the same failure occurs in Safe Mode, the cause may be deeper: system files, storage, hardware, or a problem that Safe Mode still loads. Record the exact symptom in both modes.

Change one thing at a time: disable a recently added startup item, uninstall one suspect driver/application through supported controls, reboot normally, and test. Do not disable every service permanently. If you use msconfig or Startup Settings, restore the normal boot configuration after diagnosis.

When Safe Mode is not the right tool

If the PC cannot reach Windows Recovery Environment, shows storage errors, repeatedly powers off, or displays firmware-level symptoms, move to startup repair/hardware/storage diagnostics rather than forcing Safe Mode commands.

Record the result before returning to normal mode

Write down whether Safe Mode changed the symptom, which startup items/drivers were disabled, and which test you performed. This prevents circular troubleshooting. After a normal reboot, confirm Windows is no longer configured to force Safe Mode and re-enable only the components you intentionally changed.

Final checklist

Original symptom documented.
Correct Safe Mode variant selected.
Only one reversible change tested at a time.
Normal restart confirmed afterward.
Backup made before any deeper repair.

Key takeaways

The method: enter Safe Mode through Windows Recovery Environment, reproduce the problem, change one variable at a time, then restart normally.

The key principle: Safe Mode is valuable because it changes the startup environment; use that difference as evidence instead of treating it as a one-click repair.

Official sources and references

Image credits

Voir la vidéo sur YouTube

Rechercher dans ce blog

0bamo0 - Android , Projets , Open Source