STATUS_PLUGPLAY_QUERY_VETOED (0X80000028) Fix: Driver or USB Conflict

Most Common Cause: A Single Stubborn USB Device or Hub

This error almost always shows up when Windows tries to query a device during Plug and Play enumeration — and some driver says "no." The culprit is usually a USB device that's half-dead, a cheap hub with bad firmware, or a driver that got corrupted after an update. I've seen it with everything from a knockoff mouse receiver to a webcam that refused to reinitialize after sleep.

The fastest way to find the offender is to open Device Manager, look for anything with a yellow bang, and kill it. But if you don't see one, you have to do a binary search.

1. Unplug every USB device except keyboard and mouse.
2. Reboot. If the error's gone, plug devices back one at a time, rebooting each time, until the error returns. That's your bad device.
3. For that device: right-click in Device Manager, select "Uninstall device," and check the box that says "Delete the driver software for this device." Then reboot. Windows will reinstall a fresh driver.

Had a client last month whose entire print queue died because this — a cheap USB-to-serial adapter was vetoing queries for a label printer. Once we yanked the adapter's driver, everything worked.

Second Most Common Cause: Faulty or Outdated Graphics Driver (NVIDIA/AMD)

Here's where it gets weird. Sometimes the veto comes from a graphics driver, not a USB device. The Plug and Play manager queries the display adapter during power state transitions — wake from sleep, monitor hot-plug, or driver update. If the GPU driver is old, corrupted, or has a bad power management setting, it can veto the query.

I've seen this on Windows 10 with NVIDIA driver 472.12 specifically. The error would pop in Event Viewer every time the system tried to go to sleep. The fix is brutal but effective:

1. Download the latest driver from NVIDIA/AMD directly — not from Windows Update. Use DDU (Display Driver Uninstaller) in Safe Mode to nuke the old driver completely.
2. Install the fresh driver with a clean install option.
3. If the error persists, disable the GPU's power management: go to Device Manager, find your GPU under Display adapters, right-click > Properties > Power Management tab, uncheck "Allow the computer to turn off this device to save power."

This fix has saved me three times in the last year. It's not glamorous, but it works.

Third Most Common Cause: Corrupted System Files or Registry Hive

If neither USB nor GPU is the problem, you're looking at a system-level corruption. The Plug and Play service itself can get its registry hive corrupted — usually after a failed driver install or a sudden power loss during a device enumeration. The error code 0X80000028 will show up in Event Viewer under System log, source "PlugPlayManager."

Here's the real fix:

1. Run sfc /scannow from an elevated Command Prompt. Let it finish, reboot.
2. Then run DISM /Online /Cleanup-Image /RestoreHealth. This can take 20 minutes. Reboot again.
3. If those clear nothing, check the registry at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\PlugPlay. Look for a key called Parameters — if it's missing or empty, that's not your problem. If it has values you didn't put there, export the key as a backup, then delete the orphaned values.

I had one case where a client's antivirus had locked the Plug and Play registry key — Trend Micro, if you're keeping score. Disabling the AV and running the system file checker fixed it instantly.

Quick-Reference Summary Table

Start with the USB hunt — it's the cheapest and fastest test. If that doesn't clear it, gut the GPU driver. Only go to system file repair if both fail. Most of the time, a single bad driver is the veto. Kill it and move on.