| Previous | Next |
| PEER_E_FW_BLOCKED_BY_SHIELDS_UP | E_BLUETOOTH_ATT_INVALID_HANDLE |
PEER_E_FW_DECLINED
Where the peer stack rejects the operation
PEER_E_FW_DECLINED — HRESULT 0x8063700B marks the user declined the request to enable firewall exceptions needed by Peer Collaboration. Treat it as a presence session result rather than a generic peer-networking failure.
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.
Evidence to preserve before retrying
- Record the first failing surface among Peer Collaboration sign-in and Windows Firewall consent flow.
- Preserve consent prompt result, requesting application, user/session, active firewall profile and whether the rule remains disabled.
- Place successful creation or discovery, state-changing events and the failing call on one timeline.
- Keep peer names, identities, record identifiers, invitation data and endpoints in their original Unicode or binary representation.
Controlled isolation
Repeat only through an explicit user-initiated test and observe the rule state after accepting versus declining. Change one variable only; simultaneous changes to identity, cloud, database and firewall state destroy attribution.
| Checkpoint | Question for it |
|---|---|
| Before the API | Was the required invitation workflow obtained in this process and user context? |
| At the HRESULT | Preserve consent prompt result, requesting application, user/session, active firewall profile and whether the rule remains disabled. |
| After correction | honor the decision and present clear instructions for enabling the scoped rule manually; never bypass consent by disabling firewall protection. |
Neighboring result
PEER_E_PRIVACY_DECLINED differs because firewall-declined is network-rule consent; privacy-declined is People Near Me presence consent. Keep both HRESULT values in chronological order because a corrected prerequisite can expose the next validation stage.
Safe response
Honor the decision and present clear instructions for enabling the scoped rule manually; never bypass consent by disabling firewall protection. Preserve durable graph databases, group exports, identity certificates and invitation artifacts before changing them.
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.