Kliebor

If your router supports it (and the PC is wireless) put the PC on the guest network, by default most routers have a wireless guest network with no local lan access.

Yeah mine is Family 6 / Model 151 (I7 / 12700K) which looks like it is not supported yet. Any info on what the setting Advanced Heuristics/DNA detection does and why it is off by default?

I saw in your release info that ESET now supports Intel Threat Detection. I have a 12th Gen Intel CPU which also supports Intel Threat Detection, is there a switch or indicator in ESET that shows the ITD is active? Do I need to make some settings change? In my exploration after the update, I did see a setting for Advanced Heuristics/DNA detection that is for some reason off by default, is this something that has a large drawback and therefore is off by default? From the description in your help files it seems like it would be something that would be good to have on, can someone help me understand what this switch does?

I know, I am not debating that, goodness, I will update as soon as it goes public release. I am perfectly fine with the work around until then, I have no desire to be on a potentially less stable beta version. Once the ESet team is happy with the release and it goes gold so to speak I will update and mark your post as resolution to my issue if all works as expected. Thanks,

I understand, and even said that above, I also thanked them for the update, what in my post anywhere said I thought ESet was awful? I merely stated that the posts saying the workaround is a solution are wrong. I have no idea why I keep having fanboys attacking me in comments, I am not attacking ESet people, take it easy... Thanks.

I did not say it was easy or even possible, I just stated the fact that with rapid release schedules and easy high speed access software has become far more prone to quick release with some issues and re-release to put out the fires.

I am aware that you have said this and thank you for the confirmation, what is hard is when I get "hey this workaround fixed it be happy", which is not helpful, I am aware I have a kludge fix. I just repeat myself because I do not want people to look and say oh that is the fix. The fix is only good when I can use the features of the software and not have to perform either mental gymnastics or resort to external functionality to make what is a built-in function work properly. I just feel that if I pay for software, functions your own documentation describes should work. I know a crazy thought in today's world where no software is ever released complete, PC users are essentially the world's largest unpaid QA department.

Nightowl, you simply are being obtuse at this point. As I stated, I want to be clear, this is a deficiency in the product and yes it does stop working as intended if that option, which I do want for when I play games on my PC is on. The software is supposed to prevent interruption of the user when in a full screen app. The lock screen is not a full screen app, it is placing the computer is a secure state. It should never prevent a scheduled scan. Period, full stop.

I am aware, I just do not want any illusion that this behavior is proper as it limits the use of the program in its normal state, where it senses and gets out of the way of your usage of the computer, locking the screen should be a special case not treated as the system being used for some activity by the user. I have found in the past if a 'fix' is found even if it is more of a kludge work around, the problem gets ignored. Not something I want to see here. That is all.

Very possible still kind of odd and makes the use of the program as intended with notification turned off during games effectively useless.

Disabling game mode detection worked, the scan ran at 10 PM as scheduled.

I will look into this, it just seems odd, other a/v scanners scan fine while the computer is locked. Thanks for the info.

I activated the lock screen at 6 PM like I do every night, at 9:50 PM, still locked your app performed a send of an unknown file to your servers. Something that gamer mode per what I can find in your documentation on the feature should have told the app to wait until after the full screen app was closed. Also, if screen lock is misidentified as a full screen app, that is a programming issue that should be corrected.

And as an aside, your app reported an unknown file to your servers which per your own documentation would not have happened if Gamer mode was active last night. So I can say with a great deal of probable success that gamer mode is not the problem

Gamer mode is off and would always be so when the PC is locked as I leave no full screen game type apps open, I have disabled automatic game mode, but I know no full screen apps were running last night.

As to gamer mode I am really not interested in crippling my protection, so thanks but no, just fix the product.

I lock the PC as it runs many tasks in the background as services like feeding my media server music and video to other smart speaker devices in my home. Locked with Win+L the system ran and sent a suspicious file to ESET no problem at 9:50 PM so ESET can and does run and perform tasks while locked. They need to fix the scheduler.

Please, I explained above very clearly the PC is on and locked, not sleeping, hibernating or anything else ever and ESET even ran tasks 5 minutes before 10 PM scheduled time. That is why I provided screen shots, to show the pc was awake.

This task of a file that ESET did not like fired Wednesday night when the computer was on and locked, why not my scan?

Version and scan result

My PC has sleep and hibernate disabled and runs 24 hours a day I know because other tasks, like file updates and media service is active at all hours. I have established a scan of all local computer resources at 10 PM on Wednesday because I do not use the PC then. I had the schedule setup to run at 10 PM and not to run again if it failed. It did not run so I contacted support and they remotely connected to my computer and rebuilt my scan task to run immediately if it failed to run and it worked but ran when I unlocked the PC this morning. This completely defeats the point of establishing a schedule to run the scan at night when the computer is idle. If I wanted it to run in the morning when I am trying to use the computer, I would run it then. How do I set up a scan in ESET that will just follow my directions and run while the PC is idle, I am logged in and the PC is locked for security purposes. I do not want the scan running while I am active.