Following a clean install, Windows Update remains at "Checking For Updates" forever...

Anonymous
2016-01-19T16:22:55+00:00

I've reloaded hundreds of Windows computers over the years and I like to think that I am reasonably proficient at that process.  I have just encountered an issue that required a lot of time and effort to resolve and I am posting this to try and save someone else the same ordeal.

My customer had a late model, name-brand Windows 7/64 SP1 computer with a disk drive that was failing.  I changed out the disk drive with a replacement and went through the recovery process, using the manufacturer-provided Recovery Media.  That media is supposed to be identical to the image loaded on the drive from the factory - Windows 7/64 with SP1.

Following the reload, I followed my normal procedure and launched Windows Update.  Windows Update remained at "Checking for Updates" for hours, without ever displaying any updates to install.  I restarted the PC and tried again, with exactly the same result.  The Software Distribution folder would get built and there were plenty of entries in WindowsUpdate.log, but eventually disk activity would cease but CPU activity would remain over 50%.  And Windows Update just showed "Checking for Updates" forever.

I decided the reload must have been bad and so I repeated it from scratch again with exactly the same result.  At that point I decided the image on the manufacturer's Recovery Media must be defective and so I reloaded from my MS Partner Program Windows 7/64 SP1 DVD.  I had the same exact symptoms and result again.  I thought that maybe I was not waiting long enough, so I left it running overnight.  The next morning, it was still at "Checking for Updates".

I tried additional reloads using SURT and that also remained at "Checking for Updates" without accomplishing anything.  I tried using the Windows Update Troubleshooter - with no luck.  Ditto for manually resetting Windows Update and various combinations of these techniques.  I verified that Windows was activated and that date/time were correctly set.  Nothing made any difference.

I then started meticulously documenting everything as I went along and I think I've found a solution:

After the reload, I checked the Windows Update components in C:\Windows\System32. The components are wuapi.dll, wuapp.exe, wuaclt.exe and wuaeng.dll and all are version 7.5.7601.17514 dated 11/20/2010.  Once you launched Windows update or run SURT, these are all updated directly to version 7.6.7600.320.  At that point, I get the symptoms described above and there doesn't appear to be any way to recover.

When Windows Update is launched, it first updates itself automatically and without the user having any option.  It appears that upgrading the WU components from7.5.7601.17514 directly to 7.6.7600.320 causes the issue.  I suspect that it works fine for computers that are updated incrementally.

Once WU version 7.6.7600.320 is loaded, there is no easy recovery that I could find.

CURRENT PROCEDURE:

  1. Download https://support.microsoft.com/en-us/kb/3020369 and https://support.microsoft.com/en-us/kb/3172605 in advance.
  2. Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.
  3. Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.
  4. When the installation prompts for updates, choose "Ask Me Later".
  5. Apply KB3020369 and then KB3172605 in that order.
  6. Restore the Internet connection, configure update settings to your preference and launch Windows Update as normal.

Credit to Canadian Tech, Volume Z and other contributors for developing this current procedure.

ORIGINAL PROCEDURE FROM JANUARY 19 2016 HAS BEEN DEPRECATED BY THE NEW PROCEDURE ABOVE:

  1. Download KB3083710 and KB3102810 in advance.
  2. Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.
  3. Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.
  4. Manually install KB3083710 and restart - WU components will now be version 7.6.7601.19016 dated 9/25/2015.
  5. Manually install KB3102810 and restart - WU components will now be version 7.6.7601.19046 dated 10/20/2015.
  6. Restore the Internet connection and launch Windows Update as normal.
  7. After a few minutes, you should have plenty of updates to download and install.

Ken Morley

Windows for home | Previous Windows versions | Windows update

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.

0 comments

580 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-03-15T00:33:47+00:00

    I've hidden every update to Windows Update Client for the past year...

    All Windows Update Agent updates released in the past year have been optional, non-security updates (yes, even though one or more may have been offered as an Important update).

    Tip => If you want Windows Update to continue working properly, don't hide any "Servicing Stack" updates!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-03-14T11:16:59+00:00

    XX:

    The simple solution would be to load the image again on the PC and then follow the seven steps listed on the first page of this post.

    I also tried SURT, cleaned out Software Distribution and myriad other suggestions and nothing worked.  But the seven-step process appears to work every time.

    This issue appears to be a defect with a version of the WU components on the WU website.  Depending upon what version of WU is on the image you load, WU may try to update itself when it first connects.  Be aware that, unlike other updates,  WU updates itself without notice, warning or requesting permission.  If WU updates itself with the version on the WU website, you get the "Checking for Updates" forever symptom and there is no easy way to recover other than to reload another image.

    Following the seven step process avoids the defective WU update from the WU website, thereby avoiding the problem.

    Good luck!

    Ken Morley

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-03-14T11:06:26+00:00

    Yep mine was also a 32 bit system having the issues

    Dual core too so I just recently started using RealTemp to monitor temperatures is the only way I noticed the weird cpu usage which also made the temp's rocket

    http://www.techpowerup.com/downloads/2089/real-temp-3-70/mirrors

    Not sure how many people if any has used disk cleanup and cleanup system files and removed outdated windows updates ?

    I know I have and this might be a bug using it :/

    Also I've now downloaded Net framework 4.6.1 when I would usually just stick with net 4.5.2 or on my 32 bit system with the noticeable issues it had net 3.5.... still I have no programs that require a higher net :/

    But it has 4.6.1 now just for good measure :p

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-03-14T08:32:30+00:00

    I can tell you with assuredness, that under the circumstances described by Ken Morley, this process absolutely works and works every time.  I have done this on computers on my desk and it works as if magic.   I have taken the liberty of re-drafting his procedure

    Windows Update fix (new)

    The following procedure applies in the case of install (re-install) of Windows 7.  It does not apply to usual, normal updating.

    I am afraid you are going have to do the re-install again.  Not a terrible penalty to pay.  Usually takes way less than an hour.  Then, immediately proceed with the following procedure.   It is strange, but it really does work and a lot of people have proven it.

    NEVER install anything but Windows Updates until your system is up to date.

    1. BEFORE you start the re-install, download (32 or 64 bit) KB3083710 and KB3102810 in advance, and store on a USB stick
    2. Start and complete the re-install of Windows 7 SP1
    3. Immediately after install is complete, disconnect the computer from the Internet.
    4. Manually install KB3083710 and restart.
    5. Manually install KB3102810 and restart.
    6. Restore the Internet connection and launch Windows Update as normal.
    7. After a few minutes, you should have plenty of updates to download and install.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-03-14T07:02:22+00:00

    I've got an x86 running Win 7 Home Premium with the 7.6.7601.19046 version of all components, and just started getting this error a few days ago.

    I reimaged from a June 2015 disk image, with whatever the current version of the components was then, and got the same error. I then ran the fix that MS put out for these symptoms (KB3102810) which got me back to 7.6.7601.19046. (I also ran the SURT (KB947821) from Oct 2014, but don't think that's relevant at this point.) I'm still getting the eternal "searching for updates", though, with one core maxed out by wuaueng.dll. I manually cleared out C:\Windows\SoftwareDistribution\DataStore and C:\Windows\SoftwareDistribution\Download, per MS's instructions, but DataStore fills back up with a bunch of log files in minutes.

    I don't run an AV, and the only weird thing about my system is that it's dual-boot Linux. I've had this setup for months, though, and run WU manually every week or two (system is usually off, and I only use it 1-2 days per week), without problems.

    After wasting nearly an entire day of precious weekend time researching this nonsense, I fear the end is nigh for my use of Windows. I'm going to try restoring using an even older image (maybe with just SP1), but if that fails, I'm just going to stop connecting my computer to the internet.

    Was this answer helpful?

    0 comments