Fix BlockingDeviceGUID Failing to Stop a Driver Update on Windows 11

You set a BlockingDeviceGUID registry value to block a specific driver from updating on Windows 11, but the driver still updates through Windows Update. This happens because Windows Update uses multiple channels and fallback mechanisms that a single registry key does not always override. The BlockingDeviceGUID method works only on drivers that match the exact hardware ID and that Windows Update evaluates through the targeted driver servicing path. This article explains why the registry key fails, provides the correct steps to enforce the block, and covers alternative methods when the block does not hold.

Why BlockingDeviceGUID Fails to Stop a Driver Update

The BlockingDeviceGUID registry key is part of the older Windows 8-era driver blocking mechanism. When you add a device GUID under this key, Windows Update is supposed to skip driver packages that match that device class. In practice, this block is weak for three reasons.

First, Windows Update uses a layered driver evaluation pipeline. The BlockingDeviceGUID key is checked only during the driver ranking phase. If a driver is offered through a different channel, such as a critical update or a driver from an OEM partner, the block is ignored.

Second, the block applies to the device class GUID, not the individual hardware ID. If the driver package declares a different device class GUID, the block does not match. Many modern drivers use a generic class GUID like {4d36e968-e325-11ce-bfc1-08002be10318} for display adapters, making the block too broad or ineffective.

Third, Windows Update can override local registry settings when the driver is flagged as a security update or a critical fix. The BlockingDeviceGUID key has no mechanism to prevent this override.

Steps to Verify and Correctly Set BlockingDeviceGUID

Before trying alternative methods, confirm that the registry key is correctly configured. A single typo or wrong GUID format causes the block to fail silently.

1. Open Registry Editor
   Press Ctrl+R, type regedit, and press Enter. Click Yes when User Account Control prompts.
2. Navigate to the BlockingDeviceGUIDs key
   Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DriverSearching. If the DriverSearching key does not exist, right-click the CurrentVersion key, select New > Key, and name it DriverSearching.
3. Create or open the BlockingDeviceGUIDs subkey
   Under DriverSearching, right-click, select New > Key, and name it BlockingDeviceGUIDs.
4. Add a new string value with the device GUID
   Right-click the BlockingDeviceGUIDs key, select New > String Value. Name the value 1. Double-click the new value and enter the device class GUID in this format: {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}. Use uppercase hex letters and include the curly braces. For example: {4d36e968-e325-11ce-bfc1-08002be10318}.
5. Restart the Windows Update service
   Open an elevated Command Prompt. Run net stop wuauserv and then net start wuauserv. This forces Windows Update to re-read the registry block.
6. Check that the GUID matches the device class
   Open Device Manager. Right-click the device you want to block and select Properties. Go to the Details tab and select Class Guid from the Property dropdown. Copy the value and compare it to the GUID you entered. They must match exactly.

If the block still fails after these steps, the registry method alone is not reliable. Use the Group Policy method described next.

Use Group Policy to Block a Specific Driver

Group Policy provides a more robust driver block because it is enforced at the system level and applies before Windows Update evaluates driver packages. This method works on Windows 11 Pro, Enterprise, and Education editions.

1. Open Local Group Policy Editor
   Press Ctrl+R, type gpedit.msc, and press Enter.
2. Navigate to Device Installation Restrictions
   Go to Computer Configuration > Administrative Templates > System > Device Installation > Device Installation Restrictions.
3. Enable the policy to block hardware IDs
   Double-click Prevent installation of devices that match any of these device instance IDs. Select Enabled. Click the Show button under Options.
4. Enter the hardware ID of the device
   In the Show Contents dialog, add the hardware ID of the device you want to block. You can find the hardware ID in Device Manager under the device Properties > Details tab > Hardware Ids. Enter the full string, for example PCI\VEN_10DE&DEV_1F82&SUBSYS_00000000&REV_A1. Click OK.
5. Apply the policy and force a refresh
   Close the Group Policy Editor. Open an elevated Command Prompt and run gpupdate /force. Restart the computer.

This policy prevents the driver from being installed through any Windows Update channel, including critical updates. The block applies to the specific hardware instance, not the entire device class.

Alternative Method: Hide the Driver Update Using Microsoft’s Tool

When registry and Group Policy methods are not available, such as on Windows 11 Home, you can use the official Microsoft tool to hide a specific driver update.

1. Download the Show or Hide Updates troubleshooter
   Visit the Microsoft Support website and search for Show or Hide Updates troubleshooter. Download the wushowhide.diagcab file.
2. Run the troubleshooter
   Double-click the downloaded file. Click Advanced and uncheck Apply repairs automatically. Click Next.
3. Select the driver update to hide
   The troubleshooter scans for available updates. Click Hide updates. Check the driver update you want to block. Click Next. The driver is hidden from Windows Update.
4. Verify the block
   Open Windows Update and check for updates. The hidden driver should no longer appear.

This method does not prevent the driver from being installed if it is bundled with a cumulative update. It only hides the standalone driver offer.

Common Issues When BlockingDeviceGUID Fails

BlockingDeviceGUID does not block drivers installed through Windows Update for Business

Windows Update for Business policies override local registry settings. If your device is managed through Intune or Group Policy, the BlockingDeviceGUID key is ignored. Use the Device Installation Restrictions policy instead.

Driver reappears after a Windows 11 feature update

Feature updates reset the driver store and reapply default drivers. The BlockingDeviceGUID key persists across updates, but Windows Update may re-offer the driver if the block is not recognized during the feature update setup. After the feature update, reapply the block using the Group Policy method.

BlockingDeviceGUID blocks all drivers in the same class

Because the block applies to the device class GUID, it blocks all devices that share that GUID. For example, blocking the display class GUID blocks all graphics adapters. To block a single device, use the hardware ID method in Group Policy.

BlockingDeviceGUID vs Group Policy Driver Block: Comparison

Item	BlockingDeviceGUID Registry Key	Group Policy Device Installation Restrictions
Scope	Entire device class GUID	Specific hardware ID or device instance ID
Enforcement level	Checked during driver ranking only	Checked before driver package evaluation
Override by critical updates	Yes, ignored	No, blocks all channels
Supported editions	All Windows 11 editions	Windows 11 Pro, Enterprise, Education
Persistence after feature update	Registry key persists, but block may fail	Policy persists if applied through domain or local policy

The BlockingDeviceGUID registry key is a legacy method that works only in limited scenarios. Group Policy provides a stronger and more precise block. For Windows 11 Home users, the Show or Hide Updates troubleshooter is the only built-in tool to hide a driver update. If you manage multiple devices, configure the driver block through Intune or Windows Update for Business policies for consistent enforcement.