Visit Website →
← Back to blog

Diagnose First: Windows Background Services You Can Set to Manual

September 25, 2026
Diagnose First: Windows Background Services You Can Set to Manual

Diagnose before you touch anything. Run a clean boot or scan Task Manager's startup tab first, then set the handful of genuinely optional services to Manual rather than Disabled. A short, well-tested list of services (SysMain, Windows Search, Print Spooler, and a few others) covers most of the safe changes. Start in services.msc for services and Settings for background apps, and never disable something you haven't identified.

TL;DR:

  • Running a clean boot using msconfig and halving suspect services helps accurately identify if a non-Microsoft service causes system slowdown before making changes.
  • Most safe service adjustments involve setting SysMain, Windows Search, Print Spooler, or Fax to Manual only if their functions are unnecessary, avoiding core security services like Cryptographic Services and Windows Defender Firewall.
  • Disabling per-user services is an advanced step, as some only appear after sign-in, and over-disabling services can risk system stability or security features.
  • Changes to service startup types can be easily reverted via services.msc or command line, but significant risks remain if critical security or network services are disabled.
  • Using tools like Autoruns and adherence to diagnostic steps over blind disabling guides minimize the chance of breaking essential system functions.
Tempered
tempered.to
Optimize Windows With More Control
Tempered identifies real performance constraints, explains each proposed change, and keeps an undo path for adjustments you approve.
Explore Tempered

Table of Contents

How to View the Windows Background Services List and Spot the Difference From Apps

Press Win+R, type services.msc, and hit Enter. That opens the full Windows background services list, sorted by name, status, and startup type. It's the authoritative view of what Windows itself runs behind the scenes.

Task Manager gives you two other angles: the Processes tab shows what's actively consuming CPU or memory right now, and the Startup apps tab (moved out of Task Manager into Settings on recent builds) shows what launches when you sign in. Neither replaces services.msc, but both help you correlate a slow boot with an actual culprit.

Background apps are a different animal entirely. Go to Settings > Apps > Installed apps, or Privacy & security > Background apps, to control how UWP and Store apps behave when minimized. Windows 11 lets you set each app to Always, Power optimized, or Never, with Power optimized as the sensible default for most people.

One catch worth knowing: per-user services get created only after you sign in, so some auto-start items never show up in services.msc at all. That's an edge case most basic guides skip, but it explains why a service you expect to see sometimes isn't there.

Quick rule for deciding where to look:

  1. If the item is a UWP or Store app, manage it in Settings under Background apps.
  2. If it's a traditional desktop application, control it through the app's own preferences or its Startup entry in Task Manager.
  3. If it's a true Windows service, services.msc is the only correct place to change it.

How Do You Diagnose a Slow PC Before Changing Anything?

Guessing which service is slowing you down almost always wastes time. Microsoft's own troubleshooting path uses a clean boot and it's worth following exactly as documented rather than improvising.

  1. Open the System Configuration tool by typing msconfig into the Start menu.
  2. On the Services tab, check Hide all Microsoft services, then click Disable all.
  3. On the Startup tab, open Task Manager and disable every startup item.
  4. Restart. If the problem disappears, one of the disabled items was responsible.
  5. Re-enable half of the disabled services, restart, and check again. If the problem returns, the culprit is in that half; if not, it's in the other half.
  6. Repeat this halving process, cutting the suspect group in two each time, until one service remains.

This binary-halving approach is the exact method Microsoft documents for isolating a problematic non-Microsoft service, and it also shows up in Microsoft's own Q&A guidance for Windows 11. It takes a handful of restarts, but it converges fast because each round eliminates half the remaining suspects.

If a clean boot doesn't reveal anything, the issue may live outside services entirely, in a shell extension, scheduled task, or driver. That's where Sysinternals Autoruns earns its keep. It lists every auto-start location on the system, including the ones services.msc and Task Manager simply don't show.

Pro Tip: Sort Autoruns by publisher and hide anything signed by Microsoft first. What's left is almost always where the actual problem lives.

Which Windows Services Are Commonly Safe to Change?

Here's a working list of services people commonly adjust, what each one actually does, and what to set it to. Treat "Manual" as the default recommendation over "Disabled" unless noted otherwise.

  • SysMain (Superfetch): Preloads frequently used apps into RAM to speed launches. On SSDs it can add unnecessary disk activity with little benefit. Recommended: Manual. Revert by switching back to Automatic if boot or app loading feels slower afterward. More on disabling SysMain here.
  • Windows Search: Indexes files and email for fast search results. Heavy on disk I/O during indexing, especially on older hard drives. Recommended: Manual if you rarely use Windows Search; leave Automatic if you search constantly. Revert instantly by flipping it back.
  • Print Spooler: Manages print jobs and queues. If you never print, it's dead weight; if you do, disabling it breaks printing outright. Recommended: Manual for non-printing setups, Automatic if you own a printer.
  • Connected User Experiences and Telemetry (DiagTrack): Collects diagnostic and usage data for Microsoft. Some users set it to Manual for privacy reasons; it has minimal effect on performance either way. Recommended: Manual.
  • Update Delivery Optimization: Shares Windows Update files with other PCs on your network or the internet (like a mini peer-to-peer network for patches). Can spike upload bandwidth on metered connections. Recommended: Manual on limited bandwidth connections.
  • Windows Error Reporting: Sends crash data to Microsoft. Rarely resource-intensive, but some people disable it for a quieter system. Recommended: Manual.
  • Windows Biometric Service: Supports fingerprint and facial recognition sign-in. Skip changing this if you use Windows Hello. Recommended: Manual only if your device has no biometric hardware.
  • Remote Registry: Allows remote users to modify your registry. Almost nobody needs this on a home PC. Recommended: Disabled is reasonable here, since it's rarely used and carries a security angle.
  • Fax: A legacy service for fax hardware that essentially nobody uses anymore. Recommended: Manual.
  • MapsBroker (Downloaded Maps Manager): Manages offline map downloads for the Maps app. If you never use Maps offline, it's unnecessary. Recommended: Manual.
  • Xbox-related services (Xbox Live Auth Manager, Xbox Live Networking Service, etc.): Support Xbox app features and cross-device play. If you don't use Xbox integration, these can move to Manual without consequence.

Some services should stay untouched no matter how aggressive your cleanup gets: Cryptographic Services, Windows Event Log, and Windows Defender Firewall underpin security, logging, and update verification. Disabling any of them risks breaking Windows Update, app installs, or your firewall protection entirely.

Domain-joined machines, servers, and PCs with specialized hardware (network printers, smart card readers, biometric scanners) need extra caution. A service that looks pointless on a home laptop might be load-bearing on a work machine tied to a company network.

How Do You Change a Service's Startup Type and Undo It?

Changing a startup type in services.msc is a five-click job:

  1. Open services.msc and find the target service in the list.
  2. Double-click it to open its properties window.
  3. Use the Startup type dropdown to pick Automatic, Automatic (Delayed Start), Manual, or Disabled.
  4. Click Stop if the service is running and you want to test the change immediately, or Start if you're re-enabling one.
  5. Click Apply, then OK.

Advanced users sometimes prefer the command line. The sc.exe tool can create or modify a service with a start= parameter set to auto, demand (Manual), disabled, or delayed-auto, as documented in Microsoft's sc.exe reference. Dependencies matter here: stopping a service that others rely on can cascade failures, so check the Dependencies tab before changing anything critical.

Before you change a single setting, write down the current startup type, or take a quick screenshot of the Services window. If something breaks, you can flip the setting back manually, or use System Restore to roll the whole system back to a known-good point.

What Are the Real Risks of Disabling Services?

Modern hardware runs most services efficiently in idle states already, so the performance gain from disabling a handful of them is often smaller than people expect. Windows tends to start services only when something actually needs them, which means blanket disabling rarely moves the needle much and adds real risk of breaking a feature you didn't realize depended on it.

Some categories should never be touched: anything tied to security (Windows Defender, Cryptographic Services), core networking (DHCP Client, DNS Client), or Windows Update. Breaking one of these can knock out your internet connection or leave your system unpatched.

Test any change for about a week before deciding it's permanent. If nothing breaks and performance genuinely feels better, only then consider whether Disabled is worth the small extra step over Manual.

Pro Tip: Keep a simple undo log, service name, old setting, new setting, date changed, and try Manual for seven days before ever touching Disabled. Manual services still run when needed; Disabled ones don't run at all, even if something suddenly requires them.

What Are the Real Risks of Disabling Services? — overview diagram

Why Tempered Approaches Background Services Differently

Most guides on managing the Windows background services list assume you're comfortable poking around services.msc and remembering what you changed. That's a reasonable assumption for many readers, but it's also exactly where manual cleanups go wrong: a setting gets changed, three weeks pass, and nobody remembers why a printer stopped working.

Tempered was built around that gap. It reads live hardware metrics (CPU, RAM, GPU, disk, uptime) and flags specific, measured constraints instead of applying generic tweaks. Every suggested change comes with a plain-language explanation, an expected outcome, and a one-click undo path, so testing a change for a week (the same approach recommended above) doesn't require you to keep a manual log at all. If you'd rather have that process automated than track it yourself in a spreadsheet, that's the gap Tempered fills.

The Checklist Most Guides Skip

The advice floating around most forums treats the Windows background services list like a to-do list: disable this, disable that, reboot, done. That's backwards. The diagnostic step, the clean boot and the msconfig binary search, is the part that actually matters, and it's the part most people skip because it takes fifteen extra minutes.

Diagnostic workflow for isolating Windows services

Here's what the evidence actually supports: on most modern PCs, the performance ceiling from disabling services is lower than people expect, and the risk of breaking something is higher than people admit. The conventional wisdom oversells "disable everything Microsoft doesn't need" and undersells "figure out what's actually slow first."

If you take one thing from this, prioritize the diagnosis over the list. Run the clean boot. Use Autoruns if services.msc comes up empty. Then, and only then, work through the short list of commonly safe changes, one at a time, on Manual, watched for a week before anything gets set to Disabled. An automated tool can shortcut that process, but the discipline behind it, measure first, change one thing, keep a way back, is the same either way.

For anyone who wants that discipline handled automatically, with every change explained and reversible, Tempered's plans start with a free tier before scaling into the Torque and Torque Max tiers for unlimited scans.

— Ian

FAQ

What Windows 11 background services should I disable?

There's no universal list, since every PC's usage differs, but SysMain, Windows Search, Print Spooler, and Fax are commonly safe candidates to set to Manual if you don't use their functions. Avoid touching Cryptographic Services, Windows Event Log, or Windows Defender Firewall, since those support core security and system stability.

What are some useless services I should disable in Windows 10?

Fax, Remote Registry, and MapsBroker are frequently unused on typical home PCs and can be set to Manual without noticeable downside. Manual is generally the safer choice over Disabled, since a Manual service still starts when something genuinely needs it.

What background apps should I turn off?

Check Settings under Apps or Privacy & security for Background apps, where you can set individual apps to Always, Power optimized, or Never. Power optimized is the recommended middle ground for apps you use occasionally but don't need syncing constantly.

Why do I have so many background processes running on my computer?

Windows itself runs dozens of core services for networking, security, and system maintenance, and installed apps add their own background processes and scheduled tasks on top. Running a clean boot through msconfig isolates whether a specific non-Microsoft service or startup app is adding unnecessary load, following the same halving method Microsoft documents.

How do I see a complete list of Windows services for documentation or backup?

Open PowerShell and run Get-Service | Export-Csv services_backup.csv to export every service, its status, and startup type to a file you can reference later. This gives you a dated record to compare against if a future change causes unexpected behavior.