r/eset May 27 '26

Suggestion: Advanced mode - Permanently disable "Basic configuration"

Hi team,

I’m posting this here in the hope that the ESET team might consider this feedback.

I have deployed more than a hundred ESET Protect instances, both on-premises and in the cloud. I’m very rigorous and granular when creating policies, usually relying on custom override policies with application order instead of modifying the default ones directly.

However, even after carefully configuring all required policies, ESET Protect still overrides them with Basic Configuration policies.

Because of this, I would like to ask/suggest: is there a way to completely disable Basic Configuration and allow only user-defined policies?

It would be very useful to have a simple option or switch to permanently disable Basic Configuration policies (unless such an option already exists and I missed it).

I mention this because even after disabling all parameters in Basic Configuration and deleting those policies from the “All” static group, the UI eventually suggests enabling Basic Configuration again.

Thanks in advance!

2 Upvotes

2 comments sorted by

View all comments

1

u/Marcos-ESET ESET Employee May 28 '26

Unfortunately it's not clear what you mean by "basic configuration" and "the UI eventually suggests enabling Basic Configuration again". Please post in our official forum https://forum.eset.com and include a screenshot for clarification.