Ken,
I have a 32-bit system with the same problem. When I try these installs 5&6, it says my system does not support it. I can't find a 32-bit update. Is there one?
TIA
C :)
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.
Ken,
I have a 32-bit system with the same problem. When I try these installs 5&6, it says my system does not support it. I can't find a 32-bit update. Is there one?
TIA
C :)
This is what the 32 bit x86 download page looks like. Notice that it does not give any indication or choice as to which version this is. If you want 64 bit, and you specify that in your search, you will see page that specifically says it is a 64 bit version. If your search does not specify you get this page.
Keeping in mind that "if it ain't broke, don't re-break it".....I had the same problem with 2nd-Tuesday updates that many people had -- checking, checking, checking indefinitely. When the KB3145739 update solution was posted on here, I took my WU off auto-check (strictly manual checking now), downloaded and installed KB3145739 and all has been well ever since. My question is this....I don't have KB3102810 installed. I wasn't having the problem at the time 3102810 was offered, and since it wasn't a Security update, I put it under "hidden", which is where it still is. Should I download and install 3102810 now, or just leave well enough alone?
*BUMP* -- Any thoughts on my question above, Candian Tech (or anyone)?
You saved lot of hair from my head, i was about to lose my mind ;)
I also managed to trace cause to windows update agent and 320 but never tried installing new agents BEFORE connecting to internet!
Thanks for the great thread and i'm glad i found myself here !
Ok, Found 2 that were not on my original list and had slipped in. KB3123862
KB2952664
Got them un-installed, now to go blacklist them in WU.
Thanks
List of updates that if already installed should be removed:
KB3035583
KB2952664
KB2977759
KB3021917
KB3075249
KB3080149
KB3083710
KB3083324
KB3090045
KB3112343
KB3022345
KB3068708
I believe there is an update missing from that list: KB3123862.