Tech News

Can’t Pair Some Bluetooth Devices Anymore On Windows 8 Or 10? That’s Intentional!

Written by GreenHatPro Team

Can’t Pair Some Bluetooth Devices Anymore On Windows 8 Or 10? That’s Intentional!

On June 11, 2019, Microsoft issued security updates for all fortified versions of the Windows Operating System (OS). Some of the relinquished updates patch a Bluetooth security susceptibility by “intentionally obviating connections between Windows, and Bluetooth devices that are not secure, and use well-kenned keys to encrypt connections, including security fobs”.

In other words: after the recent security update is installed, Windows avoids the pairing of certain Bluetooth appliances with Windows systems.

Can’t Pair Some Bluetooth Devices Anymore On Windows 8 Or 10? That’s Intentional!

Microsoft Pronounces As:

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 insecure Bluetooth devices.

A Support Page on the Microsoft Support website highlights the affected versions, and updates:

  • Windows 10: all versions.
  • Windows 8.1
  • Window Server 2019
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2012
  • Windows Embedded 8 Standard

The CVE reveals that the issue affects Android devices only. It lists Android version 7.0 to Android 9 as potentially affected. Whether a device is affected depends on the manufacturer. If the manufacturer used a proved example Long Term Key, it is affected by the issue.

In the Bluetooth Low Energy (BLE) specification, there is a provided example Long Term Key (LTK). If a BLE device were to use this as a hardcoded LTK, it is theoretically possible for a proximate attacker to remotely inject keystrokes on a paired Android host due to improperly used crypto. User interaction is not needed for exploitation. Product: Android. Versions: Android-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9. Android ID: A-128843052.

Administrators May Check The Event Log To Find Out If A Bluetooth Device Is Affected By The Intentional Change:

  1. Load the Event Viewer from the Start Menu.
  2. Switch to Windows Logs > System.
  3. Locate the following events:
    • Event Log: System
    • Event Source: BTHUSB or BTHMINI
    • Event ID: 22
    • 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.
  1. If you see the event listed you know that the Bluetooth device is affected by the change.

Microsoft advises to contact the manufacturer of the Bluetooth device to determine whether device updates are available. These need to update the connection options of the Bluetooth device to address the security issue for the device.

Options to connect affected Bluetooth devices, e.g. by overriding the intentional change, have not been revealed by Microsoft. The only option to restore pairing functionality for affected devices for which updates are not available is to restore an earlier version of the Windows OS. Doing so would open the system up for attacks targeting that vulnerability, however. (Via DeskmodderWindows Latest)


About the author

GreenHatPro Team

I am Blogger and SEO Specialist.

Leave a Comment