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 No comments

580 answers

Sort by: Oldest
  1. Anonymous
    2016-03-11T22:42:40+00:00

    I was criticized for naming AV companies.  But, as long as you are at this, I recommend Bitdefender AV.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-03-11T23:04:14+00:00

    Ha this and other forums see hundreds if not thousands of issues from just those 3 on my signature :)

    I could list a few more but there's character limit :(

    Criticized by whom ?

    That has been on my signature for quite a few years and many have complained = too bad the truth hurts :p

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-03-13T21:50:50+00:00

    Ken,

    I understand that Windows Update version 7.6.7600.320 is causing problems.

    Have you (or anyone) tried installing a version released AFTER 7.6.7600.320 to see if the problems remain?

    For example, the February 2016 updates for Windows 7 included KB3138612. Microsoft's description of KB3138612 states that it updates Windows Update component's to version 7.6.7601.19161.

    I wonder if that version is "safe" ... by "safe" I mean ...

    1. Does it result in "Checking for Updates" being displayed forever.
    2. Does it attempt to coerce a Windows 10 installation.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-03-13T23:00:43+00:00

    FWIW...

    • Windows Update Client for Windows 7 and Windows Server 2008 R2: March 2016 (KB3138612) installs Wuauclt.exe version 7.6.7601.19161 (superseding KB3135445).
    • Windows Update Client for Windows 8.1 and Windows Server 2012 R2: March 2016 (KB3138615) installs Wuauclt.exe version 7.9.9600.18235 (superseding KB3135449)

    If all were well with your Win7 or Win8.1 computer, the appropriate update above would have been offered & installed via Windows Update on or after 01 March 2016.

    ========================================

    Note: Neither KB3135445 nor KB3135449 is a mandatory or security-related update.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-03-14T00:26:29+00:00
    • Windows Update Client for Windows 7 and Windows Server 2008 R2: March 2016 (KB3138612) installs Wuauclt.exe version 7.6.7601.19161 (superseding KB3135445).

    If all were well with your Win7 or Win8.1 computer, the appropriate update above would have been offered & installed via Windows Update on or after 01 March 2016.

    Thanks Robear.

    I am running Windows 7 (and wish to continue to do so ... I have no desire to install Windows 10).

    Windows Update did offer KB3138612 to me in the February Updates. I hid KB3138612 and did not install it.

    My rationale: Microsoft's description of KB3138612 said that it contained some unspecified "improvements" to the Windows Update Client. Based on Microsoft's past behavior (in trying to coerce users to install Windows 10), I no longer trust Microsoft. Updates that provide unspecified "improvements" to the Windows Update Client might fix bugs and improve performance (of the Windows Update Client) ... but the unspecified "improvements" just might be yet another tactic for getting Windows 10 installed. So, I opted to hide KB3138612 (and have hidden KB3135445).

    For the reasons mentioned above (lack of trust in Microsoft), I've hidden every update to Windows Update Client for the past year. I am not experiencing any problems with the Windows Update Client, and do not want to take any chances.

    Was this answer helpful?

    0 comments No comments