Windows 11 Task Scheduler Runs Only When User Is Logged In: Fix

You have created a scheduled task in Windows 11 that should run automatically, but it only runs when you are logged into your account. This problem occurs because the task is configured to run only when the user is signed in, or the task lacks the necessary permissions to run in the background without an active user session. This article explains why this happens and provides a step-by-step fix to make your tasks run regardless of the user login state.

Why Windows 11 Task Scheduler Tasks Fail to Run When No User Is Logged In

Task Scheduler in Windows 11 allows you to automate tasks such as running scripts, launching applications, or performing maintenance. By default, when you create a task using the basic wizard, it is set to run only when the user is logged on. This setting ties the task execution to an active user session. If the user logs off or locks the screen, the task stops or does not start.

The root cause is the task’s security context. When a task runs under a user account, it requires the user’s authentication token to be loaded. This token is only available when the user is signed in. To run a task without a logged-in user, you must change the task to run under a different security context, such as the SYSTEM account or a specific service account. Additionally, the task must be configured to run whether the user is logged on or not. Without this change, the task will only execute when the user is actively signed into Windows 11.

Steps to Configure a Task to Run Without User Login in Windows 11

1. Open Task Scheduler
   Press the Windows key, type Task Scheduler, and select the app from the search results. Alternatively, press Windows + R, type taskschd.msc, and press Enter.
2. Locate the Task
   In the left pane, expand Task Scheduler Library. Find the task that is not running when you are logged out. Right-click the task and select Properties.
3. Change the Security Context
   In the General tab, select the option Run whether user is logged on or not. This is the critical setting. If you want the task to run with the highest system privileges, also check Run with highest privileges. For most administrative tasks, this is recommended.
4. Configure the User Account
   If you keep the current user account, Windows will prompt you to enter the user’s password. If the account has no password, you must set one. Alternatively, you can change the account to NT AUTHORITY\SYSTEM by clicking Change User or Group, typing SYSTEM, and clicking Check Names. The SYSTEM account does not require a password.
5. Adjust Conditions
   Go to the Conditions tab. Uncheck Start the task only if the computer is on AC power if the task must run on battery. Uncheck Start only if the following network connection is available unless the task requires network access. These conditions can block the task from running when the user is not logged in.
6. Set the Task to Run Regardless of User State
   In the Settings tab, ensure Allow task to be run on demand is checked. Check Run task as soon as possible after a scheduled start is missed to avoid missed runs. Uncheck Stop the task if it runs longer than if the task might take a long time.
7. Save and Test
   Click OK. If you changed the account to a user account, enter the password. To test, right-click the task and select Run. Log off or lock the screen and verify the task executes using Event Viewer or by checking its output.

Common Issues When Tasks Do Not Run Without User Login

Task Does Not Run After Changing to SYSTEM Account

If the task runs under the SYSTEM account but fails to execute, the task may require network resources that the SYSTEM account cannot access. The SYSTEM account has limited network permissions. To fix this, use a domain service account or a local user account with the necessary network access. Ensure the account has the Log on as a batch job right in Local Security Policy.

Task Runs Only Once Then Stops

A task configured to run whether the user is logged on or not may stop after the first run if the trigger is set to At task creation/modification. This trigger fires only once. Change the trigger to a schedule or an event. Also, check the Settings tab for If the task fails, restart every to enable automatic retries.

Password Prompt Appears When Editing the Task

When you change a task to run whether the user is logged on or not, Windows requires the user account password. If the account has no password, you must set one. If you use the SYSTEM account, no password is needed. If you forget the password, you must delete and recreate the task.

Run Whether User Is Logged On vs Run Only When User Is Logged On

Item	Run Whether User Is Logged On or Not	Run Only When User Is Logged On
Execution context	Runs in the background without a user session	Runs only when the user is signed in
User interaction	Cannot show UI or interact with the desktop	Can show UI and interact with the desktop
Password requirement	Requires account password or SYSTEM account	No password required
Use case	Automated maintenance, backups, scripts	User-specific reminders, data processing
Security	Higher risk if misconfigured; use SYSTEM carefully	Lower risk as it runs under the user session

The key difference is visibility and interaction. Tasks that need to show a window or require user input must run only when the user is logged on. Tasks that perform silent operations can run without a logged-in user.

You can now configure any scheduled task in Windows 11 to run automatically even when no user is logged in. Start by opening Task Scheduler and editing the task’s General tab. For tasks that must run silently, use the SYSTEM account and uncheck power conditions. To verify the task runs correctly, use Event Viewer under Windows Logs > Microsoft-Windows-TaskScheduler/Operational to see detailed execution logs. A practical tip: always test the task by logging off and checking the result after five minutes.