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-11T15:33:37+00:00

    Hi CT,

    I perhaps should have made it clear - I have Windows Update set as advised.  I only go to that page every month or so for a manual update, when I check against the list of bad KBs.

    Whilst I'm on, I followed FA's tip (thanks) and went back to a previous restore point, only to get a Norton error page, leading me to uninstall/reinstall N360.  Overall, no improvement.

    Ian

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-09-11T13:29:41+00:00

    Your problem is likely caused by Windows Update.  The solution is set Windows Update settings to Never. 

    Follow the instructions on this thread:

    http://answers.microsoft.com/en-us/windows/forum/windows_7-update/windows-7-update-solution/f39a65fa-9d10-42e7-9bc0-7f5096b36d0c

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-09-11T07:44:32+00:00

    Can you use a restore point to a time before the Norton updates?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-09-11T06:58:17+00:00

    Hi all,

    It's a while since i stopped following this thread, my own machines being clean and running OK, monitored by GXW - until recently, that is.

    Last week, whilst away on holiday and using my laptop, I suffered a problem that seemed to involve high CPU usage.  I checked for this on line and found this thread:

    https://community.norton.com/en/forums/chrome-huge-cpu-spike-bug-still-present#comment-7162191

    I had a reply from the Norton forum:

    When I used Windows 7 after a fresh install I had faced similar issue. Go to Add/remove programs and check if this patch is installed: Windows6.1-KB3102810-x64 if it's not installed then you can install it from here:https://www.microsoft.com/en-us/download/details.aspx?id=49540(link is external) That patch fixed that high CPU usage by svchosts memory leak issue. Let me know if it works

    I followed the procedure described and, lo and behold, my laptop's now fine.  When I came home yesterday and fired up my PC, it downloaded a week's worth of Norton updates, one of which required a restart.  Then the problems of high CPU usage started and persist.  I couldn't apply the fix advised in the Norton tread because the MS update was already there. 

    When I checked this thread, to refer to it on the Norton thread, I was surprised to see that the MS update referred to is also mentioned on this thread 0 KB3102810!  I hadn't made the connection with this thread at that point.

    I should perhaps also mention that on both machines, updating Windows is a very long process, despite GWX recording that there's no sign of W10.

    Apologies if this is covered somewhere in the 51 pages of this thread, but has anybody any ideas?

    Thanks,

    Ian

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-09-07T22:13:04+00:00

    Thanks for the additional advise. Makes complete sense,  very much appreciated.

    Kind regards to Canadian Tech.

    Was this answer helpful?

    0 comments No comments