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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-06-19T16:05:04+00:00

    You can skip KB3083710, too. :)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-06-19T15:55:41+00:00

    Thanks very much for the fix, it worked perfectly :D

    I would like to add though, that a fresh reload is not required!

    You can simply:

    Download Download KB3083710 and KB3102810.

    Disconnect from the internet (you may also need to restart your computer here)

    Then simply install both updates and restart :)

    Hopefully this will save unwanted time wastage!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-06-19T14:57:09+00:00

    will I have to re-install?

    Please don't reinstall if a current installation is stuck. In that case it's just one update the svchost can't handle. Set automatic updates to "Never check for updates" and restart. Then download and install KB3161664. Windows Update should be working properly afterwards. "KB31002810" is a typo.

    Regards, VZ

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-06-19T14:30:48+00:00

    I have never seen an update that I could not remove and/or caused a crash.  Since I have done hundreds of these, that tells me that there is a problem in your system that may well be beyond the bounds of an update process.  Added that is your description of other update problems.

    If your machine was on my desk as a client, I would advise a data backup and clean re-install of Windows 7.

    FYI, I support 150 or so client Win7 computers and have for the last 14.5 years. 

    My experience has taught me that when you recognize deeper OS issues, the best payoff is to do a re-install.  The beauty of a clean re-install is that you absolutely know you are starting fresh with no problems.  Its like a new birth.  To do other wise, you can spend days and days hunting and fixing or not many problems and never have the confidence that all is right.

    The re-install process will take from 6 to 12 hours elapsed time if you do things right.

    If you would like to proceed like that, I have a tutorial that will guide you through the process I would be happy to provide.  Just ask.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-06-19T12:52:41+00:00

    I have both the updates Ken mentioned ie KB3083710 and KB3102810. I have Windows 7 x 64 bit and am having problems with the updating. it's forever stuck on it. I tried to download update KB31002810 but can't find that one. it shows KB3102810. Please help. will I have to re-install? I have no experience of it at ll

    Was this answer helpful?

    0 comments