You are viewing our Forum Archives. To view or take place in current topics click here.
Runtime Broker High CPU Usage
Posted:

Runtime Broker High CPU UsagePosted:

Kaneki
  • 2 Million
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
So I just updated to Windows 10 and now my computer constantly will hang around 30% cpu usage when I am idling, the culprit is Runtime Broker. Does anyone know how to fix it? I end the task, but it just comes back like 10 minutes later and uses up a good 20+% of my cpu.
#2. Posted:
Kaneki
  • V5 Launch
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Anyone know how to fix this?
#3. Posted:
i0S
  • WIP 5.1
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Open registry edit (just type regedit in the search bar since you have Windows 10) and go to this path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000003

in the part where it says "dword:0000003" change it to a 4. So in the end it should say HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000004

After that restart your machine and post back whether it worked.

Doing this will disable the process from starting, which will have no adverse affect on your system.
#4. Posted:
Kaneki
  • Christmas!
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Lucritius wrote Open registry edit (just type regedit in the search bar since you have Windows 10) and go to this path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000003

in the part where it says "dword:0000003" change it to a 4. So in the end it should say HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000004

After that restart your machine and post back whether it worked.

Doing this will disable the process from starting, which will have no adverse affect on your system.

regedit isn't coming up when I search for it.
#5. Posted:
i0S
  • Christmas!
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Alright hold the Windows key and press R to open run. Type regedit in there then do what I posted above.
#6. Posted:
Kaneki
  • V5 Launch
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Lucritius wrote Alright hold the Windows key and press R to open run. Type regedit in there then do what I posted above.

I tried a different method, I just disabled it in my services. Hope this works. Thanks for your help, if this doesn't work I will try your method.
#7. Posted:
i0S
  • Christmas!
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Alright let me know if it worked.
#8. Posted:
Kaneki
  • TTG Fanatic
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Lucritius wrote Open registry edit (just type regedit in the search bar since you have Windows 10) and go to this path:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000003

in the part where it says "dword:0000003" change it to a 4. So in the end it should say HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TimeBroker] "Start"=dword:00000004

After that restart your machine and post back whether it worked.

Doing this will disable the process from starting, which will have no adverse affect on your system.

Yep didn't work, the program still opens regardless.
#9. Posted:
Kaneki
  • V5 Launch
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
Status: Offline
Joined: Dec 12, 201013Year Member
Posts: 4,019
Reputation Power: 173
I had to revert back to the insider preview builds, I will try again to install Windows 10 later, hopefully I don't still have an issue with runtime broker.
EDIT: And now It won't let me update my system, it just says Windows is up to date. UGH....
#10. Posted:
i0S
  • Christmas!
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Status: Offline
Joined: Jun 17, 201112Year Member
Posts: 2,561
Reputation Power: 231
Sorry man :/ I feel like I'm one of the very few people who hasn't had any problems with 10 yet
Jump to:
You are viewing our Forum Archives. To view or take place in current topics click here.