Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

ddelo · 02 Apr 2017

lx07 said:

When I said one directory level "lower" I may have meant "higher".

Closer to the root anyway.

I got that, from reading the script... but thanks for clarifying! :)

ddelo · 02 Apr 2017

fdegrove said:

Hi,

No such issues on 15063 when set to OFF. Service is set to start automatically (delayed start) by default.

At times it seems problems like these are "machine dependent" which makes computing a bit less uh.... scientific. LOL.

Cheers,

I wouldn't know about 15063, I'm in 14393.969 and I had set it to OFF to avoid the nagging toast notification "Your account settings are out-of-date", sometime like 8 months ago!
Apparently since then MS fixed the problem with the notification, but I didn't know and had left the setting to OFF. That's why since last August, I had something more than1800 of these 7023 errors.... since the setting affected the default Automatic (delayed start) of the Service, which was failing to start and was producing the error. And not only that, but I couldn't even start it manually...
Since changed it back to ON, the Service starts as it supposed to and NO errors!!!

I guess it's the definition of the upgrade: "Old bugs out...New bugs in" :)

fdegrove · 02 Apr 2017

Hi,

I guess it's the definition of the upgrade: "Old bugs out...New bugs in"

Yep. Except this time there are far less bugs then ever before in W10 it seems.

That said, I do not have an extremely complex set up, just a decent pc or two.

Cheers,

RoopeSeta · 02 Apr 2017

ddelo said:

And to close another issue, since I was also battling with this one too....
Errors 7023 and 10010

The 7023 error is produced, because the Connected Devices Platform Service fails to start, Automatically by default, in version 1607 and above (in 1511 was set to "Disabled")

To resolve that, navigate to: Settings > Privacy > General
Make sure you have the “Let apps on my other devices open apps and continue experiences on this device” to ON and either get into Services and start "Connected Devices Platform Service" which most likely is not running or reboot.

This will take care of all the 7023 errors and consequently the 10010 produced from this one.

Thank you! After doing this I no longer get 7023 or 10010 errors.

ddelo · 02 Apr 2017

You're very welcome! :)

x7007 · 02 Apr 2017

RoopeSeta said:

Thank you! After doing this I no longer get 7023 or 10010 errors.

To put "Connected Devices Platform Service" on Automatic in Services.msc ? or just Started with Manual Triggered ?

ddelo · 02 Apr 2017

x7007 said:

To put "Connected Devices Platform Service" on Automatic in Services.msc ? or just Started with Manual Triggered ?

If you're on version 1607 it should be "Automatic (Delayed Start)"

T0mmy1977 · 04 Apr 2017

Event ID 10016 DCOM

I follow the instructions below, and after that I do not get a single error/warning in the System event log.

You will need to take ownership then set rights against these keys. Make the Administrators the owner of these keys. Give Administrators and System Full Control.

The keys are:

HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}
HKEY_CLASSES_ROOT\AppID\{F72671A9-012C-4725-9D2F-2A4D32D65169}
HKEY_CLASSES_ROOT\AppID\{4839DDB7-58C2-48F5-8283-E1D1807D0D7D}

HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}
HKEY_CLASSES_ROOT\CLSID\{8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
HKEY_CLASSES_ROOT\CLSID\{6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}

Change DCOM Permissions

Open DCOMCNFG as an Administrator

Navigate to Component Services\Computers\My Computer\DCOM Config

Find these Applications

RunTimeBroker
F72671A9-012C-4725-9D2F-2A4D32D65169 (Located near the bottom of the list in 'Detailed View'.
ShellServiceHost

Right Click, Properties, Security Tab, Launch and Activation Permissions, Edit

Add these accounts and give them full control.

Administrators
All Application Packages
Interactive
Local_Service
Network
System

While changing permissions I was prompted several times to remove bad account references. I did this as the computer knows which accounts have been removed. Give your computer a reboot and away you can go.

Joanne · 02 May 2017

Hello...

I have decided to try to fix this error, as it is the only one left in my Event Viewer. I have already copied @lx07 's PowerShell script and replaced the Registry keys according to the error I am getting:

The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {9BA05972-F6A8-11CF-A442-00A0C90A8F39} and APPID {9BA05972-F6A8-11CF-A442-00A0C90A8F39} to the user MYCOMPUTER\Me SID (S-1-5-21-3364268583-2186901574-852866347-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.

What confuses me, and I am asking for your help, is this:

- Which Application in the Component Services / DCOM Config corresponds to the Application ID of my error? - And how do I find this?

Thank you! As soon as someone will reply to me, I will apply the fix.

Windows 10 Pro, 1703 (build 15063.250) 64 bit

PS: I have already looked at Runtime Broker and Immersive Shell, in my DCOM Config, but those Applications have different IDs. So which one should I "touch"?

EDIT: Okay, so after searching my Registry using that ID I found that it has to do with this:

Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM-12.png

I will start the procedure now and report back.

Joanne · 02 May 2017

Okay, it seems that it works: I have rebooted twice and powered on, after completely shutting down, three times and no errors at all in my Event Viewer :)

One last question, please, and apologies if it has been already answered. This is how I have set it:

Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM-ok.png

The highlighted user is the one I have added, after checking the name.

- Are the permissions I have set, shown in the screenshot, appropriate / enough? Should I set the two "Remote..." permissions, as well?

Thank you!
I am glad I resolved this, no matter how temporary it will be.