Note: In all cases I now delete the orphaned / unrecognized accounts under security for the keys in the registry as well as DCOM Config.

Error 1:

Full Error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919} and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169} 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.

To resolve this, use the exact same method as the similar error that was found in Windows 7 while editing different keys in both the registry and DCOM Config.

Solution: www.itexperience.net/2010/10/29/event-10016-the-application-specific-permission-settings-do-not-grant-local-launch-permission-for-the-com-server-application-with-clsid-c97fcc79-e628-407d-ae68-a06ad6d8b4d1/

Rockville small business computer repair services.

Windows 7 Keys:

344ED43D-D086-4961-86A6-1106F4ACAD9B (Registry)
IPBusEnum (DCOM Config)

Windows 10 Keys:

F72671A9-012C-4725-9D2F-2A4D32D65169 (Registry)
F72671A9-012C-4725-9D2F-2A4D32D65169 (DCOM Config)

Makes no sense since 8D8F4F83-3594-4F07-8369-FC3C3CAE4919 should be found under DCOM Config but it isn’t and this works.

Likely a short-term fix for an issue MS will address in a subsequent patch.

Error 2:

Full Error:

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 SERVICE SID (S-1-5-19) 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.

To resolve this, use the same method as the similar error that was found in Windows 7 while editing different keys in both the registry and DCOM Config. However, you must also complete the “Extra Step” listed after the following link:

Solution: www.itexperience.net/2010/10/29/event-10016-the-application-specific-permission-settings-do-not-grant-local-launch-permission-for-the-com-server-application-with-clsid-c97fcc79-e628-407d-ae68-a06ad6d8b4d1/

Extra Step:

Under DCOM Config – ShellServiceHost – Properties – Security – Launch and Activation Permissions, add “Local Service” and grant “Local Launch” and “Local Activation” rights.

Additional Source: www.tenforums.com/user-accounts-family-safety/58759-permissions-error-clsid-appid-since-anniversary-update-2.html

Windows 7 Keys:

344ED43D-D086-4961-86A6-1106F4ACAD9B (Registry)
IPBusEnum (DCOM Config)

Windows 10 Keys:

{4839DDB7-58C2-48F5-8283-E1D1807D0D7D} (Registry)
ShellServiceHost (DCOM Config)

Error 3:

Full Error:

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 {316CDED5-E4AE-4B15-9113-7055D84DCC97}
to the user GAIL_NOTEBOOK\Gail Faucett SID (S-1-5-21-718284177-2017924876-1317630252-1001) from address LocalHost (Using LRPC) running in the application container

To resolve this, use the same method as the similar error that was found in Windows 7 while editing different keys in both the registry and DCOM Config. However, you must also complete the “Extra Step” listed below:

Extra Step:

Under DCOM Config – Immersive Shell – Properties – Security – Launch and Activation Permissions, add “Local Service” and grant “Local Launch” and “Local Activation” rights.

Windows 10 Keys:

{316CDED5-E4AE-4B15-9113-7055D84DCC97} (Registry)
Immersive Shell (DCOM Config)

Error 4a:

Full Error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276} 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.

To resolve this, use the same method as the similar error that was found in Windows 7 while editing different keys in both the registry and DCOM Config. However, you must also complete the “Extra Step” listed below:

Extra Step:

Under DCOM Config – RuntimeBroker – Properties – Security – Launch and Activation Permissions, add “Local Service” and grant “Local Launch” and “Local Activation” rights. NOTE: I have only seen this one time when writing this but in this instance an “unrecognized value” error was displayed in DCOM Config and I selected OK when prompted to remove the value. I then added “System” and granted rights in addition to adding “Local Service”.

Windows 10 Keys:

{9CA88EE3-ACB7-47C8-AFC4-AB702511C276} (Registry)
RuntimeBroker (DCOM Config)

Error 4b:

Full Error:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276} 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.

To resolve this, use the same method as the similar error that was found in Windows 7 while editing different keys in both the registry and DCOM Config. However, you must also complete the “Extra Step” listed below:

Extra Step:

Under DCOM Config – RuntimeBroker – Properties – Security – Launch and Activation Permissions, add “Local Service” and grant “Local Launch” and “Local Activation” rights. NOTE: I have only seen this one time when writing this but in this instance an “unrecognized value” error was displayed in DCOM Config and I selected OK when prompted to remove the value. I then added “System” and granted rights in addition to adding “Local Service”.

Windows 10 Keys:

{15c20b67-12e7-4bb6-92bb-7aff07997402} (Registry)
RuntimeBroker (DCOM Config)

Note: I did not see 15c20b67-12e7-4bb6-92bb-7aff07997402 in the event viewer but found this under DCOM Config after applying 4a, seeing an error still existed and then finding the 2nd RunTimeBroker entry.

Error 5:

Full Error:

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 SERVICE SID (S-1-5-19) 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.

To resolve this, use the same method as the similar error that was found in Windows 7 while editing different keys in both the registry and DCOM Config. However, you must also complete the “Extra Step” listed below:

Extra Step:

Under DCOM Config – Immersive Shell – Properties – Security – Launch and Activation Permissions, add “Local Service” and grant “Local Launch” and “Local Activation” rights.

Windows 10 Keys:

{4839DDB7-58C2-48F5-8283-E1D1807D0D7D} (Registry)
ShellServiceHost (DCOM Config)

Source:  https://answers.microsoft.com/en-us/windows/forum/windows_10-other_settings-winpc/distributedcom-errors-flooding-event-log/22701266-e81e-40a5-9fb4-780519363f59?auth=1