Windows 10 - Task Scheduler - Not running (0x41303)

Question

I'm trying to schedule a task in Windows 10, on the event of "At log on" in order to start several programs, but it won't run after several trial/error. The task is configured as follows:

• General: Run whether user is logged on or not (it prompted the credentials inputbox, also tried Run only when user is logged on). Run with highest privilegies. Configure for Windows 7 and Windows 10 options where tried.
• Triggers: At log on, any user, enabled (tried specific user too).
• Actions: Start a program, which are "C:\Program Files (x86)\Google\Chrome\Application\chrome.exe", "C:\Program Files\Internet Explorer\iexplore.exe" (this one has Add Arguments: %HOMEDRIVE%%HOMEPATH%), "D:\ids\sqldeveloper\sqldeveloper\bin\sqldeveloper64W.exe". The route were copy/paste from the shortcut properties of each program.
• Conditions: No condition were set.
• Setting: No additional settings.
• History: disabled.

When I restart and log on, nothing happens. Checking the status panel appears the summary of the task, where in the Last Run Time is 30/11/1999 12:00:00 a.m., the Last Run Result is (0x41303), and Status column is Ready.

Tried to look others questions, but seems to be others problems. What am I missing? Is there another configuration that I must apply? Thanks in advance.

Answer 1

I had this problem as well (Windows Server 2019), with error 0x41303 and Last Run Time set to 30/11/1999.

When I changed the start time to a future time instead of past (i.e. 2 minutes from current time), the scheduled task ran successfully (result: 0x0) and repeated just fine per the trigger.

Answer 2

Task Scheduler 0x41303: Task has not yet run.

The main reason for this is if the scheduler's first run is set in the past or simply hasn't run yet. To fix:

• Try running it manually
  or
  
• Set the next trigger in the near future.
  
  The last run result should update indicating it ran but if it still doesn't run, check the task conditions.
  A full list of task scheduler return codes

Answer 3

Try open "trigger" tab, and edit the trigger detail. I found here my trigger was not enabled, I've just enabled it. This could generate error 0x41303.