Clean Boot Windows to Find Software Conflicts

What a clean boot proves

A clean boot starts Windows with Microsoft services and a minimal set of third-party background components. If the crash, stutter or installer failure disappears, a disabled component participates in the problem. It does not identify which one until you re-enable items in groups.

Prepare

Sign in as an administrator, record enabled startup entries and close work. If the PC is managed by an organization, consult its administrator. Do not use this procedure to work around security policy.

Configure the test

1. Press Win + R, type msconfig and press Enter.
2. On Services, select Hide all Microsoft services. Verify the box before continuing.
3. Select Disable all for the remaining third-party services.
4. On Startup, open Task Manager and disable enabled startup apps.
5. Restart and reproduce the exact problem.

If the problem remains, the cause may be Windows, a driver, hardware or an application component that still starts on demand. If it disappears, re-enable half the services/startup apps, restart and retest. Continue splitting the failing group until one component remains.

Finish correctly

Update, reconfigure, reinstall or remove the responsible product. Then return System Configuration to Normal startup, re-enable needed services and startup apps and restart. Leaving a PC in an undocumented partial clean-boot state creates future confusion.

Gaming uses

A clean boot is valuable when a game stops crashing after overlays, RGB suites, audio enhancement, motherboard utilities or monitoring tools are removed from the launch path. Re-enable the anti-cheat and launcher components the game requires. The goal is identification, not a permanently stripped Windows session.