What does HRESULT 0x80041820 (CI_E_NOT_RUNNING) mean?

CI_E_NOT_RUNNING

The content-index service is not running

CI_E_NOT_RUNNING is HRESULT 0x80041820. Windows documents it as “Service is not running.”

Relevant contract

This result belongs to connecting to or invoking the service before it has an active process and endpoint. The required service is stopped, failed during startup or has terminated.

Ways this state occurs

• An administrator stopped the service
• Startup fails because configuration or storage is invalid
• The service crashes
• The client contacts the host before service startup completes

Compare the failing case with a control that preserves service state and process ID and changes only startup/termination events; this prevents unrelated environment differences from dominating the test.

Telemetry fields

• Service state and process ID.
• Startup/termination events.
• Configured dependencies.
• Client target and connection timestamp.

Capture service state and process ID before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with startup/termination events, component version, UTC timestamp and correlation ID.

Verification sequence

1. Query service state on the real target.
2. Inspect the first startup failure rather than repeated client errors.
3. Verify dependencies and catalog paths.
4. Reconnect only after an explicit running and ready indication.

Preserve the component version and target identity, then alter only the condition described as the required service is stopped, failed during startup or has terminated.

Safe continuation

Start or repair the service, then create a fresh connection. Repeated immediate calls while stopped are noise. Record whether connecting to or invoking the service before it has an active process and endpoint produced any content, update or state transition before returning.

Retry only after a concrete change in service state and process ID or startup/termination events.

Limits of the HRESULT

It does not mean a particular catalog is absent or filtering is disabled. Without the call boundary for connecting to or invoking the service before it has an active process and endpoint, it also cannot identify which wrapper or configuration layer introduced the condition.

Distinguishing related codes

CI_E_SHUTDOWN describes an index in shutdown; it directly reports service availability.

Developer and administrator actions

• At step 1, record service state and process ID with the returned HRESULT
• At step 2, in telemetry, correlate startup/termination events with the target and component generation
• At step 3, for regression coverage, force the documented condition: the required service is stopped, failed during startup or has terminated
• At step 4, for operations staff, expose the corrective state change rather than a generic retry button
• At step 5, after remediation, validate one known-good control and the original failing case

Practical case

A monitoring client starts before the indexing service after reboot. Dependency-aware startup removes the false incident.

Official Microsoft references

• Microsoft: content-indexing helper-function values — official contract information relevant to this HRESULT.
• Microsoft: Content-Indexing values
• Microsoft: HRESULT values
• Microsoft: Windows Search SQL syntax