Suggestion to staff for ESET AV » Forum Post by bobj420

If i remember correctly Nod32 from ESET was what brought me to the forum in the first place and that was over a Decade ago, so in all these years it is still an issue for users.

Successfully updated karma reason!

We did have detection for it in the past but the app changed things. AV apps sometimes make it more difficult to detect them to make it harder to know what AV package is running. That said we could alter the standard message to mention ESET for those who run it.

Personally I could not recommend that particular AV package due to its ability to break core OS functionality without even letting the user know. It is very poor form.

+1

Successfully updated karma reason!

Quoting Neil Banfield,

reply 2

We did have detection for it in the past but the app changed things. AV apps sometimes make it more difficult to detect them to make it harder to know what AV package is running. That said we could alter the standard message to mention ESET for those who run it.

I know it's not going to help everyone but I really think adding a message about ESET AV would be helpful.

Quoting Neil Banfield,

reply 2

Personally I could not recommend that particular AV package due to its ability to break core OS functionality without even letting the user know. It is very poor form.

Agreed.

Successfully updated karma reason!

Jafo

Join Date 03/2001

+1574

In an ideal world...when you install a new program it would automatically uninstall Eset for you and save you the trouble...

Successfully updated karma reason!

Quoting Jafo,

reply 4

In an ideal world...when you install a new program it would automatically uninstall Eset for you and save you the trouble...

That might actually cause them to legitimately think of the app that did that as a virus

Successfully updated karma reason!

I've had ESET for over a decade and never have had any problems whatsoever...until I installed WindowBlinds. So who's to blame?

Successfully updated karma reason!

DrJBHL

Join Date 04/2002

+2877

Quoting GuruGurra,

reply 6

I've had ESET for over a decade and never have had any problems whatsoever...until I installed WindowBlinds. So who's to blame?

ESET...because Stardock's software, when downloaded from the Stardock site, contains nothing vaguely similar to malware.

Perhaps what caused all this nonsense years ago was kids downloading SD software from warez/crack sites and ESET getting complaints or reports from their software installed on Dad's computer. Who knows?

What is clear, however, is that ESET couldn't be bothered to do their due diligence vis a vis Stardock.

Successfully updated karma reason!

Quoting GuruGurra,

reply 6

I've had ESET for over a decade and never have had any problems whatsoever...until I installed WindowBlinds. So who's to blame?

ESET blocks WindowBlinds from functioning without changes in ESET itself and worse does not tell the user it is doing this and so offer an easy option for the user to say 'no thats fine'

Personally I would strongly urge against the use of that product as other AV products are fine.

Successfully updated karma reason!