Task Scheduler fails to start second action in 1607

Topic

New Reply

Hello,

I recently updated my Win10 Home PC from version 1511 to version 1607. I was pleased to see that the update process went smoothly; I used the Windows Update route. The PC is currently at OS Build 14393.693.

However, I have now noticed that all my tasks in the Task Scheduler that have more than one action specified on the actions tab are always bombing out when trying to start the second action. The first action appears to execute properly in all cases. Each time there are two error messages immediately after the first action has ended and the second action is about to start:

EventID 104: Task Scheduler failed to log on “MyTaskName” . Failure occurred in “LogonUserExEx” . User Action: Ensure the credentials for the task are correctly specified. Additional Data: Error Value: 2147943726.

Code:

– 
– 
*  
* 104 
* 0 
* 2 
* 104 
* 0 
* 0x8000000000000000 
*  
* 3059 
*  
*  
* Microsoft-Windows-TaskScheduler/Operational 
* MyPCName 
*  
* 
– 
* MyTaskName 
* LogonUserExEx 
* 2147943726 
* 
* 

EventID 101: Task Scheduler failed to start “MyTaskName” task for user “MyPCNameAdmin”. Additional Data: Error Value: 2147943726.

Code:

– 
– 
*  
* 101 
* 0 
* 2 
* 101 
* 101 
* 0x8000000000000001 
*  
* 3060 
*  
*  
* Microsoft-Windows-TaskScheduler/Operational 
* MyPCName 
*  
* 
– 
* MyTaskName 
* MyPCNameAdmin 
* 2147943726 
* 
* 

The tasks are all set to run as administrator (my user Admin), with highest privileges and whether user is logged on or not. I have tried to run the tasks directly from Task Scheduler while logged in as Admin, and it makes no difference to the outcome.

All the tasks are unchanged from Win10 Home 1511 where they worked flawlessly, and it thus appears to me that this is a problem caused by Win 10 Home 1607. The first error message suggests to check the credentials, and I have done that to no avail; anyway the first action of the task is executing properly, so the task credentials must be OK.:confused:

All my Task Scheduler actions are to “Start a program”, be it an .exe file, a .bat or .ps1 file. In one case, the second action that fails to start is identical to the only action in another task, where it executes properly. In another case the second action (failing) is identical to the first action (succeding) except for a drive and filename argument to a .bat file, but the .bat file doesn’t even start the second time.

All my other tasks, i.e. those with only one action, appear to run normally.:)

Has anybody come across this problem before and/or know of a solution?

I can most probably circumvent the problem by writing batch or powershell scripts to handle the multiple actions and thus reduce the Task Scheduler’s actions to only one in each case, but that shouldn’t really be required when Task Scheduler is obviously designed to cater for multiple actions.

Thanks in advance for any help you can give.

mo.eu

Reply | Quote

Replies

I saw a post that said check the settings for the job and to change the drop down menu for “If the task is already running…” from “Stop the existing instance” to “Do not start a new instance”.

--Joe

Reply | Quote

I saw a post that said check the settings for the job and to change the drop down menu for “If the task is already running…” from “Stop the existing instance” to “Do not start a new instance”.

Thanks Joe, but my tasks are already at “Do not start a new instance”

mo.eu

Reply | Quote

I saw another post where someone said they had contacted Microsoft about this and was told it would be fixed in a patch. I wouldn’t hold my breath though.

Sorry, but I couldn’t find anything else that seemed relevant.

--Joe

Reply | Quote

I saw another post where someone said they had contacted Microsoft about this and was told it would be fixed in a patch. I wouldn’t hold my breath though.

Sorry, but I couldn’t find anything else that seemed relevant.

Thank you anyway, Joe.
It appears that I have better start to implement my workaround to see if it actually works.

Regards,
mo.eu

Reply | Quote

Thank you anyway, Joe.
It appears that I have better start to implement my workaround to see if it actually works.

Regards,
mo.eu

Same problem here:
When i try to run Multiple scripts in single task in taskscheduler with the options ‘run wether user is logged on or not’ it does not work. For traobleshooting pourpose i have two simple batch scripts that write one line in file log. No way. Some arror code

Reply | Quote

Same problem here:
When i try to run Multiple scripts in single task in taskscheduler with the options ‘run wether user is logged on or not’ it does not work. For traobleshooting pourpose i have two simple batch scripts that write one line in file log. No way. Some arror code

Hello stele,

and welcome to the forum.

Nice to see, that I am not the only one with the problem. However, I have not found a proper solution apart from the workarounds to
(1) create a script, which in turn calls the different actions that used to be in the task,
or
(2) split the actions out into separate tasks that are timed consecutively.

Regards,
mo.eu

Reply | Quote

Hi mo.eu and thanks for the welcome.

I found in:
event viewer – applications and services log – microsoft – windows – taskScheduler – operational
two errors logs (instead to the one in history in task scheduler)

Task Start failed
EventData
TaskName test
UserContext PORTATISTELEstefa
ResultCode 2147943726

Logon failure
EventData
UserName test
ErrorDescription LogonUserExEx
ResultCode 2147943726

I am happy to say that in my case the solution is to change the user in task scheduler:

under GENERAL tab in security options: ‘When running the task, use the following user account:’
click Change User or Group…
advanced – find now and select SYSTEM
then click OK (three times)

I do not understand why the first script run and the second (identical to the first one) no with the normal user… but it works and is much more elegant, in my case, not to link the task to a single user. I Hope It can be usefull for someone else.

Reply | Quote

[bbearren]

FWIW, all my Scheduled Tasks are run as SYSTEM, and none have any failures, even those that run multiple tasks.

Always create a fresh drive image before making system changes/Windows updates; you may need to start over!

We all have our own reasons for doing the things that we do with our systems; we don't need anyone's approval, and we don't all have to do the same things.

We were all once "Average Users".

Computer Specs

• This reply was modified 5 years, 7 months ago by bbearren.

Reply | Quote