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: Newest
Most helpful Newest Oldest
  1. Anonymous
    2016-07-17T02:23:13+00:00

    Here is a web site with some advice that seems to work for me...

    http://wu.krelay.de/en/2016-07.htm

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-07-16T23:14:09+00:00

    And that is EXACTLY my point, Canadian Tech:

    Per reference, https://www.askwoody.com/category/microsoft-windows-patches-security/

    If you look at the comment about KB 3161608, you see that this particular one is supposedly found listed under the "optional updates". It provides needed speed for the endless .msu cycle of searching for updates. Not sure what your ISP ration is ( if any) but I am definitely on the MGB/KGB diet and need to conserve if possible.

    As for "greasing the skids", my laptop is not compatible with Win10, so that's an exercise in futility on their part and totally hinders any safety progress on my end.  I thiught we were supposed to be diligent about safety... they make it more and more difficult!

    Thanks!

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-07-16T22:14:29+00:00

    I know you did not write that to me, but may I chime in and offer a piece of advice?

    I look after about 150 client computers -- all of them Win7 because not a single one of them wants Win10.

    My advice and policy on the issue of which updates to apply is based on an interesting fact that was exposed by Woody Leonhard.  Not a single update has been offered that improves Win7, other than security ones since the end of 2014.

    Therefore my policy and advice is as follows:

    Allow any and all updates to Microsoft Office or other Microsoft software

    1. Do NOT allow any optional updates.  Do not even click on theOptional link in Windows Update
    2. Do NOT place checkmarks on any “Important” updates that are not already checked
    3. Hide any and all Important WINDOWS updates that are NOT marked security.  They typically occur near the end of the list.

    The reasoning for this policy is that all of the updates that are "hidden" as described serve no other purposes other than to grease the skids to force a Win10 upgrade or install intelligence gathering reporting systems on your computers.

    By the way, it is critical that WU settings is at NEVER and remains there permanently.

    When doing rebuilds, I go through these kinds of updates and check the origination date of each.  If the date is before 2015, I allow the update.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-07-16T22:02:06+00:00

    Maybe I wasn't clear- have done all that. Actually changed it from "let me choose" to "never" because it seemed more personal control over the updates was needed. The question is: if, in fact, one of these last two updates was listed as "optional", how the heck is the common everyday person to decide which "optional" one(s) to download, when they're not identified as an important security update, but they are, in fact, very important for smooth function?

    Thanks.

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-07-16T20:32:04+00:00

    Once again I find myself relying on this thread.  I first posed my affliction with this problem back in April.  The step by step solutions did eventually rectify the WU constant cycling.  Now it is July, and I was back in the same boat once again.  Even the standalone downloads wouldn't install- the installer just continued "searching for updates"! (Why are they .msu files anyways? Why can't they just be .exe's?? Anyways...) I have gone through the steps of stopping the WUI through Services, downloading KB3020369 and 3161608, installing, etc etc.  My WU has now effectively located 14 important updates and 47 optional ones.  Here's my question:  I understood from "askwoody" comments that 3161608 was only listed as an optional... WHY, if it was necessary to complete this painful process of repairing the WU function? And, if IT was optional, how is the common person like me with no formal computer training in any of this to know WHICH other optional downloads I should select for my own? 

    I truly thank you, Ken Morley and all the other comments posted that I could compare my situation to for guidance - could not have fixed anything without all the input. 

    Oh, and one other thing - when I looked at the build for the WU files, I didn't have the "320" - mine said 7.6.7601.19161

    • or was I looking at the wrong thing?

    Anyways, thanks!!

    Hi @SueQKY ,

    Change Windows Update Setting to "Check for updates but let me choose whether to download and install them." And for get this setting and leave it there.

    You can pick and choose which updates to download and install. You can also click on More Information on the right side before deciding.

    The updates that you don't wish to install, can be hidden.

    Was this answer helpful?

    0 comments