HRESULT 0x8004130C (SCHED_E_SERVICE_NOT

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Task Scheduler is not installed on the target computer. Verify the actual endpoint, Windows image and service registration before repair.

Previous	Next
SCHED_E_TASK_NOT_RUNNING	SCHED_E_CANNOT_OPEN_TASK

SCHED_E_SERVICE_NOT_INSTALLED

The target computer has no installed Task Scheduler service

SCHED_E_SERVICE_NOT_INSTALLED is the failure HRESULT 0x8004130C (-2147216628 as a signed 32-bit value). Its severity bit is set, the facility field is 4 (FACILITY_ITF), and its facility-specific code is 0x130C. AllStat describes the result as “The Task Scheduler Service is not installed on this computer.”

Contract boundary

The scheduler endpoint is absent rather than merely stopped. Microsoft documents Task Scheduler as automatically installed on supported Windows versions, so this status on a current supported system deserves verification of the target identity and operating-system image before any repair action. In practical terms, this result is returned when a client attempts to create or connect to the Task Scheduler service on the selected local or remote computer. Preserve it symbolically because a generic COM failure path loses its scheduler-specific recovery decision.

Conditions that produce it

The automation connected to a different computer, recovery image or offline Windows installation than intended.
A stripped, damaged or unsupported Windows image lacks the service registration and binaries expected by the API.
Legacy management code is running against a platform where the corresponding Task Scheduler component was never installed.
A remote inventory or provisioning system reported an obsolete endpoint after the machine was reimaged.
The HRESULT was propagated from a compatibility layer and no longer describes the computer shown in the user interface.

Rank these explanations for it by matching them to the exact method, target and scheduler state observed at failure time.

Telemetry that matters

Resolved target computer name, domain, address and operating-system build.
The Task Scheduler API generation used by the caller and whether the connection is local or remote.
Service Control Manager registration for the scheduler service on the actual target.
Windows servicing and image-health logs if service components are missing.
The original HRESULT before wrappers translate it into a generic connection error.

The decisive question for it is not whether Task Scheduler works in general, but which object, service state, compatibility rule or execution instance owned the failed operation. Before reacting to this result, collect evidence rather than restarting services, rewriting task XML or changing security settings.

Investigation workflow

Confirm the machine identity at the same endpoint used by the scheduler call.
Verify that the target is a supported Windows installation rather than WinPE, an offline image or a legacy platform.
Check service registration without assuming that a stopped service is equivalent to an uninstalled service.
Compare system component state with a healthy machine of the same Windows edition and build.
Use supported Windows repair or image servicing procedures only after missing installation is established.

Safe remediation

Repeated connection attempts cannot install the component. Correct a targeting mistake immediately; for a damaged supported Windows image, restore the Windows component through approved servicing and then reconnect. Avoid copying service binaries or registry entries from another computer. The owner of the higher-level workflow should define whether this result is terminal, retryable after a state change, or converted into an administrative action.

Avoid the wrong conclusion

The code does not mean that a particular task is absent, and it is not the same as <code>SCHED_E_SERVICE_NOT_RUNNING</code>. Starting a service can fix the latter but cannot repair genuinely missing installation state. Logging only the decimal value without task path, method and target computer is insufficient to explain this result.

How to distinguish related results

SCHED_E_SERVICE_NOT_RUNNING identifies an installed service that is stopped. SCHED_E_SERVICE_NOT_AVAILABLE says the endpoint cannot currently provide the requested operation without asserting that installation is absent.

Example from operations

A remote management console uses a stale asset record and contacts a minimal recovery environment instead of the production host. Service lookup confirms no scheduler installation in that environment; correcting the target resolves the error without changing either machine. A regression test should reproduce this result, assert the code-specific evidence, then change only the decisive condition and verify the expected recovery.

Official Microsoft references

Looking for a different code? Search another status or error code.