| 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 for this HRESULT. The decisive question is which UTC object rejected the request for this HRESULT. 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 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.
Evidence to preserve
| UTC diagnostic field | Value |
|---|---|
| Producing layer | scenario filter parser and evaluator |
| Owning state or object | filter variable scope |
| Decisive evidence | 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 |
The AllStat message names the immediate condition as “Filter variable does not exist at point of evaluation” 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.
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 for this HRESULT.
- Use a passing control on the same Windows build, then define the variable before the reference in the same scope and replay one event for this HRESULT.
- Repeat once after normal teardown to prove the result is not caused by a stale handle or leftover run state for this HRESULT.
The most informative neighbor is UTC_E_FILTER_MISSING_ATTRIBUTE. The distinction is concrete: UTC_E_FILTER_MISSING_ATTRIBUTE concerns command syntax rather than symbol lookup 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.
Correction and verification
Correct declaration/order or reference the actual event field; avoid defaulting silently to empty 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.
Do not treat this result as permission to bypass collection policy, script approval, path restrictions or trace arbitration for this HRESULT. A repair that only weakens those controls is not a valid regression result 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 variable scope
- the nearby condition remains distinguishable: UTC_E_FILTER_MISSING_ATTRIBUTE concerns command syntax rather than symbol lookup
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.