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-02-02T21:27:27+00:00

    Ian:

    As explained in my original post, the Windows Update problem where you see "Checking for updates" forever occurs immediately after a clean install IF the computer is connected to the Internet.

    That's because the first time Windows Update is launched, it will automatically download and apply Windows Update 7.6.7600.320. The user does not get any notice or have any choice in the matter.  It happens automatically and invisibly behind the scenes.

    Once that happens, Windows Update is broken and I don't know of any easy way to fix it.  That's why it is important to make sure that Windows Update 7.6.7600.320 never gets loaded in the first place.

    You asked: "isn't the best thing just to leave things as they are until/unless something breaks?".  I suppose the answer depends on how you use the computer and what your position on security is.  It might be fine to leave it unpatched if the computer will never be used to browse the Internet or used for anything critical.  But I think that using the computer to purchase things by credit card, access your bank statements and pay bills, etc. would be risky.

    If you "leave things as they are until/unless something breaks", the "break" part might be your bank account getting cleaned out or your credit card ran up to the max.  Personally, I would never trust an unpatched computer for anything important or security-sensitive.  But your mileage may vary.

    Cheers!

    Ken Morley

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-02-02T20:50:49+00:00

    Hi Ken, CT,

    Just for the record, the updating issue I have with the laptop is after a clean (?) install and the only update listed is the one I don't want.

    Both my PC and laptop are working fine, apart from the update issue.  From what I've read here, isn't the best thing just to leave things as they are until/unless something breaks?  Is it worth carrying out the routines listed?

    Thanks again,

    Ian

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-02-01T22:34:06+00:00

    window was crashed  an up grade  now  im  window 10 . had  deleted   uninstall so  need  re downroad and  install

    You will find Windows Insider-specific support in these forums: http://answers.microsoft.com/en-us/insider/forum/insider_wintp

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-02-01T15:17:07+00:00

    Hi,

    Many thanks for that comprehensive set of replies.  For now, I'll just have to acknowledge and take a detailed look when I have a couple of days spare.  In the meantime, if anybody can recommend one of the Linux packages ...

    Thanks again,

    Ian

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-02-01T14:13:18+00:00

    window was crashed  an up grade  now  im  window 10 . had  deleted   uninstall so  need  re downroad and  install

    Was this answer helpful?

    0 comments No comments