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-06-29T16:27:34+00:00

    Yep, but at least there's a new update client out. :)

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-29T16:28:02+00:00

    They did

    The fix released was win-10 :p

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-29T16:58:14+00:00

    Ken:

    I think we've all been baffled by Microsoft's lack of action.

    Most companies try to remove defective products as soon as the defect is discovered - especially if there is little or no cost to do so.  

    In this case, Microsoft is aware the existing patch is:

    1. Defective;
    2. Causing lots of customers lots of problems and frustration;
    3. Costing Microsoft significant tech support time and money;
    4. Eroding Microsoft's reputation and customer good will.

    Considering that Microsoft already has replacement patches that effectively resolve the issue, they could roll-out the solution for no cost.  So why haven't they done anything???

    The folks running MS are not stupid and so there is probably some strategic reason they prefer the status quo.

    Ken Morley

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-06-29T17:57:07+00:00

    Yeah,

    Force everyone onto W10 or IE11.. Either way MS effectively gets full access to your complete internet activity,,  information they can sell.

    We know that MS has wanted this power ever since the Windows Genuine Advantage days and the fact that MS has sued the Federal Government to stop the use of National Security Letters to get MS product users computer history and probably full access to  those computers is all the proof I need to believe that MS is lying when it says:

    1. We don't/cannot collect or provide access to your personal data. 

    If this statement was true, MS wouldn't be upset with the Feds.

    With W10 and probably the automatic update of WU on W7 and W8.X they again have full access to the whole computer like WGA gave them. 

    MS understands that Google and Facebook and Apple in particular, but there are others, with their virtually unlimited access to the users personal information have effectively got a license to print money.

    MS is trying to issue itself it's own license.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-06-29T17:58:01+00:00

    You didn't stick your tongue out enough times.

    Was this answer helpful?

    0 comments No comments