Jump to content

Disabling Real-time protection - Scan on File Open/Creation?


Go to solution Solved by Marcos,

Recommended Posts

Hello everyone, just a question.

Looking to slightly improve performance on my very old PC. Would you consider reasonably safe to disable both "Real-time file system protection / Scan on File open + creation" options? I'm leaving "File execution" enabled since that sounds more critical.

On a side note: slightly confused about the difference between File open and execution. Don't you have to open a file to execute it anyway?

Thank you

Link to comment
Share on other sites

  • Administrators

It's not safe to disable any of the scan-on options. Disabling scan on file open would allow to run script malware undetected.

Please carry on as follows:

  1. Reproduce the issue with performance
  2. Enable advanced operating system logging under Tools -> Diagnostics -> Advanced logging in the advanced setup
  3. After 30-60s stop logging
  4. Collect logs with ESET Log Collector and upload the generated archive to a safe location (e.g. OneDrive, Dropbox,...) and drop me a personal message with a download link.
Link to comment
Share on other sites

Posted (edited)

Thanks. There is no specific performance issue. EIS works fine. Just trying to make things slightly easier for the old PC.

12 minutes ago, Marcos said:

Disabling scan on file open would allow to run script malware undetected.

So, I assume only having "Scan on File execution" enabled is not enough to detect/block this? Isn't "run" the same as "execute"?

Edited by DreamAlive
Link to comment
Share on other sites

  • Administrators
  • Solution
25 minutes ago, DreamAlive said:

So, I assume only having "Scan on File execution" enabled is not enough to detect/block this? Isn't "run" the same as "execute"?

Correct. Execution of exe files and scripts by script interpreters are different things. Moreover, dll files are not executed either but are loaded by running processes.

Link to comment
Share on other sites

Something you may not be aware of.

If you let Eset's full system scan at installation run till completion, Eset has whitelisted all files on your system. This means Eset will only scan newly created files or if an existing file has been modified.

My PC is 14 years old and Eset doesn't impact its performance in any way.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...