Manage Learn to apply best practices and optimize your operations.

Conserve svchost.exe memory by disabling Automatic Updates

If your svchost.exe process seems to be consuming an inordinate amount of RAM and/or virtual memory, the culprit may be Windows Automatic Updates.

Ever wondered why the svchost.exe process seems to be consuming an inordinate amount of RAM and/or virtual memory?...

Do a Google search and you'll see that many other people are wondering why this memory-hogging occurs.

Wonder no more. The offending process is Automatic Updates. You can see the processes hosted by each svchost.exe by using Process Explorer by SysInternals. Just select the svchost.exe in question and choose 'properties'.

On our corporate computers, where access to Automatic Updates is blocked by a global policy setting (as is access to Windows Update itself), the Automatic Updates process gradually consumes more and more memory. After roughly three weeks, the svchost.exe in question was using about 200 MB of RAM and over 400 MB of virtual memory.

The solution? Disable the Automatic Updates service. Right-click on My Computer, select Manage, then select the Services tab and change the Startup Type for Automatic Updates to "disabled".

If you never use Automatic Updates, or Group Policy Settings do not permit usage of it, then there's no point running the service anyway. If you do use Automatic Updates, you may want to consider the NetChk Protect service by Shavlik Technologies, a lite version of their NetChk Pro patch management service, which is currently being offered for free for one year with licenses for up to ten machines. The service provides access not only to all Windows Update patches and updates, but Office Updates and patches from many other software vendors as well.

Please let us know how useful you find this tip by rating it below! If you have a useful Windows tip, timesaver or workaround to share, submit it to our tip contest and you could win a prize!

This was last published in August 2006

Dig Deeper on Windows Server and Network Security

Start the conversation

Send me notifications when other members comment.

By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Please create a username to comment.