| Previous | Next |
| STATUS_FLT_REGISTRATION_BUSY | STATUS_MONITOR_UNKNOWN_DESCRIPTOR_FORMAT |
STATUS_MONITOR_NO_DESCRIPTOR
Descriptor acquisition failed before mode validation
STATUS_MONITOR_NO_DESCRIPTOR is raised before Windows can build monitor capabilities from descriptor data. In typical external-display paths that data is EDID or a related display descriptor obtained through the connector and driver stack; a valid adapter and a visible target do not guarantee that a usable descriptor was returned.
Treat it as an acquisition or transport problem, not as proof that the panel has no supported modes. A disconnected cable, unstable hot-plug state, dock, KVM, protocol converter, GPU driver issue, or a monitor that returns no useful descriptor can all leave the target without data. Linux documents the same failure class: a monitor, KVM, or graphics board can supply no EDID or bogus EDID.
What to check
- Record the adapter, connector, target ID, hot-plug state, and raw descriptor bytes before applying any override.
- Compare a direct connection with the dock, KVM, cable, or converter path that was present when the failure occurred.
- Do not reuse descriptor bytes or a mode set retained from a previous monitor connection.
References
- Microsoft: WmiMonitorRawEEdidV1Block
- VESA Enhanced EDID Standard, Release A2
- Linux kernel: EDID troubleshooting and overrides
Looking for a different code? Search another status or error code.