New PC Setup: the exact Windows 11 startup/app cleanup that prevents slow boots (Task Manager + Services)

TL;DR

• (Restore point) So you can quickly undo any changes
• (Task Manager > Startup apps) Expand out and disable everything you don’t need at sign-in first—especially if you see “High impact” items.
• (Uninstall vendor updaters and trialware) Programs you won’t use (and don’t impact boot speed on their own).
• (Clean Boot-style Services) Touch none of Microsoft’s stuff; clean up third-party services through the “Hide all Microsoft services” checkbox we’re all used to.
• (Lock it in) After installing big software like Adobe, game launchers, printer suites etc., make sure you go back and re-check your Startup apps to see if they left any unwanted bioweaponry during installation.

If your fast and new Windows 11 PC tablets today but has become decidedly sluggish just another month from now, it’s probably not Windows is starting to suck, but it’s the dirt of auto-starts cluttering the launch. Papercut! It is crowded, and this is a one-two punch workflow to fix it via some hammering down of apps that launch at sign-in (Task Manager Startup apps) to begin with and too many third-party services that love to come back to haunt your boots and be in the lower side of the bride or ruin them altogether (Services). Use this article to learn the questions you need to ask yourself in what order and which things in your PC to really focus on during a cleanup, as well as what not to touch.

What this cleanup does (and might not do)

This is mostly just for typical use-cases common: a mix bag of auto-starts at boot that slow down otherwise healthy machines to a ungoldy snails pace! It won’t fix slow boots caused by firmware/BIOS delays, failing storage, or driver/hardware problems—but it gets your Windows-side startup as skinny as it can be to make it easier to troubleshoot whatever’s left.

Before you mess with anything: 5-minute baseline + a safety net

1. Do a normal reboot and time it (roughly): until you’re pressing Power to the instant you can open the Start menu and make it respond quickly. Write it down.
2. Create a restore point: open System Protection (Run: systempropertiesprotection.exe) and create a restore point named “Before startup cleanup.” (support.microsoft.com).
3. (Optional but smart) Back up important files or turn on Windows Backup if you haven’t yet—especially if this is a brand-new PC you’re still getting set up. (support.microsoft.com).
4. Plug in power (laptops) and close anything important. You’ll reboot at least once.
5. You might want to make a quick checklist for after making changes and rebooting: audio plays, Wi‑Fi works, printer works (if you use one), VPN works (if you use one).

Part 1 (must-do): Startup apps cleanup in Task Manager

In Windows 11 you can control which programs start in Settings and in Task Manager; they’re accessing the same underlying startup list but Task Manager is better for performance cleanup because it shows “Startup impact.” (support.microsoft.com).

1. Open Task Manager: right-click Start > Task Manager.
2. Select the Startup apps tab. (support.microsoft.com).
3. Click the Startup impact column header to sort with the worst offenders first (High Impact first). For each app you don’t need immediately after signing in: select it > Disable. (support.microsoft.com)
4. Reboot once after your first pass and ensure the PC still behaves normally.

How to decide what to Disable (the “need it at sign-in?” test)

As a rule of thumb—if you wouldn’t manually launch the app within the first 2–3 minutes after signing in, it probably doesn’t need to launch automatically at sign-in. And don’t panic—disabling these startup entries generally won’t uninstall the app, but just prevents it from launching automatically at sign-in. (support.microsoft.com)

Use Startup impact correctly (what “High impact” actually means)

In Task Manager, Startup impact is based on measured CPU and disk usage during startup—for example, “High impact” means more than 1 second of CPU time or more than 3 MB of disk I/O during startup. Use it as a prioritization tool: start with High impact apps you don’t need at sign-in, then work down the list. (support.microsoft.com)

Do a quick uninstall pass (so the clutter doesn’t come back)

If your PC came with trialware or “helper” apps you won’t use, uninstalling is better than just disabling startup—because many apps re-add startup entries after updates. Windows 11 supports uninstalling from Start or from Settings > Apps > Installed apps. (support.microsoft.com)

1. Go to Settings > Apps > Installed apps.
2. Sort by install date (helpful on new PCs) and remove what you don’t use (trial antivirus, duplicate media players, vendor promos, etc.). (support.microsoft.com)

Reboot once when you’re done uninstalling (some removals clean up services/drivers on reboot).

Part 2 (the real boot-saver): Services cleanup using a safe Clean Boot method

Startup apps are only half the story, though. Quite a few of us have slow boots because of third-party services that load before/around sign-in (update services, telemetry, OEM “support” services, peripheral suites, etc.). The safest way to trim these is to follow the Microsoft-recommended clean boot procedure: hide Microsoft services first, then disable the other third-party services for the duration of this experiment, and add back only the ones you need. (support.microsoft.com)

Instructions for Windows 10 and 11:

1. Open System Configuration: press Windows+S, and type msconfig, and find System Configuration. (support.microsoft.com)
2. In the System Configuration window, go to the Services tab.
3. Check Hide all Microsoft services (this is your key safety step) (support.microsoft.com)
4. Click Disable all (this disables only the visible third-party services) (support.microsoft.com)
5. Click Apply.
6. Go to the Startup tab and from there, find Open Task Manager (support.microsoft.com).
7. In Task Manager > Startup apps, Disable the items that are enabled (make sure you keep track of what you’ve changed) (support.microsoft.com) and finally, close Task Manager, click OK in System Configuration, then Restart.

After you rebooted: decide what to keep (the “minimum comfortable boot” rule)

• You are in a clean-boot environment now (no third-party services, very few startup programs). Your PC may temporary lose functions—and this is expected (support.microsoft.com).
• Time your boot again (same rough method as you did your baseline). Test your essentials—audio, Wi‑Fi, Bluetooth, webcam, VPN, printer/scanner (only if you use them).
• If all the essentials you care about work and booting feels a lot faster, you’ve confirmed the slowdown was due to third-party background software.
• Now choose your end state—(A) keep it lean by re-enabling only key services/startups or (B) use this mode to help you identify one specific offender, then uninstall/update it.

The method that avoids guesswork—Re-enable (the “half at a time” approach).

If you’re after knowing exactly who among your apps or services is making your computer slow to boot, Microsoft’s best advice is to enable items in batches (often half at a time), rebooting several times and closing in on whoever the culprit is. (support.microsoft.com)

1. Open msconfig again > Services tab > Hide all Microsoft services.
2. Enable about half of the 3rd-party services you’d previously disabled.
3. Reboot and test how the boot speed is affected and whether you have basic functionality.
4. If the slowdown reappears, the offender is somewhere in the half you just enabled; if not, it is likely in the other half.
5. Rinse and repeat (halving the list each time) until you’ve found that single service (or small set) that’s slowing your computer down. (support.microsoft.com)
6. You know the lay of the land now—prefer updating/removing the parent software that contains the bad service over just disabling the random services.

Reset back to normal startup—don’t leave msconfig in the weird state

When you’re done testing, return Windows to a normal state following the reset steps in Microsoft’s clean boot guidance (Normal startup, re-enable services, and then re-enable the startup apps you actually want). (support.microsoft.com)

Should you disable services permanently in Services.msc? (Usually: no)

Permanently disabling services (Startup type Disabled) is a high-risk, low-reward endeavor for most home users; disabling certain services only when you notice problems, un-installing what you don’t need, and using clean boot only to troubleshoot problems, not as a long-term practice, is a safer overall strategy. Microsoft itself cautions against “one size fits all” policies for hardening services, since it’s easy to break needed functionality and create/download unintended side-effects. (learn.microsoft.com)

Optional (power user): find hidden auto-start entries with Microsoft Autoruns

Some auto-start items don’t appear obvious in Startup apps, particularly scheduled tasks, shell extensions, and service-related starts. Microsoft Sysinternals Autoruns is a trustworthy utility that displays multiple auto-start locations from one utility pane and lets you disable entries just by unchecking them. Use it prudently, and only disable things you can identify. (learn.microsoft.com)

1. Get a restore point first (don’t skip this). (support.microsoft.com).
2. Download Autoruns and run it (it’s from Sysinternals). (learn.microsoft.com).
3. Enable options that hide Microsoft/signed to help you keep the focus on 3rd party items (the goal is to reduce risk) (learn.microsoft.com).
4. Disable one thing at a time, reboot, and verify. If you don’t know what it is, skip it.

How to check you actually fixed slow boots (and make sure it stays fixed)

• Re-test boot time the same way you did with your baseline (rough and not an exact science, but it’s consistent).
• After sign-in, wait 60 seconds and see if you can start working on the system right away (Start menu opens right away, and File Explorer also opens fast).
• Check Startup apps once a month (or after big software installs) and turn off anything that starts again without your permission. (support.microsoft.com)
• When you can, rather than disabling “helper” suites in Startup apps, program 1 so that it can’t add services and startup tasks later on. (support.microsoft.com)

Troubleshooting: what to do when things go wrong

1. If a device stopped working after you turned off startup apps: re-enable the last 1 you disabled and reboot. (support.microsoft.com)
2. If a feature stopped working after the Services clean boot step: open msconfig and Services. Make sure Hide all Microsoft services is checked and re-enable possibly related 3rd party services (audio, printer, VPN, touchpad). (support.microsoft.com)
3. If it’s too much trouble to undo it: use System Restore to restore back to your “Before startup cleanup” restore point. (support.microsoft.com)
4. When you’re stable again, do the cleanup 1 more time, only change fewer things per reboot, so you always know what you did that caused the problem.

FAQ