|
There is a fair amount of chatter in Microsoft forums regarding problems cause by recent Microsoft patches. [1][2][3][4] From what I can gather users are repeatedly being prompted to reinstall 3 older .NET patches on some OS distributions. It looks like MS12-035 was intended to replaced 3 older patches MS11-044, MS11-078 and MS12-016 and something isn't quite right. You may want to hold of deploying that patch until we know more. Thanks to Dave (ToyMaster) for the heads up and hard work researching the issue. I think he has a blog post pending [5] that will explain the issue in more detail. I'll keep you updated here as I learn more. Do you have any more information for us? Leave me a comment or contact us via the handler contact page.
[5] http://home.comcast.net/~itdave/site/
|
Mark 81 Posts ISC Handler |
| Subscribe |
May 23rd 2012 7 years ago |
|
I think this issue must have been fixed. I was experiencing the issue yesterday. But, today, I haven't been offered the 3 fixes and I haven't ignored the fixes. I went to Windows Update and it didn't offer them either.
|
Anonymous |
| Quote |
May 23rd 2012 7 years ago |
|
I had the same problem under XP Tablet. Downloaded the individual updates, installed them one at a time, ran Windows Update - problem resolved.
|
Anonymous |
| Quote |
May 23rd 2012 7 years ago |
|
I forget where, but one of the non-Microsoft help sites pointed me to a Microsoft Installer (MSI) update of kb942288. Installing that fixed the problem for me.
|
Dickh 3 Posts |
| Quote |
May 23rd 2012 7 years ago |
|
What I did was:
Uninstall all .NET Frameworks Run the .NET Framework remover tool (http://blogs.msdn.com/b/astebner/archive/2008/08/28/8904493.aspx) Install the latest .NET Framework (4) Install updates for this .NET Framework Seemed to solve the problem on many machines. |
mbrownnyc 19 Posts |
| Quote |
May 23rd 2012 7 years ago |
|
Similar to Matt:
(1) uninstalled .NET 1.1, 2.0, 3.0, 3.5 (2) reboot (3) Windows Update, and selected "optional update" and chose .NET 4.0 client (4) Windows Update to get 4 security-fixes and 3 "optional" fixes to that client Done. Now, my still-remaining problem is why do I have 3 similar versions of C++ Runtime installed? (I know that Audacity requires one.) |
Anonymous |
| Quote |
May 23rd 2012 7 years ago |
|
In compliment to Dickh, Windows Installer 4.5 is not published to WSUS at this time, and hasn't been since it's release: http://catalog.update.microsoft.com/v7/site/Search.aspx?q=windows+installer
|
mbrownnyc 19 Posts |
| Quote |
May 23rd 2012 7 years ago |
|
Dave has e-mailed and told us Dickh's suggestion finally led to a solution for him. He noted that even though his machines had KB942288 installed, things didn't work until he reinstalled that MS installer update. Apparently that update was updated without a corresponding change in the number or any indication on the system that the update needed to be reapplied.
|
Jim 412 Posts ISC Handler |
| Quote |
May 24th 2012 7 years ago |
|
The reissuing of KB2656352, KB2604092 and KB2604110 on May 22 seemed to fix this for many people without needing any of the other measures mentioned here.
http://technet.microsoft.com/en-us/security/bulletin/ms12-035 http://technet.microsoft.com/en-us/security/bulletin/ms11-100 |
David 11 Posts |
| Quote |
May 24th 2012 7 years ago |
|
I forget where, but one of the non-Microsoft help sites pointed me to a Microsoft Installer (MSI) update of kb942288. Installing that fixed the problem for me.
<a title="alat terapi ion listrik" href="http://terapi-listrik.com">alat terapi ion listrik</a> |
David 1 Posts |
| Quote |
May 25th 2012 7 years ago |
Sign Up for Free or Log In to start participating in the conversation!
