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: Oldest
Most helpful Newest Oldest
  1. Anonymous
    2016-06-19T23:51:16+00:00

    Re-install Windows 7

    If you are re-installing Windows 7 after Windows 10, there is a separate page on how to do that. It is titled Win10 back to Win7.

    BEFORE you start the re-install, download (32 or 64 bit versions) KB3083710,  KB3102810, and KB3161664 in advance, and store on a USB stick,  Note:  When you search for the  64 bit versions of these KB’s specify 64 bit.  The 32 bit versions do not say which version they are.

    Copy your data off first.  If you can not start Windows 7, remove the hard drive and put it into a USB external drive housing.  Connect to a working PC, copy the data off.

    Always check to ensure the hard drive you are about to rebuild is actually sound from a hardware perspective.  Download and run your hard drive manufacturer’s drive testing software.

    If you have a corrupted Windows 7 system, you are trying to recover, you want to try a System Repair disk to boot the PC.  It may be more successful in fixing and offer other alternatives.  If you do not have one, go to any other PC that has windows 7 with the same bitness (32/64).  Start globe, All Programs, Maintenance.  You need just a blank CD.  When you boot, ensure that you are in fact booting on that CD and not the hard drive.  Usually pressing F12 will lead you to the option to do so.

    Best alternative strategies to rebuild are the following in preference order:

    1. Factory restore — replaces everything on the hard drive with exactly what it had on it when you bought it.  You access this before Windows starts using a special key that can varies by brand.  F11 is the most common. This is an option only if the installed hard drive is the original.  This is not a valid strategy on a failing hard drive.
    2. “Upgrade” install using the Win7 install disk. You start as if you are re-installing from scratch but when it gets to the point where it offers the Upgrade choice you choose that.   This is not a valid strategy on a failing hard drive.
    3. Full Clean install.  The only absolutely sure way to have a perfectly clean system.  If you are not using a brand new disk, when it shows the screen to select where you want to put Windows, click on the Advanced link and delete all partitions.  Do not install any software until after ALL Windows Updates are installed and Device Manager shows all devices installed.

    You will need a Win7 install disk for 2 or 3.  You will need a legal product code for 3 and the win7 disk must match the edition of the code and its bitness (32 or 64).  If you do not have the original Windows 7 install disk, borrow one from a friend.  If you can find it, a disk with SP1 (Service Pack 1) is going to save you many hours.

    NEVER install anything but Windows Updates until your system is up to date.  Once you have the update list, install all of them together.  Installing updates in batches will not speed the process or make it better.

    1. Change Windows Update setting to Never check for updates
    2. Start and complete the re-install of Windows 7 SP1
    3. BEFORE the newly installed system can go online for the first time, disconnect the computer from the Internet.  This timing is critical.
    4. Manually install KB3083710 and restart.
    5. Manually install KB3102810 and restart.
    6. Manually install KB3161664 and restart
    7. Restore the Internet connection and launch Windows Update as normal.
    8. After a few minutes, you should have plenty of updates to download and install.

    After Windows 7, system drivers and all updates are installed and any stable applications like Microsoft Office are installed and updated, and beforeany data or dynamic applications are installed such as antivirus software, create a system image.  It will take 3 or 6 DVD ***+***Rs (not -Rs) and about an hour.  When you are done you will have a very nice bit of insurance.  Should you ever again need to re-build a corrupted system or replace a hard drive, you will have a precise duplicate of your system as it was at time you made this image.  You can restore that image to a hard drive in about 20 minutes.  Creation of System Image is found in your menu under Maintenance, Backup and Restore. 

    Another great feature about using the image is that you do not need an install disk or a product key to do the re-install the next time.

    I emphasize the need for PLUS R DVD blanks.  Do not use the more common MINUS R DVD blanks.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-06-20T00:04:53+00:00

    "You do not want any of these updates" - exactly. You do not want KB3083710. :D

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-06-20T01:44:33+00:00

    Actually the download of KB3161664 did the trick. the other updates I already have. thanks so very much. I really appreciate your help.

    kind regards

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-06-20T14:14:45+00:00

    TheFrood:

    In my cases, the reinstall is what I want to accomplish anyway.  The goal is to have a fresh, clean system in a known state that I have confidence in.  So for me, the reinstall isn't something to be avoided - it's actually the goal.

    I understand that others may have different problems and needs.

    Ken Morley

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-06-20T14:21:51+00:00

    Volume Z:

    I have done several successful reloads skipping the KB3083710 and so I don't think it's really necessary.  On the other hand, it's not problematic either.  Users can apply one or both and get the same outcome.

    Ken Morley

    Was this answer helpful?

    0 comments