| Previous | Next |
| PEER_E_INVALID_RECORD_SIZE | PEER_E_GROUP_NOT_READY |
PEER_E_UNSUPPORTED_VERSION
Diagnostic boundary for PEER_E_UNSUPPORTED_VERSION
HRESULT 0x80632090 marks a group, invitation, credential, database or structure version is not supported by the installed Peer Infrastructure. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by PeerGroupParseInvitation, import/open operations and versioned P2P structures, or reconstructed from cached text or another process?
- Preserve version field, producing OS/API version, serialized package hash, consumer OS build and the parsing/open call.
- Did shutdown, deletion, sign-out, expiration or replication occur between object selection and use?
- Does the operation succeed under the controlled comparison described below?
Peer Grouping layers membership credentials, roles, record signing and encrypted connections on top of graphing and PNRP. Local open state, online connection state and authorization state are separate.
Controlled comparison
Generate the same artifact on the target system using its installed API and compare with the cross-version artifact. 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 for this HRESULT |
|---|---|
| The HRESULT repeats with identical captured state | Inspect the caller contract and GMC trust chain; repeated network retries add no evidence. |
The call advances to PEER_E_DBINITIALIZATION_FAILED | PEER_E_DBINITIALIZATION_FAILED differs because unsupported-version is an explicit format contract; initialization-failed may be a broader load or migration failure. |
| 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
Use a mutually supported format or recreate/export through a supported migration path instead of editing version fields. 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: Grouping API functions — it uses this source for the documented peer boundary.
- Microsoft: How to connect to a peer group
- Microsoft: How group security works
- Microsoft Open Specifications: Peer-to-peer grouping overview
Looking for a different code? Search another status or error code.