| Previous | Next |
| JSCRIPT_E_CANTEXECUTE | E_FDPAIRING_HWFAILURE |
E_FDPAIRING_NOCONNECTION
E_FDPAIRING_NOCONNECTION belongs to Function Discovery and PnP-X device pairing. It marks the pairing workflow could not establish or retain the required device connection. The useful starting point is the exact API, object and state transition that returned 0x8FD00001, because a shell or application message can hide that boundary.
Where this result is raised
Function Discovery separates discovery from association and installation. A device can be visible yet reject a connection, complete discovery but fail authentication, lack a usable profile, or depend on a disabled PnP-X bus component. Pairing evidence must therefore distinguish host policy, provider state, network reachability, device capacity and user-confirmation outcomes.
Discovery can succeed through SSDP, WS-Discovery or another provider while the subsequent control channel fails. Capture endpoint metadata, network profile, protocol and device liveness separately from authentication.
Inspect the discovery provider, pairing handler, association database, network protocol, device ceremony, or PnP-X bus component that returned the HRESULT.
Evidence worth collecting
- Function-instance identity and XAddr/endpoint.
- Discovery protocol and network interface.
- Connection attempt and lower socket status.
- Device online state.
A controlled diagnostic sequence
- First: Repeat discovery and connection as separate steps.
- Next: Verify the advertised endpoint is reachable from the selected interface.
- Then: Check firewall and network isolation.
- Finally: Retain provider OnError details.
How to interpret comparison tests
| Control | Interpretation | Hold constant |
|---|---|---|
| Same device, controlled host or network | A change separates device-side state from host provider, policy and transport. | Keep firmware and ceremony type fixed. |
What this code does not justify
AUTHFAILURE means a connection reached an authentication ceremony; NOCONNECTION may fail before credentials are evaluated.
Do not delete drivers or pairing records before proving basic transport.
Verification after correction
Treat it as corrected only when the same discovered instance establishes the required channel and survives one reconnect; retain the original negative case so fallback cannot be mistaken for repair.
Technical references
Looking for a different code? Search another status or error code.