"PerAppRuntimeBroker" entries missing from registry.

Hi.
I have the usual "DistributedCOM" warning, event 10016 , CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} , APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} (this is PerAppRuntimeBroker application).
I noticed that this appears when I start a chromium browser (tried Edge, Brave, and Opera).
I tried the solutions I found here and I also did some tests of my own without any success.
After all this, I went to the registry to restore the application permissions to the original ones. I was surprised to see that the registry no longer had the key {15C20B67-12E7-4BB6-92BB-7AFF07997402} at HKEY_Local_Machine\Software\Classes\AppID (searching for APPID).
Then I went to component services to bring back the changes there. All options are grayed out and do not change.
My last chance (except the image backup/restore) , was to restore from a "restore point" I did before the tests. That didn't change anything either.
Is there any idea if the above are a problem and if so how do I fix them ?
Thanks.

bug locker said:

Hi.
I have the usual "DistributedCOM" warning, event 10016 , CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} , APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} (this is PerAppRuntimeBroker application).
I noticed that this appears when I start a chromium browser (tried Edge, Brave, and Opera).
I tried the solutions I found here and I also did some tests of my own without any success.
After all this, I went to the registry to restore the application permissions to the original ones. I was surprised to see that the registry no longer had the application (searching for CLSID and APPID) !
Then I went to component services to bring back the changes there. All options are grayed out and do not change !
My last chance (except the image backup/restore) , was to restore from a "restore point" I did before the tests. That didn't change anything either.
Is there any idea if the above are a problem and if so how do I fix them ?
Thanks.

https://docs.microsoft.com/en-us/tro...accessing-dcom

Cause

These 10016 events are recorded when Microsoft components try to access DCOM components without the required permissions. In this case, this behavior is expected and by design.

A coding pattern has been implemented where the code first tries to access the DCOM components with one set of parameters. If the first attempt is unsuccessful, it tries again with another set of parameters. The reason why it doesn't skip the first attempt is because there are scenarios where it can succeed. In those scenarios, it's preferable.

Workaround

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.

bug locker said:

Yes , after all this I'm ignoring it. The question is whether I damaged the registry.

Well hopefully you exported whatever registry keys you were intending to edit. If you didn't... you can always restore from a backup or attempt System Restore.

Posts about Event ID 10016 are so common, I actually recognized the CLSID numbers.

Good job.