Yep and published :)
http://www.zdnet.com/article/sticking-with-windows-7-the-forecast-calls-for-pain/
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.
Yep and published :)
http://www.zdnet.com/article/sticking-with-windows-7-the-forecast-calls-for-pain/
XX:
Everything about this debacle has been time-consuming and so I appreciate your taking the time to analyze and report back. Your effort helps us all save time ;)
My theory is that one particular version of Windows Update causes the issue described in my original post. Once that version of WU is installed, I don't know of any way to uninstall it to make WU functional again - that's why I have to go back and reload again from scratch.
If you are finding updates that break WU functionality and then you uninstall that update and WU works again, that is a different issue than what I described or have experienced. Also, the issue I describe is NOT with any KB or update that you select and install. It's with an update that WU downloads and installs automatically, without user notice or permission. It doesn't even appear in the list of installed updates, so there is no easy way to remove it. The only way to know whether it's been installed or not is by checking the version of the WUA exe or DLL.
To be totally clear, if Windows Update decides to update itself, the user will never know it. There's no warning, display, request for permission or even a "installation successful" notice - it's entirely hidden.
Thanks again!
Ken Morley
Roger:
Just right-click on any of the WUA DLL's or exe's, choose Properties, click the Details tab and look for the lines titled File Version and/or Product Version (these two should be identical, so use whichever you prefer).
I haven't tested this, but I've noticed that the WUA DLL's and exe's get updated as a set. I haven't seen an example yet of where they are not all the same exact version.
Ken Morley
I couldn't find a way to check the version of WU. Thank you.
Check the version of this program:
C:\Windows\System32\wuauclt.exe
That should tell you the version of WU on your computer.
I just tried this and it worked like a charm. I let it run over night and now have 247 updates available.
I couldn't find a way to check the version of WU. Thank you.