| Previous | Next |
| QPARSE_E_INVALID_RANKMETHOD | FDAEMON_E_FATALERROR |
FDAEMON_E_LOWRESOURCE
Filtering stopped because a required resource is low
FDAEMON_E_LOWRESOURCE is HRESULT 0x80041681. Windows documents it as “The system is running out of one of more resources needed for filtering, usually memory.”
Legacy API stage
This result belongs to legacy Windows content indexing and is returned while loading a filter handler and extracting text or properties from queued documents. The exact condition is: memory, commit, handles, address space or another filtering resource falls below the daemon safety threshold.
This value belongs to the legacy filter daemon and content-indexing pipeline. It identifies failure while extracting or committing indexed content, so query syntax changes do not repair it. Preserve the document, filter handler and catalog generation that owned the work item. Current IFilter documentation clarifies handler extraction contracts, while the daemon HRESULT remains tied to the legacy content-indexing pipeline and its catalog generation.
Why it appears
An unindexed document is only the outcome; it does not identify the handler, resource, partition generation, change list or word-list stage that failed.
Developer evidence
- Record the source and normalization path of filter host working set and commit, not only its display form.
- Record document size and type before releasing the relevant objects.
- Associate filter CLSID/version with the exact UTC timestamp and correlation identifier.
- Compare failing and known-good values for queue depth and retry rate under the same provider or handler version.
- Record the source and normalization path of document identity and type, not only its display form.
Hash document content while retaining file type, size, handler CLSID, extraction stage, block counts and catalog generation.
Disciplined troubleshooting
- Capture filter host working set and commit and handle count at the call boundary that returns this result.
- Confirm the operation reached loading a filter handler and extracting text or properties from queued documents with the intended document size and type.
- correlate the HRESULT with process resource counters, document identity, filter CLSID and queue depth at the same timestamp.
Run a copied document through the same filter version in an isolated queue and compare the exact extraction or commit stage with a known-good document type.
Retry conditions
Release the actual constrained resource, isolate leaking handlers and resume indexing gradually; retrying immediately under unchanged pressure is unsafe. Retry only after resource pressure, handler behavior, work generation or catalog storage state changes and stale work is discarded.
Misleading assumptions
It does not prove that all documents or all filters are affected; preserve the triggering work item, handler and catalog generation before broad recovery.
Related query outcomes
FDAEMON_E_TOOMANYFILTEREDBLOCKS names a buffer-limit condition, whereas it is a broader resource shortage.
Developer and administrator guidance
Retain the document identity, filter CLSID/version/bitness, daemon event, catalog generation and retry or quarantine history. Before rebuilding catalogs or reregistering every filter, isolate the document, handler and failed work generation.
Concrete troubleshooting case
A third-party filter leaks memory across large documents. Per-filter telemetry identifies the CLSID, and quarantining that handler restores stable indexing without rebuilding unrelated catalogs.
Official Microsoft references
Looking for a different code? Search another status or error code.