STATUS_NOT_SUPPORTED 0XC00000BB fix after Windows 22H2 update
This error shows up when Windows can't handle a syscall or driver request. Usually happens after a feature update or with broken filter drivers.
You're running Windows 11 22H2 or 23H2, maybe Windows 10 22H2. Everything was fine until you installed a feature update or a driver update. Now apps crash with STATUS_NOT_SUPPORTED (0XC00000BB). Or worse, the system blue-screens with the same code. The trigger is almost always a new kernel-mode driver or a changed system service that doesn't support the old API call.
What's actually happening here?
The error code 0XC00000BB maps to STATUS_NOT_SUPPORTED in the NT status table. It means some piece of code — usually a driver or a system service — tried to call a function or IOCTL that the kernel or the target device doesn't recognize. The kernel returns this instead of crashing outright. You'll see it most often with:
- Antivirus or security software (filter drivers that hook into file system operations)
- Virtual machine platforms (VMware, VirtualBox, Hyper-V) that install their own kernel drivers
- Third-party firewall or VPN drivers that intercept network traffic
- Broken chipset or storage drivers after a Windows upgrade
The common thread: Windows updated, but the driver didn't. Or the driver's registration got corrupted. What you're seeing is a version mismatch between the driver's expectations and what the current kernel offers.
The real fix
Skip the generic advice about running SFC or DISM — those rarely fix this. The problem is a driver that doesn't support the current kernel's IOCTL set. Here's the sequence that actually works.
Step 1: Identify the offender
Open Event Viewer (eventvwr.msc). Go to Windows Logs > System. Look for events with source BugCheck or Application Error that mention 0xc00000bb or STATUS_NOT_SUPPORTED. The event details often name the driver file — something like mfewfpk.sys (McAfee) or vlkbd.sys (VirtualBox). Write down the file name.
If Event Viewer shows nothing, open a command prompt as admin and run:
wevtutil qe System /c:10 /f:text /q:"*[System[Provider[@Name='Microsoft-Windows-Kernel-Power']]]"That pulls the last 10 system-critical events without all the noise.
Step 2: Disable or update that driver
Once you know the driver name, check if it's signed and current. Open Device Manager, enable View > Show hidden devices. Expand Non-Plug and Play Drivers. Find the driver from Step 1. Right-click > Properties > Driver tab. If the driver version is older than the date of your Windows update, that's your culprit.
Two options:
- Update it — go to the vendor's site and grab the latest version for your exact Windows build.
- Disable it — in the same properties window, set Startup Type to Disabled. Reboot. Test. If the error goes away, you've found it. You can re-enable after the vendor pushes a fix.
Step 3: Remove orphaned filter drivers
Sometimes a driver uninstall leaves its registration in the registry. Windows still tries to load it. The error fires because the .sys file is gone but the service entry remains.
Open regedit. Navigate to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ServicesLook for subkeys matching the driver name from Step 1. If you see a key for a driver you already uninstalled, right-click it and export it as a backup, then delete it. Reboot.
Step 4: Repair the kernel's syscall table (advanced)
If none of that worked, the problem might be a corrupted syscall dispatch table. This is rare but happens after botched rollbacks or third-party kernel patchers (like some anti-cheat software). Boot into Safe Mode and run:
sfc /scannow
DISM /Online /Cleanup-Image /RestoreHealthI know I said skip these — and for normal driver issues they're useless — but for a corrupted kernel image they're the right tool. If SFC finds corrupt files and can't fix them, you'll need an in-place upgrade using the Windows Media Creation Tool. That keeps your apps but replaces the system files entirely.
If it still fails
Go nuclear. Boot from a Windows USB, select Repair your computer > Troubleshoot > Reset this PC. Choose Keep my files. This rebuilds the OS image from the install media while preserving your user profile. You'll have to reinstall drivers and some apps, but it's faster than chasing ghosts in the registry.
One more thing: double-check your BIOS settings. Some motherboard vendors ship with IOMMU or AMD-V disabled by default. If you're running a hypervisor, that'll cause STATUS_NOT_SUPPORTED on VM-related IOCTLs. Enable virtualization in BIOS and try again.
Was this solution helpful?