Failed to start Task Scheduler. Additional data: Error value: 2147943726
I use Windows 10 Task Scheduler to run tasks that require me to use my personal user account (I need to use my user and not the system user due to permission issues - I'm part of an organization). Everything worked fine on Windows 7 computers, but when we upgraded to version 10, I cannot run tasks without using the System user (as mentioned earlier, it doesn't work because of permissions). I am getting the following error
Additional data: Error value: 2147943726
everything I found on the internet was advice to use the system user, except that nothing :-(
please save my day.
Here is a picture of the settings I want to change.
source to share
I have the same problem today, (HRESULT) 0x8007052e (2147943726) "unknown username or wrong password"
My solution: was to redirect the user to the Change User or Group button to get the most recent information about the user's Active Directory.
Then I was able to run the task again ...
As a best practice, you could use the "Aplicative" User instead of the regular user, which changes regularly more often.
If you are using your account, she may change your password every number of days ... and you will need to "fix" again ...
If you are using an "Aplicative" account, it may change less than a typical User ...
You can do this by going to the "General" task tab, then "Change user or group" and assign the "Aplicative" account, then click "OK".
source to share
I had the same problem with Windows Task Scheduler.
The reason for the failure is a recent change in the system user password that was configured when the task was created.
Decision:
- Go to task properties
- On the General tab, click "Change user or group ..."
- Enter the username in the "Enter the object name to select" field
- This will ask for authentication, provide your credentials
This is it !
source to share
I had to select the option "Do not store password". The task will only have access to the resources of the local computer. "That was fine, based on the task definition. For me, I suspect that some recent patch or security enhancement caused this as it seemed to move through our environment into similar ones. but different days.
source to share
I realized that the denial was due to an expired password policy. The PC got a kind of "frozen" state for the scheduler until a new password was set. The problem is resolved after the new password is accepted by the system.
It is highly recommended that you make a small change so that the scheduler will prompt for a new password entry and update the task.
source to share
I know this is a late answer, I had the same problem today, a scheduled task that I created a long time ago and stopped running a week ago. It turns out I changed the password for my username, which was the problem. as soon as I returned to the assignment, got the chance that I was asked to enter the password again.
source to share
We had the same problem cloning machines from Windows 2012 server to VMware ESX server. The clone / deploy script used sysprep to make each machine individual. With this, the users assigned with the scheduled task screwed up. Our solution was to re-generate the task via a batch file during machine startup:
REM Delete the task:
SCHTASKS /Delete /TN "NameOfScheduledTask" /f
REM Create a task to run every 5 minutes
SCHTASKS /Create /TN NameOfScheduledTask /SC MINUTE /MO 5 /TR "some command for task" /NP
source to share
I got the same error and I noticed that the location is empty. enter image description here
it's good? I have already logged into my account again. I can't edit the location, shouldn't the script path be pasted into this?
source to share