| Previous | Next |
| PEER_E_NOT_SIGNED_IN | PEER_E_TIMEOUT |
PEER_E_PRIVACY_DECLINED
Which peer contract was rejected
PEER_E_PRIVACY_DECLINED — HRESULT 0x80637004 marks the user declined the People Near Me privacy prompt, so the collaboration presence feature was not enabled. The base description names the outcome; diagnosis requires the data contract and lifecycle accepted by PeerCollabSignIn and People Near Me privacy flow.
Peer Collaboration provides serverless presence, contacts, endpoint subscriptions and invitations. Its operations depend on an interactive user context, explicit sign-in scopes and firewall/privacy consent.
Minimum diagnostic packet
| Item | Evidence for this HRESULT |
|---|---|
| Raw input | Preserve consent UI outcome, requested sign-in scope, current sign-in options, user profile and whether an application attempted to bypass the prompt. |
| 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
Repeat sign-in only through the documented interactive consent flow in a disposable test account. 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_FW_DECLINED differs because privacy-declined concerns enabling People Near Me presence; firewall-declined concerns permission to enable network exceptions. A diagnostic report should retain both the symbolic constant and the unsigned hexadecimal value.
Recommended change
Respect the decline and require the user to opt in through the Windows privacy/firewall UI; do not alter consent registry state programmatically. 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 Collaboration API — it uses this source for the documented peer boundary.
- Microsoft: Collaboration API functions
- Microsoft: People Near Me requirements
- Microsoft: Windows Firewall rules
Looking for a different code? Search another status or error code.