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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-03-15T02:54:26+00:00

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

    How would I find a list of all Windows 7 x64 "Servicing Stack" updates released in the past year? I searched on:   Windows 7 x64 "Servicing Stack" updates, and found KB3020369  [which I installed in June 2015]  ... do you know if there were others (in the past year)?

    Thanks!

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-03-15T04:41:48+00:00

    Sorry, Ken. Followed your steps and no dice. Back to the 50% CPU and eternal searching. The image I restored worked fine since last June when I last re-imaged.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-03-15T06:31:32+00:00

    I'd really like to know if it "failed" because it is 32 bit. Has anyone else performed the Ken Worley method on a 32 bit system?????

    ***I must point out that there is a timing issue about when to remove the Internet connection.   After the install,***the Internet disconnection must be done BEFORE the machine is restarted.

    _xx_, would you mind trying this again being very cautious about the timing????

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-03-15T10:36:07+00:00

    I'm surprised and sorry that it didn't work for you.  If you have the time and the patience, I would like to figure out why.

    1. Download the two patches to a flash drive so you have them available after the reload.
    2. Disconnect the PC from the Internet and leave it disconnected - this is a critical step.
    3. Perform the reload.
    4. Boot the PC, check the version of C:\Windows\System32\wuauclt.exe and wuaueng.dll and let me know those versions.
    5. Apply the first patch from the flash drive.  When doing that, you will see "Checking for updates", but it won't take long because it is only checking within the patch file - the Internet is still disconnected.
    6. Restart, check and report the versions again.
    7. Apply the second patch from the flash drive.  When doing that, you will see "Checking for updates", but it won't take long because it is only checking within that patch file - the Internet is still disconnected.
    8. Restart, check and report the versions again.
    9. Connect the Internet and verify connectivity by browsing to some web sites.
    10. Launch Windows Update and let it run for a minimum of 30 minutes or until it produces a list of available updates.  Depending upon the patch level in the image you loaded and your PC being 32-bit, it could take some time, but please be patient.

    Good luck and please let me know...

    Ken Morley

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-03-16T14:58:06+00:00

    Hello and thank you for your help.

    I have tried the fix that you have given but I get a mesg from the standalone installer say "The update is not applicable to your computer" when I try to install either update.

    Any ideals or suggestion on this?

    Thank you for your time.

    Corbin

    Was this answer helpful?

    0 comments