Why Certain DCOM 10016 Events Don't Matter

Page 5 of 7 FirstFirst ... 34567 LastLast
  1. Zardoc's Avatar
    Posts : 231
    Windows 10 Enterprise
       #41

    Hi there Blazing speed,

    Actually, I used this reg command

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
    "EnableDCOM"="N"
    
    ** To enable change Y **
    If you read the whole thread (especially #1) you will notice that most often then none DCOM errors are not problematic. They are just denied permissions and are by design. You are just told in event viewer what happened.

    Now if you are like those that EdTittel mentioned that ''simply won't settle for anything less than a clean Event Viewer on their PCs.'' then you can give permissions do the DCOM event by adding administrators or specific users.

    To easily access DCOM and change permissions I use Power Run 1.3.
    Why Certain DCOM 10016 Events Don't Matter-power-run-2019-05-07_05-25-08.png
    Double click the Dcom command and then go to (in your case PerAppRuntimeBroker)
    Why Certain DCOM 10016 Events Don't Matter-dcom-001-2019-05-07_05-36-10.png
    Why Certain DCOM 10016 Events Don't Matter-dcom-2019-05-07_05-34-35.png

    Change permissions.
    You can add users, administrators, all application packages, trusted installer even everyone (be careful of what type of permissions you give). Use at your own risk.
      My Computer

  2. f14tomcat's Avatar
    Posts : 47,383
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       #42

    Or just ignore them. Save your sanity.
      My Computers

  3. Zardoc's Avatar
    Posts : 231
    Windows 10 Enterprise
       #43

    f14tomcat said:
    Or just ignore them. Save your sanity.
    That's what I mentioned in the post. But for some it's like having a clean car even if the sky is grey
      My Computer


  4. Posts : 139
    Windows 10 Pro 64-bit
       #44

    Zardoc said:
    Hi there Blazing speed,

    Actually, I used this reg command

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
    "EnableDCOM"="N"
    
    ** To enable change Y **
    If you read the whole thread (especially #1) you will notice that most often then none DCOM errors are not problematic. They are just denied permissions and are by design. You are just told in event viewer what happened.

    Now if you are like those that EdTittel mentioned that ''simply won't settle for anything less than a clean Event Viewer on their PCs.'' then you can give permissions do the DCOM event by adding administrators or specific users.

    To easily access DCOM and change permissions I use Power Run 1.3.
    Why Certain DCOM 10016 Events Don't Matter-power-run-2019-05-07_05-25-08.png
    Double click the Dcom command and then go to (in your case PerAppRuntimeBroker)
    Why Certain DCOM 10016 Events Don't Matter-dcom-001-2019-05-07_05-36-10.png
    Why Certain DCOM 10016 Events Don't Matter-dcom-2019-05-07_05-34-35.png

    Change permissions.
    You can add users, administrators, all application packages, trusted installer even everyone (be careful of what type of permissions you give). Use at your own risk.
    Many thanks for this, but I don't see PerAppRuntimeBroker! Why Certain DCOM 10016 Events Don't Matter-perappruntimebroker-doesnt-exist.jpg
    PerAppRuntimeBroker does not exist at all in this Dcom Config.
    Also the %SystemRoot%\System32\dcomcnfg.exe does not exist by default in the PowerRun v1.3, I had to add that but I'm not seeing any help from using this PowerRun app.

    Unless I haven't done something else to make this PerAppRuntimeBroker appear in the Component Services then I don't know what else to do.

    Do I have to separately add this using Windows Registry Editor Version 5.00 ?
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
    "EnableDCOM"="N"

    ** To enable change Y **
      My Computer

  5. Zardoc's Avatar
    Posts : 231
    Windows 10 Enterprise
       #45

    PerAppRuntimeBroker does not exist at all in this Dcom Config.
    Well, that seems odd.
    Why Certain DCOM 10016 Events Don't Matter-dcom-002-2019-05-07_05-36-10.png
    Also the %SystemRoot%\System32\dcomcnfg.exe does not exist by default in the PowerRun v1.3, I had to add that but I'm not seeing any help from using this PowerRun app.
    It's possible that you might have to add the shortcut. Been using it for quite a while. But if you are in DCOM, it should be there.
    Do I have to separately add this using Windows Registry Editor Version 5.00 ?
    [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole]
    "EnableDCOM"="N"
    ** To enable change Y **
    Just paste in TXT and save as DCOM Stop.reg. Double click and it will add to registry and it will disable DCOM. To enable set N to Y
      My Computer


  6. Posts : 139
    Windows 10 Pro 64-bit
       #46

    Zardoc said:
    Well, that seems odd.
    Why Certain DCOM 10016 Events Don't Matter-dcom-002-2019-05-07_05-36-10.png

    It's possible that you might have to add the shortcut. Been using it for quite a while. But if you are in DCOM, it should be there.

    Just paste in TXT and save as DCOM Stop.reg. Double click and it will add to registry and it will disable DCOM. To enable set N to Y
    Many thanks. Unfortunately even after a fresh reinstall of Windows 10 Pro 6 days ago from official Microsoft website 1809 up to date with all windows updates. I do not see PerAppRuntimeBroker
    Why Certain DCOM 10016 Events Don't Matter-perappruntimebroker-doesnt-exist-even-after-fresh-reinstall.jpg
    As you can see I have already disabled DCOM. That was already set to N as I turned it off from the Component Services and this has been reflected in the registry.

    But I still continue to receive error messages with The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54} and APPID {15C20B67-12E7-4BB6-92BB-7AFF07997402} to the user DESKTOP-Q65KDGP\Rahul SID (S-1-5-21-823953900-1916975897-1171586770-1001) 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.

    I don't know whether it is because PerAppRuntimeBroker is missing. But since it is a fresh re-installation from official website. I have not tempered with Windows in anyway. This PerAppRuntimeBroker simply does not exist. The only thing I see is 2x RuntimeBroker in Component services. But obviously I no longer have the guts to make changes there as it will malfunction SearchUI. Plus it is not proven to work anyway. This error in the Event Viewer will not go away under any circumstance.
      My Computer


  7. Zardoc's Avatar
    Posts : 231
    Windows 10 Enterprise
       #47

    Try this reg command.

    Code:
    Windows Registry Editor Version 5.00
    
    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{1b562e86-b7aa-4131-badc-b6f3a001407e}]
    "Enabled"=dword:00000000
    "EnableLevel"=dword:00000000
    "LoggerName"="EventLog-System"
    "MatchAnyKeyword"=hex(b):00,00,00,00,00,00,00,80
    "MatchAllKeyword"=hex(b):00,00,00,00,00,00,00,00
    "EnableProperty"=dword:00000001
    "Status"=dword:00000000
      My Computer


  8. Posts : 82
    Windows 10 Pro 1903 (18362) x64
       #48

    Wish I'd found this thread earlier to confirm that these 10016 errors don't matter. I kind of knew this anyway but I fell into the camp of having some severe boredom and they annoyed me showing in my Event Log so I decided to try and get rid of them using various guides online!

    So just a quick question: by following the "solution" guides to these errors, am I OK to leave these changes (permissions etc) and just forget about it, or do I need to undo the changes I made by following the guides?

    Thanks!
      My Computers

  9. f14tomcat's Avatar
    Posts : 47,383
    Triple boot - Win 10 Pro, Win 10 Pro Insider (2) - (and a sprinkling of VMs)
       #49

    alexncfc said:
    Wish I'd found this thread earlier to confirm that these 10016 errors don't matter. I kind of knew this anyway but I fell into the camp of having some severe boredom and they annoyed me showing in my Event Log so I decided to try and get rid of them using various guides online!

    So just a quick question: by following the "solution" guides to these errors, am I OK to leave these changes (permissions etc) and just forget about it, or do I need to undo the changes I made by following the guides?

    Thanks!
    Not sure what version of Windows you are on, but in the newest, version 1903, 99.9% of these benign errors have been reclassified as Warnings by MS, and will appear in that section, not Errors. So, if you haven't upgraded yet, do so. Otherwise, just leave as is. You're ok.
      My Computers

  10. Steve C's Avatar
    Posts : 5,262
    Windows 10 Pro 64 bit
       #50

    f14tomcat said:
    Not sure what version of Windows you are on, but in the newest, version 1903, 99.9% of these benign errors have been reclassified as Warnings by MS, and will appear in that section, not Errors. So, if you haven't upgraded yet, do so. Otherwise, just leave as is. You're ok.
    The 10016 events are indeed now Warnings but I still get many related 10010 Errors. I just ignore all of them!
      My Computers


 

Related Threads
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 11:27.
Find Us




Windows 10 Forums