How to Use a Clean Boot in Windows 7 and Vista — Historical Guide

A clean boot is a temporary comparison: run the same failing task with fewer background services and startup programs, then restore the settings you changed. Before starting, record the existing configuration. Otherwise, “return to normal” can accidentally enable software that was already disabled.

1. Check that this test fits the problem

Write down the exact task, error and conditions: for example, opening the same local document with the same application. Keep that test constant. Installing updates, replacing drivers and changing startup settings simultaneously makes the result difficult to interpret.

2. Record the starting state

1. Sign in with an authorized administrator account, save work and open msconfig from Start.
2. Record the General tab's selected startup mode and checkbox states.
3. On Services, select Hide all Microsoft services. Record the names and checked states of the remaining entries, including entries already unchecked.
4. Record the same information on the Startup tab. Capture the entire list, including entries that require scrolling.
5. Keep the record somewhere accessible after restart. Note any security, backup, networking or hardware utilities that will be temporarily unavailable.

3. Make the temporary clean-boot change

On General, choose Selective startup and clear Load startup items. Leave Load system services enabled. On Services, confirm Hide all Microsoft services is checked before choosing Disable all for the remaining entries. Apply the changes and restart when ready.

This is the historical sequence documented in Microsoft's Windows 7 SP1 troubleshooting article. Do not alter the Boot tab, processor count, memory limit or other advanced boot options for this test.

After restart, repeat the recorded task and save the result. If a different error appears, record both messages. A test that could not run is not the same as a successful test.

4. Isolate the changed item in controlled groups

If the original problem disappears, restore roughly half of the previously enabled non-Microsoft services, restart and repeat the same test. Leave entries that were already disabled before troubleshooting untouched. Narrow the group according to whether the original symptom returns, recording each configuration.

Test services first, then startup programs if necessary. Before testing startup programs, make their individual checkboxes match the intended test group and ensure Load startup items is enabled; otherwise the group may never run. Use the Windows 7/Vista Startup tab, not a Task Manager instruction intended for newer Windows.

For an illustrative eight-service test, if enabling four restores the failure, subdivide those four. If it does not, return to the known test baseline before testing the other four. Dependencies and interactions can complicate this method, so repeat the final comparison before naming one item as the cause. This example is a test plan, not a reported repair.

If the original failure remains in the reduced configuration, restore the baseline and investigate another cause with the saved evidence. Avoid leaving unrelated services off merely because the first experiment did not help.

5. Restore the recorded configuration

Open msconfig again. With Microsoft services hidden, put each third-party service and startup entry back to its recorded checked or unchecked state. Restore the General-tab settings consistently with that record. Do not blindly use Enable all or Normal startup if the PC already had deliberate exclusions.

If one component is being left off for a confirmed workaround, document that exception and arrange its repair, replacement or supported update. Do not leave security software disabled as a permanent fix. On a managed PC, have IT resolve policy-controlled entries that cannot be restored.

Restart and check protection status, networking, backup scheduling and required hardware utilities, as applicable. Then repeat the original task. If the starting state was not recorded, do not invent it: use an administrator's configuration record or assistance rather than enabling everything.

Documentation review: 14 October 2026. The legacy sequence was checked against Microsoft's Windows 7 SP1 article; the isolation method against its current clean-boot guidance. No user's startup configuration was changed for this review.

Official references

Microsoft — Historical Windows 7 clean-boot sequenceMethod 2 preserves the System Configuration steps. The article's old update packages and Fix it tools are not recommendations for this guide. Microsoft — Clean-boot isolation and restorationCurrent Windows 10/11 interface; useful for the comparison method and recording disabled startup items.