Fix STATUS_RESOURCE_REQUIREMENTS_CHANGED (0x00000119)

This error pops up when a device stops mid-operation because its resource needs changed. Usually happens during hot-plug or driver update. Here's how to fix it.

What triggers this error

You're working away, and suddenly a USB device — maybe an external drive or a dock — stops responding. Or you're installing a driver update, and Windows throws STATUS_RESOURCE_REQUIREMENTS_CHANGED (0x00000119). This error specifically hits when a device has already agreed to stop (a query-stop succeeded) but then its resource requirements — like memory range, IRQ, or DMA channel — shift before the stop completes. I've seen this most often with USB 3.0 hubs on laptops after a driver update, or when hot-plugging a Thunderbolt dock on a Dell Precision 5570.

Why it happens

Think of it this way: Windows asks a device politely to stop so it can reassign resources. The device says "okay." But before Windows finishes the handshake, the device changes its mind — not intentionally, but because something in its driver or hardware configuration changed. The OS sees the resource requirements have been altered, can't reconcile them with the stop command, and raises this error. The core issue is almost always a driver that's not handling Plug and Play (PnP) transitions correctly, or a resource conflict caused by a recent change — like a BIOS update or a new device attached.

Fix it step by step

Restart the device — physically unplug and replug the USB or Thunderbolt device. If it's internal (like a network card), run devmgmt.msc, find the device, right-click, and select Disable device, wait 10 seconds, then Enable device. This resets the PnP state. I've seen this fix the error in about 1 out of 3 cases.
Roll back the driver — if this started after a driver update, open Device Manager, right-click the device, go to Properties > Driver > Roll Back Driver. If that's grayed out, you'll need to do a manual uninstall (next step).
Uninstall and reinstall the driver — in Device Manager, right-click the device, choose Uninstall device. Check "Delete the driver software for this device" if you want a clean sweep. Then restart the computer. Windows will reinstall a generic driver. If that works, you know the original driver was the problem.
Update the chipset and BIOS — go to your motherboard or laptop manufacturer's support site and grab the latest chipset drivers and BIOS/UEFI update. BIOS updates often fix resource allocation bugs that cause exactly this error. I've fixed this on Lenovo ThinkPads by updating the BIOS from version 1.23 to 1.26.
Check for resource conflicts — open Device Manager, click View > Resources by type. Look for any device showing a conflict (yellow exclamation). If you find one, you may need to move the device to a different PCIe slot or USB port, or disable a conflicting device in BIOS (like an unused COM port).
Run the Windows Hardware and Devices troubleshooter — open Settings > Update & Security > Troubleshoot > Additional troubleshooters > Hardware and Devices. It's not magic, but it can reset PnP state and catch obvious driver issues.

What to check if it still fails

If you've done all the above and the error keeps coming back, look at these:

Is the device faulty? — try it on another computer. If it works fine there, the problem is on your PC, not the device.
Are you using a hub or extension cable? — some passive USB hubs can't negotiate resource changes properly. Connect the device directly to the motherboard USB port.
Check the System Event Log — type eventvwr.msc and go to Windows Logs > System. Filter by source "Kernel-PnP" or "Device Setup Manager". Look for event IDs 411 or 412 right before the error. They'll point you to the exact device that's causing the problem.
Disable fast startup — in Power Options, uncheck "Turn on fast startup". Fast startup can mess with PnP state on shutdown, triggering resource requirement changes on the next boot. This is a known issue on Windows 10 20H2 and later.
Consider a repair install — if nothing else works, use the Windows Media Creation Tool to do an in-place upgrade (keep files and apps). It'll replace system files without wiping your data. This is the nuclear option, but I've seen it fix stubborn PnP issues that clean driver reinstalls couldn't touch.

This error is a pain, but it's usually a driver or BIOS problem. Start with step 1, and work through the list. You'll probably find the fix before you hit the repair install.