If you have KB3161608 installed, this implies having KB3161647 installed. KB3168965 is the name of the downloadable form of KB3171481. :)
Thank you kindly.
L.
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.
If you have KB3161608 installed, this implies having KB3161647 installed. KB3168965 is the name of the downloadable form of KB3171481. :)
Thank you kindly.
L.
If you have KB3161608 installed, this implies having KB3161647 installed. KB3168965 is the name of the downloadable form of KB3171481. :)
Hey Ken,
I pulled off 'removing' updated 7.6.7600.320 without having to f-disc and reinstall W7 by using system restore via booting to ERD. I'll explain in detail:
Did a clean W7 Ultimate install, including the update setup that automatically installed 7.6.7600.320. Then when I tried running Win Update it would just keep searching forever and ever. Of course I couldn't uninstall it from the control panel, so I tried system restore from the 'computer properties' tab. Restore failed.
I then unsuccesfully used this MS FixIt 971058 to diagnose and repair updates, but hang onto this cause it comes in handy later:
https://support.microsoft.com/en-us/kb/971058
Then I created a bootable Win 7 repair disc (control panel -> backups), put it in my dvd drive, rebooted, pressed F12 for boot options, selected 'boot to cd/dvd...', then let it load. Select 'repair my computer' or something to that extent, and then used 'tools...' and the System Restore option here. This one worked and I restored to just before any windows updates occurred. Rebooted. No more 7.6.7600.320!
Not out of the woods yet, those two manual updates, KB3083710 and KB 3102810 still wouldn't install (make sure you DL the correct version of those updates, x86 or x64 bit for your system, that was a first mistake I made).
Then I went back to the Windows update diagnostic FixIt, ran it again, and it succeeded except for a red 'X' to the right of 'Service Registration is missing or corrupt'. Then I rebooted, ran the same FixIt AGAIN, and this time it succeeded!
Victory! No win 7 reload required.
It's simply due to KB3102810 - even KB3138612 - being older and inferior to KB3161647 (KB3161608). Neither KB3102810 or KB3138612 can process KB3145739, KB3153199, KB3161664 or KB3168965 properly which means they are part of the general issue.
KB3161647 is designed to handle KB3145739 and KB3168965, meaning it's the only effective solution.
Regards, VZ
Hi, VZ --
I see that you associate KB3161608 with KB3161647 and KB3168965 with KB3171481. I have downloaded and installed the first and third, but not the second and fourth. Do the second and fourth contain other things that I need and should I do those as well? Or no need to?
As always, your help is most appreciated.
L.
It's simply due to KB3102810 - even KB3138612 - being older and inferior to KB3161647 (KB3161608). Neither KB3102810 nor KB3138612 can process KB3145739, KB3153199, KB3161664 or KB3168965 properly which means they are part of the general issue.
KB3161647 is designed to handle KB3145739 and KB3168965, meaning it's the only effective solution.
Regards, VZ