| Previous | Next |
| WDSTPC_E_UNKNOWN_ERROR | WDSTPC_E_KICKED_POLICY_NOT_MET |
WDSTPC_E_NOT_INITIALIZED
WDSTPC_E_NOT_INITIALIZED is an API lifecycle failure. Microsoft states that WdsTransportClientInitialize should be called before any other multicast-client function, so session creation and callback registration must occur after successful client initialization.
Initialize once and make the result visible to all client users
- Call
WdsTransportClientInitializebefore registering callbacks or initializing a session. - Store and check the actual initialization return code; do not set an application “initialized” flag before the API succeeds.
- Coordinate shutdown with worker threads so no late session operation runs after the multicast client has been torn down.
This error often exposes wrapper ordering or process-shutdown races rather than a network problem. A server address, multicast route, or content provider cannot fix an uninitialized client library. Trace the process-level initialize/shutdown lifetime separately from individual session handles. In services, also examine restart paths where static state survives longer than worker objects or where cleanup can race with queued callbacks.
WdsTransportClientInitialize · WDS transport client functions
Looking for a different code? Search another status or error code.