If you pair the device, you can look in Device Manager for the “Bluetooth class of device” property. The good news is this lets you inspect the SDP record the bad news is that the minor class of device is not part of the SDP record.) (As an aside: Microsoft has a Bluetooth Inquiry Record Verifier tool which ships as part of the Windows Driver Kit.

In Bluetooth-speak, the kind of device is the “class of device.” This is defined in the Bluetooth Assigned Numbers for Baseband. But how does the driver know? It depends on the driver. I previously blogged about how an audio device driver can tell Windows what kind of audio device it is. It was very handy to be able to collect audio logs and Code Integrity logs on Windows 7, but it turns out the Windows 7 version of Windows Performance Recorder has slightly different syntax requirements for WPRP files. Recently I was involved in a Windows 7 audio support issue that involved SHA-1 deprecation and Trusted Audio Drivers.

How to turn on HDCP or SCMS in an audio playback app.

I’ve blogged before about the Trusted Audio Drivers audio digital rights management feature:

So I have this audio problem on Windows 7….

I’ve blogged before about what to do if you have an audio problem on Windows 7:

Taking audio glitch traces on Windows 10: desktop edition.

Collecting audio logs the old-fashioned way.

Report problems, with logs, and suggest features, with the Feedback Hub.

I’ve blogged before about how to collect audio logs using Windows Performance Recorder profiles (WPRP files), among other things:

Usbaudio sys windows 10