| Previous | Next |
| UTC_E_BINARY_MISSING | UTC_E_FAILED_TO_RESOLVE_CONTAINER_ID |
UTC_E_NETWORK_CAPTURE_NOT_ALLOWED
Read this as a lifecycle result: network-capture policy gate
UTC_E_NETWORK_CAPTURE_NOT_ALLOWED (0x87C51035) is a Universal Telemetry Client result from the network or kernel diagnostic capture layer for this HRESULT. Treat this HRESULT as a state-machine report, not as a generic telemetry outage for this HRESULT. Here the relevant owner is network-capture policy gate: the scenario requested packet capture where UTC policy, destination or device configuration forbids it for this HRESULT. This is narrower than a generic failure of Connected User Experiences and Telemetry for this HRESULT.
Boundary to preserve: The documented condition is “A network capture trace is not allowed.” A comparison run should change that state, not an unrelated component setting.
Network-capture boundary: the diagnostic scenario is not permitted to collect network traffic under the current policy, capability, or security context. Record the scenario configuration, capture provider, caller elevation, and applicable policy. Deleting prior trace files cannot grant a permission that the capture path does not have.
Network and kernel captures are high-impact diagnostic actions for this HRESULT. Policy approval, capture-component startup, ETW/driver resources and rate limits are independent gates and should be verified in that order 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.
Diagnostic record
| UTC diagnostic field | Value |
|---|---|
| Producing layer | network or kernel diagnostic capture |
| Owning state or object | network-capture policy gate |
| Decisive evidence | scenario signer, capture action, interface scope, destination/ring, privacy policy and authorization decision |
| Narrow comparison | run a non-network ETW profile under the same scenario, then compare an approved capture configuration |
| Do not confuse with | UTC_E_FAILED_TO_START_NDISCAP occurs after capture is allowed but the capture component cannot start |
The AllStat message names the immediate condition as “A network capture trace is not allowed” 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.
Isolate one changing condition
- Freeze the failing scenario package, caller inputs and UTC service lifetime that produced this result.
- Collect the high-value state: scenario signer, capture action, interface scope, destination/ring, privacy policy and authorization decision for this HRESULT.
- Use a passing control on the same Windows build, then run a non-network ETW profile under the same scenario, then compare an approved capture configuration 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_FAILED_TO_START_NDISCAP. The distinction is concrete: UTC_E_FAILED_TO_START_NDISCAP occurs after capture is allowed but the capture component cannot start 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.
Capture safety
When testing this result, keep scope and duration minimal, document where the capture is stored and verify normal stop/cleanup for this HRESULT. Packet and kernel captures can contain sensitive data and consume bounded system resources for this HRESULT.
Operational response
Remove the capture action or use an approved diagnostic workflow; do not bypass policy with another sniffer 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.
Restarting Windows, clearing every ETL file or disabling diagnostic policy is not a justified first response to this result. Those actions destroy evidence and can change several independent UTC gates at once 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 network-capture policy gate
- the nearby condition remains distinguishable: UTC_E_FAILED_TO_START_NDISCAP occurs after capture is allowed but the capture component cannot start
Technical references
- Microsoft Open Specifications: Windows error-code registry — reference for network or kernel diagnostic capture while interpreting this result.
- Microsoft: Universal Telemetry Client configuration diagnosis — reference for network or kernel diagnostic capture while interpreting it.
- Microsoft: NDIS filter-driver installation and binding
- Microsoft: Packet Monitor overview
Looking for a different code? Search another status or error code.