Windows 10: Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

I am having a number of events that seem to be located repeatedly with the source: DistributedCOM

Event ID: 10010
and
Event ID: 10016

also getting repeatedly

Service Control Manager
Event ID: 7031

Those are the Errors I have gotten about 900 times since Wednseday repeatedly

I have a few warning but they all Task Scheduler and others that I am not as concerned about as those two

Any solutions?

:)

 

how to fix event viewer error 10016 (DistributedCOM)

Check this link: Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Page 2 - Windows 10 Forums

 

Event 7031 System Control Manager

Well looks like Anniversary update has finally got rid of 7031 and cortana 10016 !!!!!!

New 10016 now coming up on all of my machines..Haven't researched it yet..... CDP Activity Store / Interactive User.

Have since found

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

 

Event id 7031, you will have to wait until M$ provides a fix it happens during shutdown and its Sync Host session, I have the same.
Same for Event id 10010, Cortana, not much to do.
Now Event Id 10016 can be easily fixed. When you look @ the Event Viewer description there is a CLSID and an AppID involved.
You will have to open regedit with admin rights, navigate to HKeyClassesRoot\CLSId and when you find the id in question, right click then Permissions and temporarily change owner from TrustedInstaller to Administrators.
Same for HKEYLocalMachine\Appid.
Now open Component Services, Computer, My computer, DCOM config and find ( from the Registry keys above) the Description, it should be Runtime Broker, at least it was for me, if it's other then do it for the exact Component service, right click then Properties then Security tab, then open the Launch and Activation permissions Edit button and depending on the Event Viewer description if it's Local Service or System, click Add, add one of the two and enable the box " Local Activation".
Now go back to regedit and for the CLSID & Appid changed ownerships revert back to default TrustedInstaller.
(You should write NT SERVICE\TrustedInstaller to revert ownership to default).
Reboot and Error 10016 is gone forever. *Wink

 

Vaio 7 is right about the 10016. It's an artifact from upgrading from a previous version of windows. I also found I had to set the services that start with Net in the services app to delayed start (errors occasionally in system event log).

Later, on the same machine, I re-installed win 10 (after some nasty experiment went wrong) and choose the option to not keep anything. Cleanest event log ever and no Net* services in the services app.

 

7031 I fixed by disabling OneSyncSvc and OneSyncSvc_Session1 as described here and here

Assuming it is the same error just set the key Start to a value of 4 (disabled) in these places:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc_Session1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\OneSyncSvc_Session4 (I didn't have this one so ignored it)

Seems to have no ill effects.

@OP please try to add more detail on the errors as the same error code can be due to multiple things.

 

Event ID 131 - MANY TIMES
DeviceSetupManager
Metadata staging failed


EventID 513
CAP12
Cryptographics services failed while processing

Several warnings too
EventID 153
disk
IO operation at logical block address

EventID 219
Kernel-PnP
failed to load driver WudfRD

EventID 202
DeviceSetupManager
Says no internect connectivity but i have it

EventID 414
TaskSchedular
Found misconfiguaration in the NT TASK

EventID 201
DeviceSetpupManager
No connection to Windows MEtadata

Event ID 1000
ISCTAgent
NetDetect is now disabled - i am guessing this is ok cause its a computer

Event ID 11
Wininit
Custom dynamics libraries are ... -

 

Event 10016

I go to the registry and when i click the folder and right click to set permissions it is at All Application Packages and I can click admin and okay, but i cannot click apply and as soon as i reopen it sback to All Application Packages. Now I notice that All Application Packages has same permissions as admin so not sure if I should go on with rest of steps you all gave me

 

Also should i pay much attention to the warnings?

couple of other errors

Event ID 131
DeviceSetupManager
Metadata Staging Failed - get it alot3

Event ID 3
Kernel-Event Tracing
ReadyBoot stopped

EventID 69
AppModel-Runtime
ZuneMusic problem

 

Sorry, Vaio 7's suggestions above did not work for me for 10016. In DCOM, the entries on the Security Tab remained greyed out, even after the regedit changes. I even tried in Win 10's Safe Mode - same thing.
Also, "HKEYLocalMachine\Appid" isn't a complete guide. There's another level in between.
Still looking for an answer to this. Thanks.

 

To solve the 131 event error, make this change to registry. In essence the redirect (FWLINK) gets broken.

Windows Registry Editor Version 5.00

; 4:54 AM 7/1/2015
; This fix prevents Metedata 131 errors
; original entry is "DeviceMetadataServiceURL"="http://go.microsoft.com/fwlink/?LinkID=252669&clcid=0x409"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Device Metadata]
"DeviceMetadataServiceURL"="http://dmd.metaservices.microsoft.com/dms/metadata.svc"

Correct_METADATA_URL - Use this to fix event log error.zip

The explanation is in this thread on Eightforums... Continues Errors at startup - Page 3

------------------------------------------------------------------------------------------------------------------------------------------

To fix the CAP12 error, refer to this link: Error source CAPI2 id 513 - Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object

This is the part that needs to be done: In Admin CMD line, NOT Powershell!!


Read the link carefully and do step #4. When you copy the set command, do not use any extra spaces.


---> DO THIS IN ADMIN CMD LINE!! NOT POWERSHELL!!! <---

--------------------------------------------------------------------------------------------------------------------------------------

To fix the 10016 errors, here are two (2) links with accurate steps. Follow the steps in sequence. You MUST have admin privileges.

Solved Numerous event id 10016 errors win 8 pro 64 bit


Event ID 10016, DistributedCOM: The application-specific permission settings do not grant Local Activation permission for the COM Server application (2) - Share iT

 

Hi,

That plus also this:

since it's not necessarily the same for all machines.

Another of these all too frequent errors that occur on every single machine/install that should have been fixed a long time ago.

Cheers, *Wink

 

Same here, I followed the steps and the DCOM security tab options are grayed out.

I tried to restore my registry back but it is not letting me because I changed the permissions for the two entries to Administrator and Admin does not have full permissions.

Is there any way for me to revert back or restore my registry?

Thanks,

Rick

 

You had to change the ownership to Administrators (with an s) not Administrator (which is the built in administrator account and not the same thing).

This powershell script will take ownership of the 2 keys for the 10016 RuntimeBroker error, grant authority to Administrators group and then change the ownership back to TrustedInstaller (which it what it should be).

To do this open an elevated powershell window (right click and run as administrator). Then copy everything in the box below, paste it into the powershell window and press enter.

You can select everything in the box by triple clicking, then ctrl + C to copy and ctrl + V to paste.
Code: function enable-privilege { param( ## The privilege to adjust. This set is taken from Privilege Constants (Windows) [ValidateSet( "SeAssignPrimaryTokenPrivilege", "SeAuditPrivilege", "SeBackupPrivilege", "SeChangeNotifyPrivilege", "SeCreateGlobalPrivilege", "SeCreatePagefilePrivilege", "SeCreatePermanentPrivilege", "SeCreateSymbolicLinkPrivilege", "SeCreateTokenPrivilege", "SeDebugPrivilege", "SeEnableDelegationPrivilege", "SeImpersonatePrivilege", "SeIncreaseBasePriorityPrivilege", "SeIncreaseQuotaPrivilege", "SeIncreaseWorkingSetPrivilege", "SeLoadDriverPrivilege", "SeLockMemoryPrivilege", "SeMachineAccountPrivilege", "SeManageVolumePrivilege", "SeProfileSingleProcessPrivilege", "SeRelabelPrivilege", "SeRemoteShutdownPrivilege", "SeRestorePrivilege", "SeSecurityPrivilege", "SeShutdownPrivilege", "SeSyncAgentPrivilege", "SeSystemEnvironmentPrivilege", "SeSystemProfilePrivilege", "SeSystemtimePrivilege", "SeTakeOwnershipPrivilege", "SeTcbPrivilege", "SeTimeZonePrivilege", "SeTrustedCredManAccessPrivilege", "SeUndockPrivilege", "SeUnsolicitedInputPrivilege")] $Privilege, ## The process on which to adjust the privilege. Defaults to the current process. $ProcessId = $pid, ## Switch to disable the privilege, rather than enable it. [Switch] $Disable ) ## Taken from P/Invoke.NET with minor adjustments. $definition = @' using System; using System.Runtime.InteropServices; public class AdjPriv { [DllImport("advapi32.dll", ExactSpelling = true, SetLastError = true)] internal static extern bool AdjustTokenPrivileges(IntPtr htok, bool disall, ref TokPriv1Luid newst, int len, IntPtr prev, IntPtr relen); [DllImport("advapi32.dll", ExactSpelling = true, SetLastError = true)] internal static extern bool OpenProcessToken(IntPtr h, int acc, ref IntPtr phtok); [DllImport("advapi32.dll", SetLastError = true)] internal static extern bool LookupPrivilegeValue(string host, string name, ref long pluid); [StructLayout(LayoutKind.Sequential, Pack = 1)] internal struct TokPriv1Luid { public int Count; public long Luid; public int Attr; } internal const int SE_PRIVILEGE_ENABLED = 0x00000002; internal const int SE_PRIVILEGE_DISABLED = 0x00000000; internal const int TOKEN_QUERY = 0x00000008; internal const int TOKEN_ADJUST_PRIVILEGES = 0x00000020; public static bool EnablePrivilege(long processHandle, string privilege, bool disable) { bool retVal; TokPriv1Luid tp; IntPtr hproc = new IntPtr(processHandle); IntPtr htok = IntPtr.Zero; retVal = OpenProcessToken(hproc, TOKEN_ADJUST_PRIVILEGES | TOKEN_QUERY, ref htok); tp.Count = 1; tp.Luid = 0; if(disable) { tp.Attr = SE_PRIVILEGE_DISABLED; } else { tp.Attr = SE_PRIVILEGE_ENABLED; } retVal = LookupPrivilegeValue(null, privilege, ref tp.Luid); retVal = AdjustTokenPrivileges(htok, false, ref tp, 0, IntPtr.Zero, IntPtr.Zero); return retVal; } } '@ $processHandle = (Get-Process -id $ProcessId).Handle $type = Add-Type $definition -PassThru $type[0]::EnablePrivilege($processHandle, $Privilege, $Disable) } #------------------------------------------------------------------------------------------------------------------------------------------------------ function Takeown-Registry($key) { switch ($key.split('\')[0]) { "HKEY_CLASSES_ROOT" { $reg = [Microsoft.Win32.Registry]::ClassesRoot $key = $key.substring(18) } "HKEY_CURRENT_USER" { $reg = [Microsoft.Win32.Registry]::CurrentUser $key = $key.substring(18) } "HKEY_LOCAL_MACHINE" { $reg = [Microsoft.Win32.Registry]::LocalMachine $key = $key.substring(19) } } # take ownership $key = $reg.OpenSubKey($key, "ReadWriteSubTree", "TakeOwnership") $owner = [Security.Principal.NTAccount]"Administrators" $acl = $key.GetAccessControl() $acl.SetOwner($owner) $key.SetAccessControl($acl) # set FullControl $acl = $key.GetAccessControl() $rule = New-Object System.Security.AccessControl.RegistryAccessRule("Administrators", "FullControl", "Allow") $acl.SetAccessRule($rule) $key.SetAccessControl($acl) # reset owner $owner = [Security.Principal.NTAccount]"NT SERVICE\TrustedInstaller" $acl = $key.GetAccessControl() $acl.SetOwner($owner) $key.SetAccessControl($acl) } #------------------------------------------------------------------------------------------------------------------------------------------------------ # Grant authority to registry key Write-Host; Write-Host "Elevating privileges for this process" -f yellow; Write-Host do {$result = enable-privilege SeTakeOwnershipPrivilege } until ($result -eq $true) do {$result = enable-privilege SeRestorePrivilege } until ($result -eq $true) $key="HKEY_CLASSES_ROOT\AppID\{9CA88EE3-ACB7-47c8-AFC4-AB702511C276}" Write-Host "Granting authority to $key" Takeown-Registry($key) $key="HKEY_CLASSES_ROOT\CLSID\{D63B10C5-BB46-4990-A94F-E40B9D520160}" Write-Host "Granting authority to $key" Takeown-Registry($key) Write-Host; Write-Host "Done"; Write-Host[/quote]
The result should look like this (it should say "Done") and you can then go to component services and update your DCOM permissions for RuntimeBroker if you like.





Note if you've changed some other keys then you'll have to edit the script or do it manually but the steps are the same - change owner to Administrators, grant authority to Administrators, change ownership back to TrustedInstaller. You can easily do it using the script above by running it and then when it has run change $key to whatever you want and run the Takeown-Registry function Code: $key="HKEY_CLASSES_ROOT\AppID\{<whatever>}" Takeown-Registry($key)[/quote]

 

Hi,

Well done lx07.

Cheers, *Wink