| Previous | Next |
| ERROR_NO_BROWSER_SERVERS_FOUND | ERROR_LOG_SECTOR_INVALID |
SCHED_E_SERVICE_NOT_LOCALSYSTEM
The Task Scheduler service must be configured to run in the System account to function properly. Individual tasks may be configured to run in other accounts.
SCHED_E_SERVICE_NOT_LOCALSYSTEM is Win32 error 6200 (0x1838) and belongs to Task Scheduler 1.0 service identity.
Where the result appears
- Legacy Task Scheduler 1.0 startup.
- Task Scheduler 1.0 interfaces on older systems.
- Service-account hardening that changes the scheduler identity.
- Migration of scheduled tasks from a legacy installation.
Likely causes
- The scheduling service process is configured under an account other than LocalSystem.
- Service configuration was changed by policy or manual hardening.
- An image captured an unsupported legacy service identity.
- A security template altered the service logon account.
Troubleshooting steps
- Record the service logon account and startup type.
- Record Windows version and scheduler API generation.
- Record System and TaskScheduler event logs.
- Record service configuration change history.
- Record individual task principals, which are separate from service identity.
What to verify
Verify whether the legacy scheduling component runs under an account other than LocalSystem. Check its logon account and startup type together with the Windows version and scheduler API generation.
A focused validation should recreate the relevant part of this situation: a hardening script changes the legacy scheduling component to a custom account. Reverting the service identity while leaving task-specific accounts intact restores operation. The negative case should keep that component under the unsupported account and confirm error 6200; the recovery case should change only the service logon identity and verify the same task operation.
Handling, retry, and recovery
Restore the legacy scheduling component to its supported LocalSystem identity for the affected legacy implementation, then configure individual tasks with their intended principals. Back up task definitions before changing service configuration.
Difference from nearby codes
The error concerns the account running the scheduling service itself; it does not require every scheduled task to run as LocalSystem.
Practical example
A hardening script changes the legacy scheduling component to a custom account.
References
- Microsoft: System Error Codes (6000–8199) — reference for error 6200.
- Microsoft: Task Scheduler service — reference for error 6200.
- Microsoft: Task Scheduler security contexts — reference for error 6200.
Looking for a different code? Search another status or error code.