Fix STATUS_PNP_REBOOT_REQUIRED (0XC00002D2) - device won't start

You plug in a USB webcam, a PCIe network card, or maybe a new SSD, and Windows installs the driver but then throws this: STATUS_PNP_REBOOT_REQUIRED (0XC00002D2). The device shows up in Device Manager with a yellow triangle and says “The device will not start without a reboot.” Or maybe you updated a driver and now your printer won't print until you restart. I had a client last month who spent two hours trying to install a new Bluetooth adapter. Same error. Every time. Reboot fixed it, but he wanted to know why.

What's really happening here?

This error is Windows being lazy about resource allocation. When you install a driver for a new device, Windows often needs to reassign system resources like IRQs, memory ranges, or I/O ports. But Windows PnP manager doesn't do that on the fly—it waits for a reboot. So instead of finishing the setup, it puts the device in a “pending restart” state. That's it. Not a hardware failure, not a corrupt driver. Just a pending reboot.

The trigger is almost always a driver install or update that affects system-level resources. USB controllers, network adapters, sound cards, and especially storage controllers. If it's a simple mouse or keyboard, you won't see this. But anything that touches PCIe slots or system buses? You'll see it.

The fix: numbered steps

Skip the reboot for now if you want to understand what's happening. But the real fix is straightforward.

Open Device Manager — Right-click the Start button or press Win+X, then select Device Manager. Find the device with the yellow triangle. It's usually under “Other devices” or the category that matches the hardware.
Check the error details — Double-click the device, go to the General tab. You'll see the error code. If it's 0XC00002D2, you're in the right place.
Try this first: restart Windows — I know it's dumb, but do it. Click Start, Power, Restart. Not Shutdown then restart. A full restart. Shutdown doesn't always clear the pending state because of Fast Startup in Windows 10/11. If you want to be sure, hold Shift while clicking Restart to force a full reboot.
If restart didn't work: force driver reinstall — Right-click the device in Device Manager, select “Uninstall device.” Check the box that says “Delete the driver software for this device” if it's a new install. Then scan for hardware changes (Action menu > Scan for hardware changes) or just plug the device back in. This gives Windows a clean slate.
Still stuck? Use DISM and SFC — Open an admin Command Prompt (Win+X > Terminal (Admin) or Command Prompt (Admin)). Run these two commands in order:
```
DISM /Online /Cleanup-Image /RestoreHealth
sfc /scannow
```
This fixes system file corruption that can interfere with PnP. I've seen a corrupt driver store cause this error to hang around. Reboot after both complete.
Last resort: update the motherboard chipset drivers — Go to your motherboard or laptop manufacturer's site. Download and install the latest chipset driver package. This updates the PCIe bus driver and often clears stuck PnP states. Real story: a client's Dell Precision workstation kept getting this error for a new NVMe drive. Updated the chipset driver from 2020 to 2023. Rebooted once. Worked.

What to check if it still fails

If you've done all that and the error persists, you're in a less common situation. Here's what to check:

Is the device physically seated? For PCIe cards, reseat the card. I've seen a slightly loose card cause this because Windows detects it but can't fully initialize it. Pull it out, blow out the slot, push it in until you hear the click.
Check for driver conflicts — Open Device Manager, go to View > Show hidden devices. Look for grayed-out devices from previous installs. If you see multiple instances of the same device, uninstall all of them, then reboot and reinstall the driver fresh.
Is your Windows installation old? If you've never updated Windows in years, you can hit PnP bugs that have been fixed. Run Windows Update and install all quality updates, including optional driver updates. Windows 11 22H2 had a known PnP issue with some PCIe devices that was patched in KB5022845.
Try the driver from the manufacturer, not Windows Update — Windows Update drivers are often generic. Go to the hardware vendor's site and download their specific driver. For example, Realtek network cards work better with the Realtek driver than the Microsoft one.

One more thing: if this error shows up on a fresh install of Windows and won't go away, it's almost always a BIOS setting. Check if Secure Boot is enabled and if the device supports it. For older hardware, disable Secure Boot temporarily to see if the device initializes. I had a customer with a 2017 laptop that couldn't use a USB-C docking station with Secure Boot on. Turned it off, rebooted, device worked. Turned it back on afterward and it stayed working.