You're trying to find ways around the June/July Rollup. The only one known is to install all updates listed in the upper table at this page:
and expect having to add a new one manually each patch day.
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.
You're trying to find ways around the June/July Rollup. The only one known is to install all updates listed in the upper table at this page:
and expect having to add a new one manually each patch day.
Nooo. I have tried 3 times now to install the rollup and got the same error every time.
0x8007000d "data is invalid".
Let it set overnight and had 28 total updates show up. Took only those listed as important security and the optional security essentials.
Don't have time to screw with anymore for the next 4-5 days.
Going to disable the wifi again and leave WU in "never check".
Ok. Had some work cancel so I got some time.
Ran WU and got a list of 4 IMPORTANT list that were automatically "checked" Updates.
From what I can find on the web. KB2952664 (This is the 3rd time I have had to hide this one. MS keeps unhiding it.) and KB3162835 are W10 Malware so I hide them.
KB3139923 break the ability to run msi and the recommendation was not to install it so I hide it.
KB3170735 looks like it is tangentially associated with W10 in that it is some kind of notification that something called "Windows Journal" is going to change.. So since I don't have that I hide it too.
The "OPTIONAL" list
KB3161102 ia also part of the "WINDOWS JOURNAL" thing so I hide it.
NOW to the I hope good part.
KB3172605 -- Looks like a repackaged July 2016 Rollup for W7 SP1 which is what KB3125574 that I cannot get to install is supposed to be.
Going to save it for a single install after I get the latest security essentials KB2310138
Hi Ken:
I was dealing with the same problem as well. I found your fix, you did isolate the problem, but for a non-tech guy like me I was not able for the life of me to manually install the two files that you suggested.
I did enjoy going through the c:\Windows\System32 files you pointed out. The version numbers you stated where there. as where the dates you mentioned.
Still frustrated I continued to search for a non-techie fix. ie: something that was automatic. I did find this update on this site:
https://support.microsoft.com/en-us/kb/3135445
It work like a charm, all I had to do was let the install feature of widows do its' thing and within minutes I was back in business, downloading and installing all 244 updates from the clean install I performed.
Now when I open the wuapi.dll properties window the version information reads:
File version: 7.6.7601.19161
and
Date Modified:
2/12/2016 12:19pm
Thanks for pointing me in the right direction and I hope this helps others with the same problems.
Harry Fischer
I tried Ken Morely's fix on one of my Win 7 machines and it worked perfectly.
Later I set up another machine and it worked again only to lock up afterwards.
I also had a Sony Vaio laptop that had locked up in the windows update.
This is when I saw "Volume Z" 's post, with the link to http://wu.krelay.de/en/
So I checked it out.
I really like the layout. very clear.
I then installed the brief list of stand alone updates.
Then I installed the most recent of the Windows update clients and everything is perfect once again.
So dragged out the Vaio and did the same.
It fixed the Vaio without any clean install being required.
To Volumn Z. Thanks mate, very nice fix extremely well presented.