| Previous | Next |
| PEER_E_INVALID_ADDRESS | PEER_E_FW_BLOCKED_BY_POLICY |
PEER_E_FW_EXCEPTION_DISABLED
Diagnostic boundary for PEER_E_FW_EXCEPTION_DISABLED
HRESULT 0x80637008 marks the Windows Peer Collaboration Foundation firewall exception exists but is disabled for the active policy/profile. Investigate the first API that reports it rather than a later user-interface wrapper.
Questions that separate the failure
- Was the object returned by Peer Collaboration sign-in/listen and Windows Firewall rule inspection, or reconstructed from cached text or another process?
- Preserve active firewall profiles, rule-group enabled state, local versus policy source, application scope, listening ports and the user consent result.
- 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 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.
Controlled comparison
Enable the documented rule in a controlled test profile and verify both listener creation and inbound traffic, then restore policy. 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 it |
|---|---|
| The HRESULT repeats with identical captured state | Inspect the caller contract and invitation workflow; repeated network retries add no evidence. |
The call advances to PEER_E_FW_BLOCKED_BY_POLICY | PEER_E_FW_BLOCKED_BY_POLICY differs because disabled can be changed locally when policy permits; blocked-by-policy means central policy prevents enabling it. |
| 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
Enable only the required rule through approved user or administrator policy; do not disable the firewall globally. 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: 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.