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-05-31T04:21:36+00:00

    So, now May 30, 2016, I had basically the same problem although it started with a working Win 7 SP1 laptop system, not a clean install - Windows Update (WU) stuck never finding updates, CPU utilization at 50% even after stopping WU, stopping WU services returned CPU to normal, WU components at version 7.6.7600.320 (the apparently offending version). Spent way too many hours troubleshooting on my own and then hours with Microsoft level 2 support until finding this discussion. I had already tried many WU fix tools and techniques, a Win7 reinstall (upgrade) and finally a clean install with no change in symptoms. After 4 MS tech support agents doing dozens of remote access fix attempts (all of the WU reset tools in their arsenal, most of the same ones I tried), the update KBs they tried to install all hung without installing. I finally persuaded one tech to try downloading three KBs, DISCONNECTING my machine FROM THE INTERNET, and then installing the KBs without another new clean Win reinstall.  I did them in this order (not sure it matters) with reboot in between: KB3083710, KB3102810 (the ones Ken M. suggests, you can see that WU components are updated to 7.6.7601.19046 with this one), and also 3135445 (which is a rollup update). Not sure all three were necessary.  At that point, since I had done a clean install WU took 30-60 minutes to find 224 updates (1 GB worth), which are currently being installed! The tech said that this problem is ubiquitous and has a "Code Blue" designation (high priority to find a fix?) and that he would pass on our successful fix to his co-workers and hopefully MS engineers. Hope they actually release a simple KB fix.

    So my note is, I did this with the "bad" WU version installed and without a new clean install.

    Thank you Ken Morley for the careful analysis and finding a direction forward. Wish MS listened to the forum since this problem has been going on at least since Ken's report of it in Jan 2016 and probably longer.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-05-27T17:59:45+00:00

    I sometimes   wonder what we Window Users  would do if there wasn't anything  called " GOOGLE ' where we  could   share our problems and grievances pertaining to  our Computers. With not an iota of help extended by the " great giant " MICROSOFT  most  of us would have  dumped our Computers as they would be rendered as useless. This is what has happened with me ~ 

    ~ With the  constant " nagging "   for upgrading to Windows 10, I somehow  succumbed   to the pressure and  upgraded  to Window 10. [ I have Windows 7 laptop,Home Basic 64 bit ]

    ~ It didn't take me more than a  day  to realize that this OS  doesn't suit me so I decided to revert back to               Windows 7. [ I still had 29 days at my disposal, but I  felt  it wasn't worth the wait ]

    ~ On reverting back, I  discovered that, both, files from Task Scheduler and  Event Viewer  had become  corrupt      and after trying with  several remedial  steps, I failed and gave it up.

    ~ Since  I had backed up  all my scheduled tasks on an external drive, I thought I would format my Computer so    that  all  my scheduled  tasks  could  run.

    ~ On formatting  and wanting to  download those ' galaxy  of  windows updates '  I  discovered  that the             Computer      was " checking  for updates  till  thy kingdom come " Since this was not the  first time  I             formatted     my Computer, I was surprised with this  strange  behavior .

    ~ My several searches on Google  brought me here. I  had already given up all hopes. 

    ~ As a  last chance  I thought  I will try out what KenMorley had suggested.

    ~ I followed every step meticulously  as suggested by him and I glad that my Computer has been restored back       to    Window 7, the  way I had always loved it. 

    Just  one question ....

    **Is Microsoft   coming with a vengeance to all  Window  7 Users  who have  downgraded   back to Windows 7 ?**Seems quite likely. Here's why ! Microsoft knows too well that  when you downgrade back to  Windows 7, the problem  of Windows Updates, is bound to happen. Yet, there has been no help  from  Microsoft's side to offset  this problem... through means of a Fixit...or any other way ? Why ??? 

    A Big thank You to you KenMorley...

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-27T14:31:47+00:00

    Worked for me too. Wish I would have searched for this post 2 days earlier, would have saved me lots of grief.

    Thanks Ken

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-05-24T02:44:54+00:00

    After weeks of looking for the answer this solution worked right away.  Thanks so-o-o... much.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-05-21T20:00:18+00:00

    THANK YOU KEN MORLEY!!!

    I tried a Windows 10 Upgrade which failed...WIndows Update never Worked after that

    A fresh Install didnt work ...I got 1 Update the one where it closes and re-opens (Which was obviously the rougue 7.6.7600.320 Windows Updater)

    Eventually after trying Windows Fix This That and the next downloads...I stumbled onto this thread......Job Done in 30 Mins.

    PS The hint about not selecting too many updates at once was something I already did, after a few installs in the past where downloading 150+ Updates would fail.

    It is as simple as

    1. Download KB3083710 and KB3102810 in advance.

    Downloading these

    https://www.microsoft.com/en-us/download/details.aspx?id=49540 (X64 Ver)

    (Select the version which applies to you)

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

    1. Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.

    (I believe that if you selected "don't download Updates" for Windows Update  setting during install - this is unnecessary)

    1. Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.
    2. Manually install KB3083710 and restart - WU components will now be version 7.6.7601.19016 dated 9/25/2015.
    3. Manually install KB3102810 and restart - WU components will now be version 7.6.7601.19046 dated 10/20/2015.
    4. Restore the Internet connection and launch Windows Update as normal.
    5. After a few minutes, you should have plenty of updates to download and install.

    artfullDODGER

    Was this answer helpful?

    0 comments No comments