Windows 10: Event ID 10016

Here is a previous thread about it:

Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Windows 10 Forums

I did run Regedit (as an admin) and did go to that entry in HKEY and did try to change permissions, but I get access denied.

What to do now? 100s (many 100s) of entries in Events with this error.


RON

:)

 

Kernel-Power (63) id:41 key words : (70368744177664),(2)

The Event ID 6008 is logged to the System event log when a shutdown operation is initiated automatically by a program. Meanwhile, the
DCOM event ID 10016 is related to certain processes not having permissions to the DCOM components that are mentioned in the event logs.
The specific communications that are blocked are determined to have no adverse functionality other than generating 10016 event logs. We highly recommend that you just ignore these errors because they don't adversely affect functionality. You may
refer to this support article for more information:
DCOM event ID 10016 is logged in Windows.

We hope the information we provided helps.

 

After Windows 10 Creator's update the screensaver no longer goes away when moving mouse or pressing a key

The event log you provided can be resolved by following the resolution provided in
this article that specifically addresses DCOM event ID 10016.

 

Hey RonNewYork,
What version of Win10 do you have ? (winkey+r > type in winver > click ok)
Do any of the event viewer errors/warnings reference the Cloud Filter Service (CldFlt) or Connected Devices Platform (CDPsvc) ?


If you haven't done this already ...
Clear All Event Logs in Event Viewer in Windows Windows 10 Performance Maintenance Tutorials
Note: When your getting a lot of event viewer errors, it make things easier to track down.

 

THANKS!!!! I'll do this after I get back home tomorrow (Wed) afternoon. MUCH APPRECIATED!

 

Apologies: This post was duplicated below.

 

I cleared the Event logs with:

Get-EventLog -LogName * | ForEach { Clear-EventLog $_.Log }

(in powershell)

As for my windows version:

Major Minor Build Revision
----- ----- ----- --------
10 0 15063 0

as far as I can tell there are no events referencing the services you mentioned (cloud**)

RON

 

It's been 3 hours since I cleared the event log and there are no new system event messages. Nice! (I hope!)

 

Hey RonNewYork,
After you clear the event viewer you need to restart PC to see if you get any errors/warnings.

 

just did and back to the usual Event ID 10016 errors.

 

Yep, I figured they would *Sad
If you are seeing any errors/warnings like 10010, 7000, 7023 ... Cloud Filter Service (CldFlt) or Connected Devices Platform (CDPsvc) ... these are easy to fix.
Open Command Prompt as Administrator
sc config CldFlt start= disabled
sc config CDPSvc start= disabled
sc config CDPUserSvc start= disabled

Clear Event Viewer again and reboot.

Note: It will NOT hurt anything to disable the above anyway.

Event Id 10016 that say do not grant Local Activation permission for the COM Server application with CLSID and APPID bit harder to fix and have to addressed one by one.

 

One 7000 but all the rest are 10016. No Cloud Filter service or CDPsvc.

 

If I read that right your on 1703 (15063.0) ... the latest is 1703 (10563.540). Not saying it would fix the 10016's your seeing, but is there a reason you haven't updated to the latest?

https://support.microsoft.com/en-us/...update-history

 

no reason. I assumed that Windows would update automatically when it got around to it. Didn't seem like a big concern to me. Also, when it's my computer's time won't it just happen (of course annoyingly)? I just wish there was something that addressed the access denied issue. I run regedit as an admin.

 

K, yea it should.

For the given 10016 (APPID / CLSID) your trying to fix. You have to change the Owner from Trusted Installer to Administrators.
1. In Regedit >The Key Your Changing > Permissions > Advanced > Owner > Change > Type in Administrators > Check Names > Ok > Ok
2. In the Permissions > Administrators > Full Control > Ok
Note: I always change Owner back to Trusted Installer (nt service\trustedinstaller), but you don't have to.
3. Now you should be able to fix whatever the 10016 is complaining about in the DCOM Config.