What does HRESULT 0x00041735 (FILTER_S_DISK_FULL) mean?

FILTER_S_DISK_FULL

Indexing warns that disk space is becoming exhausted

FILTER_S_DISK_FULL is HRESULT 268085 (0x00041735) from Indexing Service. AllStat describes it as “The disk is getting full.” The severity bit indicates a nonfailure result, but the value carries a specific condition that must not be collapsed into plain S_OK.

In the legacy Indexing Service or IFilter pipeline, FILTER_S_DISK_FULL means that the disk is getting full. Handling of FILTER_S_DISK_FULL is complete only after the caller verifies what work occurred and what remains outstanding.

Diagnostic sequence

• Capture the raw value 0x00041735 before wrappers, signed-decimal formatting, exceptions, or generic success handling replace FILTER_S_DISK_FULL.
• Identify the operation that returned FILTER_S_DISK_FULL, including interface or callback, component build, thread, process, and the state-machine phase.
• For FILTER_S_DISK_FULL, prove the decisive condition: the service can prevent catalog corruption and retain enough space for checkpoint or rollback operations.
• Inspect every output, count, status array, buffer, callback, task state, media timestamp, transaction vote, or security token that remains part of the FILTER_S_DISK_FULL contract.
• Compare state immediately before and after FILTER_S_DISK_FULL; success severity does not guarantee that optional work or the caller’s intended high-level action completed.
• Reproduce FILTER_S_DISK_FULL with the smallest input that retains the same condition, then alter only the recorded cause before repeating the operation.

Where the status is encountered

• FILTER_S_DISK_FULL can be returned during legacy Indexing Service catalog processing; log the exact method and object state instead of interpreting the constant outside that contract.
• FILTER_S_DISK_FULL can be returned during IFilter text and property extraction; log the exact method and object state instead of interpreting the constant outside that contract.
• FILTER_S_DISK_FULL can be returned during search enumeration, scan scheduling, or catalog administration; log the exact method and object state instead of interpreting the constant outside that contract.

Because FILTER_S_DISK_FULL is informational, a language binding may expose it as success and hide the symbolic distinction. Keep the original HRESULT available until the code-specific branch has run.

What must be true before accepting it

For FILTER_S_DISK_FULL, verify that the service can prevent catalog corruption and retain enough space for checkpoint or rollback operations. Failure to prove the boundary can make FILTER_S_DISK_FULL look healthy while the intended operation remains unfinished.

Classify the operation phase reached at FILTER_S_DISK_FULL before releasing objects or issuing replacement work.

Evidence and telemetry

• For FILTER_S_DISK_FULL, preserve volume free bytes and configured threshold.
• For FILTER_S_DISK_FULL, preserve catalog and temporary directory sizes.
• For FILTER_S_DISK_FULL, preserve growth rate.
• For FILTER_S_DISK_FULL, preserve current scan checkpoint.
• For FILTER_S_DISK_FULL, preserve cleanup actions and resumed generation.

Also record filter_s_disk_full_operation, filter_s_disk_full_state_before, filter_s_disk_full_state_after, UTC time, process and thread identifiers, component version, and a correlation ID. Keep FILTER_S_DISK_FULL traces useful by recording object identity and timing while excluding authentication or content secrets.

Difference from nearby results

FILTER_S_DISK_FULL must be distinguished from ordinary S_OK and from failure-severity values in the same API family; its documented state changes control the next action.

The semantic difference represented by FILTER_S_DISK_FULL should be visible in both control flow and operational metrics.

Correct handling and recovery

Throttle or pause indexing, measure catalog and temporary-file growth, free or extend storage, then resume from a verified checkpoint.

Retry FILTER_S_DISK_FULL only when a documented input or state has changed. Only a meaningful state transition should cause a repeated request after FILTER_S_DISK_FULL.

Practical scenario

During a full scan the catalog volume crosses its safety threshold. The service pauses new ingestion, removes obsolete catalogs, and resumes only after free-space headroom is restored.

A regression test should reproduce FILTER_S_DISK_FULL, assert the relevant outputs and state, then change only the decisive condition and verify the expected neighboring result or ordinary completion.

Developer and administrator guidance

Code should branch on FILTER_S_DISK_FULL before a generic SUCCEEDED(hr) path whenever outputs, continuation, cancellation, or recovery differ. Telemetry should retain FILTER_S_DISK_FULL, 0x00041735, the producing method, and a correlation ID.

For FILTER_S_DISK_FULL, document ownership of retry, cancellation, cleanup, and user messaging. Administrators should validate a targeted state change for FILTER_S_DISK_FULL and then repeat the minimal reproduction.

References

• Microsoft: Filter interface values — official Microsoft material used to interpret FILTER_S_DISK_FULL.
• Microsoft: About Indexing Service filters — official Microsoft material used to interpret FILTER_S_DISK_FULL.
• Microsoft: Using custom filters — official Microsoft material used to interpret FILTER_S_DISK_FULL.
• Microsoft: HRESULT values — official Microsoft material used to interpret FILTER_S_DISK_FULL.

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