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: Most helpful
  1. Anonymous
    2016-09-07T21:55:13+00:00

    A suggestion if you ever have to do a re-install again....

    Do not load any applications at all until all Windows Updates are done. Then install Microsoft Office and do Windows Update again.  After that, make a system image so you do not have to ever do this again:

    Clean Install tip

    After Windows 7, system drivers and all updates are installed and any stable applications like Microsoft Office are installed and updated, and before any data or dynamic applications are installed such as antivirus software, create a system image.  It will take 3 or 6 DVD ***+***Rs (not -Rs) and about an hour.  When you are done you will have a very nice bit of insurance.  Should you ever again need to re-build a corrupted system or replace a hard drive, you will have a precise duplicate of your system as it was at time you made this image.  You can restore that image to a hard drive in about 20 minutes.  Creation of System Image is found in your menu under Maintenance, Backup and Restore. 

    Another great feature about using the image is that you do not need an install disk or a product key to do the re-install the next time.

    I emphasize the need for PLUS R DVD blanks.  Do not use the more common MINUS R DVD blanks.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-09-07T21:46:34+00:00

    The above current procedure method has just worked for my new install Windows 7 Home Premium 64 bit Laptop.

    It had been activated and several programmes installed with private data and files with my usual virus protection and preferred system maintenance apps. I had tried all I could with several other methods to get  the updates problem sorted, which were stuck in the endless loop with no downloads appearing over 5 days.

    I agreed with the above assumption that it was the new update agent that had caused the problem, so downloaded the 2 manual updates as advised. Shut down Auto Updates and the WiFi and rebooted.

    I then manually installed one by one the updates from USB memory stick, each requiring a reboot.

    Switched auto updates back on then the WiFi. Brilliant, Updates started to download as they should.

    All seems  to be normal now, so, great advise. I have saved for later as I do re-installs regularly, but this is the first time I have encountered this frustrating problem.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-09-05T02:02:49+00:00

    Wait a bit.  It is awaiting his "moderation" so it is not published yet, but typically is pretty soon.

    I just posted the solution to Woody's blog on the article:

    https://www.askwoody.com/2016/ms-defcon-3-get-windows-patched-gingerly/#comments

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-09-05T01:17:49+00:00

    Well CT, everything I have read says MS goal is to effectively turn W7 (W8/8.1) into W10.. Very intrusive snooping and uncontrollable updates.

    How would one go about doing this?? --->>>  "and even consider disabling the WU service,"

    The thing that most tweeks me about all this is that I really wanted to be able to play Elite Dangerous.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-09-05T00:59:46+00:00

    October is still very much of a mystery.  Read Woody Leonhard's blog at:

    https://www.askwoody.com/2016/the-fallacy-of-fragmented-patching-in-win7-and-8-1/

    Brand new article:

    https://www.askwoody.com/2016/ms-defcon-3-get-windows-patched-gingerly/

    At this point, I do not know much about what is coming.  The best I can make of it at this point, and this may well change is to advise that you set WU to Never and even consider disabling the WU service, after you September update.  That will protect your system from MS incursion.

    At this point, it appears that the risk of messing up a system is greater by allowing WU to run, then not.

    Was this answer helpful?

    0 comments No comments