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-02-09T23:19:11+00:00

    It is not clear from your description here that Windows 10 was installed in your computer at some point.  If it was, the only way to assure a Win7 well-running system is to re-install Windows 7.

    If your system is running well in all aspects, AND you follow ALL of my recommendations precisely, you will not have a problem.  If you are selective on what you do, I have no idea what the result will be.  However, if you do follow all of it, I can tell you that 150 client computers are experiencing Win10 freedom and have ever since the threat began.

    Unless, of course, Microsoft is about to release yet another sneak attack.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-02-09T23:02:03+00:00

    Hi all,

    I mentioned above that I still had to sort out my laptop, which had had to have a clean install after a failed W10 update.  This install took place before I found this thread, so I hadn't to taken any of the pre-install precautions recommended.  Nevertheless, I thought I'd try the GWX panel/file delete/update routine before going for yet another reinstall.  I now have what looks like a clean laptop with no sign of W10 on it.  It took several hours and three repeats of the process to get to a clean update and restart, though.

    The question I'm left with is this:  Perhaps because I didn't start with a controlled reinstall, am I forever going to have to monitor the updates for the files identified above, as well as running the GXX routine on start up and/or after updates.  One reason I ask is that on the last update I checked the list of files and there were three of the named files in the list, which I hid.

    Other than that, a big thank you to Ken and CT.

    Ian

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-02-09T13:48:23+00:00

    I am afraid the Microsoft-induced Windows Update problem is intentional.  It is clear to me that the company has become driven towards a singular goal.  Move its 1.5 billion users to Windows 10 no matter what it takes. 

    The WU problems we face are simply a result of Microsoft, by policy giving very low processing priority to WU for Win7 computers. 

    In my view, Microsoft has a bit less than 4 years to get their act right.  If there are not clear signs of a reasonable, acceptable alternative to Win10, we will be seeking alternatives more and more seriously.  The situation is a huge invitation for competition.

    You have probably read extensively about how people don't use PCs any more but instead prefer smart phones and tablets.  Well that observation is only a bit true.  The real truth is that when Joe Public walks into his local WorstBuy for a new PC and sees Win8 or Win10, he says what is this?  I can not use this.  The WorstBuy "advisor" says that's the only choice.  (how untrue).  It is at that point that Joe walks out and starts to think more about his alternatives and most end up with a tablet or smart phone. 

    Microsoft has built the scenario for this to happen.  Then it blamed others for the fall of the PC!

    But the reality is that the smart phone/tablet things are OUTPUT devices and are lousy for input.  If you need input functions, you need a PC.

    For many like you and I, our PC is our working tool, not a play thing or entertainment.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-09T10:33:50+00:00

    Thank you!!

    I built a new PC today and installed a brand new copy of Win7 Pro on it.  The first time I ran Windows Update it said I needed to update Windows Update, which I did, and, of course, after that the system never got past "Checking For Updates" though I let it run for more than an hour.

    Fortunately I had a restore point which had been made prior to the installation of the failing version of Windows Update, so I didn't have to reinstall Win7 from scratch.  I did a system restore to get rid of the failing WU, then followed your steps 4 through 7.  The check for updates found over 200 updates within a few minutes.

    I cannot thank you enough for sharing your solution.  You saved me a lot of time and pain, and I'm sure your post will help a lot of other people as well.

    Microsoft should be ashamed of itself for letting something this serious go unaddressed.  I've been running my business on Windows since Win 3.1, but Windows 7 may be the end of the road unless Microsoft comes to it senses and returns control over update installation to its customers.  Stability is paramount for mission critical systems.  It is simply astounding that Microsoft has lost sight of this.

    But I digress.  Again, thanks for your help.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-02-08T20:38:03+00:00

    I encourage you to remove ALL listed updates.  All of them are Win10 grease of some kind and have no value to Win7.  I added a new one to the list based on a new article by Woody Leonhard: KB3123862.

    I am happy for your success.  Thanks for the feedback.

    I Know this works.  I support 150 or so client computers and have used this.  Not a single one is threatened by Win10 malware.

    Was this answer helpful?

    0 comments