Windows 10: Continuing DCOM event viewer error

I recently started getting this error in event viewer. There are a number of threads across the web about it, but none of them has presented the solution. The error is related to Runtimebroker.exe. Any new ideas?

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\SYSTEM SID (S-1-5-18) 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.

:)

 

WerFault.exe in win 10

This application has started to spike my cpu.

I can't disable it in services.

It also starts and terminates itself every few seconds and this runs continuously.

event viewer lists an error message as below.

The server App.AppXck5aaxyarfx8gxrgfk6pvakmmxeqvepc.mca did not register with DCOM within the required timeout.

Please help if you can

 

Windows 10 - Event ID 10016 causing system crash

Thank you for the information. The error that was on the even viewer occurs when there are certain processes that do not have permission on the DCOM components mentioned in the event logs. We've found a support article that has a resolution on how to resolve
the message that popped up on the event viewer. Refer to this article and see
if the steps provided will work for you.

Keep us in the loop with the results.

 

Persistent Event Viewer Error - Windows 10 Forums

See if anything in that thread helps. I'm only getting that error once during shutdown and I'm just ignoring it.

 

cyberrufus - thanks. interesting you find it's on shutdown - I was thinking same thing. Odd.

 

First implement the ideas that you have read dealing with granting full permission to both the CLSID and the APPID via the registry.

Now run dcomcnfg and go to Runtimebroker permissions. Click the SECURITY tab, then on EDIT in the top section - Launch and Activation Permissions. Add both LOCAL SERVICE and ADMINISTRATORS entries (if not already present) and check the "Local Activation" box for each.

Then EDIT in middle section - Access Permissions - and do the same. (If SYSTEM isn't in the list of entries, add it as well.)

In section three - Configuration Permissions - verify that the ADMINISTRATOR account has full control.

Report results here. If that doesn't succeed, consider simply ignoring the error as a less frustrating alternative. *Smile