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-06-03T23:17:09+00:00

    Ken Morely,

    It has been roughly 5 months since you posted this discussion/answer thread (whatever it is exactly) and I want to give you my sincerest thanks. I replaced the hard drive in a slightly older model laptop and as previous laptop repairs/replacements went, I started with installation of clean OS (USB drive install media), then moved on to system drivers (video, wifi, etc), then go with AV software and web browser of choice (Chrome, sorry Microsoft). All it did all day yesterday was hang on "Checking for updates..." for hours or as long as I let it. No matter what I seemed to do, it hung. I did a lot of crazy stuff I've never done before checking the error on Windows Update Fixit (it was an Access Denied type error so SubinACL, some bits of code, etc) and nothing seemed to work. Your diligent and comprehensive solution is a blessing to me at this point. I had no idea what I was going to, and ultimately thought it was Windows 7 Ultimate (which I'd never installed) that had the issues. I kind of understand all the hassles, but at the same time I don't. Yeah, Microsoft would rather you install Windows 10 immediately, but I kind of feel that would be alienating a good portion of the user base. But I am not Microsoft nor big business so I can't understand marketing and business tactics. Anywho, again, my many thanks. I hope this helps anyone who runs into the same issues as I and I would direct anyone who needs this info this way. :-)

    Sincerely,

    Steph

    Was this answer helpful?

    0 comments
  2. Anonymous
    2016-06-02T23:54:09+00:00

    this KB3125574 take around 3-4 hours to check and installed overnight

    If KB3125574 is applied, you don't have to wait anything out. Before installing, set automatic updates to "Never check for updates" and restart. Additionally install KB3145739 and KB3153199 (expect this premise to change next patch day). Only then start using windows update.

    Regards, VZ

    Absolutely true. I did the first one in April and the second in May and all went well in both cases.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2016-06-02T18:06:56+00:00

    this KB3125574 take around 3-4 hours to check and installed overnight

    If KB3125574 is applied, you don't have to wait anything out. Before installing, set automatic updates to "Never check for updates" and restart. Additionally install KB3145739 and KB3153199 (expect this premise to change next patch day). Only then start using windows update.

    Regards, VZ

    Was this answer helpful?

    0 comments
  4. Anonymous
    2016-06-02T15:04:04+00:00

    First - Thank you for Ken Morley shared his effort online for someone like us. As a IT guy, I'm using another M$ PIA patch program WSUS, but occasionally still dealing with standalone Windows Update, and I'm sure this will cut our patching time from days back to hours. I remember sometime last year, checking update for Windows 7 only take like 2-3 hours , but this year taking days...

    Second - I'm here to shared my partial testing result and hope this will also benefit someone else. (As of 2 June 2016)

    Testing environment - ESXi5.5 VM, Install Windows 7 x64 SP1 from scratch.

    (Oh, make sure your Windows DVD/ISO is SP1, I'm wasting some time to find out my ISO was original non-SP1. And make sure download the correct x86 or x64 patch for your system.)

    Note: I'm only testing to the point "Check for Update" and "assume" those update should or will install correctly afterward.

    Test 1 - Install KB3102810 without internet to bring the file version to 7.6.7601.19046. (Credit to VZ - skip KB3083710.) reboot and check for update, take me around 10 minutes to show 225 updates. Then update KB3138612 - file version 7.6.7601.19161 and reboot. Check for update and within 8 minutes to show 224 updates. KB3138612 should be the current version of the Windows Update file component from M$ update server.

    Test 2 - Install KB3138612 directly on the flash install Win7 without internet and reboot. The first Check for update give error within 5 minutes but second try show 224 updates within 8 minutes. I'm assume skip KB3102810 could be another method.

    Test 3 - Install KB3125574 (KB3020369 prerequisite) directly on the flash install Win7, (I'm consider this is some kind of SP2, the size is almost 500Mb.) and bring the file version to 7.6.7601.23435. However, this KB was taking 3 hours to check update and still checking, then I stop it. Because on an old Asus laptop I flash installed 2 days ago, this KB3125574 take around 3-4 hours to check and installed overnight, (I let it run overnight.) so I'm assuming this method will work as well but take couple hours instead, which is still acceptable to me. And the total number of update down to 71 after that KB.

    Note: On all of my aged old W7 VM, all file version only go up to 7.6.7601.19161. I believe that is the latest version on the update server.

    Remember, I posted this just to shared my work and you justify which way or method is best fit for your situation.

    Roger

    Was this answer helpful?

    0 comments
  5. Anonymous
    2016-05-31T20:10:06+00:00

    Wow, worked perfect! I was pulling my hair out trying to figure out what was wrong.

    Thank you!!!

    Was this answer helpful?

    0 comments