Windows 10: RuntimeBroker.exe ERROR when accessing System?

OK........

Win 10, 64bit machine all up to date

I first thought my Rollerball Mouse was acting up as I could not 'Copy & Paste' in any Microsoft Office 10 programs and also had 'problems' cutting or copying files in Windows Explorer from one folder to another.

Disconnected the Mouse and tried the Touchpad which also stopped working correctly.

I then opened 'System' with the Icon in the sidebar and got the error message that "RuntimeBroker.exe was not in the correct place to work".

Looked on Google and found that the 'advice' was to open Task Manager and scroll down Processes till I found Runtime Broker and STOP it, which I did.........

But.......

The dam problem keeps coming back, so I have to then go into Task Manager and stop it running, then go back to what I was using and everything is OK.

The advice on Google Search Answer was after closing down to Re-Boot, but I don't and all is once again OK.

So how can I 'Permanently' fix this frustrating 'problem' please?

Thanks

:)

 

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...

 

some .exe files hang


In the last 48 hours, some .exe files do not execute. If started from explorer, explorer hangs. No error messages. These files run on another Win 10 machine. Nothing obvious in the event viewer. I note that *.exe file cannot be deleted when the system is in this state. I must reboot to regain access to the .exe file. sfc /scannnow shows no errors.

Any suggestions?

 

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?