Windows 10: Window Crash DCOM 10016

i just upgrade from win 11 23h1 to 23h3 and this 3 days its always crashing when on use The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID S-1-5-19 from address LocalHost Using LRPC running in the applic

:)

 

Dcom error 10016

Hi Eric,

I am Sumit here to assist you with this question.

10016 is present on all computers and not related to computer crashing.

DCOM event ID 10016 is logged in Windows

https://docs.microsoft.com/en-us/troubleshoot/w...

These events can be safely ignored because they don't adversely affect functionality and are by design. It's the recommend action for these events.

When you say crash, is it a random reboot or a Blue screen of death?

 

Windows 10016 DCOM Error & Freeze

Hi Haybun,

Thank you for posting your question in the Microsoft Community Forums.

I appreciate the efforts taken by you in troubleshooting this issue.

As you are facing the issue with granting Local Activation permission for the COM Server application with CLSID, suggest you to refer to the reply provided by ‘Lizette
Ags’ from this thread to check if that makes any difference.

Important: The section, method, or task provided on the link contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that
you follow the steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, refer to the following Microsoft Knowledge
Base article: How to back up and restore the registry in Windows.

Reference.

‘DCOM event ID 10016 is logged in Windows’

Awaiting your reply.

Regards,

Srimadhwa B

Microsoft Community-Moderator

 

DCOM error 10016

Hello one of your suggestions seems to have worked for a bit then i got a bluescreen think it was watchdog clock timeout the BSOD was labled as a dcom error 10016

then the problems started again