Look for HKEY_CLASSES_ROOT\AppID\{APPID-GUID}. That should tell you the name of the offending COM component. All you have to do now is go back to the Component Services snapin, find the name of that component, go the security properties of it, and edit the security ACL of that component such that what ever account the event log was bitching about is given whatever access it wanted. If you find that that the security properties of the component are greyed out so that you can't edit it, that's probably because TrustedInstaller has that on lockdown. Go back to the registry, find the corresponding reg key, take ownership/give yourself permissions to it as necessary, restart the service (or reboot the OS,) and then you will be able to modify the security settings on that COM component.
I saw this myself just yesterday with the "SMS Agent" DCOM application. The SMS (or SCCM) agent came preinstalled on the standard OS image that was being deployed to the machines I was working on.
O que está acontecendo aqui é que você não pode alterar as permissões, porque as permissões estão vinculadas a uma chave do registro que você não tem permissão para alterar porque o TrustedInstaller é o proprietário delas. Você precisa apropriar-se da chave do registro para poder modificá-la.