Error Opening [4]

Hi Eset.

Whenever I do on demand computer scan, I often gets these log entries of some Windows files with Error Opening [4] messages at the end.
Is this normal? Does ESS scan these files? If not, would it become dangerous if one or more of these files were infected by malware?

Thanks.

 

Hello encus
Take a peek on this KB article, Blue "error opening" notifications in On-demand Scanner Log

 

Done that. Thanks Janus .
If I disable the start up scan, does it mean that ESS only scans these files during computer shut down?

Thank you.

 

Yes. You can look at older logs to see what files are usually not opened on your computer

Not during the scan shown in the log. The same applies to all security software.

Probably but hopefully ESET would detect it at some other point

You are giving ESET one less opportunity to detect malware so must be reducing your protection. Probably will not matter but would only be sensible if the start-up scan was significantly impacting on your computer use.

 

Hey encus
Here is what I think : We know that Real-time protection of the file system is activated at system startup (if you have it enable ), and that All files are scanned for malicious code at the moment they are opened or created or run on your computer. So my point is that the Real time protection is protecting you when you doing a startup and shutdown of the system. And "Startup scan" is another layere to the Real time protection, that checks registry entries for known ,and new malware, (when virus database is updated).
As pointed out by "patch", Startup scan is a essential part of your protection, and is unwise to have it disabled, for a longer time.

 

"System startup file check" scans for missed threats installed in the startup zones including the Operating memory.
That scan is performed ~2 minutes after update/user logon

 

If I disable the start up scan (from the Scheduler option), is the Real Time Protection still on?
Thanks.

 

Yes, the real time protection will still be active if you turn off startup scan. But please notice as stated above, it is not wise to do so. .

 

Ok, thanks Janus. The reason I did that is to make my computer faster.

 

I wouldn't disable startup scans at all as they may discover malware immediately after an update and not just after the next computer restart when files are loaded into memory.

 

Ok, I've just enabled back the startup scan. There are 2 items related to this :
1. Automatic startup file check when user logon
2. Automatic startup file check at successful virus signature update.
I've chosen number 1 because as far as I can remember, it was checked when I installed ESS for the first time as a default setting (correct me if I'm wrong please).
Then I've noticed that the 2 items above will not be performed if the computer is running on battery. The problem now is that not everyone is using desktop PC, some are using laptop and in order to let ESS do the startup scan, user has to charge his/her laptop before turning it on. It's kind of not an effective thing for me.

Thanks.