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-21T16:03:38+00:00

    Mike:

    It took me the better part of three days to figure this issue out.  I documented it so that others wouldn't have to waste so much time.

    I can't understand why Microsoft would not just remove the bad update from the Windows Update website.  It could be they aren't aware of the issue although it's hard to believe that MS never reloads a Windows 7 PC themselves.  Or maybe they are aware and just aren't going to take any action to fix it, regardless of how simple and easy it would be.

    Chalk it up as one of life's little mysteries...

    Ken Morley

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-03-21T15:38:30+00:00

    Hello Ken,

    Thanks for your (probably) deep and time consuming searched solution. It worked exactly as said.

    I'm wondering why Microsoft is not releasing a fix and/or just remove that version of windows update files. I had two PCs on my desk this morning and both had the exact windows update version (7.6.7600.320). I was able to restore one of them to previous restore point, but unfortunately, it seems I will have to reinstall the other one. I guess that would apply to Windows Server 2008R2 since there's the KBs for this edition of Windows too.

    Best regards,

    Mike

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-03-21T01:16:09+00:00

    Ken,

    Some new research:

    1. thread going on at AskWoody about this same thing (not sure if anyone mentioned it somewhere in here):

    http://www.askwoody.com/2016/the-windows-update-takes-forever-problem/comment-page-2/

    No clear-cut solution/explanation I could find, though.

    1. I tried installing the updates in this order, starting from my image of 32 bit Windows 7 SP1. There's a restart in between each one. My philosophy was generally to install the newest ones first to see if your theory about older updates dropping out was correct.

    step 1: KB3102810 (from disk, before connecting to internet)

    step 2: KB3138612 (3/8/2016): gives WU component version 7.6.7601.19161

    step 3: 

    -- KB2900986

    -- IE11

    -- KB2670838

    -- KB2729094

    -- KB2786081

    -- KB2834140

    -- KB2882822

    -- KB2888049

    step 4:

    -- KB3139929 (IE 11 cumulative security update 3/8/16)

    -- KB2900986 (Win 7 security)

    step 5:

    -- KB3138910 (all of these are Windows 7 security updates dated 3/8/16)

    -- KB3138962

    -- KB3139398

    -- KB3139852

    -- KB3139914

    -- KB3139940

    -- KB3140410

    -- KB3140735

    After installing the 5th batch (with ~100 older updates still waiting to be installed), I'm back to the eternal "checking for updates". This makes sense, since my Windows Update broke after installing these when they came out.

    xx

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-03-19T23:09:15+00:00

    I haven't had any experience with this procedure on straight Win7 without SP1.  But I have plenty of experience trying to install all of the updates at once and none of it is good.

    I recommend installing the updates 25-30 at a time and restarting between batches.  I also do all of the Windows Security updates first and the .NET updates last.

    You will probably notice that installing the updates in batches - with restarts - results in less updates being downloaded.   I guess that's because Windows Update is not that smart about prerequisites and order.  By installing one update, you may find that eliminates two others later.  It may actually save time.  It will definitely reduce the number of updates with problems.

    Good luck!

    Ken Morley

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-03-19T21:37:06+00:00

    Yea this is the one that poked the pooch

    https://support.microsoft.com/en-us/kb/3020369

    This one has to be installed all by it's self but is checked at least it was for me along with 158 others :p

    Sounds like this update messed you up too :(

    Was this answer helpful?

    0 comments