funkyy Posted October 18, 2019 Share Posted October 18, 2019 I'm using ESET Internet Security (Win 7 x64). I'm trying to find a way to stop the "Crypto\RSA\MachineKeys\...." entries from showing in the scan results log. I Googled but despite some folk saying "stop ESET from SSL scanning" and ESET saying "don't stop SSL scanning", I can't find anyone who can say how to stop the entries appearing in the scan results log....that's all, just to stop the log filling up with these lines which ESET themselves say are only in the log for information purposes" and don't indicate any threat. I get that, I really do, but no-one seems to answer the question "How do you stop these entries appearing in the log?"!!! I tried editing the scan exclusions settings to avoid scanning the Crypto folder...I excluded two paths:- 1) C:\Program Data\Micrsoft\Crypto\RSA\MachineKeys\ 2) C:\Users\All Users\Microsoft\Crypto\RSA\MachineKeys\ but still the stubborn entries appear!! I'd appreciate any light that anyone can shine on this. Thanks guys!! Link to comment Share on other sites More sharing options...
brain_death Posted November 1, 2019 Share Posted November 1, 2019 You could change your logging level to warnings, errors or critical... Quote Minimum logging verbosity – Specifies the minimum verbosity level of events to be logged. •Diagnostic – Logs information needed to fine-tune the program and all records above. •Informative – Records informative messages, including successful update messages, plus all records above. •Warnings – Records critical errors and warning messages. •Errors – Errors such as "Error downloading file" and critical errors will be recorded. •Critical – Logs only critical errors (error starting Antivirus protection, etc...). You could also set your logs to delete themselves after a certain number of days... Quote Log entries older than the specified number of days in the Automatically delete records older than (days) field will automatically be deleted. More & How to... https://help.eset.com/eav/10/en-US/idh_config_logs.html Link to comment Share on other sites More sharing options...
funkyy Posted November 4, 2019 Author Share Posted November 4, 2019 I had posted my question more than 2 weeks ago and I had just been nosing around Software Updates when I noticed that someone had replied to my post. Great answer brain_death and apologies for not answering sooner. I've set logging verbosity to "Warnings" and I've taken a note of the details in case I ever forget!! Link to comment Share on other sites More sharing options...
zanderthunder Posted November 6, 2019 Share Posted November 6, 2019 On 11/4/2019 at 1:38 PM, funkyy said: I had posted my question more than 2 weeks ago and I had just been nosing around Software Updates when I noticed that someone had replied to my post. Great answer brain_death and apologies for not answering sooner. I've set logging verbosity to "Warnings" and I've taken a note of the details in case I ever forget!! Have you post your same question on ESET forums as well? Some cases, they will solve on their side. Link to comment Share on other sites More sharing options...
funkyy Posted November 6, 2019 Author Share Posted November 6, 2019 2 hours ago, Edward Raja said: Have you post your same question on ESET forums as well? Some cases, they will solve on their side. It's fine now Edward Raja...I followed the instructions given by "brain_death" in his post above and now I don't get a log filled with all those entries. Thanks for your answers guys!! Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.