System Configuration (msconfig) is a built-in Windows tool for controlling how Windows starts. It’s most useful for one thing: finding out whether a third-party service or startup program is causing a problem by starting Windows with only Microsoft services — a clean boot.
Open it with Win + R → msconfig (administrator rights needed).
The tabs
| Tab | What it does |
|---|---|
| General | Normal, Diagnostic or Selective startup |
| Boot | Safe Mode, boot timeout, advanced boot options |
| Services | Enable/disable services for the next start |
| Startup | In Windows 10/11, points to Task Manager |
| Tools | Shortcuts to other admin tools |
Perform a clean boot
A clean boot starts Windows with Microsoft services only. If a problem (crashes, slowness, errors, high CPU) disappears, a third-party service or app is the cause.
- Services tab → tick Hide all Microsoft services → click Disable all.
- Startup tab → Open Task Manager → disable each startup item (note which ones you disable).
- Click OK and restart.
- Test. If the problem is gone, re-enable services in halves and restart each time to narrow down the culprit.
- When finished, return to General → Normal startup.
On a Windows Server or VPS, don’t disable services you rely on for remote access (Remote Desktop Services) or management tools — keep Hide all Microsoft services ticked so they’re not affected, and have the VNC console available.
Boot into Safe Mode
Boot tab → tick Safe boot:
- Minimal — standard Safe Mode.
- Network — Safe Mode with networking.
- Alternate shell — Safe Mode with a command prompt.
Restart. Windows keeps booting into Safe Mode until you untick Safe boot — remember to turn it off.
On a remote VPS, Safe Mode without networking means no RDP. Only use it if you can reach the server’s console (VNC) from your control panel, or choose Network. Remote Desktop may still not work in Safe Mode on all versions — plan to use the console.
Other boot options
- Timeout — how long the boot menu waits on multi-boot systems.
- No GUI boot — hides the boot animation.
- Boot log — writes
C:\Windows\ntbtlog.txtlisting loaded drivers; useful for driver problems. - Base video — standard VGA driver, to rule out display driver issues.
- Advanced options → Number of processors / Maximum memory — leave these unticked. They limit Windows to fewer CPUs or less RAM and are a common cause of “my server got slower”. They don’t speed anything up.
Startup programs: use Task Manager
In Windows 10/11 and recent Windows Server versions, manage startup apps in Task Manager → Startup apps (Ctrl + Shift + Esc). The Startup impact column shows which ones slow the login. Also check:
- Settings → Apps → Startup
- Task Scheduler — many apps start via scheduled tasks; see Windows Task Scheduler.
When msconfig isn’t enough
- Can’t boot at all: use Windows Recovery Environment or edit the boot configuration — see Boot Configuration Data (BCD) explained.
- Performance problems: use Resource Monitor and CPU and RAM monitoring.
- Malware suspicion: run a Microsoft Defender Offline scan.
Summary
Use msconfig for clean boots and Safe Mode, Task Manager for startup apps, and leave the processor/memory limits alone. On a Windows VPS, keep the console handy before changing boot settings.