Windows 10: problems with runtimebroker

i needed to move a large file from my laptop to a pc. i didn't have a flash drive at hand so i removed my laptop's ssd and plugged it into the pc via an external adapter. it asked for administrator privileges to open the C: disk , which i confirmed with a "continue" button. after transferring the file i returned the ssd to the laptop. now, when i start windows, runtimebroker fails to start. also, the taskbar and the search bars aren't working for the same reason.

:)

 

Windows 10 1709 System Restore problems...

That seems to be an attempt at Option 2 in the tutorial, which requires you to
a. Boot to a command prompt (Did you?)
b. You then seem to be mixing steps 3,4 and 5, thus your command is incorrect.

I suggest Option 1 is easier.

If you still have problems, please repost listing each specific step and saying which option from the tutorial you are using. Thanks.

 

RunTimeBroker using 80% of CPU

Hi Lee, Thank you for the link. I tried some of the setting changes recommended but still the problem continued. I did the registry edit to disable RunTimeBroker as the author stated in the link you provided... he did not think RunTimeBroker a necessary
component. It is. When disabled you cannot enter any info into the Google or Bing search bar - and many web cam websites do not work at all. The default registry setting for RunTimeBroker on her machine was 3 (manual.) I set it to 2 (automatic) and the problem
is now gone. She gets an error message for the cam that caused all the trouble (that cam now is not supported - as opposed to it running and then RunTimeBroker running the system into the ground) but everything else is fine. Thank you for the help! Sandy
�

 

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?