Summary
You may experience issues pairing, connecting or using certain Bluetooth devices after installing security updates released June 11, 2019. These security updates address a security vulnerability by intentionally preventing connections from Windows to unsecure Bluetooth devices. Any device using well-known keys to encrypt connections may be affected, including certain security fobs.
For more information, see CVE-2019-2102.
Next steps
If you experience issues pairing, connecting or using Bluetooth devices after installing any of the affected security updates, please contact the manufacturer of your Bluetooth device to determine if a device update exits.
Advanced users can verify if their device is affected by checking Event Log for the following event:
|
Event Log |
System |
|
Event Source |
BTHUSB or BTHMINI |
|
Event ID |
22 |
|
Name |
BTHPORT_DEBUG_LINK_KEY_NOT_ALLOWED |
|
Level |
Error |
|
Event Message Text |
Your Bluetooth device attempted to establish a debug connection. The Windows Bluetooth stack does not allow debug connection while it is not in the debug mode. |
Affected updates
The following latest cumulative update (LCU) and Monthly Rollups released on June 11, 2019 or later for the affected platforms will experience the new behavior:
-
KB4503293 or later LCU for Windows 10, version 1903.
-
KB4503327 or later LCU for Windows 10, version 1809 and Windows Server 2019.
-
KB4503286 or later LCU for Windows 10, version 1803.
-
KB4503284 or later LCU for Windows 10, version 1709.
-
KB4503279 or later LCU for Windows 10, version 1703.
-
KB4503267 or later LCU for Windows 10, version 1607 and Windows Server 2016.
-
KB4503291 or later LCU for Windows 10, version 1507.
-
KB4503276 or later Monthly Rollup for Windows 8.1 and Windows Server 2012 R2.
-
KB4503285 or later Monthly Rollup for Windows Server 2012 and Windows Embedded 8 Standard.
The following Security Only updates are also affected:
