Windows 10: System crash with error code 10010

Hello everyone,I'm experiencing total system failures with the error code 10010 The server Windows.Gaming.GameBar.PresenceServer.Internal.PresenceWriter did not register with DCOM within the required timeout. every time I try to play the game "House Flipper 2".This error is always accompanied by warnings with the code 10016. I've gathered that this is probably the fault of some DCOM security config, but I haven't been able to fix it with the help of other guides.I've also gathered that this error is also something, that should not be as

:)

 

Error 10010

Thank you for the information. On the error description you provided, we'd like to ask if you are connected to a server or a private network because the error has something to do with a server configuration. Have you done something recently on your computer
that may have caused this?

Also, you can refer to this thread answered by Arthur
Li regarding Error 10010. Take note that serious problems could occur when the registry is modified inaccurately. Make sure to follow the steps provided carefully. For safety,
create a backup.

Keep us posted after performing the troubleshooting steps.

 

Are you getting DistributedCOM Event ID: 10010 errors with 11.4?

Only by ID in fact ever since i have installed the 11.4's i get these kind of errors
Application 'C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static\CCC.exe' (pid 2188) cannot be restarted - Application SID does not match Conductor SID..

Although i have had 0 issue's using the computer and even though it's listed as 10010 the XML tells a totally different story lol.

 

ERROR 10010

Au démarrage système on passe toujours par l'écran set up sans avoir fait F1.De nombreuses erreurs dans l'observateur d’événements. Par exemple error 10010 Win 10 release 10.0.17134.464 from Microsoft-Windows-DistributedCom. Autre exemple :Circular kernel
logger s'est arrêté avec code erreur 0xC000188.

Procédé une recherche sfc/scannow qui a détecté des erreurs et a corrigé mais le bug subsiste. que faut il faire ?

At system startup, we always go through the set up screen without having done F1. Many errors in the event observer. For example, error 10010 Win 10 release 10.0.17134.464 from Microsoft-Windows-DistributedCom. Another example: Circular kernel logger has
stopped with error code 0xC000188.

Performed a sfc / scannow search that found errors and fixed but the bug still exists.

what should be done ?