Skip to content

RuntimeBroker.exe burns CPU for no clear reason

RuntimeBroker brokers permissions for modern apps. A single bad UWP app or widget can drive it crazy.

Try this first

  1. 1Open Task Manager and sort by CPU, identify which broker instance
  2. 2Check which apps recently launched or which widgets are active
  3. 3Turn off background apps you do not use in Privacy settings
  4. 4Update or remove the offending app, often a news-feed widget

When to bring us in

For persistent high CPU after cleanup: run DISM/SFC, OS files may be corrupt.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.