| Previous | Next |
| STATUS_ARBITRATION_UNHANDLED | STATUS_WX86_CREATEWX86TIB |
STATUS_CARDBUS_NOT_SUPPORTED
The controller is limited to 16-bit PC Card operation, not CardBus mode
STATUS_CARDBUS_NOT_SUPPORTED is a platform/controller compatibility status. The current NTSTATUS text is unusually specific: the slot detected a CardBus card, but platform firmware is not configured to let the controller operate in CardBus mode, so only 16-bit PC Cards are accepted on that controller.
This matters because CardBus and older 16-bit PC Card operation are not interchangeable labels for the same electrical/software path. Microsoft driver documentation for multifunction PC Card devices distinguishes 16-bit PC Cards and CardBus devices and describes enumeration through the PCMCIA/CardBus stack. A driver update cannot by itself create a firmware mode that the platform does not expose to the operating system.
Collect the exact system model, firmware revision and settings, controller hardware IDs, card type, and bus-enumeration evidence. Compare behavior with a known 16-bit PC Card in the same slot and with the CardBus card in another compatible controller when possible. Check vendor firmware documentation before changing low-level resource settings. Reinstalling the function driver is unlikely to resolve this status when the controller never enters CardBus mode; the failure is earlier in platform configuration and bus enablement.
What to inspect
- Confirm that the inserted device is actually CardBus rather than a 16-bit PC Card.
- Inspect firmware/BIOS configuration and controller hardware IDs before debugging the function driver.
- Use bus enumeration evidence to determine whether the OS ever exposed the controller in CardBus-capable mode.
References
- Microsoft: Supporting multifunction PC Card devices
- Microsoft: Plug and Play device IDs
- Microsoft: Device Manager and PnP
- Microsoft: Using NTSTATUS values
- Microsoft Open Specifications: NTSTATUS values
Looking for a different code? Search another status or error code.