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-09-13T12:56:13+00:00

    HUmnn, I am mostly with you Ken, BUT, it is clear that the original problem of slow/never updating is made worse by 

    1. Norton ( I tried Norton many many moons ago because it was "free" on a Windows machine I purchased and as soon as I activated it, the problems with updating anything that Norton didn't support or simply installing new software  and hardware were maddening.)
    2. WIN10 Malware.. That was what got me here.. MS managed to get some of the WIN10 malware on my machine and when I finally gave up and did a clean install, I couldn't get the updates. For my part I am ABSOLUTELY convinced that MS deliberately broke their own update process for those machines MS secretly identifies as WIN10 capable to push WIN10. I say that because so far I have never seen a post here or anywhere about slow updates by someone with a machine (see my final line below) that clearly isn't WIN10 capable.

    As far as I can tell this is the only place where these three seemingly separate things are all clearly shown to be inter-related. 

    That said, the thread has become over grown and could be a real challenge for a complete novice.

    Not sure what the answer is though since I am not a pro either.

    The ONLY reason I am trying to keep a Windows machine running is to be able to eventually play Elite Dangerous and I want that machine to be on WIN7 because I don't want to give MS complete control of my computer as they are demanding with WIN10.

    It is looking more and more like there will be a Linux port of Elite Dangerous and if that happens,, my problem will be solved.

    Posted from a Dell Dimension E310 running Linux Mint 17 for 32 BIT that will dual boot to WIN7 with Avast and still updates just fine.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-09-13T11:49:20+00:00

    Not to be overly sensitive, but I think we're getting a little off-topic with the password keepers, AV recommendations and video card discussions. It would probably be better to start a separate thread for those conversations. Cheers! Ken Morley

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-09-13T01:17:26+00:00

    I will throw this in to the discussion..graphics card drivers...and I will use AMD as a example....have the same issue. The recommendation is to disable any anti-virus/malware/personal firewall/ anti-anything while downloading and/or installing. The fancier your AV, the more suspect it is. Canadian Tech's advice is sound.

    Personally, I use Panda Free anti-virus and Malwarebytes (Free version is great) Pro ($19.99 Lifetime when I bought).

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-09-12T16:44:30+00:00

    That's the least I can do!

    Thanks,

    Ian

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-09-12T16:12:41+00:00

    I would be interested in hearing how you decide and the results.

    Was this answer helpful?

    0 comments No comments