Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Page 20 of 40 FirstFirst ... 10181920212230 ... LastLast

  1. Posts : 37
    Windows 10 Pro
       #191

    f14tomcat said:
    You may be doing the wrong one. This one is not Runtime Broker. It's a funny one that has a name same as the CLSID. Look for it in what I attached and set accordingly. In Component Services, the CLSID and Component Name are the same. Add SYSTEM to local activation.

    {F72671A9-012C-4725-9D2F-2A4D32D65169} {F72671A9-012C-4725....... system


    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.
    That was that bas*rd it worked, thanks.
      My Computer


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

    Thermaltake said:
    That was that bas*rd it worked, thanks.
    You're welcome! They can be tricky, at best.
      My Computers


  3. Posts : 37
    Windows 10 Pro
       #193

    f14tomcat said:
    You're welcome! They can be tricky, at best.
    Should I lock or something that RuntimeBroker it's still open I mean it's not gray like locked, is that a problem, should I lock it or revert permissions ?
      My Computer


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

    Thermaltake said:
    Should I lock or something that RuntimeBroker it's still open I mean it's not gray like locked, is that a problem, should I lock it or revert permissions ?
    Look back at the post I made of all the code. If you do this part, it will give ownership back to TrustedInstaller. Administrators (you're one) will still have permissions to it. It's ok to leave it that way, just put the ownership back to make MS happy! :)

    When finished all Component Services
    work, change ownership back to: NT SERVICE\TrustedInstaller
      My Computers


  5. Posts : 37
    Windows 10 Pro
       #195

    f14tomcat said:
    Look back at the post I made of all the code. If you do this part, it will give ownership back to TrustedInstaller. Administrators (you're one) will still have permissions to it. It's ok to leave it that way, just put the ownership back to make MS happy! :)

    When finished all Component Services
    work, change ownership back to: NT SERVICE\TrustedInstaller
    What if I'm too lazy to do it , and leave it like this, would it do any harm or something ?
      My Computer


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

    Thermaltake said:
    What if I'm too lazy to do it , and leave it like this, would it do any harm or something ?
    Nah...never seen it cause harm. Go forth and be lazy!
      My Computers


  7. Posts : 37
    Windows 10 Pro
       #197

    f14tomcat said:
    Nah...never seen it cause harm. Go forth and be lazy!
    haha okay gloomy sunday


    thanks for help
      My Computer


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

    Thermaltake said:
    haha okay gloomy sunday


    thanks for help
    You're welcome.
      My Computers


  9. Posts : 37
    Windows 10 Pro
       #199

    Ah got happy too soon another error from DCOM 10010 and that 7023 Service control manager.

    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM-1.jpg
      My Computer


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

    Thermaltake said:
    Ah got happy too soon another error from DCOM 10010 and that 7023 Service control manager.

    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM-1.jpg
    Not something you can fix with permissions in component services. Timing issue. They generally fix themselves.
      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 03:31.
Find Us




Windows 10 Forums