Windows Not Booting Use Safe Mode to Run Your Repair Toolkit
Normal Windows will not load — but it does not have to. Safe Mode starts a stripped Windows with just enough running for your toolkit to work.
✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 6 minute read
🎥 Watch the full video — CMD Toolkit V3 GUI, portable software and 5000+ commands shown step by step
A PC that freezes on the desktop, blue-screens after login, or dies under the weight of its own startup junk is not necessarily a PC that needs reinstalling. Between 'boots perfectly' and 'will not boot at all' there is a middle state built exactly for repairs: Safe Mode. Windows loads with minimal drivers and no startup crowd, which means the thing that breaks normal Windows is usually not loaded — and your portable toolkit can run and remove the problem. Here is the full route, from a PC that will not cooperate.
The door into Safe Mode (recreated panel)
STARTUP SETTINGS — Restart to change options
------------------------------------------
4) Enable Safe Mode
5) Enable Safe Mode with Networking
6) Enable Safe Mode with Command Prompt
Press the number key for the mode you want.
For toolkit work with internet access: choose 5.
👆 The Startup Settings screen and its real options — option 5 is the technician's usual choice (panel recreated)
1
Get to the Startup Settings Screen
Two routes, depending on how much Windows still works:
If you can reach the sign-in screen or desktop: hold Shift and click Restart, then choose Troubleshoot → Advanced options → Startup Settings → Restart
If Windows never loads: interrupt the boot three times — power off as the Windows logo or spinning dots appear, three times in a row — and Windows opens its recovery environment (Automatic Repair) on its own; follow the same Troubleshoot path from there
At Startup Settings, press 5 or F5 for Safe Mode with Networking — you get internet plus the minimal system
2
Run the Toolkit and Remove the Cause
Safe Mode looks old-fashioned — low resolution, 'Safe Mode' in the corners — and that is the sign it worked:
Start CMD Toolkit V3 from your pen drive; the GUI loads because Safe Mode still runs normal Windows programs
Work the diagnosis in order: disable the startup junk, uninstall or roll back whatever was installed just before the failure, run cleanup and the repair sections that match the symptoms
If a new graphics driver started the problem, Device Manager in Safe Mode can roll it back — display drivers are the number one 'it broke after I updated' story
3
The msconfig Route — and Its Trap
On a PC that still boots to the desktop between failures, there is a setting route:
Press Windows + R, type msconfig, open the Boot tab and tick Safe boot — Minimal, then restart
Do your repair work in Safe Mode
The trap: this setting survives restarts — the PC will keep booting into Safe Mode until you open msconfig again and untick it. Forgetting this step is how a fixed PC comes back as 'now it only starts in that strange mode'
4
Know When Safe Mode Is Not Enough
Honest boundaries, as always:
If Safe Mode itself blue-screens or freezes, the fault is deeper — hardware, or core system files; the offline DISM and SFC repair from a bootable WinPE drive is the next level, covered in its own guide on this site
If the data matters and the disk sounds or behaves unwell, rescue files before further boot attempts
After a successful repair, restart normally and watch one full boot before declaring victory
The full video shows the toolkit side of this workflow — what to run once you are inside — with the GUI sections matched to the faults Safe Mode exposes.
🎥 See CMD Toolkit V3 Working in the Full Video
The complete walkthrough — GUI interface, portable software and the command library, shown live on a real PC.
Yes. Safe Mode is your same Windows with minimal drivers and services — your files, accounts and installed programs are all present. Most programs can be uninstalled there, which is precisely why Safe Mode is the standard route for removing software that breaks normal startup.
Why does the screen look low resolution in Safe Mode
Because Safe Mode loads a basic display driver instead of your graphics card's full driver. That is deliberate — if the real driver is the thing crashing Windows, Safe Mode steps around it. The display returns to normal on the next regular boot.
Safe Mode also crashes — what now
Then the problem lives below the startup layer: core Windows files, the disk, RAM or another hardware fault. Stop repeating boots, rescue the data if the disk allows, and move to offline repair from a bootable WinPE USB — DISM and SFC pointed at the Windows drive from outside.
This guide is based on the Technical Anshu CMD Toolkit V3 video • Stuck on a step? Ask in the video comments — you will get a reply 🙏