Fix ERROR_PLUGPLAY_QUERY_VETOED (0x2AB) on Windows

This error hits when Windows tries to configure a new device but a driver or service blocks the query. Here's how to find the culprit and get your hardware working again.

You plug in a USB drive, a printer, or maybe an external GPU dock, and instead of the familiar ding, you get a notification: "The Plug and Play query operation was not successful." The Event Viewer shows ERROR_PLUGPLAY_QUERY_VETOED (0X000002AB). It's infuriating because the device itself might be fine—the problem is on Windows' side.

This usually happens when you're installing a new device or updating a driver, especially after a Windows feature update. Think of a scenario: you've just upgraded from Windows 10 to 11, and your old webcam stops being recognized. Or you plug in a Bluetooth adapter and Windows decides it doesn't want to query it anymore. The error means that a driver or service returned a "veto" to Windows' query—it's like the driver said "no" to being probed, so Windows gives up.

Why Does This Happen?

Under the hood, Plug and Play (PnP) asks each device driver "hey, can I look at your capabilities?" The driver is supposed to answer yes and pass along details. But sometimes a driver is buggy, outdated, or has a pending state from a previous failed installation. When that driver returns a status that Windows interprets as a veto, you get 0x2AB. It's not a hardware failure—it's a software handshake failure.

Common culprits:

Outdated or corrupted drivers, especially for USB hubs or chipset controllers.
A leftover driver from a previous device that's now conflicting.
Windows Update installed a generic driver that doesn't match your hardware.
Some background service (like a third-party antivirus or device management tool) is blocking PnP queries.

The real fix is to identify the specific device that's causing the veto and reset its driver stack. Don't waste time on generic hardware troubleshooter—it rarely works here.

Fix It in 5 Steps

Open Device Manager and find the problem device. Press Win + X and select Device Manager. Look for any device with a yellow triangle or an error icon. If you see "Unknown device," that's your target. Right-click it and select Properties. In the Details tab, look at the Hardware IDs—note the VEN and DEV values. You'll need this if you have to manually update.
Uninstall the device driver. Right-click the problematic device and select Uninstall device. Check the box that says "Delete the driver software for this device" if it's available. This removes the corrupted driver that's vetoing the query.
Scan for hardware changes. In Device Manager, click the action menu at the top (or right-click your computer name) and select "Scan for hardware changes." Windows will re-detect the device and try to install a fresh driver. If it works, you're done. If not, move to step 4.
Install the correct driver manually. Go to your device manufacturer's website, download the latest driver for your exact model and Windows version. Run the installer as administrator. If the installer doesn't work (some are old), use Device Manager: right-click the device, Update driver, Browse my computer, then point to the folder where you extracted the driver.
Restart the Plug and Play service. Sometimes the service itself gets stuck. Open Command Prompt as administrator and run:
```
net stop pnp && net start pnp
```
Then restart your PC. This is a quick kick in the pants for the PnP subsystem.

I've seen this fix work for most people. But if you're still staring at the same error after these steps, there are a couple of deeper things to check.

When It Still Fails

Here's the part that trips up even techs. The veto might come from a non-device driver—like a filter driver installed by a security suite. To check, open Device Manager and go to View > Show hidden devices. Expand the "Non-Plug and Play Drivers" section. Look for anything suspicious (like a driver from an old antivirus). Right-click and disable it, then restart.

Also check the System Event Log for the exact device that returned the veto. In Event Viewer, look under Windows Logs > System. Find the event with source "Kernel-PnP" and event ID 400 or 410. The message will tell you which device caused the failure. Then you can target that specific driver.

If you're on a laptop, check for a BIOS update—some systems have a PnP bug that only manifests after a Windows update. Also try removing the device, shutting down completely, and restarting with the device unplugged. Then plug it in after Windows boots. It's a cliché, but I've seen it work when all else fails.

Last resort: use System Restore to roll back to a point before the error started. But try the driver uninstall first—it fixes 80% of these cases. Good luck.