KB5011543 fixes a very important Bluetooth bug that caused a BSOD on Windows 10.

KB5011543 fixes a very important Bluetooth bug that caused a BSOD on Windows 10.
  • As far as I can tell, the Search Highlights feature was not the only thing that KB5011543 did.
  • As a bonus, it also fixed a Bluetooth bug that had been causing trouble since January.
  • Another official workaround for this problem was also provided by Microsoft on the official release page for the app.


People who use Windows 10 have been getting blue screens of death because of a Bluetooth bug that Microsoft has just fixed. This is an important update for people who use the software.

Since the January KB5009596 builds, this seems to have been a thing. The fix came with the new Windows 10 builds 19042.1620, 19043.1620, and 19044.1620, which were all released this morning, under the name KB5011543.

Let's get right to it and see what we're dealing with, or were dealing with, now that Microsoft has finally fixed this terrible glitch.

We finally got rid of the problem with KB5009596.

People who have Windows devices that are paired with Bluetooth devices after installing KB5009596 or later might get this error: If your device has a problem, you'll need to start it up again.

A blue screen and the stop code "IRQ NOT LESS OR EQUAL" came with this message.

SummaryOriginating updateStatusLast updated
Devices with certain Bluetooth pairings might receive error messages on a blue screen
Devices using the Bluetooth/ServicesAllowedList CSP Group Policy might receive an “IRQ NOT LESS OR EQUAL” error message.
OS Build 19041.1503
KB5009596
2022-01-25
Resolved
KB5011543
2022-03-22
14:00 PT

Microsoft-Windows-WER-SystemErrorRe event 1001: The computer has rebooted from a bugcheck. This error will be in the System log in Event Viewer. It will say The computer has rebooted from a bugcheck. There was a bugcheck: 0x0000000a.

Finally, the same thing that brought Search Highlights to Windows 10 worked.

To avoid this problem, IT administrators who use Intune or other tools can change the Windows registry before installing this update by following the steps below.

  • Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Bluetooth\ 
  • Add the following registry entry: {0000110a-0000-1000-8000-00805f9b34fb} and {0000110b-0000-1000-8000-00805f9b34fb} to the ServicesAllowedList value

A lot more details about this issue can be found on the official Microsoft page, where the detailed report has been posted.

Have you also been affected by this horrendous bug? Share your experience with us in the comments section below.