Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Page 1 of 40 12311 ... LastLast

  1. Posts : 4
    Windows 10
       #1

    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?
      My Computer


  2. Posts : 95
    W7 x64 & W10 Pro x64 (Dual boot)
       #2

    Angry12345 said:
    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?
    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.
    Last edited by Vaio 7; 02 Sep 2015 at 13:20.
      My Computer


  3. Posts : 48
    Win 10
       #3

    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.
      My Computer


  4. Posts : 5,478
    2004
       #4

    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.
      My Computer


  5. Posts : 4
    Windows 10
    Thread Starter
       #5

    Multiple Event Errors Upgraded Event IDs 131 513


    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 ... -
      My Computer


  6. Posts : 4
    Windows 10
    Thread Starter
       #6

    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
      My Computer



  7. Posts : 4
    Windows 10
    Thread Starter
       #7

    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
      My Computer


  8. Posts : 296
    Dual-boot Win 7 & 10, both Pro 64-bit, now with a Hyper-V VM of Win 11
       #8

    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.
      My Computer


  9. Posts : 56,196
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #9

    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
    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM Attached Files
      My Computers


  10. Posts : 2,830
    Windows 10 Pro X64
       #10

    Hi,

    Read the link carefully and do step #4
    That plus also this:

    !!! Do not forget to use your security descriptor for MSLLDP driver since I guess there can be some rare cases when its different for your machine. Do not copy my SDDL descriptions, just in case. And backup the old descriptor just in case !!!
    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,
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 23:30.
Find Us




Windows 10 Forums