Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Page 18 of 40 FirstFirst ... 8161718192028 ... LastLast

  1. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #171

    not4sakn said:
    That's exactly what mine is, NT AUTHORITY\LOCAL SERVICE but I'm unable to find it under component services to change permissions unless I'm missing something.

    I also have a kernel processor power event 37 error along with several others.
    Take a look at this. I made myself a cheat-sheet of the common ones.

    Code:
    7:10 AM 10/9/2016
    
    Dcom errors and clsid's ... fixes with regedit and component services
    
    ---------------------------------------------------------------------------------------------------------
        
        Change ownership in Regedit to:        administrators
        Give FULL authority.
    
        When finished all Component Services 
        work, change ownership back to:        NT SERVICE\TrustedInstaller
    
        In each case, enter the user group/name and click "Check Names"
        to get the correct internal name.
    
    ---------------------------------------------------------------------------------------------------------
    
    Some of the more common DCOM errors are:
    
        CLSID in Regedit:            Name in Component Services    Add Local Activation for:
        -----------------            --------------------------    -------------------------
    
        {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}    Runtime Broker            NETWORK SERVICE
    
        {7006698D-2974-4091-A424-85DD0B909E23}    Windows Insider Service        dhubb {YOUR User ID}
    
        {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}    Shell Service Host        local service
    
        {F72671A9-012C-4725-9D2F-2A4D32D65169}     {F72671A9-012C-4725.......    system
    
        {316CDED5-E4AE-4B15-9113-7055D84DCC97}     Immersive Shell            dhubb {YOUR User ID}
    
        In each case, enter the user group/name and click "Check Names"
        to get the correct internal name.
      My Computers

  2.    #172

    Following is a persistent Event 10016 DCOM error that I have not been able to banish...and that has been in this thread often...the good'ol "Immersive Shell":

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97}
    to the user ATL\alaur SID (S-1-5-21-2645921604-3921278621-287550337-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.MicrosoftSolitaireCollection_3.12.12200.0_x64__8wekyb3d8bbwe SID (S-1-15-2-1985198343-3186790915-4047221937-1969271670-3792558349-1325541827-400269725). This security permission can be modified using the Component Services administrative tool.


    The permission issue in this case appears related specifically to the user. Under DCOM Config in Component Services, I have added the user in Launch & Activation Permission with Local Launch and Local Activation checked (this fails to solve the error) and then again with all 4 permissions checked but the error still persists. The app/system does not seem to exhibit any functional issues. This is more me being anal about event log errors and wanting to "find/know/solve" the reason for the error. I have successfully purged all other typical DCOM errors (other than timing related errors) but this one is eluding me. Any thoughts would be greatly appreciated.
    Last edited by galileo1564; 23 Feb 2017 at 15:13.
      My Computer

  3.    #173

    ...bump...
      My Computer


  4. Posts : 2,832
    Windows 10 Pro X64
       #174

    Hi,


    If you follow all the steps correctly the DCOM error should disappear for sure.



    Cheers,
      My Computers


  5. Posts : 29
    Windows 10
       #175

    I ran the script on WSearch {9E175B9C-F52A-11D8-B9A5-505054503030} because of this

    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {9E175B6D-F52A-11D8-B9A5-505054503030}
     and APPID 
    {9E175B9C-F52A-11D8-B9A5-505054503030}
     to the user DESKTOP-111111\COOL SID (S-1-5-21-1826351668-3361679923-1860594981-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.MicrosoftEdge_38.14393.0.0_neutral__8wekyb3d8bbwe SID (S-1-15-2-3624051433-2125758914-1423191267-1740899205-1073925389-3782572162-737981194). This security permission can be modified using the Component Services administrative tool.
    However it produced some kind of error, no idea what it means.

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

    I was still able to add myself into the WSearch DCOM and grant Local Activation permission. Now I get the 2 errors below:

    Code:
    DllHost (1496) Microsoft.MicrosoftEdge_8wekyb3d8bbwe_NOEDP_EDGE_IDB: Flush map file "C:\Users\Sam\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppData\User\Default\Indexed DB\IndexedDB.jfm" will be deleted. Reason: ReadHdrFailed.
    
    DllHost (1496) Microsoft.MicrosoftEdge_8wekyb3d8bbwe_NOEDP_EDGE_IDB: Error -1919 validating header page on flush map file "C:\Users\Sam\AppData\Local\Packages\Microsoft.MicrosoftEdge_8wekyb3d8bbwe\AppData\User\Default\Indexed DB\IndexedDB.jfm". The flush map file will be invalidated. 
    Additional information: [SignDbHdrFromDb:Create time:00/00/1900 00:00:00.000 Rand:0 Computer:] [SignFmHdrFromDb:Create time:00/00/1900 00:00:00.000 Rand:0 Computer:] [SignDbHdrFromFm:Create time:02/25/2017 03:56:29.833 Rand:3237100295 Computer:] [SignFmHdrFromFm:Create time:02/25/2017 04:04:08.211 Rand:2418119268 Computer:]
    Last edited by waitandhope123; 25 Feb 2017 at 05:48.
      My Computer

  6.    #176

    fdegrove said:
    Hi,

    If you follow all the steps correctly the DCOM error should disappear for sure.

    Cheers,
    Welllll, not quite working our that way...for me or Marco83...please see posts #89, #90, #91 and in particular #92. The issue isn't following the procedure. That part is straightforward: give permission to registry keys and add/modify DCOM permissions. I had no issues doing that on not only this error but other errors as well. The problem is, as Marco83 discovered, that the Immersive Shell DCOM permissions do not seem to solve the error.

    In particular, adding the "user" that is noted in the Event Properties for the error and giving Local Launch and Local Activation permissions does not seem to result in changing (solving) the underlying permissions problem...at least that is evidenced by the same Event Log error continuing to show up. This particular error with Immersive Shell seems to show up in quite a few posts across the web and does not seem to have any definitive solution...at least not that I have come across.

    Following (see below) is one post that claimed to have some success, I have tried this without any success:

    https://social.technet.microsoft.com...10itprogeneral

    But, I am certainly continuing to look nonetheless. If you have any other thoughts, I would be very grateful.
      My Computer


  7. Posts : 29
    Windows 10
       #177

    I also seem to have that issue, even going into DCOM and granting WSearch permission for me it still reports this, I give up

    Code:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {9E175B6D-F52A-11D8-B9A5-505054503030}
     and APPID 
    {9E175B9C-F52A-11D8-B9A5-505054503030}
     to the user DESKTOP-111111\COOL SID (S-1-5-21-1826351668-3361679923-1860594981-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.MicrosoftEdge_38.14393.0.0_neutral__8wekyb3d8bbwe SID (S-1-15-2-3624051433-2125758914-1423191267-1740899205-1073925389-3782572162-737981194). This security permission can be modified using the Component Services administrative tool.
      My Computer


  8. Posts : 56,806
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #178

    To all DCOM error sufferers. It is understandable to want a squeaky clean Event Log. These persistent DCOM "errors" have been around for a very long time. Years. The same 3 or 4 always seem to pop up. They really do not cause any harm, and tend to be from timing issues when Windows starts up. After the initial logging of these events, they don't continue over and over. There are built in retries. The system settles down. No ill effects. Other errors can and will occur, for a variety of reasons. Unless these common Event Log errors are causing you obvious system problems, try to just ignore them. I know, it grates on the sense of wanting an OS as perfect as possible.

    Legitimate system errors that cause malfunction or worse are understandable to want to get fixed. But, some of these are just not going to easily go away. Even if temporarily fixed, they tend to come back.

    This is all just my opinion. I've fought these errors thru many OS releases and Insider Build versions.

    TC
      My Computers

  9.    #179

    @f14tomcat

    I agree...these are MS issues that have persisted over some time and across several OS versions. It is true that they tend to be benign errors...and that it is more about the user ("me") being somewhat anal about seeing Event Log errors.

    It is worth noting that the Immersive Shell error that I am seeing is being generated "only" upon initiating the "Microsoft Solitaire Collection". No other Immersive Shell errors are occurring. When activating this application, it "logs on" (or "signs in") to the MS Xbox game user ID (successfully). Which, since the error is related specifically the named user account, begs an interesting question: is there something related to the gaming sign in that happening behind the scenes that is tripping over permissions - or timing - but that records itself as a "local user" permissions error? Since this is involves an additional remote sign-in using local credentials, I wonder if the remote sign-in is generating a timing error...?

    Regardless, I agree that it is probably time (no pun intended) to stop "beating this horse"...as it doesn't seem to be "moving"....
      My Computer


  10. pau
    Posts : 3
    GNU/Gentoo Linux
       #180

    Hi,

    this is the error i'm getting in the event viewer when my computer freezes:
    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) 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.

    After fixing CLSID and APPID, running the following script in the power shell as adminsitrator, how can i know which is the app name i need to find in Administrative Tools -> Component Services? Please, hope someone can tell me the name i need to look for there
    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

    Thanks in advanced :)
      My Computer


 

  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 07:06.
Find Us




Windows 10 Forums