Windows 10: Persistent Event Viewer Error

I'm getting the following event viewer error every 15-30 minutes whenever a non-admin account is logged in:

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 XX\YY SID (S-1-5-21-1462133472-353174448-3584519177-1002) 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.

I've tracked the AppID down to RuntimeBroker. I've found a few posts mentioning a similar error for this application under windows 8, and suggesting changing the security settings as described. When I try to do this though, all the settings for RuntimeBroker are disabled, and cannot be customised. I've tried launch the admin tool as administrator, but it's still locked down.

Any ideas?

Kevin

:)

 

Windows Store Apps Stuck on "Working" Status

Did you installed all updates?

Make sure there is no pending update and then restart your PC.

If problem persist, open event viewer and see what event is logged associated with Windows Store error and post the error code.

 

Windows 10 - remote procedure call failed

Hi,

Is this error displayed even after you restart your PC?

The "Remote procedure call" error might be displayed when a service called upon by Windows is not responding. If you have already restarted the PC and yet see this error message, I would recommend you to boot the computer in Safe mode and check if the issue
persists. You can follow the steps suggested in this article to boot the computer in Safe mode:

http://windows.microsoft.com/en-us/windows-8/windows-startup-settings-safe-mode

If the issue persists in the Safe mode as well, then check the Event viewer for any reports which will help us determine which service is causing this issue. To check the Event Viewer logs, follow these steps:

1. Type "Event Viewer" in the search box in the task bar. This will bring up the Event Viewer tile, Click to open the event viewer.

2. In the left pane, expand out Windows Logs. Click on system logs and highlight the first event in the log and use your arrow keys to scroll down.

3. Most of your event will be Information. You may see Yellow Warnings or Red Errors. If you see any red error, you can double click on it to bring it up and copy the contents to a document.

 

Same here, except I'm running an Administrator account.

 

You guys could try this.

Remember to favorite the location of the edit in regedit so you know where to go if it needs changing.

 

Hi,

To solve the DCOM error follow the instructions given by Vaio 7 in this thread:

Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Worked for me on several installs.

Cheers, *Wink

 

Thanks, made the change, will monitor to see if the events go away!

 

kev - what results, and which change did you do?

 

With all the rushing about over christmas I never got round to following it up. Just looked now though, and I'm still getting the error in the logs. The solution I tried was the link from swarfega. This allowed me to change the permissions in the DCOM config for the class in question. I'm not sure why that hasn't done the trick, as I was expecting it to work. There are a whole bunch of these errors for different components when my wife's account is logged in. I'll have to have another look when I can find some time!

 

By the way, I THINK I'm getting the error message when I shut down as part of restart. Not when I start up again. It's an error in the shut-down process, I think. Wonder what that means.

 

Just checked, and mine are not related to a shutdown or restart, nor any sleep related events. I also noticed that I might have spoken too soon - my wife's account no longer gets the RuntimeBroker errors (though she does get others), it's the account "NT AUTHORITY\SYSTEM" that is still triggering them. So it looks like the linked solution does fix the problem (which is what you'd expect) but I need to do it for some more accounts and some more components. Now I know it fixes it though, it's worth going through and making the effort

 

kev and others - confirmed that I am getting the error messages when I shut down my Win 10, not when i start it. Weird.

 

Hi,

Could you post a screenshot of the error message in event viewer.
I suspect it's a number of services that try to restart at shutdown.

Cheers, *Wink

 

fdegrove - Hope you can open the attached - is a zip of a doc. Had to delete some of the screenshots to meet 10 Forum's limit.

Copy of DCOM errors - screenshots 1-2-16.zip

 

Hi,

That's the typical DCOM error that's been around for awhile.
Follow the instructions as described in a previous post here of mine and you should get rid of it forever.

Cheers, *Wink