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. Anonymous
    2016-09-21T18:44:23+00:00

    No problem, CT.  Glad of the expert support here and on other fora.

    Ian

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-09-21T15:28:22+00:00

    Thanks for the explanation.   It is nigh on to impossible to keep track of names here.  So, I find it very difficult to connect different postings.  Please realize that I like a lot of others, answer a lot of posts here every day.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-09-21T08:15:18+00:00

    Hi CT,

    I guess it was me who confused the thread with a random post on 11 September, following on from, but not replying to Neil Hellewell's post of 7 September.  I'd made the post because of the reference on a Norton thread to Windows KB3102810.

    You replied on the same date with advice on Windows Update scheduling, ie never.

    I replied the same date noting my situation v/v Windows Updates.

    You replied on the same date with a long post on AV strategy, including links to references on the subject.

    I replied the same date thanking you for the references and saying I'd have a look at them, making a reference to password managers in the process.

    You replied on 12 September, noting your position on password managers, acknowledged by me on the same date, noting that I was going to look at the references on AV.

    You replied on the same date saying you'd be interested in what I decided and why, which I acknowledged on the same date.

    There were then a few posts on unrelated matters, until my post of 14 September, which was a reply to Ken Morley's post of 13 September.  In that post, Ken had rightly said that the subject was getting off-topic.  My reply was to hold my hands up to say it was my fault. 

    I then went on to make the mistake of editing that post on 17 September with a note to you, instead of clicking on your last post.

    Does that clear it up?

    Sorry for any confusion.

    Ian

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-09-19T18:01:36+00:00

    I do not know what posting of mine you are referring to.  I have no posting on this thread dated Sept 19 on the subject of AV.   What is your question?

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-09-19T16:45:29+00:00

    Is it this you're questioning CT?

    EDIT: 17.9.16 - For CT - Running on the free AVG.  Still a lot of CPU activity, but not stopping anything working.  What Ihave noticed, though, is a big increase in use of RAM.

    I was responding to your post of 12.9.16, where you were asking for feedback on your recommended reading (about your suggestion of ditching SV "suites):

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

    Ian

    Was this answer helpful?

    0 comments No comments