What does HRESULT 0x87C51046 (UTC_E_FILTER_INVALID_TYPE) mean?

UTC_E_FILTER_INVALID_TYPE

Locate the rejected contract: filter value type declaration

When UTC_E_FILTER_INVALID_TYPE (0x87C51046) is returned, the producing layer is scenario filter parser and evaluator. The symbolic name points to a narrow UTC contract that can be tested directly. The rejected object or state is filter value type declaration, and the specific condition is that a command declares or produces a type the installed evaluator does not support. Keep this first HRESULT even if a later service call reports another error.

UTC filters are typed programs, not plain text searches. Parsing, command validation, name lookup, signature binding and evaluation are distinct phases. Capturing the normalized expression and inferred operand types is essential for a useful diagnosis.

Capture checklist

Comparison with a passing case

1. Export the relevant Microsoft-Windows-UniversalTelemetryClient/Operational events and preserve their ActivityId or request correlation alongside this result.
2. Capture command/operand, declared type, literal representation, schema version and evaluator capability. Do this before restarting the service or deleting any working directory.
3. Perform this one-variable comparison: replace the type with one accepted by the same command while retaining equivalent test data.
4. After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created.

Nearby result: UTC_E_FILTER_ILLEGAL_EVAL — compares individually valid types that cannot be compared together.

Typed-filter note

Save the filter after variable substitution and type inference, not only the authoring XML. A visually plausible expression can still fail because the runtime command table, scope or operand types differ from the authoring tool. Test with one synthetic event whose fields and types are known exactly.

Resolution and regression test

Use supported primitive/domain types and perform conversion at the producer boundary.

Technical references

• Microsoft Open Specifications: Windows error-code registry — reference for scenario filter parser and evaluator while interpreting this result.
• Microsoft: Universal Telemetry Client configuration diagnosis — reference for scenario filter parser and evaluator while interpreting this result.
• Microsoft: Windows Event Log query schema — reference for scenario filter parser and evaluator while interpreting it.
• Microsoft: Querying Windows Event Log