I am experiencing an issue where there is no error dialog shown when running a batch job through Windows Task Scheduler. However, the dialog error is shown if I run the batch job file manually outside of Task Scheduler.
By default Scheduled Tasks are run as the System user.
The logged-in user does therefore not receive any error messages.
If you don't use "Create Basic Task", but instead "Create task" in the Task Scheduler, you can define under which user credentials a scheduled task will run.
By default Scheduled Tasks are run as the System user.
The logged-in user does therefore not receive any error messages.
If you don't use "Create Basic Task", but instead "Create task" in the Task Scheduler, you can define under which user credentials a scheduled task will run.
Plerry, 19 Jun 2025, 01:59
I actually had my user credentials setup properly to run the task; however, I had configured the task with the setting "Run whether user is logged on or not" and once switching this to "Run only when user is logged on" did error dialog prompts resume as intended.
A strange case to have to contend with. Regardless, thank you for your assistance Plerry. :)
however, I had configured the task with the setting "Run whether user is logged on or not" and once switching this to "Run only when user is logged on" did error dialog prompts resume as intended.
Adam, 24 Jun 2025, 01:42
This setting is what dictates if a task uses SYSTEM or not. Checking it uses the SYSTEM account, different than your user account of course, so the reported behavior is seen.
This seems odd, because SYSTEM should have access to basically everything, and the path must have been valid if it worked after changes unrelated to the path...
This setting is what dictates if a task uses SYSTEM or not. Checking it uses the SYSTEM account, different than your user account of course, so the reported behavior is seen.
If you run a scheduled task under specified user credentials (other than SYSTEM), that task will use the access rights of the specified user, including stored network credentials, and user specific stored drive mappings.
This even if the specified user is not logged in.
This seems odd, because SYSTEM should have access to basically everything,
Although true for local drives, that does not apply to network drives that require user credentials.
