Windows 10: Dcom error

Over several generations of Windows 10 (now 2004) the Pro 64-bit version throws a DCom error that the Home version (shown on top) does not, when clicking on "Com+ Applications. And the "running processes" entry is missing in the Pro version.

This doesn't appear to be causing issues, but is a puzzlement. Clues?




:)

 

DCom persistent error


Remote proxy factory 32 class writes a Dcom Event Viewer error when EDGE, with multi-tabs, is closed...saying that it doesn't have activation permission for NJNxxx\My Account. It has.

In this HOME version, there are two registry entries for the RPF32 class. In each, Desktop-NJNxxx\Users; Desktop-NJNxxx\My Account; Desktop-NJNxxx\Administrators and SYSTEM have full control.

The same entries appear in DComcfg, along with Local Service, which has been given local launch permission for both RPF32class entries.

So, the permissions procedure has been followed, yet the error persists. Why?

(This box has HOME Win10. Another, with PRO, uses default Dcom settings and doesn't reference 'Desktop-NJNxxx. ' It instead lists the user name, and it never throws the Dcom error. That's likely not relevant - just a naming convention difference.)

 

DCOM Errors

Installed 1803 17133.1 works OK but masses of DCOM errors relating to Windows Defender Security Centre. Anyone else having this problem. No DCOM errors at all in 1709.

 

I solved the DCOM Error.

I have managed to fix it on my laptop.
After the Win10 1803 update, these are the only 2 DCOM errors I have found in my comp.
-Windows.SecurityCenter.WscBrokerManager
-Windows.SecurityCenter.WscDataProtection

1. Open Regedit.
2. CTRL + F "Windows.SecurityCenter.WscDataProtection", this will automactically lead you to Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCen ter.WscDataProtection.
You may do the same to find the location for Windows.SecurityCenter.WscBrokerManager.

3. Perform the usual steps to grant DCOM permissions.
-> Right click the key >> permissions
-> Click advanced
-> At the top change the Owner to COMPUTERNAME\Administrators
-> Click OK
-> Check full control for user SID to grant full controls for the user.