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-03-05T17:49:21+00:00

    Not at all - credit always should go to where it is due.

    First, you are correct that the number of updates are different.  I actually went through your method twice.  The second time because of the number of failed updates.  I thought it was because I activated Win7 in the middle of the updates but that was in fact not the case as there are failures even if I don't update until it is all done.  The first time I went through, there were 151 updates, the second time 152.  The data size was 492.6 Mb and 527.7 Mb respectively.

    About the updates that failed.  It appears that my machine automatically did another update last nigh and many of those that failed was successful then.  So the failed ones will continue to be replaced.

    I agree that this problem affect both AMD and Intel alike.

    The machine is now running like a top so thanks again for your help.  I have been tearing out my hair for the last 2 weeks and so this is simply wonderful.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-03-05T15:43:49+00:00

    Ken, I am not at all convinced that there is a problem with WU, other than M$ simply has given Win7 WU last priority in the queue. 

    I suspect a lot of the problems people are having are due to their "Security" software, which I refuse to allow on my client computers.  That may account for the reason I see so little of these problems in their computers.

    A lot of it is Win10 simply bozoing its way into the process and owners, being bamboozled into taking foolish actions, which result in devastating damage.

    My impression is that the vast majority of people who get into trouble, were just impatient and ended the WU session before it could complete itself, resulting in the many problems we see.

    I just had 2 brand new PCs on my desk this past couple of days.  They needed over 100 updates each.  The process was slower than it was a year ago, but much better than over the last few months.  Wait times were down to 20 minutes or so.  The entire update process in each case was problem free.

    I have also done many, many ordinary monthly WUs without a hitch.

    In all cases, I hide every Windows Update dated after May, 2015, that is not marked Security, and I use GWX Control Panel in every case.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-03-05T12:49:12+00:00

    Robear:

    As another suggestion, Microsoft could just fix what appears to be a major defect in Windows Update.  I'm sure they are aware of the issue as it is impacting many, many users.  I'm equally certain they have the technological prowess to engineer a solution.  All that appears to be missing is the motivation.

    If Microsoft addressed the root cause of the problem, we could all avoid Premium Support, the seven steps listed in my original post and posting on this forum.  That would save a lot of time, effort and heartburn for everyone.

    Cheers!

    Ken Morley

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-03-05T12:42:04+00:00

    jlow9m:

    Thanks very much for the generous feedback.

    Regarding the updates that failed, it has been my experience that installing many updates at once is less reliable than installing a few dozen, restarting and then installing the next batch.  As a rule, I generally try to limit to 25-30 at a time.

    If you watch closely, you may notice the list of available updates changing between batches.  I attribute that to some updates being deprecated by others once they become effective following a restart.

    The first update will list everything including he kitchen sink as available for installation, but all are not actually necessary, desirable or even possible to install.  The key is to install the updates in reasonably-sized batches (followed by a restart) until there is nothing left to install.  I don't even worry about individual failures unless I am at the end of the update process, it is showing an update that is needed and the update won't install.

    Also, the update order has a lot to do with the time involved and overall success.  I find that if I install all security-related and OS patches first and save the .NET updates for last, many of the .NET updates will disappear from the list, saving the download and install time.

    Regarding the AMD processor issue, I haven't yet seen any evidence yet validating that hypothesis.  I think the problem affects AMD/Intel alike.

    Ken Morley

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-03-05T01:14:41+00:00

    If need be, you may obtain Microsoft-sponsored Premium (i.e., paid) Support via the Answer Desk => http://answerdesk.microsoftstore.com

    Was this answer helpful?

    0 comments