Hi Dahall, thanks for your reply.
The task was not running, I could see status was "Ready" and I was monitoring for an executable run by this and it was not present on task manager.
If I switch from Calendar to Time trigger, it works perfectly. Obviously that forces me have to re-register the task each time it is run.
My reasoning for running it on both login and calendar/time trigger is that if the computer is rebooted, I want the task to run as soon as possible and not have to wait 15 - X minutes to start. The program closes itself if it detects another instance running.
Was the task triggered on your Windows 10 instance after loading it? I don't know, it might be a bug on my particular release, but it happened with 2 different installation mediums.
Thank you.
The task was not running, I could see status was "Ready" and I was monitoring for an executable run by this and it was not present on task manager.
If I switch from Calendar to Time trigger, it works perfectly. Obviously that forces me have to re-register the task each time it is run.
My reasoning for running it on both login and calendar/time trigger is that if the computer is rebooted, I want the task to run as soon as possible and not have to wait 15 - X minutes to start. The program closes itself if it detects another instance running.
Was the task triggered on your Windows 10 instance after loading it? I don't know, it might be a bug on my particular release, but it happened with 2 different installation mediums.
Thank you.