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

580 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2016-07-11T16:53:39+00:00

    Nope this should be all

    https://support.microsoft.com/en-us/kb/3161608

    Until tomorrows round hits and another issue surfaces :)

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-07-11T15:58:35+00:00

    Download KB3102810 or KB3138612 or KB3161664

    Oops. KB3161664 does not belong in that row. It's not an update client. If you just install KB3161608 (Update rollup including latest update client), this will address all issues currently known. The problem will not turn up again later in the updating process.

    Regards, VZ

    Hi, VZ --

    I haven't done KB3161608 since I used KB3161664 (and its two previous incarnations) to fix the monthly update issue.  If I do KB3161608, is there any other update needed before doing it (as prerequisite; I have SP1 on my Win7 already)?  I'm nervous about these things.  ;-)

    Thanks again for the monthly replacement update "fix" info.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-06-30T21:28:24+00:00

    You're right, I changed the KB# in the post.

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-06-30T19:20:34+00:00

    Download KB3102810 or KB3138612 or KB3161664

    Oops. KB3161664 does not belong in that row. It's not an update client. If you just install KB3161608 (Update rollup including latest update client), this will address all issues currently known. The problem will not turn up again later in the updating process.

    Regards, VZ

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-06-30T17:57:26+00:00

    Ken:

    You said "I'm sure that there is some way to recover a system once 320 is installed.  But I know that it's going to be difficult and complex enough that it makes more sense to simply reload again."

    This is definitely possible Ken - as VZ and others have confirmed, a number of entries on this post have been successful recovering from 320, as have I - multiple times now, and it is very straightforward, not difficult at all. I have yet to see it fail.

    Why don't you try the procedure below the next time you do an install and then amend your first post in this tree? A windows reinstall is not necessary when 320 has installed. This will save you time.

    The "Checking for updates..." message you get when you are installing patches on top of 320 only occurs if your network cable is plugged in. Just unplug the network cable and the patches will install.

    I have verified that this install procedure works perfectly with either 3102810 or 3138612 installed on their own without the other one. Both on multiple installs. It just works. Next time I do an install I will try 3161608. Might also try without the "Never check for updates" step to see if can be done even easier.

    1. Let 320 autoinstall or try it on a machine where it has autoinstalled.
    2. Download KB3102810 or KB3138612 or KB3161608 (64 or 32 bit matching the Win7 (SP1) version being installed)
    3. CPL - Windows Update - Change Settings - Never check for updates (not recommended) - OK
    4. Disconnect network cable
    5. Reboot.
    6. Run one of the above MSI installers you downloaded. You will only need one of them. It will start "searching for installed updates" then immediately ask if you want to install the KB. OK to that. If the network cable is not disconnected here, it will stay searching for installed updates forever.
    7. After successful installation, reconnect network cable, then reboot again.
    8. Search for updates, it will find 200+ of them within a short while. I usually choose to install updates other than Windows updates before I do this step.
    9. Starting here, I have found that Windows isn't able to install all 200+ updates in one go, it is however possible to do it in 5 reboots. Or rather it is possible to check them all, and install them in one go but you will get a bunch of time consuming fails. This happens for me even if I don't let Windows install 320, so it is not unique to fixing a machine with 320 installed.
    10. For some reason KB9<something>: "Windows 7 Service Pack 1" will be in the list of updates Windows wants to install. I have definitely seen it on Windows 7 ultimate SP1 and Windows 7 professional SP1, the latter both with VLK versions and single license versions. If this is in the list it has to go in first and on its own. I have tried bundling others in with it but this one has always failed when doing that. So check this one on its own, let it install, then reboot, then search for updates again.
    11. Uncheck all fixes, then check and install all fixes up to ~ KB291000 including optional ones. It'll be about half of them. Reboot, then search for updates again.
    12. Install all remaining fixes except the latest .net version as it seems to want to go in on its own. Reboot.
    13. Install the remaining .net version. Can't remember if it wants a reboot or not, if it does, reboot and search for updates, or else just search for updates.
    14. Install the remaining updates and reboot. Your machine should now be at the latest update status without a single failed update in the history.

    Gurra1

    (edit 30/6: fixed incorrect KB#)

    Was this answer helpful?

    0 comments