Windows 10: The built-in Task Scheduler v1.0 of Windows has a bug.

The built-in Task Scheduler v1.0 of Windows has a bug. 1 Set the trigger to use a time schedule to execute once a day, and check the option in the settings to start immediately after the time is missed. In this way, multiple task schedules are created. After a power outage or shutdown, all the schedules are missed. When the computer is turned on again, the execution order is messed up. After many tests, it is randomly messed up and not executed in the order of the set time. I hope that after a power outage or shutdown, it can be executed 100% in order even if the time is missed. Or the last

:)

 

Window's Task Scheduler Not Running

Hi,

To assist you better, kindly provide us more details by answering the following questions:

• Have you tried recreating the task? If so, are you getting the same issue?
• Have you tried creating a new task?

Meanwhile, we suggest that you ensure that the Task Scheduler is running. You can verify if the service is running by following these steps:

• Press Windows key + R on your keyboard.
• Type services.msc and hit Enter.
• Under Services (Local), make sure that the Task Scheduler service's status is
  Started or Enabled.

Should you need further assistance, feel free to get back to us.

 

Task Scheduler with error message The selected task »CreateChoiceProcessTask« no longer exists

Hi,

Thank you for posting your query on Microsoft Community. Let me assist you.

I suggest you to clear the task from Task Scheduler using the below steps and check if the issue still persists.

Steps:-

• Type Task Scheduler on Search bar.
• Click on Task Scheduler Library.
• Select the particular task and right click on it.
• Select End.

Hope this information is helpful. Please do let us know if you need further assistance, we’ll be glad to assist you.

 

Scheduled tasks run with elevated privileges can't access stored Windows credentials

It seems that after Creators update scheduled tasks run with elevated privileges ('run with highest privileges' option) can't access stored Windows credentials. Is that a bug or an intentional change and is there a recommended workaround?

Here's one way to reproduce the behaviour:

• Start Credential Manger and add some Windows share credentials.
• In a console window type 'cmdkey /list', which should list the added credentials
• Create a task in a task manager:
  • Trigger: on user logon
  • Action: run cmd.exe
  • Tick the 'run with highest privileges' option
• Reboot the machine and log in
• In the console window (let's call it 'console 1') opened from the scheduled task type 'cmdkey /list'. This most likely won't display the credentials added in step 1 and properly listed in step 2. ->
  This looks like a bug
• Now, without closing 'console 1' open another console window as an administrator (let's call it 'console 2') and type 'cmdkey /list'. This will properly list credentials added in step 1.
• Switch to 'console 1' and type 'cmdkey /list' again. This time the credentials are listed properly, unlike in step 5. It looks like an access to Windows credentials was somehow 'unlocked' by step 6.