Safe mode is a boot configuration flag, not a hidden menu. Set it for one boot, do the repair, and delete the flag again — otherwise the machine keeps starting with half the drivers missing.
Set **bcdedit /set {current} safeboot minimal**, reboot, and remove the flag with **bcdedit /deletevalue {current} safeboot** when the work is done. **msconfig** shows the same setting in a checkbox.
**bcdedit /enum {current}** prints the entry you are about to change, and **/export** stores the whole configuration. A typo in the identifier here costs more time than the backup takes.
bcdedit /enum {current}
bcdedit /export C:\bcd-before-safemode
Get-Item C:\bcd-before-safemode | Select-Object Name,Length**safeboot** with the value **minimal** loads the basic driver set without networking; **network** adds the network stack. Either way the change takes effect at the next restart.
bcdedit /set {current} safeboot minimal
bcdedit /enum {current} | findstr /i "safeboot description"
shutdown /r /t 5Shift and Restart, or three failed boots, open the recovery environment. Startup Settings then offers the same safe mode variants without any command line.
shutdown /r /o /t 5
:: Troubleshoot > Advanced options > Startup Settings > Restart
:: press 4 for safe mode, 5 for safe mode with networkingSafe mode is for removing a driver, uninstalling software or resetting a policy that blocks normal boot. Check which mode you are in before you start, because network features may be absent.
Get-CimInstance Win32_ComputerSystem | Select-Object BootupState,Model
Get-CimInstance Win32_BootConfiguration | Select-Object Name,BootDirectory
Get-Service | Where-Object Status -eq 'Running' | Measure-Object**/deletevalue** removes the setting, and the next boot is a standard one. Verify with the same enum command: the safeboot line must be gone.
bcdedit /deletevalue {current} safeboot
bcdedit /enum {current} | findstr /i "safeboot"
shutdown /r /t 5A leftover flag, a failed update or a stuck pending operation can keep the machine in the reduced state. Check the entry, the pending rename operations and the Setup log before editing anything else.
bcdedit /enum ALL | findstr /i "safeboot identifier"
Get-ItemProperty 'HKLM:\SYSTEM\CurrentControlSet\Control\Session Manager' -Name PendingFileRenameOperations -ErrorAction SilentlyContinue
Get-WinEvent -LogName Setup -MaxEvents 20 | Select-Object TimeCreated,Id,MessageA second boot entry or a pending update still carries the flag. Run bcdedit /enum ALL and look for safeboot on every entry, not only {current}.
Use minimal's sibling: set the value to network with bcdedit /set {current} safeboot network, or pick option 5 in Startup Settings.
Safe mode loads the basic display driver at 800x600. That is expected; the normal driver returns after the flag is removed.
A boot configuration change can trigger a recovery prompt on an encrypted volume. Have the key ready before you change bcdedit values.
No. It only changes which drivers and services load. Anything you delete or uninstall stays that way after the normal boot.
Not a Microsoft account password. For a local account, safe mode still needs the old password to sign in; the recovery environment is the correct route.
It loads the network stack and the basic drivers only, so browsing is possible but graphics and audio stay minimal. Use it when the repair needs a download.
Run bcdedit /deletevalue {current} safeboot and reboot. If the entry was damaged, restore the exported store with bcdedit /import C:\bcd-before-safemode from an elevated shell.
Free · no account needed · tracks your progress