Why Certain DCOM 10016 Events Don't Matter

Zardoc said:

Hi there Blazing speed,

Actually, I used this reg command

Code:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
"EnableDCOM"="N"

** To enable change Y **

If you read the whole thread (especially #1) you will notice that most often then none DCOM errors are not problematic. They are just denied permissions and are by design. You are just told in event viewer what happened.

Now if you are like those that EdTittel mentioned that ''simply won't settle for anything less than a clean Event Viewer on their PCs.'' then you can give permissions do the DCOM event by adding administrators or specific users.

To easily access DCOM and change permissions I use Power Run 1.3.

Double click the Dcom command and then go to (in your case PerAppRuntimeBroker)



Change permissions.
You can add users, administrators, all application packages, trusted installer even everyone (be careful of what type of permissions you give). Use at your own risk.

Many thanks for this, but I don't see PerAppRuntimeBroker!
PerAppRuntimeBroker does not exist at all in this Dcom Config.
Also the %SystemRoot%\System32\dcomcnfg.exe does not exist by default in the PowerRun v1.3, I had to add that but I'm not seeing any help from using this PowerRun app.

Unless I haven't done something else to make this PerAppRuntimeBroker appear in the Component Services then I don't know what else to do.

Do I have to separately add this using Windows Registry Editor Version 5.00 ?
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
"EnableDCOM"="N"

** To enable change Y **

Zardoc said:

Well, that seems odd.


It's possible that you might have to add the shortcut. Been using it for quite a while. But if you are in DCOM, it should be there.

Just paste in TXT and save as DCOM Stop.reg. Double click and it will add to registry and it will disable DCOM. To enable set N to Y

Many thanks. Unfortunately even after a fresh reinstall of Windows 10 Pro 6 days ago from official Microsoft website 1809 up to date with all windows updates. I do not see PerAppRuntimeBroker

As you can see I have already disabled DCOM. That was already set to N as I turned it off from the Component Services and this has been reflected in the registry.

But I still continue to receive error messages with The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DESKTOP-Q65KDGP\Rahul SID (S-1-5-21-823953900-1916975897-1171586770-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.

I don't know whether it is because PerAppRuntimeBroker is missing. But since it is a fresh re-installation from official website. I have not tempered with Windows in anyway. This PerAppRuntimeBroker simply does not exist. The only thing I see is 2x RuntimeBroker in Component services. But obviously I no longer have the guts to make changes there as it will malfunction SearchUI. Plus it is not proven to work anyway. This error in the Event Viewer will not go away under any circumstance.

f14tomcat said:

Not sure what version of Windows you are on, but in the newest, version 1903, 99.9% of these benign errors have been reclassified as Warnings by MS, and will appear in that section, not Errors. So, if you haven't upgraded yet, do so. Otherwise, just leave as is. You're ok.

The 10016 events are indeed now Warnings but I still get many related 10010 Errors. I just ignore all of them!