Support for Windows 8.1 will end on January 10, 2023
Thank you for your loyalty. We want to help you prepare and recommend you move to a Windows 11 PC to stay supported and secure.
Summary
This update improves Bluetooth driver diagnosis by exposing more information in the Bluetooth driver.
More Information
Important Do not install a language pack after you install this update. If you do, the language-specific changes in the update will not be applied, and you will have to reinstall the update. For more information, see Add language packs to Windows.
Method 1: Windows Update
This update is provided as an Optional update on Windows Update. For more information on how to run Windows Update, see How to get an update through Windows Update.
Method 2: Microsoft Download Center
The following files are available for download from the Microsoft Download Center: The following updates are available for download from the Microsoft Download Center:
For more information about how to download Microsoft support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help prevent any unauthorized changes to the file.
How to capture and analyze Bluetooth ETW traces
This section describes how to capture and analyze Bluetooth traces for the following drivers:
-
bthport
-
hidbth
-
btha2dp
The size of the Event Tracing for Windows (ETW) logs and the parsed output file are typically quite large, especially for bthport and btha2dp. Although complete traces are necessary to analyze the scenario in detail, for specific drivers, you can enable only those drivers.
How to capture Bluetooth ETW traces
To capture Bluetooth event traces without installing any additional software after a restart, follow these steps:
-
Open an elevated Command Prompt window. For example, right-click Start, and then click Command Prompt (Admin).
-
Set up the scenario of interest.
-
Start a capture session by pasting the following sequence of commands into the Command Prompt window.
Note Press Enter after each command.
mkdir %USERPROFILE%\desktop\Bluetooth_Traces logman create trace -n BthTrace -o %USERPROFILE%\desktop\Bluetooth_Traces\bth_ETW_trace.etl -nb 128 640 -bs 128 logman update trace -n BthTrace -p Microsoft-Windows-BTH-BTHPORT @REM -- these are traces for bthhid -- logman update trace -n BthTrace -p "{5794AE18-A6E8-4348-A3FB-0EB1C0AD14B0}" @REM -- these are traces for btha2dp -- logman update trace -n BthTrace -p "{DDB6DA39-08A7-4579-8D0C-68011146E205}" logman start -n BthTrace -
Perform the action that you want to capture. Keep the Command Prompt window open.
-
Stop the capture session when you are finished by pasting the following sequence of commands into the Command Prompt window.
Note Press Enter after each command.logman stop -n BthTrace logman delete -n BthTrace
How to parse Bluetooth ETW traces
Bluetooth events are logged in the %USERPROFILE%\desktop\Bluetooth_Traces\bth_ETW_trace.etl file. The events can be parsed by using the Tracerpt.exe utility that's installed with Windows.
Run the following command:
tracerpt bth_ETW_trace.etl –o bth_ETW_report.xml
This command generates the full XML report for the ETW events that have been logged. The events resemble those in the following examples.
HidBth events are identified with the {5794ae18-a6e8-4348-a3fb-0eb1c0ad14b0} provider GUID, and BthA2DP events are identified with the {DDB6DA39-08A7-4579-8D0C-68011146E205} provider GUID. The events can be better decoded by using event information, as in the following example:
The event information for BthHid resembles the following:
The event information for BthA2DP resembles the following:
References
Learn about the terminology that Microsoft uses to describe software updates.
