A man studies a computer monitor displaying a memory usage chart and a list of running processes.
A MakeUseOf writer says three Windows services on their 8 GB DDR4 PC used more idle RAM than their web browser, and that disabling them freed memory for apps they actually use. The measurements are one person's PC and one set of moments, so treat them as an anecdote. The method and the cautions around it are worth understanding.

A man studies a computer monitor displaying a memory usage chart and a list of running processes. What the author measured​

Manuviraj Godara used Sysinternals Process Explorer instead of Task Manager, and watched the Working Set column while Windows sat idle. The article doesn't give the Windows edition, build, browser, measurement length or any before-and-after "available memory" figure.

The biggest Windows process the author saw was the Microsoft Defender Antivirus service (MsMpEng.exe), which they left alone. The three services they changed, with the ranges they reported at different idle moments, were:

ServiceReported idle memoryWhat the author did
Print Spooler (spoolsv.exe)22–70 MBSet to Manual (no printer owned)
Connected User Experiences and Telemetry (DiagTrack)56–163 MBDisabled outright
Click-to-Run (ClickToRunSvc)31–150 MBSet to Manual (no Office use)

The author also turned off Windows Search (WSearch) and Phone Link. They put the Phone Link processes (CrossDeviceService.exe and PhoneExperienceHost.exe) at around 180 MB combined.

Note that DiagTrack was disabled, not set to Manual. The article blurs this in places, and the difference matters, as covered below.

Why a Working Set number isn't a guaranteed saving​

Microsoft's documentation says the working set is the set of memory pages touched recently by a process's threads. Microsoft's Win32 documentation adds that it covers both shared and private data, and that the shared part includes the pages holding the instructions the app executes, including system DLLs. In other words, the number isn't memory that belongs only to that service.

Two practical consequences follow:

  • Working set shrinks under pressure. Microsoft's guidance, as relayed in a TechNet forum answer, says pages stay in a working set when free memory is above a threshold, even if unused, and get trimmed when free memory falls below it. On a plentiful-RAM machine the figure can look inflated. On a squeezed 8 GB machine it may fall without you doing anything.
  • Private memory is the better "what would I get back" clue. Task Manager's own columns separate private working set (can't be used by other processes) from shared working set. Process Explorer exposes similar private-versus-shared breakdowns, so check those before drawing conclusions.

The honest test is system-level. Note Available memory in Task Manager's Performance tab at idle, change one service, reboot, wait the same amount of time, and compare. The article never did this, so its "several hundred MB" gain is an estimate, not a measurement.

There's also a side effect to know about. The svchost.exe article on Wikipedia notes that on client systems with more than 3.5 GB of memory since Windows 10 version 1703, services no longer share host processes and each runs in its own process. That is why individual services show up as separate line items, with a bit of overhead each. It is also why the author's hover-over-the-svchost trick works when a service still sits inside a shared host.

Service by service: what changing it really means​

Print Spooler​

Microsoft describes the spooler as the component that is loaded at system startup and runs until shutdown (per Microsoft's Win32 print documentation). Its job covers locating and loading printer drivers, spooling print calls into jobs and scheduling them. "No printer" is the author's situation, not a universal one. Network printers, PDF or "print to file" virtual printers and any software that prints through Windows all lean on it. Set it to Manual and the first print attempt may fail or stall until the service is started.

Click-to-Run​

Microsoft's Microsoft 365 Apps documentation explains that installation creates a scheduled task called Office Automatic Updates 2.0, which checks for updates regularly, and that Click-to-Run then unpacks downloaded files and applies them in the background. If Microsoft 365 apps are not installed, the author's logic holds. If they are installed, leaving the service off risks missing security updates. Microsoft documents this workflow but does not suggest disabling it, so for Office users the better lever is probably update policy, not the service.

DiagTrack​

This is the most delicate of the three. Microsoft's privacy documentation separates diagnostic data from required service data, which is sent so connected features can function and is unaffected by the diagnostic-data settings you pick. So the DiagTrack service isn't a universal off switch for Windows data collection, and Microsoft's pages reviewed here don't establish that disabling it is safe on every system. Managed or enterprise PCs may also have policy that re-enables it, so check your organisation's rules first.

Manual versus Disabled​

The author prefers Manual because the service then won't run unless needed. That's broadly right, but Manual is not "never". A manual service can still be started by an application or by a trigger. Microsoft's service documentation notes that trigger-start services consume no resources until their trigger fires, as opposed to auto-start services that run from boot to shutdown. A Disabled service can't be started at all until you change it back, which is why a Disabled setting is the likelier one to break a feature quietly.

A cautious way to try this​

This is editorial advice rather than a Microsoft checklist:

  1. Open Process Explorer (procexp64.exe for 64-bit, procexp.exe for 32-bit, procexp64a.exe for Arm) and sort by Working Set. Process Explorer's page says it runs on Windows 11 and Windows Server 2019 and later for current builds.
  2. Hover over any svchost.exe entry, or right-click and choose Properties, to see which service sits inside it.
  3. Record Available memory in Task Manager before you change anything.
  4. Press Windows key + R, type services.msc, press Enter, right-click the service, choose Properties and note its current Startup type.
  5. Change one service at a time, preferring Manual. Reboot, wait, and compare Available memory.
  6. Test the related feature (print a page, run Office updates, use Phone Link). If it breaks, restore the original Startup type.

Our take​

The real lesson isn't "disable these three". It's that Working Set is a noisy gauge, that the savings on a roughly 8 GB machine will be modest, and that a feature you never use is a better target than a service you merely don't recognise. Phone Link, for example, accounted for more reported memory than any single named service in the article. If your PC has 16 GB or more, the tidy-up probably isn't worth the risk of a surprise breakage.

Leave Defender alone, as the author wisely did. And if a service name sounds boring, that doesn't mean it's idle: it may be quietly doing something your next Windows Update needs.

 

References

  1. I measured what Windows services actually use at idle, and 3 cost more RAM than my browser MakeUseOf 2026-10-24T17:00:19+00:00
  2. Memory Performance Information - Win32 apps | Microsoft Learn learn.microsoft.com
  3. Process Working Set - Win32 apps | Microsoft Learn learn.microsoft.com