| Previous | Next |
| UTC_E_FILTER_MISSING_ATTRIBUTE | UTC_E_FILTER_VARIABLE_NOT_FOUND |
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 for this HRESULT. The symbolic name points to a narrow UTC contract that can be tested directly for this HRESULT. The rejected object or state is filter value type declaration, and the specific boundary is that a command declares or produces a type the installed evaluator does not support for this HRESULT. Later service errors should not replace this first result in the incident record for this HRESULT.
UTC filters are typed programs, not plain text searches for this HRESULT. Parsing, command validation, name lookup, signature binding and evaluation are distinct phases for this HRESULT. Capturing the normalized expression and inferred operand types is essential for a useful diagnosis for this HRESULT. Record the configuration package or scenario generation together with the Windows build; otherwise a repaired file can be tested against a stale in-memory graph and appear to fail for the same reason for this HRESULT.
Capture checklist
| UTC diagnostic field | Value |
|---|---|
| Owning state or object | filter value type declaration |
| Producing layer | scenario filter parser and evaluator |
| Do not confuse with | UTC_E_FILTER_ILLEGAL_EVAL compares individually valid types that cannot be compared together |
| Decisive evidence | command/operand, declared type, literal representation, schema version and evaluator capability |
| Narrow comparison | replace the type with one accepted by the same command while retaining equivalent test data |
The AllStat message names the immediate condition as “Filter command contains an unsupported type” for this HRESULT. In practice, the useful extension is to ask whether the request was rejected before any side effect, after partial setup, or during cleanup for this HRESULT. Verify the existence and ownership of the expected output—session, directory, process, result object or emitted event—rather than assuming the message describes the final system state for this HRESULT.
Comparison with a passing case
- Export the relevant
Microsoft-Windows-UniversalTelemetryClient/Operationalevents and preserve their ActivityId or request correlation alongside this result. - Capture command/operand, declared type, literal representation, schema version and evaluator capability for this HRESULT. Do this before restarting the service or deleting any working directory for this HRESULT.
- Perform this one-variable comparison: replace the type with one accepted by the same command while retaining equivalent test data for this HRESULT.
- After the comparison, record the next HRESULT and whether the requested session, action, trigger or output object was actually created for this HRESULT.
The most informative neighbor is UTC_E_FILTER_ILLEGAL_EVAL. The distinction is concrete: UTC_E_FILTER_ILLEGAL_EVAL compares individually valid types that cannot be compared together for this HRESULT. Keeping both symbolic names in logs prevents a broad “DiagTrack error” bucket from hiding whether the failure occurred during parsing, authorization, resource acquisition, execution or teardown for this HRESULT.
Typed-filter note
Save the filter after variable substitution and type inference, not only the authoring XML for this HRESULT. With this result, a visually plausible expression can still fail because the runtime command table, scope or operand types differ from the authoring tool for this HRESULT. Test with one synthetic event whose fields and types are known exactly for this HRESULT.
Resolution and regression test
Use supported primitive/domain types and perform conversion at the producer boundary for this HRESULT. Apply that change only to the owning boundary for this HRESULT. A successful repair must make the controlled case cross this boundary while retaining the intended policy, trace providers, destination and security context for this HRESULT.
Avoid broad registry resets or global service-policy changes until the single-owner comparison has been run for this HRESULT. They can hide the original configuration generation without proving the contract was corrected for this HRESULT.
- the same request now produces its documented success or nonfatal status without a second hidden retry
- the operational log shows one coherent request lifetime and no orphaned action, timer, process or trace session
- teardown followed by a second run does not reuse stale state or recreate filter value type declaration
- the nearby condition remains distinguishable: UTC_E_FILTER_ILLEGAL_EVAL compares individually valid types that cannot be compared together
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
Looking for a different code? Search another status or error code.