"Keith Nuttle" wrote

| The application-specific permission settings do not grant Local
| Activation permission for the COM Server application with CLSID
| {2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}

If you look up CLSIDs they're often informative. In this case
it seems to be a Metro shepherd called runtimebroker. The problem
sounds very similar to cellphones: A Metro app is trying to do
something it doesn't have permission for. (Since it involves DCOM
I expect it involves calling home. DCOM refers to running components
remotely.) Just like on Android, the solution is to let it do
anything it wants if you want to get out alive.

It seems to be a common problem, but not just with recent
10 versions. Here's one of the many advice pages that turned up:

https://www.kapilarya.com/fix-event-...-in-windows-10