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

    I too encountered this issue when reinstalling Win7x64. While there are many posts with "Solved" and "Fixed" tagged & posted here and elsewhere, there is only one solution that will work every time:

    This assumes your pc is functional, if not, use a different machine to: 

    1. Goto MS Download and search for, then save to flash drive for later install:

         1. KB3083710

         2. KB3102810

    1. Reinstall MS Win 7 with SP1 if possible - this saves time. (yes, start over)

    Otherwise install MS Win 7 and run update until you see the SP1 update listed. Be Careful, the updates listed when your OS is ready for SP1 include one that *#$%s up Win7's update agent.

    Note: Also, avoid installing any optional updates and definately use the list of updates to avoid posted on the thread.

    1. At that point, ONLY check/update SP1, DO NOT add/update any other files listed, optional or important, that are listed with SP1.
    2. Once SP1 is installed, disconnect your machine from network/router or whatever you use to goto internet (Important). Then, restart your machine and Insert Flash drive from step 1 and:
    3. Install KB3083710
    4. Install KB3102810
    5. Reboot machine and reconnect to network/router/internet...
    6. Run update as usual, avoiding installing those KBs listed on this thread (Unless you want the constant "Windows 10" is available nagging you at all times and using up your machine's resources.

    That's it. Update will run fine, though there will be 150 - 200 or so updates waiting for you. It won't stop or stay at 0% and update runs at [your connection] normal speed.

    All those other solutions, i.e., turning off BITS etc,or renaming the files in "C:\Windows\SoftwareDistribution\ or running the MS Fix, or... do not work and waste your time...I know because I wasted nearly a week following these dead end, useless instructions. In fact, it seems that some people purposely posted incorrect soltions (just my opinion). What I posted above works 100% of the time. All other solutiuons offered don't come close.

    If this solution has been posted before, I apologize. However, it couldn't hurt to post this again due to all the misinformation, misguided, and simply wrong solutions I have encountered while trying to solve this frustrating problem.

    Good Luck!

    Umrk

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-04-19T15:47:07+00:00

    And the good news is: You only need KB3102810.

    Regards, VZ

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-04-19T16:04:09+00:00

    Thank you, Ken.  Coming from you, that is great feedback.  Your contribution with this solution is a very big one.  I have used it a number of times with great success.  Sorry, this thread has become so polluted with responses not relevant to your solution.

    Was this answer helpful?

    0 comments
  4. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  5. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more