Joe S

Betta is like an Airplane prototype. But can security software do the same? Why not? It is ok to roll out beta OS, medications, countries, ecosystems and world orders even before a GUI is developed. It is just the matter of enthusiastic or unaware test pilots.. =

Not going to renew, half my subscription wasted. Maybe one day when they get their ducks lined up I will come back. 
 

As a customer my confidence in ESET has been severely shaken, not just because there has been no formal or informal apology but also due to the blatant disregard for it's customers with the callus, and what is now apparent **** up release of v16.2.

If it were not for the fact how easy it is to roll back I would be seeking to take this matter beyond this post of mere disgust.

@ixtel Thanks for providing the DL link for 16.1.14, that saved my day (luckily i had a recent export of the settings before updating).
2 ESET: I don't understand why would you release a non-major product update which removes an important feature which was in your product for years. Was your Q/A team on vacation or did seriously nobody raised a concern about this at all? The statement that the feature will be back in v17 is just doubling-down. Some of your clients are not just casual users running auto-mode but advanced users with a bit "longer" list of FW rules with explicit definitions ...
After my version got updated and my workstation was restarted I had to go through like 40 FW prompts (as none of my exiting rules was relevant anymore). And no, i don't have 40 programs auto-starting after logon but i got multiple prompts for the same process and even after creating permanent rules i got another prompt, multiple times. Also realizing that ALL of the rules have "ALL" for remote and there is not even a way how to restrict network i was almost sure this seems to be some sort of bug or there is now some switch in settings i need to click to get more advanced FW capabilities ... well, then i found this thread, realized that it is not a bug but "feature" ... so I've rolled back to 16.1. and disabled automatic product updates.
I am usually reading major release (16->17 etc) notes/changelogs before i pull the plug but this was unexpected back-stab. I really don't understand why this change could not wait until you have new UI but with all of the existing functionality integrated...
Alex

How about you properly test your forced updates with that lenovo tool before you release them on a non-beta channel? The way you've handled this entire situation is unacceptable. This should've been rolled back the moment there was an issue and then take your sweet time while it's "looked into" not on the customer's payroll.

Are the developers aware of the dysfunctionality they introduced? Do they understand that when I set in "interactive mode" once "no" that it always means "no"?
No means no and don't ask me every freaking day over again and again!
"Interactive mode" does not mean that I get entertained every day by being asked the same dumb question over and over again!
(My late grandfather was capable of that because he had Alzheimer's.)
Do to ESET developers suffer from that?
Are the developers aware that this needs to be fixed a.s.a.p to work again like in previous versions?
Or are the developers interested in sabotaging the company they work for driving all eventually out of business?
If this is not fixed soon I will have to look for another solution and also advise all my clients of such as I'm getting increasingly complaints from my clients about this persistent newly introduced service defects.
If ESET developers still don't understand it, perhaps this analogy helps:
Would they like to have an "interactive mode" car that every time in the morning when you want to start it asks you a litany of questions if you really want to start the car and why do you want to start the car etc.? Unless you answer all you cannot start the car.
Although you can set your answers in "interactive mode" as being permanently stored so you won't ask you anymore it will continue to ask you every morning and every time you want to start the car the same routine of questions again which you have to answer so that you can actually start your car and continue!
How long would you put up with this?
"Verschlimmbessern"! Don't fix things that don't need fixing neither constantly improve something nobody asked for and that's working, all to a point where it's useless!

don't understand why there is no way to roll back option. what kind of update do you make. are you starting to become Microsoft?
so many issues it caused me until I understand it's the eset firewall. as soon as I disabled the firewall protection everything worked.

Agree totally!
Went back to 16.0.26.0.
Work's fine, no duplicate rules as it should be.

I will also add that as I have posted in other forum replies, it is virtually impossible to block nVidia telemetry via a firewall;
https://www.ghacks.net/2016/11/07/nvidia-telemetry-tracking/
As deleting this .dll can cause other issues, the only effective way to block the telemetry is via IP address blocking.

Your only viable solution is to uninstall 16.2, install 16.1, and if you don't have settings backups from 16.1 redo all the rules from start.
It's a pain but it will save you nerves and time in the long run.

The English word, although not that emotionally charged, is ‘counterproductive’. Imho the better one is is ‘Chalta hai’, a Hindi expression that roughly translates to "it's okay" or "slide" or "slack". It reflects a laid-back attitude towards work and perhaps life itself, when problems are ignored or not sufficiently addressed .

Yes, Licensing is another issue. I used to be a reseller but cheap OEM deals were removed and prices jacked. Sure it created a revenue stream from end users in a short run. But that collapsed promoting and supporting cycles a year - two long.. Imho it now bounced in the product quality now.

No thanks, I would rather have a stable and fully functional product like im paying for.

My solution, like many others on this forum, was to downgrade to v16.1.14 and block any version updates until ESET resolves this mess.  I'll keep checking in monthly to see what progress is being made.

Having the exact same issue here since the update.  Been pulling my hair out having to approve the same rule x15 times, sometimes more.  Having spent a short time fumbling though the new UI I thought it were something I was doing wrong.

Very poor move on ESETs behalf to push this update out half finished.  I cannot express enough how disappointed I've been with this service for the past year.  One more straw on the camels back.

The Germans have a wonderful word concoction for such actions.
"Verschlimmbessern"  To make something worse by improving.
To improve something that works just fine so long and so often until it becomes useless and dysfunctional.
I seriously have to take into consideration if I can continue to recommend ESET to clients.