| Previous | Next |
| HNS_INVALID_JSON_REFERENCE | HNS_INVALID_IP |
HNS_ENDPOINT_SHARING_DISABLED
HNS_ENDPOINT_SHARING_DISABLED is an HRESULT used by Windows Host Networking Service (HNS). It indicates that the requested operation requires endpoint sharing but the relevant configuration does not allow it.
What to check for HNS_ENDPOINT_SHARING_DISABLED
- Verify whether endpoint sharing is supported and enabled for the selected HNS network mode.
- Check host policy and container-runtime settings that may restrict shared endpoints.
- Use separate endpoints when sharing is not permitted by the platform configuration.
For HNS_ENDPOINT_SHARING_DISABLED, Microsoft documentation on Windows container networking and HNS
Diagnostic interpretation of HNS_ENDPOINT_SHARING_DISABLED
HNS_ENDPOINT_SHARING_DISABLED has the HRESULT value 0xC03B001D. AllStat records the condition as “Endpoint sharing is disabled.”. For HNS_ENDPOINT_SHARING_DISABLED, 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_SHARING_DISABLED
- Record the exact COM method or Windows API, its input object, the calling thread, and the full 0xC03B001D 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_SHARING_DISABLED or the hns / endpoint / sharing / disabled operation.
- For HNS_ENDPOINT_SHARING_DISABLED, 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_SHARING_DISABLED
Retry HNS_ENDPOINT_SHARING_DISABLED only when the owning API documents a transient state or after the condition described as “Endpoint sharing is disabled.” has changed. For HNS_ENDPOINT_SHARING_DISABLED, 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.