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-04-16T01:50:33+00:00

    I will not be waiting for you May 10 reply.  I know now that this process works very well indeed.  I have done WU on 5 computers so far.  The WU wait time varies from 2 min to 16 min depending on the age and power of the computer.  This is a very important discovery and my hat's off to its discoverers.   I would give credit to the right person if I knew who that was.

    To be clear, the process repeated here is:

    Extremely frustrated all day yesterday trying every solution posted on the Internet. Then this morning I found this comment on Softpedia's website and it absolutely works (very easy - but why should we have to do this?):

    To resolve this issue: first install KB3145739 manually. Go to Microsoft website to download and then install.

    Next you should restart and finally you can check for updates in manual mode.

    It takes between 5 or 10 minutes.

    Comment posted by: Chooky

    14 Apr 2016 13:00 CMT

    http://news.softpedia.com/news/windows-update-hanging-when-downloading-april-12-patches-502886.shtml

    http://answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-update-hangs/dbd539c3-bfc6-42df-a6ff-0e55ef7938eb?page=6

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-04-16T01:35:22+00:00

    I will reply to you on 10th May, after verifying that this KB is the cause, to tell if you are right or wrong, but please wait until the next patch day, thanks.

    Now I have this KB, on 10th May I will know for sure if that was the cause. (Because now I have ALL the updates, so I have to wait the next month).

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-04-16T01:33:33+00:00

    I am referring to these threads:

    https://beta.postimg.org/image/64zl41p3h/

    I wrote on the first 3d, the user (I  reported the abuse), told me to follow anotherlink to  another thread, ok, I did, after 1 minute the same; ok, I followed a second 3d, suggested by this "user"; ok, on the third link? on the 4th?

    sorry I dont have enough time for practical jocke!

    Sorry Gordon but this were better via PM (otherwise too much OT, do you agree?).

    Send me a PM. But I already reported the abuse,  therefore I guess its not so important continuing to discuss here, ok?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-04-16T00:40:52+00:00

    Trilly -

    I just followed the instructions at that URL and it worked. Updates took 5 minutes to list the updates I have not yet made and I downloaded one of the Security Updates with absolutely no problem at all.

    Please post this answer where Ken and all the others can see it.

    Ken's idea is not necessary and sending someone to do a complete OS re-install is always a bad idea.

    Gordon

    about:

    PS: I just read

    http://answers.microsoft.com/en-us/windows/forum/windows\_7-update/windows-update-hangs/dbd539c3-bfc6-42df-a6ff-0e55ef7938eb?page=6

    at the bottom, there is a so called solution: I have 314573.

    Question: does this mean that on patch thusday May 2016 all will be ok?

    In other words:

    Are you sure that the cause of this issue was KB314573?

    Anyway on 10th (11th) May I will be able to verify and reply. thanks.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-04-15T23:59:39+00:00

    I am sorry, but I don't understand what "Threads" you are referring to PA Bear.

    I am responding to the threat lad I am following that is some 19 pages long at this point and is so confusing  with conflicting comments and discussion of the issue in vague and incomprehensible terms.

    Instead of getting angry, please try to explain what you mean in detail so that I can follow and then I will be able to avoid upsetting you.

    Was this answer helpful?

    0 comments No comments