| Previous | Next |
| PEER_E_CIRCULAR_CHAIN_DETECTED | PEER_E_NO_CLOUD |
PEER_E_CERT_STORE_CORRUPTED
Which peer contract was rejected
PEER_E_CERT_STORE_CORRUPTED — HRESULT 0x80630801 marks the local certificate store used by the Peer Infrastructure cannot provide a consistent, parseable identity or group certificate set. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by Identity Manager, Windows certificate store and identity/group import functions.
Peer identities are secure peer names backed by user-scoped certificate and private-key material. The same identity may be referenced by PNRP registrations and by one or more secure peer groups.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve affected user and profile, certificate-store location, certificate thumbprints, private-key links, store access errors and recent profile or disk recovery actions. |
| Owning context | Record the Windows user, process integrity, graph or group handle, database path and selected cloud. |
| Previous success | Save the last successful create, open, enumerate, parse, register or sign-in result that produced the object. |
| Result order | Retain the first HRESULT so cleanup failures do not replace the code that rejected the request. |
Focused reproduction
Enumerate peer identities and certificates under the owning user, then compare with a clean profile or a verified encrypted identity export. Use disposable identities or groups when the test publishes names, creates credentials or modifies a replicated database.
Why the comparison code is different
PEER_E_NO_KEY_ACCESS differs because corruption is malformed or inconsistent certificate data; no-key-access is inability to read otherwise valid key material. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Restore the user certificate store or import a known-good protected identity/group export; preserve private keys before any destructive cleanup. Avoid deleting every peer database, certificate store or firewall rule because broad resets erase evidence without proving the caller contract was repaired.
Proof of repair
- The original input now passes the precise check represented by this HRESULT.
- The operation reaches the intended graph, group, record, PNRP or collaboration outcome.
- Unrelated identity material, membership credentials and replicated records remain unchanged.
Technical references
- Microsoft: About the Peer Identity Manager API — it uses this source for the documented peer boundary.
- Microsoft: Creating a peer identity
- Microsoft: Identity and group configuration import and export
- Microsoft: Common Peer Infrastructure return codes
Looking for a different code? Search another status or error code.