Skip to main content

Fix Task Scheduler failed to start, Event ID 101

 

Fix Task Scheduler failed to start, Event ID 101


If you schedule a task using Task Scheduler and the task failed to start and is logged as Event ID 101, on your Windows 11/10 client PC or on Windows Server, then you are at the right place! In this post, we will identify the most likely culprit, as well as provide the suitable solutions you can apply to resolve the issue.

Task Scheduler failed to start, Event ID 101

Task Scheduler failed to start “\Task Name” task for user “Domain\username”. Additional Data: Error Value: 2147943785.

Task Scheduler failed to start, Event ID 101

If your schedules task fails to run and you see the Task Scheduler failed to start with Event ID 101 in Event Viewer, you can try our recommended solutions below in the order presented below to have the issue promptly resolved on your machine.

  1. Add user to ‘Log on as a batch job’ group
  2. Make sure Task Scheduler service is set to Automatic and running
  3. Delete and recreate the Task

Let’s have a quick look at the description of the listed solutions. 

1] Add user to ‘Log on as a batch job’ group

Add user to 'Log on as a batch job' group

The main culprit to the Task Scheduler failed to start – Event ID 101 on Windows 11/10 client machine or Windows server was revealed to be permissions-related. The applicable fix here is to simply add the user to the “Log on as a batch job” property on the server or client machine as the case may be. To perform this task, do the following:

  • Press Windows key + R to invoke the Run dialog.
  • In the Run dialog box, type secpol.msc and hit Enter to oprn the Local Security Policy console.
  • In the console, on the left navigation pane, click Local Policies to collapse the section.
  • Now, click User Rights Assignment.
  • On the right pane, double-click on Log on as a batch job policy to edit its properties.
  • In the Properties window, click the Add User or Group button to add the appropriate username to the group.
  • Finally, click Apply > OK to save changes.
  • Exit Local Security Policy console.

Next time the job runs, it should run successfully without issues.

Read:  Task Scheduler not running or starting programs

2] Make sure Task Scheduler service is set to Automatic and running

Set Task Scheduler service to Automatic

It’s possible the issue you are currently facing is due to the Task Scheduler service is disabled and not running or not set to automatic startup which is the default setting on your machine. To rule out this possibility, you need to make sure Task Scheduler service is set to Automatic and running. To perform this task, do the following:

  • Press Windows key + R to invoke the Run dialog.
  • In the Run dialog box, type services.msc and hit Enter to open Services.
  • In the Services window, scroll and locate the Task Scheduler service.
  • Double-click on the entry to edit its properties.
  • In the properties window, click the drop-down on the Startup type and select Automatic.
  • Next, make sure the service is started by clicking the Start button if not greyed out.
  • Click Apply > OK to save changes.
  • Restart PC.

If this service is set to automatic and running but the issue in hand persists, try the next solution.

Read: System error 1058 has occurred, The service cannot be started

3] Delete and recreate the Task

Delete and recreate Scheduled Task

Before you do this, you can try running the task manually in Task Scheduler and see if the job runs successfully. You can refresh the history of the tasks by pressing F5 or clicking the refresh button. If it fails to run manually you can troubleshoot it from there until it does run manually. Otherwise this solution as a last-ditch effort requires you to delete the scheduled task if the task is not too complicated and then rec

Comments

Post a Comment

Popular posts from this blog

Reset 120 day RDS Grace period on 2016 and 2019

  Reset 120 day RDS Grace period on 2016 and 2019 Enter the following command to check Grace Period: wmic /namespace:\\root\CIMV2\TerminalServices PATH Win32_TerminalServiceSetting WHERE (__CLASS !=””) CALL GetGracePeriodDays  Confirm-deletion-of-the-timebomb-key-in-the-registry If you have a home lab environment or another lab where you continually test various solutions, licensing, and trial expiration is a challenge that you constantly tend to run into. It is just part of the fun of lab environments. While most trials are fairly “hard and fast” and don’t allow you to reset the trial expiration, if you work with Microsoft Windows Server and Remote Desktop Services (RDS), there is a “hack” that allows you to effectively reset the expiration of  Remote Desktop  Services grace period where you can essentially rewind the clock on your RDS licensing if you are making use of this role inside your lab environment. I am using Windows Server 2019 for my Windows workloads in my lab environment
Post a Comment
Read more

Remote Desktop Services session timeout Setup in RD Session Host in Windows Servers

  If you face a session time-limit policy issue that gets disconnected in the meantime. You can follow the steps below in order to fix the issue, By default, the user’s RDP session in Windows may stay disconnected until the user or administrator terminates, or the computer is restarted. However, it is quite convenient since a user may connect to his old RDP session and go on working with running programs. In order to terminate disconnected RDP/RDS sessions automatically in a specified time period, you need to set session limits (time-outs) correctly. If you are using an RDS server, you will have to configure session time-out parameters from the RDS collection settings in the Session tab menu. You will have to Specify the time period after which you want to disconnect the RDP session. Lastly, a disconnected session option (by default, a session period is unlimited – Never). Thus, you can set the maximum duration of an active session (Active session limit) and end an idle session (Idle s
Post a Comment
Read more

GitLab Repository Command Line Instructions

Start project repository Command line instructions You can also upload existing files from your computer using the instructions below. Git global setup git config --global user.name "Jaime Moncada" git config --global user.email "jaimemoncadajr@gmail.com" Create a new repository git clone https://gitlab.com/jaimemoncadajr/library-system.git cd library-system touch README.md git add README.md git commit -m "add README" git push -u origin master Push an existing folder cd existing_folder git init git remote add origin https://gitlab.com/jaimemoncadajr/library-system.git git add . git commit -m "Initial commit" git push -u origin master Push an existing Git repository cd existing_repo git remote rename origin old-origin git remote add origin https://gitlab.com/jaimemoncadajr/library-system.git git push -u origin --all git push -u origin --tags Credit :  https://gitlab.com OR Simple Way to Push an existing
2 comments
Read more