[German]Microsoft has also fixed an issue that can cause bluescreens in Bluetooth functions with preview update KB5011543 dated 22 March 2022. This affects Windows 10 versions 20H2 to 21H2 and was caused by cumulative update KB5009596 dated 25 January 2022 or later. Here is some information about it.
Advertising
Preview update KB5011543
Preview update KB5011543 was released as optional on 25 March 2022 for Windows 10 versions 20H2 to 21H2 (see my blog post Windows 10 / Windows Server Preview Updates (March 22, 2022) for details). In the list of fixed issues, the support post states:
Addresses a known issue that might cause some devices to receive error messages on a blue screen when those devices are paired to Bluetooth devices. This issue occurs when certain configuration service provider (CSP) policies are in place that affect the Bluetooth A2dp profile.
In short, the update is intended to fix a problem known to Microsoft when pairing Bluetooth with other devices. When using Bluetooth A2DP profiles, bluesceens can occur with various devices.
Note: CSP policies are not common outside of corporate environments. So the problem does not occur with private users and private devices.
Microsoft's support post on the problem
Microsoft has posted the article Devices with certain Bluetooth pairings might receive error messages on a blue screen on the Windows 10 Health Status page in the Know-Issues section as of 23 March 2022, which picks up the details. The problem may occur after installing KB5009596 or later updates. Affected users may receive the error message when pairing devices with Windows 10 via Bluetooth:
our device ran into a problem and needs to restart.
The ends thing then ends with a blue screen and the stop code: IRQ NOT LESS OR EQUAL. The entry can then be found in the system log in the event display on the affected devices:
Microsoft-Windows-WER-SystemErrorRe event 1001
The computer has rebooted from a bugcheck. Die Fehlerprüfung war: 0x0000000a
However, this problem only occurs when certain configuration service provider (CSP) policies are in place that affect the Bluetooth A2dp profile. The problem can occur in one of two scenarios:
Advertising
- During reboot at the end of the update installation process, if the Windows client device was previously paired with mobile phones or other audio devices via Bluetooth.
- After the updates are installed, users pair their updated Windows client device with a new mobile phone or audio device via Bluetooth.
In addition, Microsoft states that the update may be listed in the Windows Update installation history as "Installation failed on <date> – 0x800f0845" – this is after it was rolled back due to an error after installation. Once the 22 March 2022 update KB5011543 is installed, the error should be resolved.
Workaround, if needed
To mitigate this issue (if update KB5011543 is not to be installed), IT administrators using Intune or other tools can change the Windows registry before installing this update by following these steps:
- Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PolicyManager\current\device\Bluetooth\
- Add the registry entries {0000110a-0000-1000-8000-00805f9b34fb} and {0000110b-0000-1000-8000-00805f9b34fb} to the ServicesAllowedList entry.
If the update has already been installed and BlueScreens occur, Windows should be started in safe mode. Then the relevant registry entries can be added. In addition, Microsoft has created a possibility to roll back the causing update by means of KIR. The rollback guideline can be downloaded here. However, all this is not necessary if the optional update KB5011543 has been installed.
Question that is possibly related to this: Asking because the timing seems about right. I have a desktop computer that was working OK with a USB 3.0 Plug-in Bluetooth 5.0 dongle, then it wasn't. When looking into the Device Manager where the Bluettooth items are typically present, they are no longer present. MS help just says to delete them and they will repopulate, well you can see the problem of deleting something that does not exist . . .
Other searches online mentioned that these items won't show up if the Bluetooth radio is turned-off. I went and found the original BT drivers from 2008, and of course they were for WIN 7. Regardless, I have been running WIN 10 since it came out and the BT part has been working OK, so the questions is: what did MS do recently that unintentionally turned-off the BT functionality?
FWIW: I have this same problem on a laptop that has built-in BT. It worked OK, then this summer the same problem occurred. However, on the laptop I can get the BT USB dongle to work, despite the BT functionality not showing-up on the Device Manager list.
I also have a MS Surface 3 tablet and the internal BT there is still functional and shows up in the Device Manager list.
Any and all help is appreciated, as the Help Desk folks at MS were completely and utterly useless.