| Previous | Next |
| ERROR_FSFILTER_OP_COMPLETED_SUCCESSFULLY | ERROR_INTERRUPT_STILL_CONNECTED |
ERROR_INTERRUPT_VECTOR_ALREADY_CONNECTED
the requested interrupt vector already has an active connection.
ERROR_INTERRUPT_VECTOR_ALREADY_CONNECTED identifies this condition: A driver attempted to connect an interrupt vector that is already connected under the applicable sharing and affinity rules. The cause can be duplicate initialization, stale teardown state, or incorrect resource descriptors.
Where the result appears
- driver start or restart.
- MSI/MSI-X vector setup.
- legacy line-based interrupt registration.
- recovery after partial device initialization.
What to collect
- translated interrupt resource and vector.
- interrupt mode, polarity, sharing, and affinity.
- number of prior successful connect calls.
- driver start/stop trace and cleanup status.
Handling and recovery
Prevent the second connection or disconnect the original one through the documented lifecycle before reconnecting. Validate that each successful IoConnectInterruptEx-style operation has exactly one matching disconnect and that restart paths reset ownership state.
Common misinterpretation
Do not assume a hardware IRQ conflict solely from this status. Duplicate software registration in the same driver is often the more direct explanation.
References
Looking for a different code? Search another status or error code.