New type of DCOM error with W10 1803


  1. Posts : 21
    Windows 10 Pro
       #1

    New type of DCOM error with W10 1803


    Fresh install of W10 1803 x64 here.

    I am not overly concerned about DCOM errors but since I know what the fix is I usually make an effort to fix them. However the usual steps contained in this thread:

    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Windows 10 Forums

    are not compatible.

    The errors I am seeing are:

    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
    Windows.SecurityCenter.WscBrokerManager
    and APPID
    Unavailable
    to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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.
    &
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
    Windows.SecurityCenter.WscDataProtection
    and APPID
    Unavailable
    to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) 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.
    Unlike in examples solved in the above-linked solution, Windows.SecurityCenter.WscBrokerManager does not appear in HKeyClassesRoot\CLSId.

    It does however appear in these keys:

    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscBrokerManager\
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\CLSID\{d87234b3-92c2-34ba-bc7b-419ab2467575}\
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscBrokerManager\
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\WindowsRuntime\CLSID\{0dd0d106-1786-3c4c-ac91-455e8f21eaaf}\


    The same goes for Windows.SecurityCenter.WscDataProtection

    It only appears in these keys:

    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscDataProtection\
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\CLSID\{ef23ccfd-e2ca-3659-9d22-e631c621c10e}\
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscDataProtection\
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\WindowsRuntime\CLSID\{4788dfd0-5738-3827-956b-696aae3f960e}\

    None of the CLSID's above appear anywhere else in the registry.

    Nothing in DCOM Config seems to fit the bill.

    Any ideas?
      My Computer


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

    WastedJoker said:
    Fresh install of W10 1803 x64 here.

    I am not overly concerned about DCOM errors but since I know what the fix is I usually make an effort to fix them. However the usual steps contained in this thread:

    Windows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Windows 10 Forums

    are not compatible.

    The errors I am seeing are:



    &


    Unlike in examples solved in the above-linked solution, Windows.SecurityCenter.WscBrokerManager does not appear in HKeyClassesRoot\CLSId.

    It does however appear in these keys:

    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscBrokerManager\
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\CLSID\{d87234b3-92c2-34ba-bc7b-419ab2467575}\
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscBrokerManager\
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\WindowsRuntime\CLSID\{0dd0d106-1786-3c4c-ac91-455e8f21eaaf}\


    The same goes for Windows.SecurityCenter.WscDataProtection

    It only appears in these keys:

    Code:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscDataProtection\
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsRuntime\CLSID\{ef23ccfd-e2ca-3659-9d22-e631c621c10e}\
    HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\WindowsRuntime\ActivatableClassId\Windows.SecurityCenter.WscDataProtection\
    HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\WindowsRuntime\CLSID\{4788dfd0-5738-3827-956b-696aae3f960e}\

    None of the CLSID's above appear anywhere else in the registry.

    Nothing in DCOM Config seems to fit the bill.

    Any ideas?
    Nothing to worry about, just dumb and an eyesore. Believe it or not, it's by design from MS, honest. I saw it, too, and had to investigate. Found this:

    https://support.microsoft.com/en-us/...ws-server-2016
      My Computers


  3. Posts : 4,224
    Windows 10
       #3

    What a great find in that support article, Dick ( @f14tomcat )! I'd long suspected there was some odd reason why the errors didn't really matter, and you've provided conclusive proof. I'm in favor of asking @Brink to add a pinned thread to this forum silo just to link to and explain the matters there. Thanks so much for sharing this!
    Best wishes,
    --Ed--
    Last edited by EdTittel; 11 May 2018 at 07:37. Reason: Notify OP and Brink of great info find!
      My Computers


  4. Posts : 7,904
    Windows 11 Pro 64 bit
       #4

    I'm pleased I've long ignored these errors based on advice from the forum that although you can 'fix' them, nobody really understands the implications of fixing the errors.
      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 17:12.
Find Us




Windows 10 Forums