Following a clean install, Windows Update remains at "Checking For Updates" forever...

Anonymous

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:

Download https://support.microsoft.com/en-us/kb/3020369 and https://support.microsoft.com/en-us/kb/3172605 in advance.
Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.
Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.
When the installation prompts for updates, choose "Ask Me Later".
Apply KB3020369 and then KB3172605 in that order.
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:

Download KB3083710 and KB3102810 in advance.
Disconnect the computer from the Internet so Windows Update cannot automatically update itself to 7.6.7600.320.
Perform a fresh reload from Recovery Media or Windows 7/64 with SP1 RTM.
Manually install KB3083710 and restart - WU components will now be version 7.6.7601.19016 dated 9/25/2015.
Manually install KB3102810 and restart - WU components will now be version 7.6.7601.19046 dated 10/20/2015.
Restore the Internet connection and launch Windows Update as normal.
After a few minutes, you should have plenty of updates to download and install.

Ken Morley

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

Anonymous

2016-06-29T12:40:54+00:00

Hey VZ, sorry to jump in on your discussion but ive started having problems again with windows update still hanging "Searching for updates" & would appreciate your help & anyone else's input if there having the same issue i'm having. Long story short I followed Kens advice and yours on manually downloading one or both of the WU KB3083710 & KB3102810 to install the WU component to the latest Version to 7.6.7601.19046 dated 10/20/15 which still remains. Now for a few months my updates have been fine but recently I downloaded this update:-

(Update for Windows 7 for x64-based Systems (KB2506014)

Installation date: ‎11/‎06/‎2016 00:04

Installation status: Successful

Update type: Important

An issue has been identified that could allow a user with administrative permissions to load an unsigned driver. This update resolves that issue. You can help protect your system by installing this update from Microsoft. After you install this update, you may have to restart your system.

More information:

http://support.microsoft.com/kb/2506014

Help and Support:

http://support.microsoft.com

which MS said would resolve security issues)

Now ive not checked for any updates since I allowed this one to be installed manually, even though it wasn't listed as a security update itself but within the update it explains it is hence the reason I downloaded it. I yesterday turned on my laptop an just wanted to check for any new security updates and now im back where I started hanging searching for updates. Can you advise me whether this update is causing the problem I now have or have I made a big mistake & do I have to go back to do another clean install which I really don't want to do as I have my machine how I want it, or is there an easy fix for this.

best regards
Was this answer helpful?

0 comments No comments
Anonymous

2016-06-29T12:08:17+00:00

I am not positive whether I used "Ask Me Later" or "Never Update".

But that's what marks the difference between 7.6.7600.320 getting automatically installed or not. You can't skip "Set up Windows" anyway, so what I'm saying is: If you have to make a choice, why not make the right one.

Regards, VZ
Was this answer helpful?

0 comments No comments
Anonymous

2016-06-29T11:21:31+00:00

Ken,

I think there are two separate things going on with my system. Maybe some other systems too.

1st and worst is that I have a machine that MS thinks will run W10 and MS is bound and determined to force me onto it.

The other is that MS issued a broken updater and for whatever reason, probably to push IE11 adoption since systems with IE11 don't seem to have the update issue, refuses to fix it.

I know what WU settings I had left the machine in on April 2nd (NEVER) when I completed the re-installation of W7 Home Premium 64 bit and the blocking of ALL (at that time) known W10 malware.

Then on April 17th, the updater updated and downloaded and installed everything related to W10 that I had blocked including IE11. So, even my process using Never10 may have a flaw with regard to blocking the W10 malware even though it did get my system running.

I was able to roll it back with a system image but even that was a PITA.. So, for now, since I have a separate linux mint opera/chromium system for my web activities, I am keeping the wifi adapter in the W7 machine disabled.

In the mean time, your re-installation/recovery plan is probably the best option for recovering an older W7 machine that isn't W10 capable.

If you do a rewrite you need to put more emphasis on the necessity to disconnect from the internet to actually get it to work. I missed that twice and I used to operate, maintain and teach the operation and maintenance of Naval Nuclear power plants so missing an instruction was a bit embarrassing.

Perhaps a walk through on how to get and make a SP1 installation disc would also be in order since that would remove the necessity for any internet connection until the system was past needing a lot of updates.

Just the thoughts of a novice that now knows far more than I ever wanted to know about this/these topic(s).
Was this answer helpful?

0 comments No comments
Anonymous

2016-06-29T10:31:06+00:00

Davi:

When I tested disabling Windows Update through the prompt during Windows 7 reinstallation, I am not positive whether I used "Ask Me Later" or "Never Update". I think it was "Never Update", but I can't really be sure. I did formally track the WUA versions before, during and after and found that technique was successful for me.

With all of that said, I still prefer to just pull the network cable and know for sure. That's what works best for me.

Ken Morley
Was this answer helpful?

0 comments No comments
Anonymous

2016-06-29T10:13:15+00:00

Lura:

I've only tried using the Convenience Roll-Up once, but the result was not good. I think that *might* be related to trying to install all updates at once.

I always install updates in reasonably sized batches of 20-30 with a restart between batches. That takes longer, but for me seems to provide more consistent results with less conflicts.

While the conventional update process takes longer, I don't think it's much longer. Using the Convenience Roll-Up wasn't exactly speedy.

I'll try the Convenience Roll-Up again when I have more time, but for now, I am not using it.

Ken Morley
Was this answer helpful?

0 comments No comments