Windows 10: 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.)

:)

 

Update for Windows 10 for x64-based Systems (KB3081704) - Error 0x80070643

I tried the same install and my errors were DCOM/COM errors

I've been seeing DCOM permissions errors since the bad update that broke the store and its apps and broke the start menu

it also corrupted my user profile which I had to recreate

I still see about 50 DCOM permission errors per day

I think this problem maybe be DCOM permissions problems

are there any DCOM troubleshooters?

fixing DCOM permissions can be tricky, you need to also modify permissions in the registry to allow editing of the DCOM

not ready to do that yet.

Microsoft you need to fix this.

rob

 

Persistent PC freeze and crash with Dcom 10016 being the problem

Hi there.

Thanks for the reply, you are right.

I was trying to take ownership of the keys and managed once I changed from "trusted installer" to my ID, the 2 main culprits were

1.Runtime Broker

2.ShellServiceHost

Both of which were throwing up different CLSID and each time managed to change it the pc would freeze. Almost every 2 minutes, I had to boot into safe mode, and even command a few times.

But it's been two weeks since I changed all my registers and truncated a few entries and now not one freeze.

I'm shocked that MS would let this problem go on for so many people.

Thanks again for the info, take care.

Best Regards

Shayne