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: Newest
  1. Anonymous
    2016-06-28T18:28:44+00:00

    ASK ME LATER doesn't work to stop the WU from automatically updating itself if there is an internet connection.

    YES IT DOES.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-28T17:34:15+00:00

    ASK ME LATER doesn't work to stop the WU from automatically updating itself if there is an internet connection. 

    In my experience, the WU will update itself even when Update is set to NEVER if it can get to the update site. That is why I currently have my wifi adapter disabled. It is the only sure way I can keep MS from screwing with my computer when my back is turned like they did on April 17th after I had spent days getting the machine working on the 2nd of April.

    But, again, the broken update to the updater will not install if SP1 is not installed. That is the secret. Get SP1 on it and manually install an update to the updater that is newer than the broken one. 

    There are now at least 4 seperate proceedures for doing that.

    This can be very confusing for a novice.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-28T15:17:50+00:00

    You can unplug the network cable, disable the WU service, set Windows Updates to "NEVER", poison DNS so that WU can't resolve the update site or any combination thereof.

    It doesn't get easier than selecting "Ask me later" at "Set up Windows".

    http://winadmin.exteen.com/images/WinThinPC/i09.jpg

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-06-28T14:17:44+00:00

    DaviNUNYA:

    Anything you do to prevent Windows Update from patching itself to the 320 version avoids the problem.  You can unplug the network cable, disable the WU service, set Windows Updates to "NEVER", poison DNS so that WU can't resolve the update site or any combination thereof.

    You are absolutely correct that Windows Update will automatically update itself first, without any notice or user intervention if Windows Update is enabled and the computer can reach the Windows Update website.  By the time you see "Checking for updates.." on the screen, Windows Update has already downloaded and installed the broken Windows Update version and it's too late.

    I've had some trouble communicating that detail adequately.  I think some folks are under the impression that the problem update is shown in the list of available updates or something that the user can decided to install or not install.  

    If the network cable is connected and Windows Update is enabled, the computer will get the broken version of Windows Update.

    Ken Morley

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-06-28T14:16:58+00:00

    Yep I prefer this process too it just needs a quick edit for current times :)

    Not sure why M$ left out ie11 from the rollup but it figures they just complicated matters.

    Was this answer helpful?

    0 comments No comments