Typical fix for Event 10016 Immersive Shell does not work - why not?


  1. Posts : 318
    Dual-boot Win 7 & 10, both Pro 64-bit, now with a Hyper-V VM of Win 11
       #1

    Typical fix for Event 10016 Immersive Shell does not work - why not?


    After a few Event 10016 Warnings for the AppID for Immersive Shell that

    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 DESKTOP-3*****N\[My User Name] SID (S-1-5-21-[10 9 10 digits]-1001) from address LocalHost (Using LRPC) running in the application container Microsoft.Windows.ShellExperienceHost_10.0.18362.145_neutral_neutral_[13 characters] SID (S-1-15-2-[many digits]). This security permission can be modified using the Component Services administrative tool.
    I turned myself into Trusted Installer, started dcomcnfg, went to Immersive Shell - Properties - Security tab - Launch and Activation Permissions, added DESKTOP-3*****N\[My User Name] and made sure both Local Launch and Local Activation were checked.

    However, many hours later, the same Warning has recurred! So why isn't the typical fix working?

    Yes, I know not to bother with Event 10016, but my question is why the typical fix doesn't work.
    Is it because I haven't satisfied (a) "from LocalHost (Using LRPC)" or (b) from the specified "application container" in the fix? If yes, how do I satisfy those parameters?

    By the way, in dcomcnfg for Immersive Shell, the other three User Names (System, Administrators and Interactive) also have Remote Launch and Remote Activation checked, but my added user name does not. Is that the fix? And would that be secure?

    Also, since the "Administrators (DESKTOP-3*****N\Administrators)" category was already there, with all four boxes checked, why did I get the Warning at all? My user account on my machine is an "administrator" account. Could it be because I do not need a password to log on to my own machine (which is sitting on my desk at home)?

    Or could it be because when I originally installed Win 10, I set my installation to Local Account and not Microsoft Account? (I do have an account with MS Outlook email and the machine does know that, but I'm still mostly Local Account as a user, as far as I can tell.)

    I'm Win 10 Pro 64-bit version 1903. Thanks.
    Last edited by glnz; 30 Jun 2019 at 13:54.
      My Computer


  2. Posts : 7,905
    Windows 11 Pro 64 bit
       #2

    Just ignore these 'errors'. Trying to fix them might have unintended consequences.
      My Computers


  3. Posts : 72
    Win 10 Pro 19043.1237 (X64) (21H1)
       #3

    while this does not help answer your inquiry, I have narrowed this particular warning down to Notifications on my Win 10 1903. Every time I receive a Notification, this particular Dcom warning raises it's ugly head !
    Also like you, I prefer to try and find the why instead of ignoring or disabling annoying error/warnings in event viewer !
    - - - Updated - - -

    Still trying to learn who the "ALL APPLICATION PACKAGES" group actually is but after adding
    the "ALL APPLICATION PACKAGES" group for Immersive Shell, giving them Local Launch and Local Activation privileges, I no longer receive Event 10016 Warnings for Immersive Shell
    that was related to any Notifications I was receiving !
      My Computer


  4. Posts : 392
    W10
       #4

    See pinned topic at the top of the forum: Why Certain DCOM 10016 Events Don't Matter
      My Computer


  5. Posts : 318
    Dual-boot Win 7 & 10, both Pro 64-bit, now with a Hyper-V VM of Win 11
    Thread Starter
       #5

    jdc1 - yes, and that's what I noted at the start of this thread. My question was why the normal "fix" doesn't work in this case.
      My Computer


  6. Posts : 392
    W10
       #6

    Sorry for not seeing that, I'll bow out now
      My Computer


 

  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 08:00.
Find Us




Windows 10 Forums