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: Oldest
  1. Anonymous
    2016-06-29T19:35:29+00:00

    Really?? This is MS solution??

    http://www.infoworld.com/article/3086811/microsoft-windows/microsoft-releases-kb-3161647-kb-3161608-to-fix-slow-windows-7-update-scans.html

    "

    First, you have to install last year's servicing stack update, KB 3020369, before you can install the speedup patch. Microsoft doesn't document that anywhere, but various reports indicate that you need it installed. Note that there were problems with KB 3020369 triggering a "Stage 3 of 3" hang. There's a description and a workaround in my post from a year ago.

    Second, Microsoft doesn't have a download for the Win7 scan fix by itself. The only way you can get KB 3161647 is by installing the update rollup KB 3161608. KB 3161647 contains the "fix for a Windows Update error 0x8007000E on some computers while they are updating" as well as "some reliability improvements." The update rollup KB 3161608 includes four fixes that are completely unrelated. Confused yet? 

    This means Windows 7 users must install six unrelated patches in order to get Microsoft's Win7 updating mess untangled -- seven unrelated patches, if you include KB 3020369. If one of those seven patches isn't to your liking, sorry bucko, you're relegated to the eight-hour-wait list."

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-29T20:35:58+00:00

    I have been wondering throughout this whole process about the Never Update option - I have yet to find it even though I have searched repeatedly.  Not to mention searched how to find it or set it.  I see the Ask me later, the Automatic Update and the partial auto update.  ?

    Well, all this time I have been thinking I must be amazingly stupid for not being able to find the Never Update option - and the problem is that it was NEVER THERE TO FIND.  It just showed up this morning, exactly where I have been thinking it should have been all along.  And I am guessing that it finally showed itself because I got the SP1 installed yesterday.  Yahoo...  So you can ignore this one Ken.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-29T22:27:25+00:00

    This explains why I too never saw NEVER when I did my re-installation. The option doesn't become available until SP1 is installed.

    Absent a screen shot, I don't think it is an option during the installation process. Probably to make sure people eventually put everything in automatic so MS get full control.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-06-29T23:25:46+00:00

    You can always prevent automatic installation of update agent 7.6.7600.320. Either by choosing "Ask me later" when installing Windows 7 SP1, or by setting "Never check for updates" before updating from Windows 7 SP0. Of course the option is there in Windows SP0.

    And your life does not depend on keeping 7.6.7600.320 away. If KB3083710 can be replaced by KB3102810, so can 7.6.7600.320. And meanwhile we are even beyond relying on KB3102810 through the Convenience Rollup or the June Rollup.

    If ever, avoiding 7.6.7600.320 is essential no more.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-06-29T23:47:36+00:00

    This explains why I too never saw NEVER when I did my re-installation. The option doesn't become available until SP1 is installed.

    Absent a screen shot, I don't think it is an option during the installation process. Probably to make sure people eventually put everything in automatic so MS get full control.

    You are right - it is not an option in the installation process either.  I have been there several times now and I can assure you not there...  NOT going back for a screen shot to convince VZ.

    Was this answer helpful?

    0 comments No comments