Safe Mode is one of the most reliable ways to troubleshoot Windows issues. When a system won’t behave normally, booting into Safe Mode loads only essential drivers and services, making it easier to identify what’s wrong.
This post explains how to reboot a Windows computer into Safe Mode using PowerShell or Command Prompt, when to use each option, and how to safely return the system to a normal boot afterward.
What Safe Mode actually does
Safe Mode starts Windows with:
- Minimal drivers
- No third-party startup applications
- Limited background services
- Basic display and input support
Because of this, many problems caused by drivers, updates, or software conflicts simply do not load.
Different Safe Mode options
Windows provides a few Safe Mode variants, each useful in different situations.
Safe Mode
Loads only the most basic components. Best for general troubleshooting.
Safe Mode with Networking
Adds network drivers so you can access the internet or internal resources.
Safe Mode with Command Prompt
Starts directly into a command-line environment instead of the desktop.
When Safe Mode is useful
Safe Mode is commonly used to:
- Remove malware or unwanted software
- Uninstall broken drivers
- Fix startup or boot loop issues
- Troubleshoot blue screen errors
- Run system tools like SFC or DISM
- Diagnose problems when Explorer will not load
Important things to know before you start
You must run all commands as Administrator.
These changes affect the next reboot, not the current session.
If Safe Mode is enabled and not removed afterward, Windows will continue booting into Safe Mode repeatedly.
Always make sure you know how to undo the change.
Rebooting into Safe Mode using PowerShell
Open PowerShell as Administrator.
Safe Mode (minimal):
bcdedit /set {current} safeboot minimal
shutdown /r /t 0
Safe Mode with Networking:
bcdedit /set {current} safeboot network
shutdown /r /t 0
Safe Mode with Command Prompt:
bcdedit /set {current} safeboot minimal
bcdedit /set {current} safebootalternateshell yes
shutdown /r /t 0
The system will reboot immediately into the selected Safe Mode option.
Rebooting into Safe Mode using Command Prompt (CMD)
Open Command Prompt as Administrator.
Safe Mode (minimal):
bcdedit /set {current} safeboot minimal
shutdown /r /t 0
Safe Mode with Networking:
bcdedit /set {current} safeboot network
shutdown /r /t 0
Safe Mode with Command Prompt:
bcdedit /set {current} safeboot minimal
bcdedit /set {current} safebootalternateshell yes
shutdown /r /t 0
How to return Windows to normal boot
This step is critical. If you skip it, the system will stay in Safe Mode on every reboot.
Run the following commands in PowerShell or CMD as Administrator:
bcdedit /deletevalue {current} safeboot
bcdedit /deletevalue {current} safebootalternateshell
shutdown /r /t 0
After rebooting, Windows will start normally.
How to confirm you are in Safe Mode
You will usually notice:
- “Safe Mode” text in the corners of the screen
- Lower screen resolution
- Black desktop background
You can also verify from the command line:
systeminfo | findstr /i "Boot Mode"
Command line Safe Mode vs GUI methods
Command-line methods are ideal for:
- Remote troubleshooting
- Automation and scripting
- Systems with broken GUIs
- Helpdesk and admin workflows
GUI methods (Shift + Restart or Advanced Startup) are usually better for end users.
Common issues and fixes
Access denied errors
Make sure PowerShell or CMD is opened as Administrator.
System keeps booting into Safe Mode
Run:
bcdedit /deletevalue {current} safeboot
No network access
Verify that Safe Mode with Networking was used.
Final thoughts
Rebooting into Safe Mode using PowerShell or Command Prompt is a clean, reliable, and script-friendly approach to Windows troubleshooting. It’s especially useful when graphical tools fail or when managing systems remotely.
Just remember to always remove the Safe Mode setting once troubleshooting is complete.