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-06-17T09:16:41+00:00

    Hi Ken,

    thanks for this insightful information.

    I just got back to Windows after leaving when Microsoft upgraded to VISTA.

    I just bought a version of Windows 7 yesterday!!! I bought Windows 7!!

    And like you mentioned this problem occured right from the start.

    I have a clean install and can try above steps as much as i need to but before i do, i gotta question.

    When i look up the mentioned DLL's and check their PROPERTIES there is a previous version of the file in RESTORE with the version and date you mention above.

    Is it as simple as in RESTORE to previous version of the file? So disconnect from the internet restore the files restart and see if will have the same effect.

    I ask this because it has been at least 10 years when on a windows computer.

    Kind regards,

    Arnold

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-06-15T13:39:44+00:00

    Yep I posted the link here :)

    Glad it helped

    Cheers.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-06-15T13:06:40+00:00

    Personally I am absolutely convinced it is part of the MS W10 marketing plan. Never had the problem until I unknowingly installed one of the W10 nagware "updates" on my computer. 

    My thread on this is here http://answers.microsoft.com/en-us/windows/forum/windows\_7-update/windows-7-home-premium-refuses-to-update/4fa84834-ea3f-414d-89b1-b2e703adf741 and thankfully someone linked me to this one.

    If I have anything to contribute it is the list of trojan nagware updates MS shoves out in their "recommend" updates lists that automatically get installed if your computer is set for auto update. 

    I also detail what I have done to keep it from happening to me again.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-06-15T10:32:21+00:00

    Ken,

    Excellent analysis and it worked perfectly, now downloading 240 updates after third clean install of Windows 7 HP 64. 

    As I am often asked to upgrade old Win XP installations, this is going to save me considerable time and effort.

    I wonder whether there is a conspiracy at play here to force Win 10 installations in frustration over the Win 7 update issue or whether it is plain incompetence on behalf of Microsoft.  This problem is all over the forums and nowhere have I found anything from Microsoft that goes anywhere near a solution. There are recommendations, but your work here is the only solution to this very well known problem.

    I'm just going to write here that this is the only solution I know to the 'Following a clean install of Windows 7, windows update remains at "checking for updates" forever....' and hopefully this post will get to the top of Google search lists.

    Well done Ken, thank you.

    Kind regards,

    Wayne

    Following a clean install, Windows Update remains at "Checking For Updates" forever...

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2016-06-13T18:13:10+00:00

    One thing that helped me with win7 was to check my time, and delete files from  C:\users\all users\application data\microsoft\network\downlder and then install (KB947821)

    Was this answer helpful?

    0 comments No comments