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-06-29T07:45:38+00:00

    It seems to be a matter of presentation. There is a post from three days earlier speaking of a 3083710-3102810 combination.

    http://answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-update-agent-767600320/aa7abd69-bfac-4a11-afe1-f60d0e811124

    Regards, VZ

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-06-29T01:40:29+00:00

    The key to prevention is the WU setting of NEVER.  It is the only way to take complete control of what happens to your investment.  It does NOT mean never update.  It simply means MS, you are never going to be allowed to decide how and what to do to my machines.

    Ken is a true champ.  His solution to the re-build problem is a huge time saver for millions.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-06-29T01:32:18+00:00

    YEP.. You are the MAN!!

    I just couldn't do your plan because the updater froze up as soon as I installed SP1.

    Davi

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-06-29T01:12:42+00:00

    That Canadian tech guy was probably me.  Here is my formula for blocking Win10.  I have used it for the last 9 months or so on my clients' 150 or so Win7 machines.  It works perfectly and is not difficult at all.  The key is the strategy that refuses all WINDOWS updates that are not Security.  It is based on the fact that Microsoft has not issued a single update that improves Win7 since 2014, other than security patches.  In fact, when I re-build systems, I selectively hide all non-security updates that are dated after Jan 1, 2015.

    Prevent Windows 10

    If you do not want Windows 10 and wish to prevent it from being installed on your computer…..

    Once you have followed the procedure below, and set Windows update to NEVER, once a month, start Windows Update (WU) manually, check for updates.  When you get the list of “important” updates, right-click and choose hide on EVERY update in the Windows grouping that does not describe itself as Security.  Allow the Malicious software removal tool or any C++ updates.  Do not use ANY optional updates or place a checkmark in any unchecked updates.  Proceed to update.

    Microsoft has committed to support Windows 7 until at least January 14, 2020.

    A lot of people have tried Windows 10 and decided they want their Windows 7 back.  If you are one of those, once you have Windows 7 back, you will need to take steps to keep it that way.

    http://www.infoworld.com/article/3043656/microsoft-windows/first-aid-for-forced-windows-10-upgrades.html

    Change the Windows Update Setting to Never check for updates.  Once a month, about 2 days after the 2nd Tuesday, start WU and then hide every update except for ones specifically labeled Security.  In other words, only security updates should be applied.  In all of 2015 and since, there was not a single update that  improved Windows 7 other than fixing security issues.

    Some may feel uncomfortable with the setting — NEVER.  Well you needn’t be.  Never means you are never giving Microsoft a chance to decide what you download and install.  It should NOT mean you will never update.  The difference is that now you take control and the responsibility of updating of Windows and Office.

    Read Woody Leonhard (one of the most respected writers in the trade)  http://www.infoworld.com/article/2983777/microsoft-windows/how-to-clean-the-windows-10-crapware-off-your-windows-7-or-81-pc.html?nsdr=true   Woody’s advice is that if you have Windows 7, keep it, you are better off by far.

    First download and run GWX Control panel.  http://ultimateoutsider.com/downloads/  It will allow you to prevent any future operating system upgrades and delete downloaded Win10 files, but it will not remove all of Microsoft’s spyware that is already installed on your computer.

    The following process will remove those features which you do not need.

    1. Take Windows Update off automatic — Never check for updates
    2. Windows Update, Installed updates, WAIT a long time till you see the green bar complete its long trip to the right
    3. Now, search for each of the listed (below) updates, uninstall them.  You must wait until the list is re-created each time. You need to wait till you see the number at the bottom of the search window exceed a few hundred.
    4. You do not need to restart after each uninstall, click later, until you are done.
    5. Then, clear the search box and after the list is again displayed (the number at the bottom again exceeds several hundred), enter another KB number.
    6. Restart the PC.  It may take a long time to process this.

    If you choose “check for updates, but let me choose whether to download and install them”, Microsoft will download “important” updates like KB3035583 to your computer.  It will be pre-checked — selected.  Unless you check Windows Update (WU) and discover this BEFORE you shut down, it will install it during the shut-down process.

    List of updates that if already installed should be removed:

    KB3035583

    KB2952664

    KB2977759

    KB3021917

    KB3075249

    KB3080149

    KB3083710

    KB3083324

    KB3090045

    KB3112343

    KB3123862

    KB3022345

    KB3068708

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-06-29T00:45:24+00:00

    Well, LuraAnne..

    In this thread there is Ken's way and about 50 posts in I think someone from Canada posted a similar way using different WU updater files. I saw but cannot find again a MS tech thing that was SO TECHNICAL having you play around in the registry that I didn't look any deeper at it.

    Then there is the way I did it. 

    BUT, I ended up having to wipe the machine and start from scratch because I didn't catch it in time and MS basically bricked the machine when they shoved a W10 upgrade on me and nothing seemed to actually work to roll it back.

    So, once I got serious about getting the machine running again, I had a secondary goal which was to block all the W10 malware. Toward that end when I tried to do a re-installation I selected ASK LATER so I could control when and what updates were downloaded as suggested in many places in many tech articles about how to stop the W10 garbage, but as soon as I installed SP1, the update system froze up.

    So I started looking for how to unfreeze it and Started my thread and someone posted there suggesting I look here.

    I tried and failed using Ken's plan and the other one. I now understand that I failed because I didn't notice or understand that none of the suggested alternate WU update clients would load until SP1 was installed and that the internet connection MUST be disconnected before you do the restart after installing SP1. 

    If SP 1 is on the machine, and it is connected to the internet, it will get the bad updater.

    Ken says that selecting ASK LATER during the initial installation will prevent that, but, as noted above, that was not my experience. 

    Regarding the "Roll up File". I have been watching the comment sections of tech articles on CNET, Computer world and such and so far, the comments sections seem to be a mixed bag. It works for some people and doesn't for others. At present I don't need it because i managed to get my machine fully up-to-date and I have a system image with bloatware removed,, except I have IE11 blocked because the latest version of it is tainted with W10 nagware. This is only a problem if you have a machine that is supposedly W10 capable as mine supposedly is but,,, for reasons unknown I ended up with a brick and had to start over.

    Was this answer helpful?

    0 comments