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: Most helpful
  1. Anonymous
    2016-03-07T23:58:02+00:00

    Thanks lots.  Once I searched for KB ... 64 bit,  I got to right file.  Ran them both.  So far so good.  Now time ot turn on Updates.... !!!!  Really appreciate help.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-03-07T22:23:14+00:00

    Ken, I have a PC on my desk right now that I tried this on.....

    Your Step 4 produced a result that said the update failed.  KB3083710 -- produced an error 

    My next steps were to download KB947821 and KB3102810

    Disconnect the Internet

    Run KB947821, restart

    Run KB3102810

    Connect to the Internet

    Run WU, Update list in 5 minutes

    As you said, the entire process was quite quick.

    I am guessing the key may be to Internet disconnection

    I need to add here that it has become my practice to HIDE any WINDOWS update that is NOT labeled Security that is dated May, 2015 onwards.  This strategy is based on Woody Leonhard's telling us that Microsoft has not produced any update to Win7 that improve Win7.   I am presuming that all that come in that month or from that point onwards are either spy tools or things that accelerate the Win10 aggression.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-03-07T22:06:08+00:00

    You have to make the right choice.  I think there is a version for the 32- or 64-bit OS.  Choose the wrong one and you will get that message.

    I chose 64 bit with sp1 which is the load disk.  Will try again.  Thanks.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-03-07T19:37:31+00:00

    SAME PROBLEM HERE SO I TOOK YOUR ADVICE WITH A MODIFICATION.

    1-DOWNLOADED THE 2 UPDATES AS SUGGESTED

    2-DISCONNECTED THE INTERNET

    3-RESTART COMPUTER

    4- WITH INTERNET STILL DISCONNECTED INSTALLED FIRST UPDATE THEN RESTART

    5-REPEATED STEP 4 WITH INTERNET STILL DISCONNECTED

    6-RESTARTED COMPUTER AND THEN TURNED ON INTERNET

    7-CHANGED UPDATE SETTING TO - NOTIFY ME BUT DONT DOWNLOAD OR INSTALL

    8-CHECK FOR UPDATES

    9-256 + UPDATES APPEARED IN ABOUT 5 MINUTES AND INSTALLED THEM 50 AT A TIME

    THANKS VERY MUCH FOR YOUR HELP.

    PS LOOKS LIKE MICROSOFT HAS SCREWED UP AGAIN

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-03-07T14:39:10+00:00

    I have experienced this.  The 32 bit is not labeled 32.  The 64 bit version is labeled 64.  Easy to make this mistake.  Classic M$.  So, it you want the 64 bit, use 64 as part of the search term.

    Was this answer helpful?

    0 comments No comments