Windows 10: Event ID 10016, CLSID and APPID

This is unfortunately not the 5th or 100th such post on this topic in these forums.

But I've followed the advice on many of the threads, believe in my heart of hearts that I've done it right, and the problem is persisting.

At each computer restart, my event log logs the following four times:

Before I tried to fix it, I was getting it two times. So wow, what a (non) good fixer am I!

Solved Numerous event id 10016 errors win 8 pro 64 bit (yes, I know that is from a Windows 8 forum) is the most recent guidance I followed. It parallels the general guidance I have read here, which is:

• Open regedit
• Navigate to the keys being flagged (in my case, that is CLSID {6B3B8D23-FA8D-40B9-8DBD- B950333E2C52} and APPID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D})
• For each key, change the ownership, then grant "full control" permission to the corrected key owner
• Go into DCOM Config
• Edit the security properties of WPN Srumon Server to give proper launch and activation permissions to the user
• Reboot

And yet I'm failing. I reviewed the tutorial referenced above, and what I did, and that the changes took place, but I am still getting those errors on restart - again, same error repeated four times.

Can someone, specific to my own case described above, give me very clear step-by-step instructions on what to do?

I've even seen it said in this forum that simply deleting the keys that are being flagged has solved the problem for some people, although I would rather avoid that unless I get some assurance that the problem can be solved that simply.

:)

 

Event 7031 System Control Manager

There is a link in the Windows EightForums, where the procedure is offered to solve 10016 errors.

(thread: Numerous event id 10016 errors win 8 pro 64 bit)

Solved - Numerous event id 10016 errors win 8 pro 64 bit

I have followed that procedure and the errors for a few CLSID and APPID stopped.

The errors for CLSID {C2F03A33-21F5-47FA-B4BB-156362A2F239} and APPID {316CDED5-E4AE-4B15-9113-7055D84DCC97}, those I didn't manage to solve though.

=

 

Update failing

Hi SampathT,

the DCOM errors can be fixed quite easily by modifying some registry permissions and dcom permissions. Therefor you need to resolve the appid and clsid to an application/program name. Check out this site for a step by step tutorial:

Event ID 10016 The application-specific
permission settings do not grant Local Activation permission for the COM Server application with CLSID

The 2nd dcom error could be the cause of your 0x800F080D error.

Let me know if it helped

 

Hey asus2016,
4839DDB7-58C2-48F5-8283-E1D1807D0D7D is ShellServiceHost

You don't have to do the RegEdit stuff if you use PowerRun ... it's a standalone program (no install)
1. Download PowerRun - PowerRun v1.1 (Run with highest privileges)
2. Unzip the file and run PowerRun.exe or PowerRun64.exe
3. Add Dcom Config by clicking the + Gear Icon
Location - %SystemRoot%\System32\dcomcnfg.exe
Working Dir - %SystemRoot%\System32
Click Apply List
4. Double Click on the dcomcnfg.exe you just added to open Dcom Config
5. When in Dcom Config click View > Detail so you know you're working on the right App ID
6. Right Click on ShellServiceHost > Properties > Security Tab > Customize > Edit
7. Add LOCAL SERVICE (if need be) and check Local Launch and Local Activation
8. Close Dcom Config
9. Close PowerRun
10, Reboot PC

 

1. Please type Regedit into Start Menu.
2. Go to HKEY_Classes_Root\CLSID\*CLSID*.

Note: *CLSID* stand for the ID that appears in your event viewer error. In your case, it's {6B3B8D23-FA8D-40B9-8DBD- B950333E2C52}.

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. Click Apply and grant full control to Administrators.
6. Close the tab then go to HKEY_Local_Machine\Software\Classes\AppID\*APPID*.

Note: *AppID* is the ID that appears in your event viewer. In your case it's {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}.

7. Right click on it then select Permission.
8. Click Advance and change the owner to Administrators.
9. Click the box that will appear below the owner line.
10. Click Apply and grant full control to Administrators.
11. Close all tabs and go to Control Panel --> Administrative Tools.
12. Open Component Services.
13. Click Computer, click My computer, then click DCOM Config.
14. Look for the corresponding service that appears on the error viewer.

Note: For this step, look for the one that appeared at the right panel of the RegEdit. For example, the AppID {4839DDB7-58C2-48F5-8283-E1D1807D0D7D} registry key contains the "ShellServiceHost" data with a (Default) as a value name. Now look for "ShellServiceHost".

15. Right click on it then click Properties.
16. Click Security tab then click Customize in the Launch and Activation permissions section. Click Edit. Click Add. Add a Local Service. Then Apply.
17. Tick the Local Activation box.

 

FreeBooter, thanks - you have helped me solve this!

For others who may find this thread, which I'm now marking "solved," here are the two critical errors I had made:

• The registry keys that need to be edited will likely be different from one machine to the next. Note FreeBooter's comments below steps 2 and 6 above. You need to edit ownership and permissions to the keys showing in YOUR event viewer, not the ones documented in other people's posts!
• In fixing the AppID registry key, as FreeBooter says in Step 14, you need to note the service referenced by that key, then in DCOM Config, adjust the properties and permissions of THAT service - not the ones that might be documented in other people's posts

I do have one additional question for which I'll invite answers. One of the services I had to tweak was Runtime Broker. And the computer had TWO "Runtime Broker" services on it. On one of the services, the security customization permissions were grayed out, and, crossing my fingers, I tried the other service and I was able to make the changes. What's with the two Runtime Broker services?

 

You are very welcome @asus2016!