JWT

Seems I need a large slice of humble pie and I owe Marcos an enormous apology.
I was basing my experience and frustration from v16.2.  Rather than trying v17 I behaved like a child throwing a tantrum trying to get his own way and being uncooperative.

I would like to confirm all is well and working as it should since upgrading to v17.0.16.0.
The update speed and process from V16.1 was as easy as one click and less than 2 minutes, this includes reboot.
No rules or settings were lost or changed.  I'm impressed.

Last but not least I would like to publicly apologise to Marcos for my recent behaviour and immature posts.

I'm sorry if my instructions were confusing, will try to re-phrase it:
1, Install ESET v17.0.16 from scratch
2, Disable automatic activation of gamer mode for applications running in full-screen mode as shown above
3, Switch to interactive firewall mode and try to reproduce the issue.
If you are able to reproduce it:
1, Collect logs with ESET Log Collector and upload the generated archive here. Also provide step-by-step instructions how we can reproduce it on our end.
2, Raise a support ticket and supply technical support with ELC logs for a start.
We're willing to help you but need your co-operation.

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.

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.

But why would you release such unfinished state of application and essentially make beta testers out of users while removing expected functionality until some time in the future you say?! Makes zero sense to treat users like that.

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.

I had to downgrade to 16.1.14 and block EIS from making version update, current 16.2.x is unusable, I couldn't use any software that makes online license checks, they were all having timeouts and closing, making me loosing my work.

I'm not sure what you mean by "communication problems."  I'm using interactive mode, not policy mode.  This is fact, 100%.  Are you saying the the "pre-release" update will solve the first issue where I'm getting popups for IP 127.0.0.1 now where things were working fine before?  If that update won't fix this issue, what's the ETA for an update that will?
For the port and IP being removed from the advanced interactive rule creation, what's the ETA for a release that will add that feature back?  This feature, as I mentioned, played a role in me selecting ESET over its competition when I paid for a license.  If it's not restored, I will not be renewing my licenses.  Actually, I feel that I was taken already, as with the paid license I expected to receive updates, and this update is not usable.
For the last issue with profiles, can you concisely describe what the change was intended to achieve?  It's confusing to me, as I had several custom profiles, and then there was the (a single) default.  Now, in addition to my custom profiles, there seem to be choices for "public" or "private" profiles.  The profile is not shown and not available to be shown as a column in the firewall rules, making them harder to manage - I have to click into each rule to check its associated profiles.
I've already reverted to 16.1.14.0 and will stay at that version until these issues have been resolved, as especially the second issue (missing port/IP during rule creation) makes the product unusable for me.  You should consider making a mass refund available to your customers if you do not intend to revert this.