Microsoft Bluetooth A2dp Source not working properly (Code 52)

Recently, some Windows 10 users with Bluetooth devices have been experiencing some problems. The issue comes up with an error that says-

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52). 

In this post, we are going to show you how to get this error under control and out of your life.

Microsoft Bluetooth A2dp Source not working properly (Code 52)

The key to fixing getting rid of this error is to sign the Bluetooth A2DP file with the built-in System File Checker, that’s it. Apart from that, there are other generic suggestions as well:

  1. Run System File Checker
  2. Run Hardware and Devices Troubleshooter
  3. Revert the system or run System Restore.

In the Windows 10 search box, type Command Prompt or CMD. When the search results show up, right-click on the Command Prompt option, and select Run as Administrator:

Now, type the following command into the CMD, then hit the Enter key: 

DISM.exe /Online /Cleanup-image /Restorehealth

Once the DISM scan is complete you need to run the System File Checker, and that’s easy by executing the following command:

sfc /scannow

While the scan is doing its thing, please do not close the CMD until the process is completed.

Restart your computer.

This should help – but if it doesn’t, try these suggestions:

Hope something here helps you.

You may also like...