Problems with Microsoft Security Essentials
Earlier today, we learned that the Microsoft Security Essentials tool began falsely identifying Google Chrome as a piece of malware ("PWS:Win32/Zbot") and removing it from people's computers. — If Chrome is working correctly for you, then there's no need to take any action.
Context & Ripple Effects
This is not the first time the Google–Microsoft browser rivalry has been fought through a security lens: back in September 2009 Google publicly objected to Microsoft's handling of Chrome Frame security, framing the dispute as protectionism dressed up as safety. What changed with this incident is the mechanism — Microsoft's own consumer antivirus, Security Essentials, began labeling Chrome itself as the PWS:Win32/Zbot password-stealing trojan and deleting it from users' machines.
The story moved fast: GeekWire reported the same day that Microsoft had already issued a fix after the mistaken removal, while Google's post reassures anyone whose Chrome still runs that no action is needed. The speed of both the breakage and the repair is the real signal — a single bad signature could strip a top-tier browser off Windows PCs within hours.
First-order effects
- Users running Security Essentials lost Chrome without warning once definitions tagged it as Zbot; Microsoft's fix restores the browser, and Google directs unaffected users to take no action.
- Google's choice to answer on the official Chrome Blog turns a routine false positive into a public trust test for Microsoft's consumer security brand.
Second-order effects
- Every antivirus vendor is reminded of the asymmetric cost of a bad signature on a widely installed application — forcing tighter pre-release review of definitions and faster rollback paths.
- The episode hands Google fresh ammunition in a rivalry already aired publicly during the 2009 Chrome Frame dispute, raising the stakes on how quickly Microsoft's correction propagates to affected machines.
Third-order effects
- When the operating-system vendor also ships the default antivirus, a misfiring signature stops being a mere bug and becomes a competitive event — pressuring the security industry toward kill-switch mechanisms for erroneous definitions.
- If incidents like this recur, they erode confidence in bundled default security tools and give independent security vendors and browser makers an argument for keeping those layers separate.
The trend: Competition between platform owners is increasingly waged through security infrastructure — signatures, warnings, and removal tools — rather than feature lists alone.