Try this one,
August 2015 Windows Update for Vista Requires One Hour to Run to Completion
Is Microsoft throttling bandwidth for users running Windows Update on Vista machines to give a higher priority to Win 10 users?
I've run multiple Windows Updates since Patch Tuesday on 11-Aug-2015 and couldn't get them to run to completion on my 32-bit Vista machine until 16-Aug-2015. There were no errors - it just reported that it was checking for updates and never finished, even if I let it run for over an hour. Process Explorer showed svchost.exe constantly consuming ~50% of my CPU (i.e., complete saturation of one of my Intel Duo cores) and that a thread for the Windows Update service (wuauserv) was responsible for all that CPU activity.
I assumed that my Windows Update service was corrupted but after reading posts by other Vista users having the same problem (see ScousaJay's post *Windows Update Just Seems to Hang While Checking* in the Windows VistaForums for one example) I tried a manual update again on 16-Aug-2015. Windows Update finally ran to completion and offered 17 important updates and one optional update for Silverlight but it took approx. 35 min before it reported that updates were available and the entire process, including the downloads, installs and monthly Malicious Software Removal scan, took almost a full hour. A typical Patch Tuesday normally takes about 10 min on my machine from start to finish.
Here's what the CPU consumption looked like for my successful Windows Update of 16-Aug-2015, with the "Checking for updates..." phase running between the 70 and 35 min marks and re-start to complete the installation around the 15 min mark.
32-bit Vista Home Premium SP2 * Firefox 40.0.2 * IE9 * NIS 2014 v. 21.7.0.11
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS
Windows for home | Previous Windows versions | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
47 answers
Sort by: Newest
-
Anonymous
2016-05-27T06:49:59+00:00 -
Anonymous
2016-05-26T21:29:59+00:00 I think we have to seriously wonder why this company hasn't already fixed this problem for us.
I think, for one thing, there are too many people posting on various sites around the Net for it to be claimed by company executives that this should not be a concern for them because it is only bothering a few people with bad machines. In other words, I think we can point the finger at Microsoft being at the heart of the problem without being shot down as fools.
By the way, I used the "turn off Windows Update" technique to stop the Task Manager from going beserk all the time and I see that the MSE program still gets its updates without any trouble. I assume somebody has already posted that information, but I will confirm that turning off Windows Update doesn't cause trouble with MSE, if anyone is interested.
A question, if I may, is there any other thread on the Net that can claim to be the definitive thread on this topic?
-
Anonymous
2016-05-24T14:10:34+00:00 Here are a few more Vista users who reported the temporary workaround suggested in my previous 16-May-2016 post significantly reduced the time "Checking for updates..." spent searching for available updates. If you managed to install your April 2016 Patch Tuesday updates last month you should only have to pre-install one missing Win32k.sys update listed on Dalai's webpage ***Search for Windows Updates takes forever? - A possible solution*** - KB3153199 - before running Windows Update to download your remaining May 2016 Patch Tuesday updates.
copiman: Current tips on updates
Ichabod22: Vista Windows update hangs with "checking for updates"
Intelektualista: *Windows Vista Update Hangs at "Checking For Updates"*
SorinCas: Windows Vista Won't Install New Updates After SP2 Installed
Just an aside, but I also posted comments in post # 162 of the VistaForums thread windows update just seems to hang while checking about a similar problem that Win XP users experienced three years ago after Win 8.1 was released. From Woody Leonhard's old November 2013 article Microsoft to fix Windows XP update SVCHOST redline issue 'soon':
"In other words, when you run Windows Update, the program has to bang against Microsoft's internal database of patches and figure out which patches need to be applied and which ones have been superseded and can be ignored. Since IE6 and IE7, in particular, have been around since the dawn of time, that's an enormous pile of patches to sort through."
I don't know if Vista is currently suffering from the identical issue but I wonder now if Microsoft could permanently fix these slow Windows Updates in Vista and Win 7 by expiring some of the outdated updates in the supersedence chain for programs like the IE browser and the MS .NET Framework.
32-bit Vista Home Premium SP2 * Firefox v46.0.1 * IE9 * NIS v21.7.0.11
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS
-
Anonymous
2016-05-16T14:41:26+00:00 I should also mention that Woody Leonhard's InfoWorld article Windows 7 update scans taking forever? KB 3153199 may solve the problem suggests that that pre-installing monthly Windows kernel-mode driver (Win32k.sys) updates like KB3145739 (Apr 2016) and KB3153199 (May 2106) from the Microsoft Download Center every month can "trick" Windows Update into running Patch Tuesday updates faster - at least for Win 7 users
- but it's only a temporary solution and the problem will return the next month. Feedback <here> on the AskWoody.com site confirms that many Win 7 users are having success with this workaround. Woody Leonhard posted a link to ***Search for Windows Updates takes forever? - A possible solution*** that tracks the recommended win32k.sys update (both Win 7 and Vista) that must be installed each successive month before running the Patch Tuesday updates. From the author of that webpage:
"The term 'solution' might be a little bit exaggerated, since the following HowTo only tries to make sure that the Update Agent doesn't need to check all updates, so the check for new updates is done faster. Futhermore, it's only a temporary solution; most likely the issue will appear again with the next Patchday."
I haven't tried this workaround yet, but there are a few users in the VistaForums thread *windows update just seems to hang while checking* who tried pre-installing KB3153199 before running their May 2016 Patch Tuesday updates and reported that it allowed them to install their remaining updates in a reasonable amount of time.
32-bit Vista Home Premium SP2 * Firefox v46.0.1 * IE9 * NIS v21.7.0.11
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS
-
Anonymous
2016-05-16T13:43:27+00:00 It's been 10 months now since I first reported this issue and the problem is only getting worse. There are now multiple threads in multiple forums where Vista users see the initial "Checking for updates..." phase of Windows Updates hang for long periods of time during Patch Tuesday updates. In my case "Checking for updates..." ran for 4 - 5 hours during my April and May 2016 Patch Tuesday updates before it reported that updates were available for download.
Here's a sample screenshot from my March 2016 Patch Tuesday updates. The last hour of the "Checking for updates...." phase (between the 90 and 30 min marks) was the constant consumption of ~ 50% of my CPU by the Windows Update service (wuauserv) running under svchost.exe. The download of 11 available updates, installation, and monthly Malicious Software Removal Tool scan completed normally between the 30 and 10 min marks. The dark grey band at 5 min was the system restart to complete the installation.
The Windows Update Agent (WUA) at C:\Windows\system32\wuaueng.dll on my 32-bit Vista system is currently v7.6.7600.256 and hasn't been updated since June 2012. If Microsoft isn't deliberately throttling bandwidth for Patch Tuesday updates to give priority to Win 10 users then perhaps it's about time that they released an update for the WUA to fix this problem.
32-bit Vista Home Premium SP2 * Firefox v46.0.1 * IE9 * NIS v21.7.0.11
HP Pavilion dv6835ca, Intel Core2Duo T5550 @ 1.83 GHz, 3 GB RAM, NVIDIA GeForce 8400M GS