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-05-12T23:59:04+00:00

    Look at Windows Update Agent 7.6.7600.320

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-05-12T23:57:48+00:00

    Please read the trouble ticket I generated that was eventually fixed when I found Ken's info. look closly at the info I generated when I originally did my testing and then the results I had doing Ken's fix.  This update agent is in fact the primary culprit.

    Windows Update Agent 7.6.7600.320

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-05-12T19:04:22+00:00

    The updates listed worked for me but only after updating Internet Explorer from IE9 to IE11, (ie9 is the version you would be on if you just installed sp1.)

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-05-12T18:53:11+00:00

    Bru20 -- First, go into your Windows Update and change your settings to "Never check for updates", then restart your computer. Once you restart, WU will no longer start checking automatically -- that's what has you stuck in the loop. Then go to one of the online links above (ending in 52214 for 32-bit, 52232 for 64-bit) and follow the instructions to download and install it; it will do it as a standalone. Restart your computer when instructed. Then you should be able to open WU and click on "Check for updates". My advice to you after that -- and this was wise advice given to me by Canadian Tech -- is to leave your WU setting on "Never check for updates". I hope this works for you. It did for me, beautifully.

    I appear to be sorted, at least for now.  I would only go into the endless checking for updates when the check was initiated manually, on its own it worked fine.  I will be leaving my setting as is for now.  I'm not sure if I needed to manually install the few updates I did to jump start WU, I really think the MS servers have issues.  Regardless, I can relax until next month.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-05-12T18:39:28+00:00

    Thanks Bru20.  That recommendation to set to Never is not popular, but it works for me and my 154 client computers.   A lot or people mistakenly think that means that you will never update.  That simply is up to the user.  Never means never give Microsoft control of your computer.  It means you take the responsibility and control over the update process.

    Canadian Tech -- I'm assuming that your reply was for me; my posting was to Bru20, and I'm hoping the instructions help as they did for me, both last month and this.

    The odd thing is that I never thought about setting WU to "never check..." until this issue came up -- and yet, I've always had everything else that is subject to updating set to "never check" and simply make a point of regularly (religiously) checking for them myself as a routine. I think people are afraid they'll forget to check. I'd rather have as much control over things as possible. So, I thank you again.

    Regards, mrshvd3

    Was this answer helpful?

    0 comments