STATUS_ARBITRATION_UNHANDLED (0x40000026) – Fix in 3 Steps

What This Error Actually Means

The error STATUS_ARBITRATION_UNHANDLED (0x40000026) pops up in Device Manager for some PCI or legacy device—usually a sound card, network adapter, or a weird USB controller. What's actually happening here is that Windows's resource arbiter (the part of the kernel that assigns IRQs, memory ranges, and I/O ports) tried to hand off arbitration to a parent device, but that parent also passed the buck. The chain ends with nobody claiming the resource, so the device stays in a failed state.

You'll see this most often on older machines (pre-2018) after a BIOS update, a driver rollback gone wrong, or when you plug a PCIe card into a slot that's already shared with something else. I've seen it on a Dell OptiPlex 7050 after a driver update for the integrated audio chip—suddenly the Realtek HD Audio showed this code.

The fixes below follow a logical progression. Start with step 1—most of the time that's all you need. If not, move down.

Step 1: The 30-Second Fix – Reboot and Rescan

Before you dig into BIOS settings or registry hacks, try this: reboot the machine, then open Device Manager, expand the device showing the error (look for the yellow exclamation mark), right-click it, and select Scan for hardware changes. This forces Windows to re-run the resource arbitration from scratch.

Why does this work sometimes? The arbiter caches resource assignments during boot. A full restart clears that cache. But the scan button specifically triggers a re-negotiation of resources for that device tree. I've seen this fix it for maybe 30% of cases—especially if the error appeared immediately after plugging in a new device while the system was running.

If the yellow mark disappears, you're done. If not, don't repeat the scan—it won't help the second time.

Step 2: The 5-Minute Fix – BIOS and Resource Reservation

This step targets the root cause: the parent device didn't have the resources the child asked for. Most commonly, it's an IRQ or memory range conflict with a legacy device.

1. Update your BIOS/UEFI firmware. Go to your motherboard vendor's site, find the latest BIOS for your exact model, and flash it. This isn't a guess—BIOS updates routinely fix ACPI table bugs that mess up resource routing. On my Asus Z370 board, a BIOS update from 2019 fixed a similar arbitration error for a PCIe Wi-Fi card that kept showing 0x40000026.
2. Disable unused legacy devices in BIOS. Enter BIOS (usually F2 or Del during boot), look for Legacy USB Support, Serial Port, Parallel Port, and Onboard Audio. Disable any you don't use. This frees up IRQs and I/O ranges that the arbiter can then hand to the problematic device.
3. Check PCIe slot assignment. If the error is on a PCIe card, move it to a different slot. Some slots share resources with M.2 slots or SATA ports. Consult your motherboard manual for lane sharing diagrams.

After these changes, boot into Windows and check Device Manager. If the error is gone, you're set. If not, step 3 is the nuclear option.

Step 3: The 15+ Minute Fix – Manual Resource Reassignment via Registry

This is for when Windows still can't figure out the arbitration. You're going to force a specific resource assignment using the registry. Back up your registry first—one wrong value and the device won't work at all.

1. Open Device Manager, find the device with the error, right-click, select Properties > Details tab, and from the dropdown choose Device instance path. Copy that string (e.g., PCI\VEN_8086&DEV_153B&SUBSYS_153B8086&REV_01\3&11583659&0&E0).
2. Open Registry Editor (regedit) and navigate to:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\<device instance path>\Device Parameters
3. Look for a DWORD value called ResourcePolicy. If it doesn't exist, create it (DWORD 32-bit). Set it to 1. This tells the arbiter to ignore the parent's resource hints and try a direct assignment.
4. Reboot. If the error persists, go back and set ResourcePolicy to 2 (force legacy mode) or 3 (force ACPI mode). Test each value.

What's actually happening here is you're overriding the default arbitration behavior. Value 1 lets Windows choose without parent hints. Value 2 forces the legacy ISA-style allocation (good for ancient hardware). Value 3 forces ACPI-based allocation (better for modern systems). The reason this works is that some devices ship with broken ACPI tables that lie about which resources their parents control.

If none of these values fix it, you have a hardware-level conflict—either a faulty card, a bent pin on the slot, or a motherboard that needs RMA. Try the device in another machine to confirm.

Quick Recap

• Step 1: Reboot + rescan. Works 30% of the time.
• Step 2: Update BIOS, disable legacy ports, move PCIe card. Works 60% of the time.
• Step 3: Registry ResourcePolicy tweak. Works for most remaining cases.

If you're still stuck after all three, the hardware itself is likely dead. Don't waste hours—swap the card or motherboard.