Windows 10: Error: RuntimeBroker.exe

How to solve this error / problem?



Description



Faulting Application Path: C: \ Windows \ System32 \ RuntimeBroker.exe

Problem reference number

Problem name problem: MoAppCrash

Full name of the package: Microsoft.Windows.Cortana_1.13.0.18362_neutral_neutral_cw5n1h2txyewy

Application name: praid: runtimebroker07f4358a809ac99a64a67c1

Application version: 10.0.18362.1

Application timestamp: 4539d5a0

The name of the module with the error: SettingsEnvironment.Desktop.dll

Module version with error: 10.0.18362.387

Module timestamp with error: 10b406e4

Exception code: c0000005

Exception Offset: 000000000002b605

Version of the subject system: 10.0.18363.2.0.0.256.48

Locale ID: 1045

Additional information 1: 789a

Additional information 2: 789aeef51da05995f207dcf202006add

Additional information 3: 8c17

Additional information 4: 8c17ec3e550b29b30cbdc624f58b6172



Additional information about the problem

Package ID: 2231854cbf4d6555e46715be303ff626 (1470167709957223974)




***Modified title from: How to solve this error / problem?***

:)

 

Live tiles not working and runtimebroker errors

Hey sorry I did not reply earlier.

It seems live tiles are now fixed, the apps needed to be launched again for the live tiles to be fully reset it seems.

However I'm still getting the RuntimeBroker errors in the System log. It seems to happen when I open the start menu and stay on it for a few seconds (seems the timing is similar to the time needed for the live tiles to animate).

I don't have much clues about those RuntimeBroker errors, trying to fix the permission did not work so...

 

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

 

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?