How to Perform a Clean Boot in Windows

What is a Windows Clean Boot?

Clean Boot is a Windows startup mode where the operating system loads with a minimal set of drivers and all third-party startup services and programs are disabled. This is a powerful diagnostic tool that helps determine if a specific application, service, or driver is causing system instability, boot errors, or conflicts.

Unlike Safe Mode, Clean Boot uses standard Microsoft hardware drivers but completely excludes background processes installed by the user or PC manufacturer.

Why is this needed?

Perform a Clean Boot if you observe:

• Random errors, freezes, or Blue Screen of Death (BSOD) issues.
• Problems installing or updating programs/Windows updates.
• Malfunctioning of a specific application.
• Suspicion of malware masquerading as a system service.
• Unexplained failures in network, audio, or peripheral functionality.

Step-by-Step Guide to Performing a Clean Boot

Step 1: Create a Restore Point (Mandatory!)

All changes we make can be easily undone, but for full safety, create a restore point.

1. Open Control Panel → System and Security → System.
2. On the right side of the window, click System protection.
3. On the System Protection tab, select the system drive (usually C:) and click Create.
4. Enter a description (e.g., "Before Clean Boot") and click Create.

Step 2: Launch the System Configuration Utility

1. Press the Win + R key combination.
2. In the window that appears, type msconfig and click OK.

Step 3: Configure Boot Settings

In the System Configuration window:

1. Go to the General tab.
2. Select the Selective startup option.
3. Uncheck the Load system services box. This is the key step that will disable all third-party services.
4. Switch to the Startup tab.
5. Click Open Task Manager.
6. In the Task Manager that opens, on the Startup tab, disable all items (right-click → Disable or use the button at the bottom). Close Task Manager.
7. Return to msconfig and go to the Services tab.
8. Check the box Hide all Microsoft services. All remaining services in the list are third-party.
9. Click Disable all.
10. Click Apply and OK.

Step 4: Restart Your Computer

The system will prompt you to restart. Click Restart. The computer will boot into Clean Boot mode.

Step 5: Check System Behavior

After booting, check if the original problem (crash, error, freeze) reoccurs. If the problem disappears, it means its cause is one of the services or startup programs you disabled.

Step 6: Return to Normal Boot Mode

To revert everything:

1. Open msconfig again.
2. On the General tab, select Normal startup.
3. Click Apply → OK and restart your computer.

Next Steps After a Clean Boot

If the problem is gone, you need to find the culprit. Re-enable items one by one:

1. Go back to msconfig (or Task Manager for Startup).
2. Re-enable half of the disabled third-party services/programs.
3. Restart and check if the problem returns.
4. Repeat the process, halving the group of enabled services each time, until you find the one causing the crash. Once you identify the specific service/program, you can:
   • Update it to the latest version.
   • Uninstall and reinstall it.
   • Find an alternative to the unstable software.
   • Leave it disabled if it is non-critical.

Important Warnings

• Internet and sound may not work. This is expected, as drivers for network cards and audio chips from manufacturers (Realtek, Intel, etc.) are disabled. To access the internet temporarily, you can re-enable the corresponding service or driver, but this may compromise the diagnostic goal.
• Do not leave the system in Clean Boot mode for long. This is a temporary diagnostic mode. Many important functions (updates, Defender, some components) may work incorrectly.
• If the problem does NOT disappear in Clean Boot, the cause is likely in the hardware, basic Windows drivers, or corrupted system files. In this case, use other tools (sfc /scannow, DISM, memory check, chipset driver updates, etc.).

Clean Boot is a method of elimination. It helps narrow down the potential causes of failures to third-party software, significantly simplifying further troubleshooting and resolution.