New
#31
Personally I believe it to be server traffic,
The default setting is to check for updates at 2am = off peak hours.
Windows Update Hangs at "Checking for Updates"
-
-
-
New #33
Personally I've experienced 1 - 2 Gb memory usage by svchost netsvcs when windows update is running a few times during the last six months.
I also experienced windows hanging when checking for updates and sure - if you leave it checking overnight it does eventually find the updates.
According to the experts 1 -2 Gb memory usage by svchost is perfectly normal and there's nothing to worry about and all you need to do is install more RAM.
Funny thing is that when I manage to fix it (it's not easy) memory usage returns to normal levels during scheduled windows update checks. I still haven't figured out what causes it. Whenever I see it - datastore.edb seems to be the culprit.
-
New #34
One of the more recent updates was actually designed to reduce the amount of resources taken up by Windows Update, especially in low-spec computers.
It did appear to have some effect - but I really don't know how much.
-
New #35
Well, as my motherboard can only handle 4GB of RAM, installing more is not an option.... When Windows Update is actually doing its job (searching for and installing updates), it uses normal amounts of memory. It only ever starts leaking when it is running idly in the background. Keep me in the loop if you gather more information about the cause.
-
New #36
the svchost process is a catch-all, and covers a large number of services (not just WU). you possibly need to look in more detail using the Resource Monitor instead to try and work out the actual culprit - you may even find that it's WebRoot.
-
New #37
Well, the leaking happened this most recent time after I had already uninstalled WebRoot. But if the leaking stops as soon as the WU service stops, I thought that was confirmation that the leaking was coming from WU?
-
New #38
Not at all - it could be that something else is blocking or being blocked by WU.
You have found an effect with multiple potential causes, and you need to whittle these down.
-
New #39
Webroot used to have a special uninstaller now it's just type appwiz.cpl in the start menu search and enter :/
-
Quote
Related Discussions