Why Certain DCOM 10016 Events Don't Matter

Page 6 of 6 FirstFirst ... 456
  1.    #51

    Zardoc said: View Post
    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
    I can confirm that ever since I've changed the Enabled to a 0 from 1 I stopped receiving these DCOM 10016 warnings/errors that I previously had. Everything else can be left alone by default. In fact by default all are the same. You just set the Enable to a 0 from a 1 and now no more of these errors in event log viewer. This worked in both 1809 and is now working in 1903.
    Here's the proof. Click image for larger version. 

Name:	No more DCOM errors.jpg 
Views:	1 
Size:	534.2 KB 
ID:	237339
    These particular DCOM 10016 errors and warnings are no longer showing up in my event viewer! This is great discovery, indeed!
      My ComputerSystem Spec

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

    Steve C said: View Post
    The 10016 events are indeed now Warnings but I still get many related 10010 Errors. I just ignore all of them!
    I do, too. Have for years.
      My ComputersSystem Spec


  3. Posts : 71
    Windows 10 Pro 1903 (18362) x64
       #53

    f14tomcat said: View Post
    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.
    Thanks for the fast reply.

    The worry I had was that by me messing with the permissions in the registry and DCOM Config tool (as per the online help guides for this 10016 error) that I may have opened up myself to some security issues, but if this is not the case then I'll just leave as is. I don't really want to have to do a re-install! Thanks for confirming.
      My ComputersSystem Spec

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

    alexncfc said: View Post
    Thanks for the fast reply.

    The worry I had was that by me messing with the permissions in the registry and DCOM Config tool (as per the online help guides for this 10016 error) that I may have opened up myself to some security issues, but if this is not the case then I'll just leave as is. I don't really want to have to do a re-install! Thanks for confirming.
    You're welcome.
      My ComputersSystem Spec

  5.    #55

    Steve C said: View Post
    The 10016 events are indeed now Warnings but I still get many related 10010 Errors. I just ignore all of them!
    I feel less obsessed about warnings than I do errors. They are the exact warnings that were classified as errors before the update.
      My ComputerSystem Spec

  6. glnz's Avatar
    Posts : 148
    Dual-boot Win 7 & 10, both Pro 64-bit
       #56

    EdTittel and all here - many thanks for your posts. Just this Sunday, I upgraded my Win 10 Pro 1803 to 1903 (with a brief stop at 1809), and last night started getting these 10016 errors - those CLSID and AppID numbers exactly.

    In the past, I have changed settings in DCOM. But, for now, for this CLSID and AppID, I shall no nothing.

    However ... they seemed to start this time after TWO CHANGES:

    1. I fixed a different Event 10016 event warning in an unusual way by changing its Service start in Registry -- see
      Event ID 10016, DistributedCOM Windows.SecurityCenter.WscBrokerManager
    2. I installed yesterday's GiveAwayOfTheDay free version of AOMEI Partition Assistant Professional Edition 8.2.


    So, are these two changes triggering the Event 10016 Warnings described here Or are they inherent to Win 10?

    Thoughts? Thanks.
    Last edited by glnz; 4 Weeks Ago at 11:57.
      My ComputerSystem Spec


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

    glnz said: View Post
    EdTittel and all here - many thanks for your posts. Just this Sunday, I upgraded my Win 10 Pro 1803 to 1903 (with a brief stop at 1809), and last night started getting these 10016 errors - those CLSID and AppID numbers exactly.

    In the past, I have changed settings in DCOM. But, for now, for this CLSID and AppID, I shall no nothing.

    However ... they seemed to start this time after I installed yesterday's GiveAwayOfTheDay free version of AOMEI Partition Assistant Professional Edition 8.2. So, is that new app (or its installation) triggering them? Or are they inherent to Win 10?

    Thoughts? Thanks.
    You seem to have answered your own question. Unless you highly believe in coincidence. In 1903, the 10016 errors are now Warnings, not Errors. They were reclassified by MS. If things started going wonky when you installed the Freebie, uninstall the Freebie (and hope you get all the parts). See if your situation clears up. I'm not knocking the Aomei "free" giveaway, but remember the old saying....

    "If the product is free, you are the product".
      My ComputersSystem Spec

  8. glnz's Avatar
    Posts : 148
    Dual-boot Win 7 & 10, both Pro 64-bit
       #58

    f14tomact - thanks. But I was editing my post directly above yours while you were responding.
    Please re-read mine two above and advise again - would much appreciate your expert thoughts.
      My ComputerSystem Spec

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

    glnz said: View Post
    f14tomact - thanks. But I was editing my post directly above yours while you were responding.
    Please re-read mine two above and advise again - would much appreciate your expert thoughts.
    That is a long thread, filled with reg hacks all over the place. Changing a service from delayed to immediate (auto-normal) may have the effect of the service trying to start when other dependencies have not fully started and timing issues result causing errors. I'd like to know if these are actually showing as errors (red) not warnings (yellow). As I stated, the historic 10016 "errors" were reclassified in 1903 as warnings, and if present should appear in Warnings, not Errors.

    If I were you, I would revert that reg entry back to 1, delayed, and see if the picture changes. If still getting them, uninstall that Aomei best you can (Revo is great for deep cleaning), reboot and see what you get. Doing multiple things simultaneously makes troubleshooting real tough.
      My ComputersSystem Spec

  10. glnz's Avatar
    Posts : 148
    Dual-boot Win 7 & 10, both Pro 64-bit
       #60

    All - SInce I continue to get new Warnings about
    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}
    I thought I might try to add the "missing" permission settings in dcomcnfg. HOWEVER, when I hit the Edit button in Launch and Activation Permissions on the Security tab in Properties for PerAppRuntimeBroker, I got this:

    Click image for larger version. 

Name:	image.png 
Views:	49 
Size:	11.6 KB 
ID:	238051

    That is a new one on me. I hit Cancel.

    Also, I searched regedit for the AppID {15c20b67-12e7-4bb6-92bb-7aff07997402}, and I did not see anything that looked like the mentioned nondisplayable permission entries.

    What is that WIndows Security warning, and what happens to my life if I hit Remove?

    Thanks.
      My ComputerSystem Spec


 
Page 6 of 6 FirstFirst ... 456

Related Threads
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...
I have been seeing the following even in my laptop's System log for quite some time. (Months.) The error says essentially: The user CALM1\BobTB, does not have Local Activation permission to the DCom app named RuntimeBroker. The...
Before the update i had 0 of these errors now with 1709 i get them daily and everytime on boot up aswell (the keys change from day to day tho) So is this a critical error and does it need to be fixed? Or is it a mess by microsoft and just...
Cortana and DCOM Error Event 10016 in Performance & Maintenance
My PC was giving many DCOM error 10016 involving Cortana as follows: The machine-default permission settings do not grant Local Activation permission for the COM Server application with CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID...
Solved DCOM error 10016 in Performance & Maintenance
I'm told this is a rather common error after upgrading from Windows 7 to Windows 10, but I have read many posts and suggested solutions, but I still get the error in the System Event Log when starting up. I suppose I could ignore it, as there does...
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 21:11.
Find Us