Windows 10: Bluetooth malfunction & dreadful 10016 DCOM error

I have a new Hades Canyon NUC NUC8i7HVK with a fresh Win 10 Pro installation. The latest Windows updates installed as well as the latest Intel bluetooth drivers (Intel 8265 that came with the NUC).


I've been experiencing a very annyoing bluetooth issue. Namely, I'm able to pair with any bluetooth device (headphones, speaker) and use it UNTIL I restart the computer. Then 90% of the times fails to connect no matter what I do. The only solution is to remove the previously paired device and pair again.


I looked at the Event Viewer and found some errors in the System log.

1. The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

2. The mutual authentication between the local Bluetooth adapter and a device with Bluetooth adapter address (40:ef:4c:32:63:0d) failed.


These 2 always appear together, at the time I try to connect to a device, so my guess is that they are connected. Reading that DCOM errors are not really errors and can be safely ignored, drives me crazy.

I googled a lot to find a solution. Came across a number of variations of this "solution":

https://shauncassells.wordpress.com/2015/09/28/windows-10-event-10016-fix-the-application-specific-permission-settings-do-not-grant-local-activation-permission-for-the-com-server-application-with-clsid-d63b10c5-bb46-4990-a94f-e40b9d520160-and-a/


But I only achieved a total bluetooth blackout - I couldn't even pair again. Fortunately I'd created a system restore point before doing registry shenanigans and I'm back at square one.


Any help is appreciated.

:)

 

DCOM error 10016 on shutdown

Is this procedure supposed to resolve the DCOM 10016 errors or the Service Control Manager 7031 errors? The recent MS updates have apparently solved the DCOM 10016 errors I was getting for "Runtime Broker." Now they only happen for Cortana.

It is actually the SCM 7031 errors that I would like to eliminate now.

 

DCOM error 10016 on shutdown

I had been getting the DCOM error 10016 on shutdown immediately followed by 4 SCM 7031 errors for quite some time until the MS August 10 updates were installed. I am still getting the SCM 7031 errors but the DCOM 10016 errors have stopped. Has anyone
else had this experience? I am running Win 10 Version 1511 on a desktop.

 

DCOM error 10016


Well, I am bumfuzzled! I went in to my Event Viewer to take a look before applying the process referenced by Qwinn to fix the 10016 Dcom errors. There were no new ones, so I rebooted several times and still no 10016 Dcom errors! I don't know why, but I'm glad they are gone. Thanks to Qwinn and I will save your reference for future use, if needed.