Hi.
I solved the problem following this advice:
This behavior can occur if the registration for the Distributed Component Object Model (DCOM) interface in either of the following registry locations contains both RunAs and LocalService entries:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppId\ {D99E6E74-FC88-11D0-B498-00A0C90312F3}
or
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppId\ {D99E6E73-FC88-11D0-B498-00A0C90312F3}
When this occurs, the Certification Authority service does not start because it does not expect both values to be set.
To resolve this issue, remove the RunAs entries under both of the following registry locations
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppId\ {D99E6E74-FC88-11D0-B498-00A0C90312F3}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppId\ {D99E6E73-FC88-11D0-B498-00A0C90312F3}
Make sure that the LocalService entry exists under the following registry locations with a data value of CertSvc
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppId\ {D99E6E74-FC88-11D0-B498-00A0C90312F3}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppId\ {D99E6E73-FC88-11D0-B498-00A0C90312F3}
Attention: Before modify the registry, please make sure to backup the registry and make sure that you understand how to restore the registry