Local Activation Permission  

Andre2210 said:

i got no new errors after applying the fix and making those permissions "standard" .
it ads the "System" in permission list too, and removes a Admin or User that was listed
i don't think that one was important.
might have been my own Admin name in another code.
System was important to ad to the list.

everything works fine on permissions "standard" and system log is clean of error.
i also did a recent fresh install of windows 10 via restore options and tool it downloads.
Brought me directly to build 14393 again.
so figures the clean error free list i guess.

"The CDP activity Store" was the only problem for me , not anymore now.

I have one system with this issue after a Clean install of AU .222 on the Weekend , and it does not know what dcomcfg is when i use the Run DBX , but I found it In the Windows Administration Folder (not System) on the Start Menu (Component Services) thanks to another post here, however once I open the Properties of the F7267xxxxxxxx Object and then the Security Tab there is no "Standard" , do you mean switch all 3 to "Use Default" ?

EDIT ...solved ...see next post.......

Found this on another thread from @Vaio7 and @f14tomcat and Borgus which helped me figure it out........

here with a bit of a re-write.....

I now realise I followed this info found in several posts on TenForums
to the correct locations for the 10016 Error involving

CLSID {8D8F4F83-3594-4F07-8369-FC3C3CAE4919}
and APPID {F72671A9-012C-4725-9D2F-2A4D32D65169}

1. Open Regedit.
2. Go to HKEY_Classes_Root\CLSID\*CLSID*.
Note: *CLSID* stand for the ID that appears in your event viewer error.
3. Right click on it then select permission.
4. Click Advance and change the owner to Administrators. Also click the box that will appear below the owner line.
5. Apply full control.
6. Close the tab then go to HKEY_LocalMachine\Software\Classes\AppID\*APPID*.
Note: *AppID* is the ID that appears in your event viewer.
7. Right click on it then select permissions.
8. Click Advance and change the owner to Administrators (not Administrator).
9. Click the box that will appear below the owner line.
10. Click Apply and grant full control to Administrators. (leave REGEDIT open)
10a. If the Default Value for the Key = "Value not set" see the note below instead of going to 11

11. Press Windows key and R, to bring up the RUN box.
12. Type dcomcnfg and <enter>
13. Click Computers, click My Computer, then click DCOM Config.
14. Look for the corresponding service (in the Name column) that appears as the *AppID* (F72671A9.....)
15. Right click on it then click properties.
16. Click security tab then click Customize in the Launch and Activation permissions section if needed. Click Edit. Click Add. Type Local Service in Object Names. Click Check Names (Ok?) Then OK button.
17. Select Local Service Under User Names and Tick the Local Activation box.
(Local Launch should be checked already)
18. Click OK , then OK again and Close Component Services.
19. Now go back to regedit and for the CLSID & APPID where you changed ownerships and
revert them back to the default TrustedInstaller by Copy and pasting this :

NT SERVICE\TrustedInstaller

***note
If this does not work and you still get the 10016 Error on Booting it is likely due to the fact that the usual fix cannot be made because the Default isn't listed (ie seen as "value not set") for Local Machine registry entry
App ID {F72671A9-012C-4725-9D2F-2A4D32D65169}. Thus, it's unknown what DCOMCNFG item to open, so that Local Service and Local Activation can be added. So the fix here is to just delete the Key instead after Exporting it for Safety, and then on reboot open Dcom again and you will be prompted to update a missing entry, (Say Ok) . Thereafter the AppID reappears in the registry and its default is listed as CDP Remote Text Handler and No further edits/additions need be made to that entry in Dcom or the Registry.

*****to delete the key you will need to take Ownership as above 1st if you skipped down to this Note


KB

Other possible location of F72671A9-012C-4725-9D2F-2A4D32D65169 is HKEY_CLASSES_ROOT\AppID\

So far so good on reboot I think ...how do you clear the log and start it clean again ?

it looks like I have the CAPI2 error as well.

Thanks guys

KB

**Edit1: the Win+R Key command is dcomcnfg not dcomcfg as per Borgus's Post for the DCOM APP.

Also see:
EventID 10016 - NT AUTHORITY\SYSTEM - name not found

Kbird said:

Found this on another thread from @Vaio7 and @f14tomcat which helped me figure it out........ here with a bit of a re-write.....


Now Event Id 10016 can be easily fixed. When you look @ the Event Viewer description there is a CLSID and an AppID involved.

You will have to open regedit with admin rights, (if you are Admin you should have them) navigate to HKey>ClassesRoot\CLSId and when you find the id in question, right click > Permissions and temporarily change owner from TrustedInstaller to Administrators.
(note plural..with an s )

Same for the HKEY>LocalMachine\Appid. ( as seen in event log)

Now open Component Services, ( in Windows Admin. Tools) >Computer> My computer> DCOM config and find the Registry keys above for the exact Component service, right click >Properties>Security tab, then open the Launch and Activation permissions with the Edit button

and depending on what the Event Viewer description said about if it was a User (eg NT Authority\System.) ....or if it's a Local Service ,
click Add, add one of the two (type System) and enable the box " Local Activation". >ok/apply

Now go back to regedit and for the CLSID & AppID where you changed ownerships revert them back to the default TrustedInstaller.

copy and pasting this from the other thread worked for me NT SERVICE\TrustedInstaller

Reboot and Error 10016 is gone forever.


So far so good on reboot I think ...how do you clear the log and start it clean again ?

it looks like I have the CAPI2 error as well.

Thanks guys

KB


edit I just found @lx07 has posted a Script to help with this tooWindows 10 Event ID 10010 and 10016 Errors With DistributedCOM - Page 2 - Windows 10 Forums

@Kbird

To clear the event logs, look at Shawn's tut:

Event Viewer - Clear All Event Logs in Windows - Windows 10 Forums

----------------------------------------------------------------------------------------------------------------

CAPI2 error can be fixed by running this command with Admin Command line. NOT Powershell! NO spaces. One continuous line.

Code:

sc sdset MSLLDP D:(D;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;BG)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SY)(A;;CCDCLCSWRPDTLOCRSDRCWDWO;;;BA)(A;;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;SO)(A;;LCRPWP;;;S-1-5-80-3141615172-2057878085-1754447212-2405740020-3916490453)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

Here is the supporting link:

Error source CAPI2 id 513 - Cryptographic Services failed while processing the OnIdentity() call in the System Writer Object

Kbird said:

Thanks Dick , I should of known Brink had a Tutorial on clearing Logs :)

And it seems at least so far that the above Command has worked for CAPI2 as well.

just need to figure out what a AppModel Runtime Error is now :) any idea what a windows communication app 17.xxxxx 0x490 error is about?


KB.

Not sure, I think I've seen that referenced with Store Apps failing to install. Like Groove Music and Movie App. All I can remember. When I just Googled it, first result back was YOUR post here on TF!

Kbird said:

Oh well you did better than me :) I got nothing on google...

I usually un-install Apps like Twitter , Get office etc from the start menu , that I never use ( and M$ kindly puts back every Major Update) , I wonder if that is the issue.... ie not a true uninstall maybe...

I briefly got another 10016 Error (different App ID etc) but after a few Reboots it has not reappeared yet.


KB.

I think you've got the major ones. MS & DCOM can be mysterious. A lot of the time, they turn out to be harmless or fix themselves after a few retries. They're a nuisance to see, though.

A hint...after you have found them in Regedit, add the CLSID key to the Regedit favorites (top of screen). Then if you need to go back, it's quick...and it's a record of what you changed.