DrJBHL DrJBHL

Update to Problematic .NET Updates

Update to Problematic .NET Updates

 

I just got an email from WindowsSecrets.com and felt it important to inform you of potential Update problems. Now normally, I harp on keeping Security and software/drivers updated but this time

Susan Bradley who is a highly regarded writer and reporter has issued a warning about the latest round of updates of .NET from Microsoft:

 

“ .NET is one of the most troublesome updates we deal with.

In case you think you need June's .NET security updates, I'm here to tell you they're trouble — skip them.

The list of known issues documented in KB 2538814, however, is long. In the worst-case scenario, you have to rip out all of the .NET versions on your system using the Aaron Stebner tool. In the least-terrible case, you must run a repair install of .NET 4, if it gets stuck.

Here's what's on offer:

MS11-039 — XP: KB 2478656, KB 2478658, and KB 2478663; Vista: KB 2478657, KB 2478659, and KB 2478663; Win7: KB 2478662 and KB 2478663

MS11-044 — XP: KB 2518864, KB 2530095, KB 2518864, and KB 2518870; Vista: KB 2518863, KB 2518865, and KB 2518870; Win7: KB 2518867, KB 2518870, and KB 2518869 “

- Susan Bradley

Bradley also advises a pass on the latest Office 2010 updates because they didn’t come out in Public Beta yet.

If you don’t update with the .NET patches, the chance for exploitation are very low, according to Microsoft. I‘d advise listening to Bradley and although my update happened before her column was sent (and went uneventfully), pass on these two.

I also advise reading her articles on WindowsSecrets.

 

Source:  http://windowssecrets.com/patch-watch/keeping-you-up-to-date-say-no-to-net-again/

Update:

Daiwa has posted a thread I'm linking here because his problem came from the June .NET update.

Problems from the .NET update can resemble malware infection (superficially) and file corruption. yrag solved this problem

so it's well worth your while to know of the thread's existence:  https://forums.wincustomize.com/411380

67,411 views 29 replies
Reply #26 Top

Such a gloryhogduck, I tell ya.  :P

Reply #27 Top

Already did my updates as well and experienced no problems.

 

 

Edit... just saw the date on the original post, but my answer remains the same :)

Reply #28 Top

Good to know some (likely most) appear unaffected.  Possible it could be specific scanners on specific OS's.  Just know that borkville came close on the heels of the security update and after the cleanup, all 4 machines are bork-free again.

Reply #29 Top

Quoting yrag, reply 24
Just for a hoot.....
End of yrag's quote

No UI love there, either.

Fuhgeddaboudit.