| Previous | Next |
| STATUS_SECUREBOOT_NOT_SUPPLEMENTAL_POLICY | STATUS_HDAUDIO_EMPTY_CONNECTION_LIST |
STATUS_AUDIO_ENGINE_NODE_NOT_FOUND
The miniport advertises an audio engine but exposes no matching node
A WaveRT miniport that supports hardware audio-engine controls exposes IMiniportAudioEngineNode and a corresponding topology node identifier. PortCls uses that node to query formats, volume, mute, peak meter, and other engine properties. This status means the interface claim and the filter topology do not agree.
The defect is normally in the audio driver descriptor or miniport implementation, not in an application selecting the wrong output device. A package mismatch can also combine a PortCls-facing binary with incompatible topology data.
What to inspect
- Inspect the KS filter descriptor and verify that the advertised audio-engine node ID exists.
- Check IMiniportAudioEngineNode methods against the same node constant used in topology descriptors.
- Compare the installed INF, miniport binary, and endpoint configuration from one driver package.
- Use PortCls or audio-driver ETW and kernel debugging to identify the failed node lookup.
References
- Microsoft Open Specifications: NTSTATUS values
- Microsoft: IMiniportAudioEngineNode
- Microsoft: PortCls driver interfaces
- Microsoft sample: audio engine node implementation
Looking for a different code? Search another status or error code.