Windows 10: High CPU on Runtime Broker, Service Host: SysMain and Disk Defragmenter.

Discus and support High CPU on Runtime Broker, Service Host: SysMain and Disk Defragmenter. in Windows 10 BSOD Crashes and Debugging to solve the problem; apparently the service host: disk defragmenter, runtime broker and service host: SysMain are using a lot of cpu on my laptop. i also have 6 runtime... Discussion in 'Windows 10 BSOD Crashes and Debugging' started by DonaldDiehl, Sep 19, 2020.

  1. DONALDDIEHL
    DonaldDiehl Win User

    High CPU on Runtime Broker, Service Host: SysMain and Disk Defragmenter.


    apparently the service host: disk defragmenter, runtime broker and service host: SysMain are using a lot of cpu on my laptop. i also have 6 runtime brokers. what do i do?

    :)
     
    DonaldDiehl, Sep 19, 2020
    #1
  2. BLAINEBRADFORD
    BlaineBradford Win User

    Runtime Broker high CPU usage

    I am running Windows 10 Pro (Version 1511 for x64, update KB3149135) and had problems with Runtime Broker.exe using anywhere from 30% to 90% of my CPU. Disabling hints and removing OneDrive did not help me, but I found the advice in this article helpful.
    I used the PowerShell commands as admin and uninstalled all of the suggested apps save the windows store. Not sure which one finally did it but I don't really care as long as I'm not running at 50 degrees Celsius constantly.

    Here is the URL: How To - Fix the Runtime Broker High CPU Usage Error
     
    BlaineBradford, Sep 19, 2020
    #2
  3. OMIDREZA
    Omidreza Win User
    Runtime Broker high CPU usage

    I found that if I just don't minimize the groove music app then runtime broker doesn't eat my cpu. So temporarily I don't minimize the groove music but it's very ridiculous that minimizing the app cause cpu usage by runtime broker. I hope microsoft fix
    this issue with grove music.
     
    Omidreza, Sep 19, 2020
    #3
  4. SELSMORAN
    selsmoran Win User

    High CPU on Runtime Broker, Service Host: SysMain and Disk Defragmenter.

    Runtime Broker consuming laptop CPU


    Hi. Runtime Broker starts-runs and consumes allmost
    all CPU-time.
    Laptop fan keeps running until I stop the process.
    Tried different suggestions but it still keeps starting.
    E.g. disabling time broker service.
    Problem still occurs for some reason.
    Please help with how you solved it.
     
    selsmoran, Sep 19, 2020
    #4
Thema:

High CPU on Runtime Broker, Service Host: SysMain and Disk Defragmenter.

Loading...

  1. High CPU on Runtime Broker, Service Host: SysMain and Disk Defragmenter. - Similar Threads - High CPU Runtime

  2. Service Host: Disk Defragmenter always popping up on startup and using CPU?

    in Windows 10 BSOD Crashes and Debugging
    Service Host: Disk Defragmenter always popping up on startup and using CPU?: This began today, where every time I would turn on my PC, this service would open and start using up CPU power, I don't know what's causing it. Should I be concerned?...

  3. Service Host: Disk Defragmenter always popping up on startup and using CPU?

    in Windows 10 Gaming
    Service Host: Disk Defragmenter always popping up on startup and using CPU?: This began today, where every time I would turn on my PC, this service would open and start using up CPU power, I don't know what's causing it. Should I be concerned?...

  4. Service Host: Disk Defragmenter always popping up on startup and using CPU?

    in Windows 10 Software and Apps
    Service Host: Disk Defragmenter always popping up on startup and using CPU?: This began today, where every time I would turn on my PC, this service would open and start using up CPU power, I don't know what's causing it. Should I be concerned?...

  5. Service Host SysMain causing High CPU and Memory usage in Windows 10

    in Windows 10 News
    Service Host SysMain causing High CPU and Memory usage in Windows 10: [ATTACH]A lot of users have reported that the SysMain process (earlier known as Superfetch) […] This article Service Host SysMain causing High CPU and Memory usage in Windows 10 first appeared on TheWindowsClub.com. read more...

  6. Service Host: SysMain using high memory.

    in Windows 10 BSOD Crashes and Debugging
    Service Host: SysMain using high memory.: So Service Host: SysMain is using high ram for some reason 96%. Not only that but other Applications are using higher ram than usual, im not sure what this means. All of this happened out of no where, if you know what this means please let me know. Thank you....

  7. High CPU on Runtime Broker, Service Host: SysMainand Disk Fragmenter.

    in Windows 10 BSOD Crashes and Debugging
    High CPU on Runtime Broker, Service Host: SysMainand Disk Fragmenter.: apparently the disk fragmenter, runtime broker and service host: sysmain are using a lot of cpu on my laptop. i also have 6 runtime brokers. what do i do?...

  8. Service host agent activation runtime high cpu and power consumpion

    in Windows 10 BSOD Crashes and Debugging
    Service host agent activation runtime high cpu and power consumpion: Windows 10 version 2004 19041.508 After updating to 2004 from 1909. my laptop battery goes insane as it no longer last for more than 5 hours like it used to be. I checked task manager and found that theres a service called Agent Activation, this service constantly use 8-15%...

  9. Runtime broker and Windows shell Experience Host high cpu usage

    in Windows 10 BSOD Crashes and Debugging
    Runtime broker and Windows shell Experience Host high cpu usage: Solutions I already tried: * HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker Changing Start into 4 * Removed the slideshow notification * Closed all my personal tray apps * Performed an offline scan using Windows defender * Performed a normal scan using...

  10. Runtime Broker using high memory and cpu usage

    in Windows 10 Support
    Runtime Broker using high memory and cpu usage: after upgrading to windows 10 my laptop fan always working fast ... when i checked this issue, i see runtime broker in task manager with high resourse usage ... when i click on end task, everything be normal... but runtime broker run itselft immediately ... i googled this...