New
#171
Take a look at this. I made myself a cheat-sheet of the common ones.
Code:7:10 AM 10/9/2016 Dcom errors and clsid's ... fixes with regedit and component services --------------------------------------------------------------------------------------------------------- Change ownership in Regedit to: administrators Give FULL authority. When finished all Component Services work, change ownership back to: NT SERVICE\TrustedInstaller In each case, enter the user group/name and click "Check Names" to get the correct internal name. --------------------------------------------------------------------------------------------------------- Some of the more common DCOM errors are: CLSID in Regedit: Name in Component Services Add Local Activation for: ----------------- -------------------------- ------------------------- {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} Runtime Broker NETWORK SERVICE {7006698D-2974-4091-A424-85DD0B909E23} Windows Insider Service dhubb {YOUR User ID} {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} Shell Service Host local service {F72671A9-012C-4725-9D2F-2A4D32D65169} {F72671A9-012C-4725....... system {316CDED5-E4AE-4B15-9113-7055D84DCC97} Immersive Shell dhubb {YOUR User ID} In each case, enter the user group/name and click "Check Names" to get the correct internal name.