Sorry for the long title.
This past Tuesday Microsoft released a slew of new security patches. I won't go into detail about all of them, but suffice it to say we're seeing KB979909 become a pretty hairy thorn in our side.
We deploy all of our updates via SCCM. In my pilot testing I've noticed quite a few machines that come up with an error code of -2147023293 with a HexErrorCode of 80070643. This error basically means a fatal error during installation.
Microsoft's recommendation on how to fix this is referenced here: http://support.microsoft.com/kb/923100/ however what I'm seeing in my environment is nearly a 10% failure rate on my pilot users. There's no real easy way to fix this remotely, and my help desk will be busy for a couple of days fixing this issue for the amount of calls they'll be receiving.
Other people are seeing the same problems. For the time being, we're pulling the update until we see a better solution than uninstall all versions of .NET as the fix.
Below are links to other people experiencing the same problem with this update. Some are also seeing problems with KB982168, and KB979906.
http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Q_26246663.html
If you're having the same problem, post a comment below.
5 Responses
Hi, I fixed this problem, not by re-installing .Net as recommended by Microsoft, but by (re-)registering Windows Script Host with "regsvr32.exe wshom.ocx"
Looks like both KB979909 and KB979906 execute VBScripts as part of the updates, so if the Windows Script engine isn't properly set up they won't work.
As a bonus, the Mr. FixIt scripts work now, too.
Thanks for your reply eigenaut - that didn't actually help me (I have 68 machines on our network failing to install KB979909 AND KB979906), however it set me searching on a similar theme and I ended up running this command instead which also reregisters part of the windows script host.
regsvr32 scrrun.dll
I've put this in a GPO startup script and all my machines are now isntalling - big relief! Thanks for the prompt...
Yes, these .Net patches stink. Curious how the next week will go as my 6,000+ users begin installing these patches via SCCM software updates. Not one 979906 (related to .Net 1.1) had gone successfully in my environment during testing - so I pulled it. We've got over 1,000 user's with .Net 1.1 installed . It's odd - when I install the patch manually - it looks for a temp directory or source files or something. For 979909 - I've had 1 failure so far - although all event logs & SCCM logs showed it was successful on that machine; only SCCM reported it as "Failed" after the "Pending Verification" step. It even was showing in Add/Remove Programs. I ended up stopping the Automatic Updates service, deleted the SoftwareDistribution folder, rebooted & tried the patch again. Success via SCCM now...we obviously need to address the 979906 failures & our .Net 1.1 concerns. Would be nice to just get rid of it...and we'll soon be pushing .Net 4.0 out - oh joy...I <3 .Net...
I hear ya sknyfats. Oddly enough I haven't had any issues with 979906. Mainly 979909. I'm going to production with 979906 on Friday.
Here's a potential explanation for the root cause of the failed updates:
http://blog.usabilitythinking.com/2010/06/root-cause-for-corrupted-net-framework/