Windows 10: runtimebroker.exe

runtimebroker.exe keep crashing constantly, how to stop or remove it

:)

 

RuntimeBroker problems!

I never seen a RuntimeBroker issue. I'm suggesting you to try basic fixes. Did you run sfc /scannow and Dism /Online /Cleanup-Image /ScanHealth and Dism /Online /Cleanup-Image /RestoreHealth ? What antivirus you have? Is it up to date?

 

On Windows 10 Pro x64, DCOM Config shows two RuntimeBroker entries

After successfully correcting some 10016 errors that pointed to RuntimeBroker permissions, I've ended up with two (2) entries in DCOM Config for RuntimeBroker.

After several days, the 10016 errors have not reappeared and my system seems to be running fine but there remains two RuntimeBroker entries in DCOM.

SFC /scannow was no help nor did DSIM find anything (I didn't think either would)

Any suggestions?

 

Event ID 10016

Solved Numerous event id 10016 errors win 8 pro 64 bit

Here is the basic outline ...

1. Search the registry for the CLSID
2. Make note of the Default Value, which is the name (ex. ShellExperienceHost, RuntimeBroker) you're going to look for in DCOM
3. Change the Owner to Administrators
4. Give Administrators Full Control
5. Repeat steps 1-4 for the APPID
6. WinKey + s > type in component services > click on Component Services in list
7. Component Services > Computers > My Computer > DCOM Config
8. Change the View to Details
9. Find the name from step 2 (ex. ShellExperienceHost, RuntimeBroker)
10. Right Click on the Name > Properties
11. Select the Security Tab
12. Launch & Activation Permissions > Click Edit
13. Look for the offending user from the 10016 (ex. System, Local Service) and make sure it has the activation requested (ex. Local Activation). If the offending user does NOT exist, you have to add it and give it Local Launch and Local Activation
14. Click Apply
15. Close DCOM and Regedit
16. Reboot PC

Note: Make sure you understand the steps before doing them