Cause of Windows 10 Bluetooth Problems. Bluetooth problems on Windows 10 computers are usually caused by a combination of software and hardware issues. Sometimes multiple Bluetooth devices cause conflicts with each other and the computer to which the Bluetooth devices are trying to connect. Download drivers for Bluetooth devices for free. Operating System Versions: Windows XP, 7, 8, 8.1, 10 (x64, x86) Category: Devices. Subcategory: Bluetooth devices. Popular Drivers. Chipsets network cards modems smartphones. Are you tired of looking for the drivers for your devices?
To verify, open the Bluetooth control panel on the device. Then, go to another Bluetooth-enabled device, open the Bluetooth control panel, and verify that you cannot see the name of the device. 1 (default) – Allowed. When set to 1, other devices will be able to detect the device. To verify, open the Bluetooth control panel on the device. How to Fix Bluetooth Device Not Showing in Device Manager in Windows PCFacebook Page: on twitter: https://twitter.c. Windows 10 - Bluetooth device control buttons not work after first Foobar run 2018-10-28 04:19:57 I have weird problem with Foobar2000 on Windows 10 (build 1803) and Bluetooth control steering Play/Pause, Next, Previous, Volume by buttons on headphones after first run Foobar after system start or restart.
-->Applies to:Microsoft Defender for Endpoint
Microsoft recommends a layered approach to securing removable media, and Microsoft Defender for Endpoint provides multiple monitoring and control features to help prevent threats in unauthorized peripherals from compromising your devices:
Discover plug and play connected events for peripherals in Microsoft Defender for Endpoint advanced hunting. Identify or investigate suspicious usage activity.
Configure to allow or block only certain removable devices and prevent threats.
Allow or block removable devices based on granular configuration to deny write access to removable disks and approve or deny devices by using USB device IDs. Flexible policy assignment of device installation settings based on an individual or group of Azure Active Directory (Azure AD) users and devices.
Prevent threats from removable storage introduced by removable storage devices by enabling:
- Microsoft Defender Antivirus real-time protection (RTP) to scan removable storage for malware.
- The Attack Surface Reduction (ASR) USB rule to block untrusted and unsigned processes that run from USB.
- Direct Memory Access (DMA) protection settings to mitigate DMA attacks, including Kernel DMA Protection for Thunderbolt and blocking DMA until a user signs in.
Create customized alerts and response actions to monitor usage of removable devices based on these plug and play events or any other Microsoft Defender for Endpoint events with custom detection rules.
Respond to threats from peripherals in real-time based on properties reported by each peripheral.
Note
These threat reduction measures help prevent malware from coming into your environment. To protect enterprise data from leaving your environment, you can also configure data loss prevention measures. For example, on Windows 10 devices you can configure BitLocker and Windows Information Protection, which will encrypt company data even if it is stored on a personal device, or use the Storage/RemovableDiskDenyWriteAccess CSP to deny write access to removable disks. Additionally, you can classify and protect files on Windows devices (including their mounted USB devices) by using Microsoft Defender for Endpoint and Azure Information Protection.
Discover plug and play connected events
You can view plug and play connected events in Microsoft Defender for Endpoint advanced hunting to identify suspicious usage activity or perform internal investigations.For examples of Defender for Endpoint advanced hunting queries, see the Microsoft Defender for Endpoint hunting queries GitHub repo.
Sample Power BI report templates are available for Microsoft Defender for Endpoint that you can use for Advanced hunting queries. With these sample templates, including one for device control, you can integrate the power of Advanced hunting into Power BI. See the GitHub repository for PowerBI templates for more information. See Create custom reports using Power BI to learn more about Power BI integration.
Allow or block removable devices
The following table describes the ways Microsoft Defender for Endpoint can allow or block removable devices based on granular configuration.
| Control | Description |
|---|---|
| Restrict USB drives and other peripherals | You can allow/prevent users to install only the USB drives and other peripherals included on a list of authorized/unauthorized devices or device types. |
| Block installation and usage of removable storage | You can't install or use removable storage. |
| Allow installation and usage of specifically approved peripherals | You can only install and use approved peripherals that report specific properties in their firmware. |
| Prevent installation of specifically prohibited peripherals | You can't install or use prohibited peripherals that report specific properties in their firmware. |
| Allow installation and usage of specifically approved peripherals with matching device instance IDs | You can only install and use approved peripherals that match any of these device instance IDs. |
| Prevent installation and usage of specifically prohibited peripherals with matching device instance IDs | You can't install or use prohibited peripherals that match any of these device instance IDs. |
| Limit services that use Bluetooth | You can limit the services that can use Bluetooth. |
| Use Microsoft Defender for Endpoint baseline settings | You can set the recommended configuration for ATP by using the Defender for Endpoint security baseline. |
Restrict USB drives and other peripherals
To prevent malware infections or data loss, an organization may restrict USB drives and other peripherals. The following table describes the ways Microsoft Defender for Endpoint can help prevent installation and usage of USB drives and other peripherals.
| Control | Description |
|---|---|
| Allow installation and usage of USB drives and other peripherals | Allow users to install only the USB drives and other peripherals included on a list of authorized devices or device types |
| Prevent installation and usage of USB drives and other peripherals | Prevent users from installing USB drives and other peripherals included on a list of unauthorized devices and device types |
All of the above controls can be set through the Intune Administrative Templates. The relevant policies are located here in the Intune Administrator Templates:
Note
Using Intune, you can apply device configuration policies to Azure AD user and/or device groups.The above policies can also be set through the Device Installation CSP settings and the Device Installation GPOs.
Note
Always test and refine these settings with a pilot group of users and devices first before applying them in production.For more information about controlling USB devices, see the Microsoft Defender for Endpoint blog.
Allow installation and usage of USB drives and other peripherals
One way to approach allowing installation and usage of USB drives and other peripherals is to start by allowing everything. Afterwards, you can start reducing the allowable USB drivers and other peripherals.
Note
Because an unauthorized USB peripheral can have firmware that spoofs its USB properties, we recommend only allowing specifically approved USB peripherals and limiting the users who can access them.
- Enable Prevent installation of devices not described by other policy settings to all users.
- Enable Allow installation of devices using drivers that match these device setup classes for all device setup classes.
To enforce the policy for already installed devices, apply the prevent policies that have this setting.
When configuring the allow device installation policy, you must allow all parent attributes as well. You can view the parents of a device by opening Device Manager and view by connection.
In this example, the following classes needed to be added: HID, Keyboard, and {36fc9e60-c465-11cf-8056-444553540000}. See Microsoft-provided USB drivers for more information.
If you want to restrict to certain devices, remove the device setup class of the peripheral that you want to limit. Then add the device ID that you want to add. Device ID is based on the vendor ID and product ID values for a device. For information on device ID formats, see Standard USB Identifiers.
To find the device IDs, see Look up device ID.
For example:
- Remove class USBDevice from the Allow installation of devices using drivers that match these device setup.
- Add the device ID to allow in the Allow installation of device that match any of these device IDs.
Prevent installation and usage of USB drives and other peripherals
If you want to prevent the installation of a device class or certain devices, you can use the prevent device installation policies:
- Enable Prevent installation of devices that match any of these device IDs and add these devices to the list.
- Enable Prevent installation of devices using drivers that match these device setup classes.
Note
The prevent device installation policies take precedence over the allow device installation policies.
The Prevent installation of devices that match any of these device IDs policy allows you to specify a list of devices that Windows is prevented from installing.
To prevent installation of devices that match any of these device IDs:
- Look up device ID for devices that you want Windows to prevent from installing.
- Enable Prevent installation of devices that match any of these device IDs and add the vendor or product IDs to the list.
Look up device ID
You can use Device Manager to look up a device ID.
- Open Device Manager.
- Click View and select Devices by connection.
- From the tree, right-click the device and select Properties.
- In the dialog box for the selected device, click the Details tab.
- Click the Property drop-down list and select Hardware Ids.
- Right-click the top ID value and select Copy.
For information about Device ID formats, see Standard USB Identifiers.
For information on vendor IDs, see USB members.
The following is an example for looking up a device vendor ID or product ID (which is part of the device ID) using PowerShell:
The Prevent installation of devices using drivers that match these device setup classes policy allows you to specify device setup classes that Windows is prevented from installing.
To prevent installation of particular classes of devices:
- Find the GUID of the device setup class from System-Defined Device Setup Classes Available to Vendors.
- Enable Prevent installation of devices using drivers that match these device setup classes and add the class GUID to the list.
Block installation and usage of removable storage
Sign in to the Microsoft Azure portal.
Click Intune > Device configuration > Profiles > Create profile.
Use the following settings:
- Name: Type a name for the profile
- Description: Type a description
- Platform: Windows 10 and later
- Profile type: Device restrictions
Click Configure > General.
For Removable storage and USB connection (mobile only), choose Block. Removable storage includes USB drives, whereas USB connection (mobile only) excludes USB charging but includes other USB connections on mobile devices only.
Click OK to close General settings and Device restrictions.
Click Create to save the profile.
Allow installation and usage of specifically approved peripherals
Peripherals that are allowed to be installed can be specified by their hardware identity. For a list of common identifier structures, see Device Identifier Formats. Test the configuration prior to rolling it out to ensure it blocks and allows the devices expected. Ideally test various instances of the hardware. For example, test multiple USB keys rather than only one.
For a SyncML example that allows installation of specific device IDs, see DeviceInstallation/AllowInstallationOfMatchingDeviceIDs CSP. To allow specific device classes, see DeviceInstallation/AllowInstallationOfMatchingDeviceSetupClasses CSP.Allowing installation of specific devices requires also enabling DeviceInstallation/PreventInstallationOfDevicesNotDescribedByOtherPolicySettings.
Prevent installation of specifically prohibited peripherals
Microsoft Defender for Endpoint blocks installation and usage of prohibited peripherals by using either of these options:
- Administrative Templates can block any device with a matching hardware ID or setup class.
- Device Installation CSP settings with a custom profile in Intune. You can prevent installation of specific device IDs or prevent specific device classes.
Allow installation and usage of specifically approved peripherals with matching device instance IDs
Peripherals that are allowed to be installed can be specified by their device instance IDs. Test the configuration prior to rolling it out to ensure it allows the devices expected. Ideally test various instances of the hardware. For example, test multiple USB keys rather than only one.
You can allow installation and usage of approved peripherals with matching device instance IDs by configuring DeviceInstallation/AllowInstallationOfMatchingDeviceInstanceIDs policy setting.
Prevent installation and usage of specifically prohibited peripherals with matching device instance IDs
Peripherals that are prohibited to be installed can be specified by their device instance IDs. Test the configuration prior to rolling it out to ensure it allows the devices expected. Ideally test various instances of the hardware. For example, test multiple USB keys rather than only one.
You can prevent installation of the prohibited peripherals with matching device instance IDs by configuring DeviceInstallation/PreventInstallationOfMatchingDeviceInstanceIDs policy setting.
Limit services that use Bluetooth
Using Intune, you can limit the services that can use Bluetooth through the 'Bluetooth allowed services'. The default state of 'Bluetooth allowed services' settings means everything is allowed. As soon as a service is added, that becomes the allowed list. If the customer adds the Keyboards and Mice values, and doesn’t add the file transfer GUIDs, file transfer should be blocked.
Use Microsoft Defender for Endpoint baseline settings
The Microsoft Defender for Endpoint baseline settings represent the recommended configuration for ATP. Configuration settings for baseline are located in the edit profile page of the configuration settings.
Prevent threats from removable storage
Removable storage devices can introduce additional security risk to your organization. Microsoft Defender for Endpoint can help identify and block malicious files on removable storage devices.
Bluetooth Device Control Windows 10 Disable
Microsoft Defender for Endpoint can also prevent USB peripherals from being used on devices to help prevent external threats. It does this by using the properties reported by USB peripherals to determine whether or not they can be installed and used on the device.
Note that if you block USB devices or any other device classes using the device installation policies, connected devices, such as phones, can still charge.
Note
Always test and refine these settings with a pilot group of users and devices first before widely distributing to your organization.
The following table describes the ways Microsoft Defender for Endpoint can help prevent threats from removable storage.
For more information about controlling USB devices, see the Microsoft Defender for Endpoint blog.
| Control | Description |
|---|---|
| Enable Microsoft Defender Antivirus Scanning | Enable Microsoft Defender Antivirus scanning for real-time protection or scheduled scans. |
| Block untrusted and unsigned processes on USB peripherals | Block USB files that are unsigned or untrusted. |
| Protect against Direct Memory Access (DMA) attacks | Configure settings to protect against DMA attacks. |
Note
Because an unauthorized USB peripheral can have firmware that spoofs its USB properties, we recommend only allowing specifically approved USB peripherals and limiting the users who can access them.
Enable Microsoft Defender Antivirus Scanning
Protecting authorized removable storage with Microsoft Defender Antivirus requires enabling real-time protection or scheduling scans and configuring removable drives for scans.
- If real-time protection is enabled, files are scanned before they are accessed and executed. The scanning scope includes all files, including those on mounted removable devices such as USB drives. You can optionally run a PowerShell script to perform a custom scan of a USB drive after it is mounted, so that Microsoft Defender Antivirus starts scanning all files on a removable device once the removable device is attached. However, we recommend enabling real-time protection for improved scanning performance, especially for large storage devices.
- If scheduled scans are used, then you need to disable the DisableRemovableDriveScanning setting (enabled by default) to scan the removable device during a full scan. Removable devices are scanned during a quick or custom scan regardless of the DisableRemovableDriveScanning setting.
Note
We recommend enabling real-time monitoring for scanning. In Intune, you can enable real-time monitoring for Windows 10 in Device Restrictions > Configure > Microsoft Defender Antivirus > Real-time monitoring.
Block untrusted and unsigned processes on USB peripherals
End-users might plug in removable devices that are infected with malware.To prevent infections, a company can block USB files that are unsigned or untrusted.Alternatively, companies can leverage the audit feature of attack surface reduction rules to monitor the activity of untrusted and unsigned processes that execute on a USB peripheral.This can be done by setting Untrusted and unsigned processes that run from USB to either Block or Audit only, respectively.With this rule, admins can prevent or audit unsigned or untrusted executable files from running from USB removable drives, including SD cards.Affected file types include executable files (such as .exe, .dll, or .scr) and script files such as a PowerShell (.ps), VisualBasic (.vbs), or JavaScript (.js) files.
These settings require enabling real-time protection.
Sign in to the Microsoft Azure portal.
Click Intune > Device configuration > Profiles > Create profile.
Use the following settings:
- Name: Type a name for the profile
- Description: Type a description
- Platform: Windows 10 or later
- Profile type: Endpoint protection
Click Configure > Windows Defender Exploit Guard > Attack Surface Reduction.
For Unsigned and untrusted processes that run from USB, choose Block.
Click OK to close Attack Surface Reduction, Windows Defender Exploit Guard, and Endpoint protection.
Click Create to save the profile.
Protect against Direct Memory Access (DMA) attacks
DMA attacks can lead to disclosure of sensitive information residing on a PC, or even injection of malware that allows attackers to bypass the lock screen or control PCs remotely. The following settings help to prevent DMA attacks:
Beginning with Windows 10 version 1803, Microsoft introduced Kernel DMA Protection for Thunderbolt to provide native protection against DMA attacks via Thunderbolt ports. Kernel DMA Protection for Thunderbolt is enabled by system manufacturers and cannot be turned on or off by users.
Beginning with Windows 10 version 1809, you can adjust the level of Kernel DMA Protection by configuring the DMA Guard CSP. This is an additional control for peripherals that don't support device memory isolation (also known as DMA-remapping). Memory isolation allows the OS to leverage the I/O Memory Management Unit (IOMMU) of a device to block unallowed I/O, or memory access, by the peripheral (memory sandboxing). In other words, the OS assigns a certain memory range to the peripheral. If the peripheral attempts to read/write to memory outside of the assigned range, the OS blocks it.
Peripherals that support device memory isolation can always connect. Peripherals that don't can be blocked, allowed, or allowed only after the user signs in (default).
On Windows 10 systems that do not support Kernel DMA Protection, you can:
Create customized alerts and response actions
You can create custom alerts and response actions with the WDATP Connector and the custom detection rules:
Wdatp Connector response Actions:
Investigate: Initiate investigations, collect investigation package, and isolate a machine.
Threat Scanning on USB devices.
Restrict execution of all applications on the machine except a predefined setMDATP connector is one of over 200 pre-defined connectors including Outlook, Teams, Slack, etc. Custom connectors can be built.
Custom Detection Rules Response Action:Both machine and file level actions can be applied.
For information on device control related advance hunting events and examples on how to create custom alerts, see Advanced hunting updates: USB events, machine-level actions, and schema changes.
Respond to threats
You can create custom alerts and automatic response actions with the Microsoft Defender for Endpoint Custom Detection Rules. Response actions within the custom detection cover both machine and file level actions. You can also create alerts and automatic response actions using PowerApps and Flow with the Microsoft Defender for Endpoint connector. The connector supports actions for investigation, threat scanning, and restricting running applications. It is one of over 200 pre-defined connectors including Outlook, Teams, Slack, and more. Custom connectors can also be built. See Connectors to learn more about connectors.
Where Is Bluetooth Device Control Windows 10
For example, using either approach, you can automatically have the Microsoft Defender Antivirus run when a USB device is mounted onto a machine.
Related topics
-->Note Looking for drivers for your Bluetooth audio device? See Fix connections to Bluetooth audio devices and wireless displays.
Note For information about Bluetooth support prior to Windows 10, see Bluetooth Support in Previous Windows Versions.
Which Bluetooth versions does Windows 10 support?
Windows 10 for desktop editions (Home, Pro, Enterprise, and Education) and Windows 10 Mobile support the following Bluetooth versions:
- Version 1.1
- Version 2.0
- Version 2.0 with EDR
- Version 2.1
- Version 2.1 with EDR
- Version 4.0
- Version 4.1
- Version 5.0
Windows Server 2016 does not support Bluetooth.
Which Bluetooth profiles have in-box support in Windows 10?
Windows 10 for desktop editions in-box Bluetooth profiles:
Windows 10 (Version 1803) supports Bluetooth version 5.0 and the following Bluetooth user profiles:
- Advanced Audio Distribution Profile (A2DP 1.2)
- Audio/Video Control Transport Protocol Target (AVCTP 1.4)
- Audio/Video Distribution Transport Protocol (AVDTP 1.2)
- Audio/Video Remote Control Profile (AVRCP 1.6.1)
- Battery Service over GATT Profile (1.0)
- Bluetooth LE Generic Attribute (GATT) Client
- Bluetooth LE Generic Attribute (GATT) Server
- Bluetooth Network Encapsulation Protocol (BNEP 1.0)
- Device ID Profile (DID 1.3)
- Device Information Service over GATT Profile (DIS 1.1)
- Dial-up Networking Profile (DUN 1.1)
- Generic Access Profile (GAP)
- Generic Audio/Video Distribution Profile (GAVDP 1.2)
- Hands-Free Profile (HFP 1.6)
- Hardcopy Cable Replacement Profile (HCRP 1.2)
- HID over GATT Profile (HOGP 1.0)
- Human Interface Device (HID 1.1)
- Human Interface Device Service (HIDS)
- Interoperability (IOP)
- Logical Link Control and Adaptation Protocol (L2CAP)
- Object Push Profile (OPP 1.1)
- Personal Area Networking User Profile (PANU 1.0)
- RFCOMM (1.1 with TS 07.10)
- Scan Parameters Profile Client over GATT Profile (ScPP 2.1)
- Security Manager Protocol (SMP)
- Serial Port Profile (SPP 1.2)
- Service Discovery Protocol (SDP)
Windows 10 Mobile in-box Bluetooth profiles:
- Advanced Audio Distribution Profile (A2DP 1.2)
- Audio/Video Remote Control Profile (AVRCP 1.3)
- Bluetooth LE Generic Attribute (GATT) Client
- Device ID Profile (DID 1.3)
- Hands-Free Profile (HFP 1.6)
- HID over GATT Profile (HOGP 1.0)
- Human Interface Device (HID 1.1)
- Message Access Profile (1.1)
- Object Push Profile (OPP 1.1)
- Personal Area Network Access Point (PAN NAP 1.0)
- Phone Book Access Profile (PBAP 1.1)
- Serial Port Profile (SPP 1.2)
Windows 10 for desktop editions in-box Bluetooth profiles:
Control Panel Bluetooth Device Windows 10
| Profile | Description |
|---|---|
GATT | Bluetooth LE Generic Attribute (GATT) Client |
A2DP 1.2 | Advanced Audio Distribution Profile |
AVRCP 1.3 | Audio/Video Remote Control Profile |
DI 1.3 | Device ID Profile |
DUN 1.1 | Dial-Up Networking |
HCRP 1.0 | Hardcopy Cable Replacement Profile |
HFP 1.5 | Hands-Free Profile |
HID 1.1 | Human Interface Device |
HOGP 1.0 | HID over GATT Profile |
OPP 1.1 | Object Push Profile |
PANU 1.0 | Personal Area Network User |
SPP 1.2 | Serial Port Profile |
Windows 10 Mobile in-box Bluetooth profiles:
| Profile | Description |
|---|---|
GATT | Bluetooth LE Generic Attribute (GATT) Client |
A2DP 1.2 | Advanced Audio Distribution Profile |
AVRCP 1.3 | Audio/Video Remote Control Profile |
DI 1.3 | Device ID Profile |
HFP 1.6 | Hands-Free Profile |
HID 1.1 | Human Interface Device |
HOGP 1.0 | HID over GATT Profile |
MAP 1.1 | Message Access Profile |
OPP 1.1 | Object Push Profile |
PAN NAP 1.0 | Personal Area Network Access Point |
PBAP 1.1 | Phone Book Access Profile |
SPP 1.2 | Serial Port Profile |
New features and recommendations for Windows 10 and later
Reinstall Bluetooth On This Computer
To learn more about the new features and hardware developer recommendations for the different versions of Windows 10, see Bluetooth in the Hardware component guidelines section.
Related topics