How do i get rid of CLSID error?

[theo.esk]

Hi All

Every computer i've have had to repair with windows 10 on them, those includes my own have this little irritating and frustrating error in the computer management application with a D-Com process:

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 DESKTOP-G0UDV4Q\Live SID (S-1-5-21-1860564475-244970800-1680596971-1001) 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.

more details:

- System

- Provider

[ Name] Microsoft-Windows-DistributedCOM
[ Guid] {1B562E86-B7AA-4131-BADC-B6F3A001407E}
[ EventSourceName] DCOM

- EventID 10016

[ Qualifiers] 0

Version 0

Level 2

Task 0

Opcode 0

Keywords 0x8080000000000000

- TimeCreated

[ SystemTime] 2018-03-23T21:51:41.292079800Z

EventRecordID 1183

Correlation

- Execution

[ ProcessID] 384
[ ThreadID] 3484

Channel System

Computer DESKTOP-G0UDV4Q

- Security

[ UserID] S-1-5-21-1860564475-244970800-1680596971-1001


- EventData

param1 application-specific
param2 Local
param3 Activation
param4 {D63B10C5-BB46-4990-A94F-E40B9D520160}
param5 {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
param6 DESKTOP-G0UDV4Q
param7 Live
param8 S-1-5-21-1860564475-244970800-1680596971-1001
param9 LocalHost (Using LRPC)
param10 Unavailable
param11 Unavailable

i'm terribly sorry for this abnormal long post this time. i always figure that the more details you can divulge the better--- right ?

Questions:
1: How to get rid of it?
2: how to solve it?
3: Why is it even faulty all the time?
4: what is it good for?

Cheers!

 

[johnbl]

you can give the app proper rights to access the loopback driver

https://social.technet.microsoft.com/Forums/en-US/10ee51dc-c73d-4033-bfc2-5fa9ee5991a2/windows-10-distributed-com-runtime-broker-failing?forum=win10itprogeneral

it means that the app wants permission to talk to its own machine using a network connection.
localhost = 127.0.0.0 and has special meaning for old network communications. (it means the local manchine) It would allow you to open one window and have a app make a network connection to another window on the same machine.

for the most part everyone will get this error log and it will not have any real effect since the app can connect to the machines assigned ip address.

 

[theo.esk]

you can give the app proper rights to access the loopback driver

https://social.technet.microsoft.com/Forums/en-US/10ee51dc-c73d-4033-bfc2-5fa9ee5991a2/windows-10-distributed-com-runtime-broker-failing?forum=win10itprogeneral

it means that the app wants permission to talk to its own machine using a network connection.
localhost = 127.0.0.0 and has special meaning for old network communications. (it means the local manchine) It would allow you to open one window and have a app make a network connection to another window on the same machine.

for the most part everyone will get this error log and it will not have any real effect since the app can connect to the machines assigned ip address.

Thank you for the quick response. the link you've posted, a is rather uhm confusing and a, quite frankly, frustrating guide. because, why would all that be necessary ? ...
when you do a clean install of windows 10 it should be that, that particular error should not be present. it shouldn't be at all, because with a clean install everything is reset and wiped, no personal apps or what ever personal setting is reset to default Windows 10. RIGHT ? -- or am i missing something here?

for the most part everyone will get this error log and it will not have any real effect since the app can connect to the machines assigned ip address.

then why would this be an error?... as far as i know you are absolutely right, but i find it odd that in such an advanced piece of OS as windows 10, this is a error that is just so hard to get rid of.

 

[johnbl]

it is an annoying log entry and there are dozens like it. even a clean install of windows will not fix the problem. It would be considered a minor bug since it does not actually break anything. Just makes a log enrty and annoys people like me. I used to clean these up and give them rights but the bug just comes back after some updates. I just ignore them now. to get it fixed you would have to look up the app id, find out who wrote it and get them to fix the setup.
(I assume it is a Microsoft app but I did not search for it to figure it out) The writer of the app may not even know that it causes a windows log entry. (or they might not care)

you can give the app proper rights to access the loopback driver

https://social.technet.microsoft.com/Forums/en-US/10ee51dc-c73d-4033-bfc2-5fa9ee5991a2/windows-10-distributed-com-runtime-broker-failing?forum=win10itprogeneral

it means that the app wants permission to talk to its own machine using a network connection.
localhost = 127.0.0.0 and has special meaning for old network communications. (it means the local manchine) It would allow you to open one window and have a app make a network connection to another window on the same machine.

for the most part everyone will get this error log and it will not have any real effect since the app can connect to the machines assigned ip address.

Thank you for the quick response. the link you've posted, a is rather uhm confusing and a, quite frankly, frustrating guide. because, why would all that be necessary ? ...
when you do a clean install of windows 10 it should be that, that particular error should not be present. it shouldn't be at all, because with a clean install everything is reset and wiped, no personal apps or what ever personal setting is reset to default Windows 10. RIGHT ? -- or am i missing something here?

for the most part everyone will get this error log and it will not have any real effect since the app can connect to the machines assigned ip address.

then why would this be an error?... as far as i know you are absolutely right, but i find it odd that in such an advanced piece of OS as windows 10, this is a error that is just so hard to get rid of.