Tag Archive for: mistake

Trend Micro antivirus modified Windows registry by mistake — How to fix

/in


Trend Micro

Trend Micro antivirus has fixed a false positive affecting its Apex One endpoint security solution that caused Microsoft Edge updates to be tagged as malware and the Windows registry to be incorrectly modified.

According to hundreds of customer reports that started streaming in earlier this week on the company’s forum and on social networks, the false positive affected update packages stored in the Microsoft Edge installation folder.

As users further revealed, the Trend Micro Apex One flagged the browser updates as Virus/Malware: TROJ_FRS.VSNTE222 and Virus/Malware: TSC_GENCLEAN.

Fix and workaround available

The cybersecurity software maker addressed the issue and published an advisory urging customers to update their products and ensure that the Smart Scan Agent Pattern and Smart Scan Pattern are updated to the latest version.

“Trend Micro is aware of a detection issue that was reported earlier today regarding a potential false positive with Microsoft Edge and a Trend Micro Smart Scan pattern,” the company said.

“The pattern has been updated to remove the detection in question and we are doing an investigation on the root cause of the issue. More information can be provided after the investigation is complete.

“Please confirm that both the Smart Scan Agent Pattern is 17.541.00 or later AND Smart Scan Pattern is 21474.139.09 or later which resolves the issue.”

Trend Micro also shared a temporary workaround if the pattern update didn’t fix the issue which requires adding multiple Microsoft Edge folders to Apex One’s exclusion list.

Restoring registry changes

While the fix provided by Trend Micro for the false positive can easily be applied by updating Apex One, some customers also reported that this issue also led to Windows registry entries being altered after the agent’s Damage Cleanup tool was executed.

“It was reported that some customers observed some registry changes as a result of the detection depending on their endpoint cleaning configuration settings,” Trend Micro added.

Widnows Registry changes seen by Trend Micro customer
Widnows Registry changes seen by Trend Micro customer

This requires affected users to restore backups made by the Apex One agent through a procedure that will help revert the changes made…

Source…

Fire dept. rejects Verizon’s “customer support mistake” excuse for throttling

/in

Enlarge / A West Covina firefighter pulls a hose away from a horse barn that burns as the Mendocino Complex Fire moves through the area on July 31, 2018 in Lakeport, California. (credit: Getty Images | Justin Sullivan)

A fire department whose data was throttled by Verizon Wireless while it was fighting California’s largest-ever wildfire has rejected Verizon’s claim that the throttling was just a customer service error and “has nothing to do with net neutrality.” The throttling “has everything to do with net neutrality,” a Santa Clara County official said.

Verizon yesterday acknowledged that it shouldn’t have continued throttling Santa Clara County Fire Department’s “unlimited” data service while the department was battling the Mendocino Complex Fire. Verizon said the department had chosen an unlimited data plan that gets throttled to speeds of 200kbps or 600kbps after using 25GB a month but that Verizon failed to follow its policy of “remov[ing] data speed restrictions when contacted in emergency situations.”

“This was a customer support mistake” and not a net neutrality issue, Verizon said.

Read 17 remaining paragraphs | Comments

Biz & IT – Ars Technica