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. 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

  2. Anonymous
    2016-05-12T15:16:19+00:00

    AdminTechACD:

    You didn't mention whether or not the computers were freshly loaded and, if so, whether they were loaded with Windows 7 SP1.  Can you please clarify?  If you already have clarified and I just missed it, I apologize in advance ;)

    The procedure I described is specifically for the case where a fresh load with Windows 7 SP1 results in Windows Update NEVER working again (not slow, delayed, patches listed in reverse order or some other condition).  

    I think some users here incorrectly assume that a slow-to-update issue *must* be related to the issue I originally described.  It might be related or it might not be related, but in either case is beyond the scope of this thread.

    Thanks!

    Ken Morley

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-05-12T14:51:35+00:00

    both laptops found the same amount of 

    updates* in roughly the same amount of time**.   

    Like I say: Don't include KB3083710. It reduces the accelerating effect of KB3102810.

    Regards, VZ

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-05-12T13:16:36+00:00

    My results.... (these are my own results and my own account - I'm not offering an alternative method, or trying to discredit or disprove anything any one else has posted. )

    I had two identical laptops side by side. The only thing I did similarly on both was :

    1: Disabled all Networking hardware in BIOS

    2: set Windows Update to "Ask Later" then "Check for updates, but do not download or install".

    3: Unchecked : "receive important updates as critical updates"

    On Laptop 1 ; I enabled networking, let Update install its update - and it started checking.

    On Laptop 2 ; installed KB3083710, reboot ; install KB3102810, reboot.

    Enable Networking, connect and run windows update - it starts checking.

    Bottom line for me is - both laptops found the same amount of

    updates* in roughly the same amount of time**.

    *1 important, 165 recommended, 70 optional.

    ** about 45min to an hour

    Ken's method does work - make no mistake.

    Whether it's necessary 100% of the time? ...only trying without it will tell you. 

    I've seen it work with and without... All I know is, its a pain in the **** if it happens - so bottom line for me is... Ken's fix does work - may not be necessary 100% of the time - but do you want to risk that if time is a factor? In my case No... so for now, I'm implementing Ken's process along with my own touches.

    Good luck everyone... And Thank You Ken for this thread and your digging through this.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-05-12T02:41:22+00:00

    Ken's solution WORKS!

    Like so many who have come to grief with Win 7 "Win update" failing, I tried to see what was the problem.

    After many installations I had determined that SP1 was fine but the moment Windows Update updates itself immediately after SP1 thats when it locks up.

    Ken's solution addresses this, and provides the fix.

    The only addition I would add is that the early downloading of the two KB files, KB3083710 and KB3102810 come in two varieties. 32 bit and 64 bit.

    The std does not say 32 bit so you must search for the KB file with 64 bit added to your search description.

    My first try failed due to my having 32 bit KB files for my 64 machine.  Second go with the 64 bit KB files worked absolutely perfectly.

    The issue still remains though for my Sony Vaio laptop that no longer updates and any other machine that you may have had that did the Windows update after SP1 installed.  Once locked up I don't know how to go back to the precise point but I might continue to play with that in the hope that a restore point etc might get me going again.

    I would also like to express my thanks to Ken for working this fix out.  Excellent.

    Was this answer helpful?

    0 comments No comments