Ir0n

Yeah seems it simply doesn't work (as intended) - back to Kaspersky I guess.

So I tried a couple of things - first of no matter which parameters I select (following your suggestions so far) I can't make Eset pick up a missed Scan schedule - it works fine for as long as I am online at the point in time it's supposed to run or if I choose a trigger like "first time of the day the machine boots up". But if I set it to run at 8 AM and only boot the PC for the first time at lets say 10 it doesn't work at all - no matter what I do.

No, not at all - power plan is set to high performance and hibernate is off.

Version no.: 10.0.369.0 Deleted and re-created the job multiple times in the meantime as it was mentioned somewhere else that might resolve the issue but unfortunately no improvement at all so far.

Thank you for the fast reply - actually I am certain all the settings are fine but still it doesn't do anything no matter what. Here's a screenshot of the settings: hxxp://fs5.directupload.net/images/161128/n6f7wpi6.png Should the task be listed in windows task scheduler? Guess not but at this point I look at every single root cause.

Have purchased Nod32 together with a new PC (so no other AV software been installed prior). Unfortunately scheduled scans never start no matter what I try. Currently it's set to Weekly Scan > Saturdays at 6:00 AM > If task skipped start: As soon as possible (also tried immediately if the last run was done 24 hours or longer ago). Triggered it once manually on the 13th but the past Saturdays, the 19th and 26th it didn't run at all - shouldn't it start right when I log on (or after a set amount of time), if at 6:00 AM the PC wasn't running?