Not again they did not (but indeed they did): Microsoft's antiviral software's been "accidentally" wiping Google Chrome from the face from the map, or at best in the hard disk drives of countless users' Home windows-based computer systems.
The problem comes from a bug within the company's antiviral security suite, an off traffic slice of software named Microsoft Security Necessities. It is a free gift utility that bundles realtime anti-virus and adware and spyware checking under one roof. Within the splashy marketing 35mm slides around the product site, Microsoft calls it "anti-annoying."
(MORE:�Google Snatches Over 1,000 IBM Patents)
Aside from the part where it has been annoying the heck from Google Chrome customers, becasue it is been crippling or outright zapping the browser from Home windows Computers, mistaking Chrome for any trojan viruses equine. Oops.
"I've been using Chrome on my small office PC for more than a year. Today, once i cranked up laptop computer, a Home windows Security box put their hands up and stated I'd a burglar Problem that must be removed," authored one user on the internet Chrome's official forum last Friday.
"I clicked on the Particulars button and saw it was 'PWS:Win32/Zbot'," continues the consumer. "I clicked on the Remove button and restarted my PC.�Now I don't have Chrome. It's been removed or uninstalled.�The Chrome.exe file is finished.�Was there a real problem, or perhaps is this only a method for Microsoft to stay it to Google "
Microsoft's not mincing words concerning the screwup, acknowledging that "On September 30th, 2011, an incorrect recognition for PWS: Win32/Zbot was recognized and, consequently, Google Chrome was unintentionally blocked and perhaps taken off clients Computers."
The organization states it's "already fixed the problem," so there's that. All's fair for each other and periodic mess Browse on, Chrome customers, browse on.
MORE:�Surprise, Google Plus Adds Games
Matt Peckham is really a reporter at TIME. Find him on Twitter at @mattpeckham or on Facebook. You may also continue the discussion on TIME's Facebook page as well as on Twitter at @TIME.
No comments:
Post a Comment