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: Newest
  1. Anonymous
    2016-03-19T21:16:21+00:00

    Hey Ken,

    Sorry busy week at work.

    I followed all of your steps, and I tried some variations as well.

    My "bare SP1" file versions for the WU components for my 32 bit system are 7.6.7600.256 (dated 6/2/2012).  KB3083710 installed the 7.6.7601.19016 (9/25/2015) versions, and KB3102810 installed 7.6.7601.19046 (10/20/2015) (as well as that Windows 10 ad generator....unbelieveable....but I digress). I actually only have an original Win 7 disc from 2008, not a Win 7 SP1 disc, so my SP1 came from Windows Update. I made the SP1 image right after installing SP1 only, though, so there are no other updates.

    After then checking for updates for about 10 minutes, I get 127 important updates (522.5MB worth). Of those, 26 fail. When I recheck for updates after a re-start, I'm right back at the eternal "checking for updates".

    I also tried two variations, with the same ultimate results:

    1. going straight to KB3102810
    2. starting with an image from June 2015, which had WU component version 7.6.7601.18804 (3/24/2015); this actually never pulls down any updates after applying both of the above patches, and stalls immediately at "checking for updates".

    I actually went through most of the generic troubleshooting with an MS tech rep via chat, but I had to cut it off after about an hour because I needed to go to bed. :) I was planning to pick up with MS again today or tomorrow.

    xx

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-03-18T19:35:00+00:00

    @faithfulforver only...

    To avoid confusion & duplication of effort, please post any/all further follow-up in replies to your own, new thread => http://answers.microsoft.com/en-us/windows/forum/windows_7-update/computer-freezing-and-blue-screen-errors/1daaee62-6d6a-4a2d-9fd2-b2f4fe0e0743 (10 Mar-16)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-03-16T21:29:39+00:00

    faithfulforever:

    This thread is intended to help folks experiencing a specific problem: after reloading the PC from scratch, Windows Update is stuck at "Checking for Updates" indefinitely.  Since your issue is entirely different, this thread is not applicable and won't be any help to you.

    I suggest that you find an existing thread similar to the problem you are experiencing or that you start a new thread.

    When you post on that thread, I further suggest that you provide the basic information that others will need in order to help you.  BSOD's contain a wealth of information about the problem.  At a minimum, you should post the first several lines verbatim from the BSOD screen.

    Good luck!

    Ken Morley

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-03-16T21:12:45+00:00

    Best to ask a new question

    Mcafee bites.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-03-16T20:52:19+00:00

    I didnt encounter "checking for updates" problem, I get the blue screen after updates are automatically downloaded on my computer. I get the blue screen and it automatically reboot, most of them time after the reboot attempt, it will freeze. I have to manually shut the computer down. When I turn it back on, I get the windows recovery windows with "start windows normally" highlighted. Some time it will freeze before windows start(log in). Sometimes, I am able to go ahead and use my computer without any interruption but, once I get a new update, it the same thing again. I wanted to stop the blue screen. In my previous respond, I dont think I made it clear enough, that's it is the blue screen.

    Was this answer helpful?

    0 comments No comments