SOLVED Event id 10016 Runtime Broker

[Bob53]

Hi,
Have been having this issue for some time. See link below
https://www.windows10forums.com/articles/event-id-10016-distributedcom.47/

Ran through the excellent procedure which has corrected this problem. Only issue now is I get same event id now on boot up but this time the app-id relates to Runtime Broker.
Do i need to run through similar procedure again or will that just result in a another different problem?
Actual error i am receiving-.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{D63B10C5-BB46-4990-A94F-E40B9D520160}
and APPID
{9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

 

[Regedit32]

Hi Bob,

You'll need to take ownership as before of the two keys you posted and then go make the necessary changes in the DCOM section also as before.

Alternatively, I could post a script you can copy and paste into an elevated PowerShell window which will take care of the ownership issue in the Registry; leaving you with the task of running just the Component Service app to make the DCOM changes necessary.

Let me know if you want the script; otherwise I'll let you do it manually as you have all ready done on another issue.

 

[Bob53]

Hi,
Thanks for your reply.
Apologies but that particular error appears to have cleared itself.
Just seeing the odd 10016 now relating to WSearch but only about 6 a day.
Not sure what is triggering them though.
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{9E175B6D-F52A-11D8-B9A5-505054503030}
and APPID
{9E175B9C-F52A-11D8-B9A5-505054503030}
to the user DESKTOP-VP49S44\jdwal SID (S-1-5-21-511602772-3162397508-2104593841-1002) from address LocalHost (Using LRPC) running in the application container Unavailable SID (S-1-15-2-1368704970-3516957338-4031622612-1138795767-1799457103-1893835786-3736290776). This security permission can be modified using the Component Services administrative tool.

Also seeing lots of ID 3104 ., about 30 a day.
Are these related?

May be better to mark as solved and create a new post if these cause any problems but as yet all running ok.

 

[Regedit32]

Hi Bob,

Glad the other Runtime Broker issue resolved itself. Often they do, and there is no need to go to the extremes of editing the DCOM's.

You are correct in assuming the 3014 error is related to your Windows Search issue popping up.

The 3014 error is an Event Gather Exception for the Windows Search indexing. I'm not able to tell you what precisely triggered that error; it could be as simple as you shutting down the computer while indexing was taking place, or coincidentally deleting a file as it was being indexed.

Generally, the simplest way to resolve the 3014 error is to rebuild the Index by:

• Pressing windows key and S key together to give focus to the Search box
• Typing Indexing Options then pressing Enter key
• Clicking the Advanced button in the Indexing Options window
• Then in the Advanced Options window that opens clicking the Rebuild button in the Troubleshooting pane
  
  Note: That will delete the current index and build a new one. That can take quite some time depending on how large your hard drive is, and how much information Is stored on it.

Regards,

Regedit32

 

[Bob53]

Thanks for your support.