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-02-03T22:36:02+00:00

    All I can add at this point is that I do clean re-installs quite frequently and have never run into the problem you describe.  My procedure is as follows:

    1. Custom install
    2. Delete all partitions except for OEM
    3. Install
    4. Check drivers, if Network driver is missing, find and install it.  Others can wait.
    5. Begin Windows Update.  Setting to NEVER.  Could take 4 to 6 hours, but it ALWAYS produces a list of updates.
    6. Right-click and hide the undesirable updates.
    7. Some driver updates will be proposed in Important and Optional.  Accept those
    8. Install ALL of the rest of the updates at the same time.  Could take an hour or several to do this.
    9. Restart
    10. Start Windows update again and repeat.  Do this until no more updates are offered.
    11. Install MS office software
    12. Start Windows update again and repeat, and repeat till no more offered
    13. Clear temp and recycle
    14. Defrag

    Clean Install tip

    After Windows 7, system drivers and all updates are installed and any stable applications like Microsoft Office are installed and updated, and before any 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 that point.  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-02-03T22:34:36+00:00

    Hi Ken,

    One reason I didn't want to start with your 7-step routine was step 3.  The last thing I need is to spend several hours more downloading and processing yet another new install.  I naively thought that MS would have the answer and, with the intro of a case number, would be able to get them to perform. [I wonder what he'd have been able to do if I'd got my wallet out?]

    In any case, sorry to be repetitive, but I still need advice on how to individually download and install updates (steps 1, 4, 5).  If you can help with this (sorry if it's a bit basic, but I don't want to waste any more time), I'll start again and report back.

    I can't afford to do this on my PC as it's too imprtant to "lose".  So I do need to sort out the automatic W10 download fault if I'm to install the manual updates (unless the answer to the above question is all I need).

    Thanks for your patience,

    Ian

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-02-03T21:17:16+00:00

    Ian:

    I am a little surprised that you've gone through all of this effort, but haven't even tried the seven step process I outlined at the beginning of this post.  The whole purpose of my posting this was to save others time and trouble.

    You said:

    His reply was a bit of a shocker:  "There is no way to avoid it.  You really need to go through it and fix it"!

    What the MS tech REALLY meant to say is that he didn't know of a way to stop it.  There is a way to stop it and it is clearly described within the sevens steps.  In fact, stopping 7.6.7600.320 from being applied is critical to resolving the problem.  If 7.6.7600.320 gets installed, I do not know of any way to recover other than to start over.

    I think I've made this about as simple and straightforward as I can.  I suggest that you at least give it a try, because it really doesn't take very long - certainly not as long as all of the posting, calling MS, etc.  Why don't you just take the easy way out?

    Ken Morley

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-02-03T20:09:53+00:00

    Hi again,

    I made an attempt to follow the above guidance but didn't get anywhere, so re-contacted MS Customer support, cross-referencing the original case number.

    There was no disagreement when I suggested that the problem was based on the rogue update 7.6.7600.320.  He spent about half an hour looking at the problem before suggesting that I could make use of their "advanced tools" if I paid.  I politely declined, whereupon he proceeded to spend about another three-four hours, off and on, investigating.  Some of the work he did looked like the tasks mentioned above, but I couldn't keep up.

    He eventually gave up, suggesting the only way out was an ISO install of W10 or W7.  I declined the offer of W10 and asked whether, if I go to the lengths of a fresh install, there was any way of preventing the appearance of the rogue file.  His reply was a bit of a shocker:  "There is no way to avoid it.  You really need to go through it and fix it"!

    It looks as if I'll have to go through it all again.  I'll follow the advice noted above and see if I can stay one step ahead.

    I still need help with the other issue, though - how to prevent downloading of W10 on my PC when I try to install downloaded security updates.

    Ian

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-02-02T22:24:48+00:00

    Thanks for the quick response, Ken.  I wasn't aware of the issue when I reinstalled W7, else I could have avoided the problem.  Since I use my PC for serious business and it's also infected, I'd better get on with it.  Two questions, though:

    I asked in a  post above, how do you download and, particularly, install updates one by one (sorry of it sounds a silly question).

    Second, on MY PC, even when I hide the W10 update download, not just unselect it, when I try to download the other 74 or so updates, it still tries to download W10.  Will the processes described above deal with this?

    Another question whilst I remember - before I reinstalled W7, I did try the restore routine but it just hung.  Again, same basic problem?

    Thanks again,

    Ian

    Was this answer helpful?

    0 comments