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-12-28T15:50:44+00:00

    Sue:

    That is exactly my point:  Whether it's due to a customer's older incompatible hardware, a business-critical app that won't run under Windows 10 or whatever, the customer's needs should govern the choice - not Microsoft's.

    I don't blame Microsoft for encouraging the adoption of Windows 10.  But some of Microsoft's "encouragement" methods are unethical and probably just this side of legal.  I am not advocating anything, but it wouldn't shock me to hear of a class action lawsuit or possibly government intervention at some point.

    The shame of it is that these actions tarnish Windows 10 - an otherwise fine product. These ham-handed efforts will probably end up as a chapter in some Business School textbook as a perfect example of how NOT to motivate customers.

    Again, just my opinion.

    Ken Morley

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-12-28T14:58:50+00:00

    I think you are being too easy on MS Ken.. 

    I just bought a refurbished Dell 790 with Win 7 Pro and it arrived with 4 of the 15  Win 7 KB's that have been identified as part of the "updates" that try to force people onto WIN10, 

    I removed and hide them and ran WU and two of them came back up in the list of recommended updates.

    MS has NOT given up on being sneaky and underhanded. They are even un-hiding rejected updates.

    BTW, it came with the TWO recommended KB's on it and the WU so far works fine but I am keeping it on Never update and I get to see the MS notice on every startup that I have a severe problem the requires IMMEDIATE action.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-12-28T14:53:49+00:00

    The irony of this is- NO, everyone's pc/ laptop is  NOT compatible with downloading a new OS- i.e.,Windows 10. We have, therefore, been made to suffer by these methods, OR-  buy a new device. It's all well and good for IT professionals such as yourself, to be able to pick and choose which system best fits your work environment/ devices. We, as individual consumers, however, object to being manipulated especially because we don't possess such technical expertise. Not intending to sound like I'm preaching to the choir, thanks for the response-

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2016-12-28T14:12:07+00:00

    Sue:

    It's true, of course.  

    Microsoft really, really wants users to upgrade to Windows 10 and they tried to make it really, really hard for users to stay with Windows 7.  The article you reference details some of the ham-handed and/or unscrupulous steps that Microsoft employed to force the change.

    We all know that it would take minutes for Microsoft to remove the broken Windows Update version from the update catalog and we've all wondered why they haven't done it.  I think you would have to be naive or foolish to recognize the oversight for anything other than what it is:  an unscrupulous attempt by Microsoft to make life more difficult for Windows 7 users. 

    The irony is that, as the article you reference points out, Windows 10 is quality, modern OS and I prefer using it over Windows 7.  But ultimately, it is up to the user or their IT administration to choose the OS best suited to their needs.  It is fine for Microsoft to encourage Windows 10 adoption.  But it's flat wrong for Microsoft to try to force Windows 10 if the change is not in the customer's interest.

    The above represents my opinion and everyone is free to develop their own.

    Ken Morley

    Was this answer helpful?

    0 comments No comments