That stuff is outdated. KB3172605 will install version 7.6.7601.23453.
Regards, VZ
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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:
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:
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.
That stuff is outdated. KB3172605 will install version 7.6.7601.23453.
Regards, VZ
Ahhh,,I was trying to install these:
You must install KB3020369 FIRST, then KB3172605
I guess things have changed since the time this was written, or I have missed something. Win7 SP1 64bit new installation (disconnected from internet and chose the "do not update" option in the installer) and neither of the KB's will install...giving the message 'does not apply to your computer' (or similar). Any advice out there?
- After a few minutes, you should have plenty of updates to download and install.
Ken Morley
Indeed! After a few minutes Windows did tell me there were lots of updates on my newly installed Windows 7 SP1 build running on VMware Fusion on a MacBook Air. And, of course, I am installing all those updates right now.
Ken, I have been trying to solve this issue for several days. Lots and lots of people have posted "solutions" but ONLY YOURS WORKED. Thank you so very much for taking the time to clearly state the exact steps required to fix this problem!!!
You are truly a ROCKSTAR!!!
Sincerely,
Randy Sandberg