Running from the Windows Task Scheduler

@ProactiveServices does this bug still exist? Was it captured anywhere in a GitHub issue?