MS security tool interferes with Chrome and Adobe updates
Nanny software niggles nixed
Microsoft has updated its security protection tools following a glitch that prevented third-party applications – including Google Chrome and Adobe Reader – from updating properly.
The Enhanced Mitigation Experience Toolkit (EMET) is designed to thwart a range of tricks used by malware writers to infect systems. However a recent update of the tool went awry, which meant users had to restart their systems after applying recent Adobe software patches – a potential nuisance in corporate environments in particular.
Worse still, the misfiring Microsoft tool prevented updates of Google Chrome from installing, at least in cases where multiple users on the same machine have installed the browser and the administrator account is yet to apply a security patch.
Microsoft acknowledged the conflict, explained in more depth in an advisory here, and updated its tool.
In its own advisory, Google said EMET covers security functionality already bundled with Chrome, arguing it offers benefits only in guarding against exploits against legacy applications. ®
not a Microsoft fanboi
But did you even read the technet bulletin? a couple of 3rd party apps have a minor interoperabilty problem and it is microsofts fault? Would you rather they didn't fix the problem?
Still any excuse to roll out the tedious (insert your favourite villan here) bashing.
FYI I have to work with most flavours of Windows, OSOL, and Debian Linux, they are tools to be used and all have weaknesses that need patching at times, some more than others.
I think you'll find...
It's Adobe and googles updating routines which are working in direct violation of the windows architecture.
Adobe are legendary for writing software for the windows platform, that isn't actually compliant with the Windows architecture. Non-standard installers, non-standard interfaces, and of course, non-standard updating routines.
This behaviour was almost acceptable back in the days of Windows 95, when you bypassed the standard windows libraries so that you could tweak your assembler written game kernel to run on a 66Mhz Pentium, but things have moved on.
We use the incredibly powerful SCCM to manage software distribution and updating, but even with amazing tools like that, each new Adobe update makes me die a little inside.
re: leaving the user with no flash capability at all.
an improvement then ;)