REGISTRY PERMISSIONS RESET AFTER REBOOT FULL
Launch and Activation Permissions > Edit > Add System and give it full control.Find the RunTimeBroker > Right Click > Properties > Security Tab.Navigate to Component Services > Computers > My Computer > DCOM Config.WinKey + X > Command Prompt (Admin) > Type in DCOMCNFG.Need to ensure DCOM permissions are setup Click okay a lot > Ensure you apply permissions to all child objects.(note you can only do this if you are a member of the administrators group and it is now the owner) if the administrators group is not listed add it and give it full control.If the local system administrators group is listed ensure it has full control.Please note if you are domain joined you’ll have to change where you are searching from to your local computer.At the top change the Owner to COMPUTERNAME\Administrators.WinKey + X > Command Prompt (Admin) > Type in Regedit.Open Regedit with Administrators privileges and navigate to the keys above (remember you have to do this twice).You will need to take ownership then set rights against two different keys. That said, I am not sure any change is actually required. To do this you have to modify permissions on two registry keys and then change the DCOM permissions. The fix is to give local administrators and System rights to the DCOM.
REGISTRY PERMISSIONS RESET AFTER REBOOT UPGRADE
The W10 upgrade exacerbated the issue due to missing security accounts after a W10 upgrade. It would appear that an application was installed on these machines at some point and that it did not do a proper install. This security permission can be modified using the Component Services administrative tool. To the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). The Error The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID It just an annoying thing but also slows down a windows 10 Login. Looks like the TrustedInstaller from a previous application and the RunTime Broker did not give System and Local Administrators permission during a Windows 10 upgrade. Ran into a lot of DCOM (DistributedCOM) errors on Windows 10 machines after upgrades.
0 kommentar(er)
