topic Re: Cannot edit HOSTS file in Endpoint

Cannot edit HOSTS file

BorisL — Tue, 08 Mar 2022 15:17:08 GMT

Harmony Endpoint Antimalware 86.10 wrongly detects a computer administrator attempting to change the HOSTS file and blocks the change.

Is there a way to bypass this?

Re: Cannot edit HOSTS file

G_W_Albrecht — Tue, 08 Mar 2022 16:27:10 GMT

The user/admin has to shutdown EPS locally before the change.

Re: Cannot edit HOSTS file

BorisL — Tue, 08 Mar 2022 16:40:54 GMT

First. Not possible to give local admins that possibility. What's the purpose of the uninstall password, then? It's like telling someone: "remove your antivirus, then reinstall it" If that is the solution, then we would have to look for another product.

Second. It does not happen in all systems. In 2 out of 3 Windows 10 computers with the Endpoint active, local admin can change HOSTS.

Re: Cannot edit HOSTS file

G_W_Albrecht — Tue, 08 Mar 2022 19:26:37 GMT

Contact TAC to get this resolved ! Looks like a bug. I did not mean to uninstall, only shutdown client...

Re: Cannot edit HOSTS file

BorisL — Tue, 08 Mar 2022 19:33:36 GMT

Thank you for the interest and help.

But I just spent almost 3 months with TAC on a bug in Harmony Endpoint which wrongfully locked files (finally solved last week). I am not willing to go through that ordeal (tests, zooms, more tests, files back and forth) again...

Re: Cannot edit HOSTS file

Chris_Atkinson — Tue, 08 Mar 2022 23:10:19 GMT

You could pilot E86.25 on one of the machines, else if there is a specific protection being triggered there might be other workarounds available....

Re: Cannot edit HOSTS file

jcortez — Tue, 08 Mar 2022 23:21:22 GMT

@BorisL

It does sound like an issue that needs to be looked at by our Endpoint Tac Teams. This is our process and if it needs a fix, this is the only path.

If you continue to see issues with our client either try our latest version, E86.25, to see if that resolves it or create a SR.

Re: Cannot edit HOSTS file

BorisL — Wed, 09 Mar 2022 06:00:01 GMT

Fix for other problem was applied to 86.10.69 and we were told to upgrade to 86.30 when available. So, maybe, 86.25 will fix one thing and break another one.