| Previous | Next |
| UTC_E_FILTER_INVALID_TYPE | UTC_E_FILTER_FUNCTION_RESTRICTED |
UTC_E_FILTER_VARIABLE_NOT_FOUND
Where the UTC workflow stopped: filter variable scope
The code UTC_E_FILTER_VARIABLE_NOT_FOUND (0x87C51047) belongs to scenario filter parser and evaluator, inside the Universal Telemetry Client/DiagTrack workflow. The key question is which UTC object rejected the request. It identifies filter variable scope and reports that an expression references a variable that is not defined at that point in parsing or evaluation; it does not by itself prove that all Windows diagnostic data collection is unavailable.
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.
Evidence to preserve
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario filter parser and evaluator |
| Owning state or object | filter variable scope |
| Evidence to collect | variable name, defining command, branch/state, evaluation order, scope and event payload |
| Narrow comparison | define the variable before the reference in the same scope and replay one event |
| Do not confuse with | UTC_E_FILTER_MISSING_ATTRIBUTE concerns command syntax rather than symbol lookup |
Controlled reproduction
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: variable name, defining command, branch/state, evaluation order, scope and event payload.
- Use a passing control on the same Windows build, then define the variable before the reference in the same scope and replay one event.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state.
Nearby result: UTC_E_FILTER_MISSING_ATTRIBUTE — concerns command syntax rather than symbol lookup.
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.
Correction and verification
Correct declaration/order or reference the actual event field; avoid defaulting silently to empty.
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 it.
- Microsoft: Windows Event Log query schema
- Microsoft: Querying Windows Event Log
Looking for a different code? Search another status or error code.