| Previous | Next |
| EAS_E_CURRENT_CONNECTED_USER_NEED_TO_CHANGE_PASSWORD | PEER_E_NOT_INITIALIZED |
PEER_E_IPV6_NOT_INSTALLED
Diagnostic boundary for PEER_E_IPV6_NOT_INSTALLED
HRESULT 0x80630001 marks the Windows Peer Infrastructure cannot start its PNRP, graphing or grouping path because IPv6 is unavailable to the caller. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGraphStartup, PeerGroupStartup, PeerCollabStartup and the PNRP Winsock namespace provider, or reconstructed from cached text or another process?
- Preserve IPv6 component state, interface bindings, address inventory, the initialization API used, and the first service or Winsock error recorded before this HRESULT.
- Did shutdown, deletion, sign-out, expiration or replication occur between object selection and use?
- Does the operation succeed under the controlled comparison described below?
The Windows Peer Infrastructure is composed of Graphing, Grouping, Identity Manager, PNRP and Collaboration APIs. Initialization and platform prerequisites must be established before object-specific calls can be interpreted.
Controlled comparison
Initialize the same Peer API after confirming that at least one intended interface has IPv6 enabled; compare that with a host where only IPv4 is present. Keep identity, graph or group ID, cloud and user context fixed unless one of them is the tested variable.
Decision table
| Observed result | Next action |
|---|---|
| The HRESULT repeats with identical captured state | Inspect the caller contract and startup boundary; repeated network retries add no evidence. |
The call advances to PEER_E_NO_CLOUD | PEER_E_NO_CLOUD differs because IPv6 can be installed while the requested PNRP cloud is still absent; that later namespace failure is a different checkpoint. |
| The controlled run succeeds but production does not | Compare user token, database path, cloud, endpoint, certificate chain and effective firewall policy. |
Safe remediation and verification
Restore the IPv6 component and bindings required by the legacy peer stack instead of adding an application-specific IPv4 fallback that the API does not support. Back up exportable identity and group configuration, and hash database or invitation artifacts before modifying them.
The repair is complete only when the intended operation succeeds and its resulting connection, record, membership, endpoint or collaboration scope can be independently enumerated.
References
- Microsoft: Common Peer Infrastructure return codes.
- Microsoft: What is the Peer Infrastructure?
- Microsoft: Programming considerations for Peer-to-Peer applications
Looking for a different code? Search another status or error code.