Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM

Page 35 of 40 FirstFirst ... 253334353637 ... LastLast

  1. Posts : 4
    Windows 10
       #341

    Thank you!

    Sadly, this solution does not work for me
      My Computer


  2. Posts : 5,478
    2004
       #342

    Mike0094 said:
    Thank you!

    Sadly, this solution does not work for me
    It might help if you quoted who (me I guess) suggested something, what you did and what didn't work.

    Ideally you should note the error or warning messages received.

    Otherwise I can only say I'm sorry to hear that whatever you did (whatever it was), didn't work.
      My Computer


  3. Posts : 4
    Windows 10
       #343

    Vaio 7 said:
    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.
    I tried to use this method, my issue is a system error ( event ID 10016) :

    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 michele\my pc SID (S-1-5-21-2832376193-1952021688-2811500842-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.SkypeApp_12.8.487.0_x64__kzf8qxf38zg5c SID (S-1-15-2-2246530975-808720366-1776470054-230329187-4153223113-3550430174-4193313734). This security permission can be modified using the Component Services administrative tool.
      My Computer


  4. Posts : 63
    Windows
       #344

    You can try adding launch and activation permissions for user "All Application Packages" and see if that helps. I assume you have already added those permissions for the user "my pc"; if not, do that first. Finally, even after having added all the right permissions you may still see these error messages. Microsoft badly broke their DCom system in Windows 10, so some of these errors cannot be resolved. Word on the street is that you can ignore these errors safely, but nobody knows for sure.
      My Computer


  5. Posts : 5,478
    2004
       #345

    Pirx said:
    You can try adding launch and activation permissions for user "All Application Packages" and see if that helps.
    Why? Why would you want to give all apps that authority? To do what?

    Sure it would remove the error message but at the expense of giving every single Windows Store app the authority to do whatever they want. Authority for Store Apps is complex and a "whatever, do what you want" approach is rather cavalier I think.

    Pirx said:
    Word on the street is that you can ignore these errors safely, but nobody knows for sure.
    Or you can randomly give authority to processes to do what they want and swap an increased risk for less messages.

    Only you can decide if randomly changing permissions is better than living with incorrectly written messages to a log you would only look at if you had a problem.

    I agree with your point though on the whole.
      My Computer


  6. Posts : 24
    win10
       #346

    Pirx said:
    You can try adding launch and activation permissions for user "All Application Packages" and see if that helps. I assume you have already added those permissions for the user "my pc"; if not, do that first. Finally, even after having added all the right permissions you may still see these error messages. Microsoft badly broke their DCom system in Windows 10, so some of these errors cannot be resolved. Word on the street is that you can ignore these errors safely, but nobody knows for sure.
    So people without any knowledge about registry&co should just ignore this error yes?
      My Computer


  7. Posts : 24
    win10
       #347

    Vaio 7 said:
    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.
    is the last step important?
    "Now go back to regedit and for the CLSID & Appid changed ownerships revert back to default TrustedInstaller."
    because ive found a more detailed guide to your way of fixing this but theres no mention of it..
      My Computer


  8. Posts : 7,254
    Windows 10 Pro 64-bit
       #348

    I generally say that unless the error is marked as critical, then don't worry too much about it. But it depends on the nature of the error. Worth looking from time to time but not fretting over.
      My Computers


  9. Posts : 5,478
    2004
       #349

    swarfega said:
    Worth looking from time to time but not fretting over.
    I disagree. I think it isn't worth looking into at all unless as a hobby.

    I'm signing off this thread now but good luck to y'all fiddling with it.
      My Computer


  10. Posts : 7,254
    Windows 10 Pro 64-bit
       #350

    I think thats what I said. Generally its not worth the time.
      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 19:00.
Find Us




Windows 10 Forums