| Previous | Next |
| PEER_E_CANNOT_START_SERVICE | PEER_E_INVALID_GRAPH |
PEER_E_NOT_LICENSED
The state transition represented by the HRESULT
PEER_E_NOT_LICENSED — HRESULT 0x80630004 marks the operating-system edition or installed peer feature does not authorize this legacy Peer-to-Peer protocol component to run. A previously successful call does not guarantee that the later handle, identity, record or network presence is still valid.
Reconstruct the sequence
- Identify the first call among PeerGraphStartup, PeerGroupStartup and platform feature detection that returned the HRESULT.
- Preserve Windows edition and build, optional-feature inventory, product policy result, API family requested and whether the same binary works on a supported reference system.
- Correlate graph, group, PNRP and collaboration events with application cancellation, disconnect, shutdown and sign-out events.
- Run the narrow comparison: invoke only the startup routine on two clean systems with different supported-feature inventories, without changing application data.
The Windows Peer Infrastructure is composed of Graphing, Grouping, Identity Manager, PNRP and Collaboration APIs. Initialization and platform prerequisites must be established before object-specific calls can be interpreted.
Interpretation matrix
| Observation | Interpretation |
|---|---|
| No create, open or enumerate call returned the object | The failure is upstream of the platform prerequisite described here. |
| A close, delete, disconnect, expiration or sign-out event came first | Investigate an object-lifetime race before malformed network data. |
| The controlled run advances to another HRESULT | The original startup boundary was corrected and the new code names the next unmet prerequisite. |
Closest alternative diagnosis
PEER_E_CANNOT_START_SERVICE differs because a licensed component may still fail to start its service; licensing and service health must be diagnosed separately. The two codes can occur in one workflow, but they do not justify the same remediation.
Correction and proof
Treat this as a platform capability decision: use a supported OS/component combination or replace the dependency with a maintained networking design. Verify the result by enumerating the expected records, members, connections, endpoints or presence state rather than merely observing that the call stopped failing.
Source material
- Microsoft: Common Peer Infrastructure return codes — it uses this source for the documented peer boundary.
- Microsoft: What is the Peer Infrastructure?
- Microsoft: Programming considerations for Peer-to-Peer applications
Looking for a different code? Search another status or error code.