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-05-10T22:02:24+00:00

    If you don't forget to change your windows update settings the stand alone installers search won't take very long at all

    I'm thinking KB3153171 is a better manual install KB3153199 is a patch for 3153171 it must be installed first

    https://www.microsoft.com/en-us/download/details.aspx?id=52187

    https://www.microsoft.com/en-us/download/details.aspx?id=52069

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-10T20:59:21+00:00

    Ken Morley - you are deserving of the Programmer of the Year award.  I followed all of the 7 steps you outlined in the first message in this thread,  and IT WORKED. IT CURED THE ENDLESS LOOP. We are not worthy Sir !. 

    After three days of installs and reinstalls , leaving machine on overnight etc, I too, found that after 7.6.7600.320 got applied the updates would hang forever. But I didn't know what to do to cure it... until I found your SOLUTION.

    There was one tiny variation I made to your 7 steps.  I have a 2010 copy of Windows 7 Home premium x64  upgrade version, from a 3 licence family pack. It does not have SP1 builtin. So for Step 3.  I reloaded my Windows 7, then immediately installed SP1 which I had previously burned on a disk.

    Also After applying the 2 numbered fixes,  I did have to wait about 15 minutes with Searching for Updates showing before it came back with 216 updates !.   During that 15 mins I had to click the mouse every 5 mins to stop hibernate happening.  I then had about 6 or 7 more update ,  restart and search for updates to run through before I got finally up to date.  My experience running these 6 or 7 updates sessions showed me that late in the evening ,  10 to 11pm Pacific Time, the response time from the Windows Update servers is much quicker than in the mornings.

    Hardware used? For those who care,  I purchased a government surplus IBM Thinkcentre 8113 M52 of 2006 vintage,  with no hard drive. I put in 4 GB Lenovo ram,  a new 1 TB hard drive, and flashed the bios to 2009. Because my windows 7 is an upgrade, I had first to load Windows XP. My old XP without SP1 wouldn't load, so I found an XP with SP1 image dated November 2013 on the internet.  This loaded, then I could apply my upgrade Windows 7.  What am I doing with this old museum piece ? It is getting an Auzentech  sound card with Sp/dif that I own, and will sit near my stereo and be used as a music CD repository and a Midi repository only.

    Once again,  thanks so very much for your SOLUTION, I was banging my head against the wall with frustration.

    Oh ... yes ,  unfortunately the relentless repetition of  "get Windows 10" now has worn me down I am hearing rumours that they will cut off the "free" update in July.  So I might upgrade soon.

    Thanks very much Ken.

    Graham

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-10T20:53:35+00:00

    How can these additional security updates affect the time required for searching updates?

    I guess that MS behaviour becomes a bit strange...

    (3 hours on my laptop. now I try on desktop, but i know...the issue will never be resolved. On June patch day: it will change again but I will need always 3 hours).

    Was this answer helpful?

    0 comments No comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more

  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.


    Comments have been turned off. Learn more