HRESULT 0xC03B0002 (HNS_ENDPOINT_NOT_FOUND): meaning and diagnosis

Status / error code:

Category:

Constant name:

Source:

Facility:

Operating System:

Description:

Host Networking Service could not find the requested network endpoint.

Previous	Next
HNS_NETWORK_NOT_FOUND	HNS_LAYER_NOT_FOUND

HNS_ENDPOINT_NOT_FOUND

HNS_ENDPOINT_NOT_FOUND is an HRESULT used by Windows Host Networking Service (HNS). It indicates that the endpoint was deleted, never created, or was addressed with a stale identifier.

What to check for HNS_ENDPOINT_NOT_FOUND

Enumerate endpoints on the intended network and verify the endpoint GUID used by the operation.
Check container lifecycle logs for a prior stop, removal, or failed endpoint-creation operation.
Do not reuse endpoint identifiers persisted from an earlier container or network instance.

For HNS_ENDPOINT_NOT_FOUND, Microsoft documentation on Windows container networking and HNS

Diagnostic interpretation of HNS_ENDPOINT_NOT_FOUND

HNS_ENDPOINT_NOT_FOUND has the HRESULT value 0xC03B0002. AllStat records the condition as “The endpoint was not found.”. For HNS_ENDPOINT_NOT_FOUND, in practice, interpret that wording at the boundary owned by the Windows component or COM interface that returned the HRESULT, rather than treating the value as a generic Windows message.

Evidence to capture for HNS_ENDPOINT_NOT_FOUND

Record the exact COM method or Windows API, its input object, the calling thread, and the full 0xC03B0002 value before a wrapper converts it to an exception or Boolean result.
Capture any IErrorInfo text, activity identifier, event-log entry, and subsystem trace that mentions HNS_ENDPOINT_NOT_FOUND or the hns / endpoint / found operation.
For HNS_ENDPOINT_NOT_FOUND, check the documented return contract of the specific API because the same HRESULT can require different recovery in different interfaces.

Retry and recovery for HNS_ENDPOINT_NOT_FOUND

Retry HNS_ENDPOINT_NOT_FOUND only when the owning API documents a transient state or after the condition described as “The endpoint was not found.” has changed. For HNS_ENDPOINT_NOT_FOUND, configuration, policy, format, and authorization failures normally require correction first; an immediate loop can hide the original call site and add secondary errors.

Looking for a different code? Search another status or error code.