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-01-22T21:27:35+00:00

    Cite:

    • Windows Update is taking an unusually long time to scan and install updates (Win7)

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

    [Revision 2.0 - 26 October 2016]

    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...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....

    Chances are the computer came with a Norton free-trial or a McAfee free-trial preinstalled. When you did the clean install, the free-trialware would have been installed again (but invalid now).

    Did you (a) uninstall the Norton or McAfee free-trialware AND THEN (b) download/run the Norton Removal Tool or the McAfee Consumer Products Removal Tool & reboot (c) BEFORE you installed a legit anti-virus application AND BEFORE you attempted to install any updates?

    
This is a Consumer-specific forum. You will find appropriate support for Win7 in these IT Pro-specific forums =>
[https://social.technet.microsoft.com/Forums/windows/en-US/home?category=w7itpro](https://social.technet.microsoft.com/Forums/windows/en-US/home?category=w7itpro)

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments
  2. Anonymous
    2016-02-01T12:55:38+00:00

    Canadian Tech:

    I agree with you entirely.  If a Windows 7 to Windows 10 Upgrade fails, I would never have any confidence in that PC without doing a clean restoration to Windows 7 from the media.

    While fixing a failed Windows 10 upgrade might be possible, it would probably take until sometime after Windows 14 is released ;)  Anyone who values their time and sanity should just reload to Windows 7.

    Ken Morley

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  3. Anonymous
    2016-02-01T12:29:28+00:00

    Ian:

    From my experience, once Windows Update 7.6.7600.320 is installed, you won't have a successful outcome no matter what you do.  Once that version gets installed, it's time to reload from the Windows 7 media.

    To manually apply KB3083710, browse https://support.microsoft.com/en-us/kb/3083710, scroll down to "Method 2" and download the file that matches your OS version and architecture.  These are Windows Update Standalone Installer files that have a compact, embedded version of Windows Update included in the file.  

    When you execute the file, you will notice that it begins "Checking for updates" just like online Windows Update does.  After the scan completes, it will have only found a single update - the one that is included within the file.  Select the update and apply as normal.

    Since these Windows Update Standalone Installer files will go through the "Checking for updates" scan just like online Windows Update, the scan will never finish if Windows Update 7.6.7600.320 is already installed.

    Once you get to the point where you can successfully run the normal, on-line Windows Update, I always apply updates in batches of no more than about 50 and then restart before applying the next batch.

    When you see the Windows 10 Upgrade in Window Update, right-click on it and choose "Hide update" and you shouldn't see that option again.  You can always "Restore hidden updates" later if you change your mind.

    Good luck!

    Ken Morley

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  4. Anonymous
    2016-01-22T21:40:21+00:00

    Robear:

    That's a good thought, but note that I had exactly the same symptoms and results regardless of whether I loaded from the manufacturer's media or the Microsoft RTM media.  We know that the Microsoft RTM media doesn't include any anti-virus.

    Besides, I was ultimately able to successfully load from the manufacturer's media, provided I followed the procedure outlined.  I went through the whole process twice just to make sure it wasn't a fluke.

    I still think that there is some problem with the Windows Update version 7.6.7600.320 that you get automatically from the Windows Update servers.  Once that was loaded, Windows Update never worked again.  And there doesn't appear to be any easy way to recover.

    Thanks for the suggestion!

    Ken Morley

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments
  5. Anonymous
    2016-01-20T20:15:25+00:00

    Worked for me!

    Thanks!

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments