New
#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
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.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.
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.