What does HRESULT 0x80041738 (FILTER_E_IN_USE) mean?

 
Previous Next
FILTER_E_UNREACHABLE FILTER_E_NOT_OPEN

FILTER_E_IN_USE

Another process is using the document in an incompatible way

FILTER_E_IN_USE is HRESULT 0x80041738 (-2147215560 signed; 2147751736 unsigned). Its severity bit is 1, facility is 4 (FACILITY_ITF for these values), and code field is 0x1738. For FILTER_E_IN_USE, standard HRESULT severity rules classify the value as a failure. AllStat describes the value as “The document is in use by another process.”

State represented by the HRESULT

FILTER_E_IN_USE belongs to opening content that is reachable but locked against the access mode required by the handler. The decisive interpretation is that a sharing or application-level lock prevents a stable filtering read. For FILTER_E_IN_USE, keep the symbolic constant and method stage together in logs; its hexadecimal value alone cannot identify the owning transition or input.

For FILTER_E_IN_USE, the IFilter contract is stateful: GetChunk selects a chunk, then GetText or GetValue consumes content according to STAT_CHUNK flags. In the FILTER_E_IN_USE investigation, method order and filter-instance ownership are therefore part of the evidence. This context narrows the responsible component without replacing the code-specific checks below.

Likely triggers

  • At step 1 for FILTER_E_IN_USE, the producer saves with exclusive sharing
  • At step 2 for FILTER_E_IN_USE, antivirus or conversion software temporarily owns the file
  • At step 3 for FILTER_E_IN_USE, the handler requests stronger access than necessary
  • At step 4 for FILTER_E_IN_USE, a stale lock remains after an abnormal process exit

The useful hypothesis for FILTER_E_IN_USE must explain both opening content that is reachable but locked against the access mode required by the handler and the documented condition. Compare the failing case with a control that preserves locking process when available and changes only requested share and access modes; this prevents unrelated environment differences from dominating the FILTER_E_IN_USE test.

Data for diagnosis

  • FILTER_E_IN_USE: Locking process when available.
  • FILTER_E_IN_USE: Requested share and access modes.
  • FILTER_E_IN_USE: File identity and last-write time.
  • FILTER_E_IN_USE: Duration and recurrence of the lock.

For FILTER_E_IN_USE, capture locking process when available before releasing objects, closing handles or reconnecting. Retain the raw HRESULT with requested share and access modes, component version, UTC timestamp and correlation ID. Bound the FILTER_E_IN_USE telemetry to diagnostic metadata because document content, credentials and unrestricted query text may be sensitive.

Investigation order

  1. Attempt a read with the same sharing semantics. Associate this observation specifically with FILTER_E_IN_USE.
  2. Identify the producer and whether the lock is part of an atomic save. Associate this observation specifically with FILTER_E_IN_USE.
  3. Wait for file size and write time to stabilize. Associate this observation specifically with FILTER_E_IN_USE.
  4. Avoid copying a half-written file merely to bypass the lock. Associate this observation specifically with FILTER_E_IN_USE.

Change one variable per FILTER_E_IN_USE control run. Preserve the component version and target identity, then alter only the condition described as a sharing or application-level lock prevents a stable filtering read. This isolates whether FILTER_E_IN_USE is causal rather than merely repeatable.

Correct response

Use bounded delayed retry after the writer closes the document. Escalate persistent locks instead of spinning. For FILTER_E_IN_USE, record whether opening content that is reachable but locked against the access mode required by the handler produced any content, update or state transition before returning. If completion remains unknown, the FILTER_E_IN_USE path must not replay non-idempotent work until the owner confirms final state.

The retry gate for FILTER_E_IN_USE should be a concrete change in locking process when available or requested share and access modes. A timer alone cannot demonstrate that the FILTER_E_IN_USE contract condition has changed.

Scope of the signal

It does not imply an ACL denial, missing file or malformed document. Without the call boundary for opening content that is reachable but locked against the access mode required by the handler, FILTER_E_IN_USE also cannot identify which wrapper or configuration layer introduced the condition.

Related HRESULT values

FILTER_E_ALREADY_OPEN is internal filter-instance state; FILTER_E_IN_USE concerns competing ownership of the source document. In FILTER_E_IN_USE telemetry, preserve neighboring constants separately because the same visible symptom may require a different caller action, owner or recovery gate.

Developer and administrator actions

  • For FILTER_E_IN_USE, check At the code boundary, keep locking process when available beside the returned HRESULT.
  • For FILTER_E_IN_USE, check In telemetry, correlate requested share and access modes with the target and component generation.
  • For FILTER_E_IN_USE, check For regression coverage, force the documented condition: a sharing or application-level lock prevents a stable filtering read.
  • For FILTER_E_IN_USE, check For operations staff, expose the corrective state change rather than a generic retry button.
  • For FILTER_E_IN_USE, check After remediation, validate one known-good control and the original failing case.

Example in a pipeline

A desktop application rewrites a presentation under an exclusive lock. The indexer retries after the rename completes and receives stable bytes. In this scenario, handling FILTER_E_IN_USE at its real contract boundary prevents the application from collapsing a precise state into an unhelpful generic “search failed” message.

Official Microsoft references

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