Runtime Broker (RuntimeBroker.exe) High Memory & CPU: How to Fix on Windows 10/11

Quick Fixes

Try these low-effort actions first; they resolve many cases in under two minutes.

1. Restart Runtime Broker — Ctrl+Shift+Esc → Task Manager → Processes → Runtime Broker → End task (it restarts automatically).
2. Disable Windows Tips — Settings → System → Notifications → uncheck Get tips and suggestions when using Windows.
3. Update Store Apps — Microsoft Store → Downloads → Check for updates → Update all.
4. Reset Store Cache — Win+R → wsreset.exe → Enter.
5. Reboot — especially after Windows/Store updates; recheck idle behavior for a few minutes.
6. Sanity Check the File Path — Task Manager → Details → right-click RuntimeBroker.exe → Open file location; it must be C:\Windows\System32\RuntimeBroker.exe.

Requirements & Safeguards

These keep changes safe and make rollbacks painless.

1. Administrator Account to adjust services, repair apps, and run system tools.
2. Create a Restore Point — Win+R → SystemPropertiesProtection.exe → Create.
3. Connectivity for Windows Update and Microsoft Store updates.
4. Optional Tools for deeper signal:
   1. Resource Monitor (resmon.exe)
   2. Event Viewer (eventvwr.msc)
   3. Windows Terminal (Admin) for DISM/SFC and PowerShell checks

Step-By-Step Guide: Diagnose and Fix the Cause

Work in order and check Task Manager after each step. Aim to identify the exact trigger with minimal disruption.

1. Verify the Binary and Digital Signature

   Rule out impostors and confirm you’re dealing with the Microsoft process.

   

   • Task Manager → Details → right-click RuntimeBroker.exe → Open file location → verify C:\Windows\System32\RuntimeBroker.exe.
   • Right-click → Properties → Digital Signatures → verify signer is Microsoft Windows.
   • If the path/signature is wrong, skip to Step 9 (Security Check) immediately.

2. Establish an Idle Baseline and Observe Triggers

   Measurement beats guesswork; capture idle behavior and correlate spikes with events.

   • Task Manager → Details → add columns CPU time and Working set (memory).
   • Idle the system for 5–10 minutes. Then trigger a few notifications (Mail/Calendar/Weather) and observe if spikes directly follow.

3. Disable Windows Tips and First-Run Experiences

   These suggestion pop-ups are frequent wake-up calls for Runtime Broker.

   

   • Settings → System → Notifications.
   • Uncheck Get tips and suggestions when using Windows.
   • Uncheck Suggest ways to get the most out of Windows and finish setting up this device.
   • Uncheck Show the Windows welcome experience after updates and when signed in to show what’s new and suggested.

4. Tame Windows Spotlight and Content Feeds

   Static backgrounds and fewer content calls reduce Broker activity.

   

   • Windows 11: Settings → Personalization → Lock screen → choose Picture (not Spotlight).
   • Windows 10: Settings → Personalization → Lock screen → Picture/Slideshow and uncheck Get fun facts, tips, and more…
   • If desktop Spotlight is enabled (Win11): Settings → Personalization → Background → Picture.

5. Limit Background Activity for Noisy Apps

   Over-eager Store apps are the most common culprit; restrict their background work.

   • Windows 11: Settings → Apps → Installed apps → choose app → Advanced options → Background app permissions: Never.
   • Windows 10: Settings → Privacy → Background apps → disable non-essentials.
   • Prioritize Mail & Calendar, Photos, Weather, News, Xbox Game Bar, Phone Link; observe Runtime Broker for a few minutes after each change.

6. Update Store Apps and Clear the Store Cache

   Buggy or stale app builds regularly cause recurring Broker spikes.

   

   • Microsoft Store → Downloads → Check for updates → Update all.
   • Win+R → wsreset.exe → Enter (Store will reopen).
   • Reboot if the reset didn’t auto-restart the Store; retest idle behavior.

7. Repair or Reset Problematic Store Apps

   Resetting a single app’s state is often enough to stop repeated wake-ups.

   • Settings → Apps → Installed apps (Win11) / Apps & features (Win10) → pick suspect app → Advanced options.
   • Click Repair; if no change, click Reset.
   • Relaunch and monitor Runtime Broker again.

8. Test the Time Broker Service (Advanced, Reversible)

   Background task churn flows through TimeBrokerSvc; toggling it is a clean diagnostic.

   

   • Win+R → services.msc → locate Time Broker / TimeBrokerSvc.
   • Properties → set Startup type: Manual → Stop → OK.
   • Use the PC normally for 10–15 minutes and observe.

   Note: Live tiles (Win10), Alarms, some push notifications, and Store app refresh may pause. Revert to Automatic (Delayed Start) when done testing.

9. Security Check for Masquerading

   An off-path or unsigned executable can mimic Runtime Broker and burn resources.

   

   • If the file isn’t in C:\Windows\System32 or lacks a Microsoft signature:
   • Start → Windows Security → Virus & threat protection → Scan options → Microsoft Defender Offline scan.
   • Remove detections, reboot, and re-validate the file path/signature.

10. Repair System Components

    Corruption in the component store or system files can manifest as odd Broker activity.

    • Open Windows Terminal (Admin) and run:

      dism /online /cleanup-image /restorehealth
      sfc /scannow

    • Reboot and reassess Runtime Broker at idle.

11. Collect Diagnostics for a Clear Verdict

    A little telemetry quickly highlights the offending app or subsystem.

    • Resource Monitor (resmon.exe) → CPU → Processes: watch RuntimeBroker.exe for 10–15 minutes at idle.
    • Event Viewer → Applications and Services Logs → Microsoft → Windows → AppModel-Runtime, BackgroundTaskInfrastructure, TimeBroker — look for repeated warnings/errors tied to a specific app.
    • Optional PowerShell spot-check:

    Get-Process RuntimeBroker |
      Select-Object Name, Id,
        @{Name='CPU_s';Expression={[math]::Round($_.CPU,2)}},
        @{Name='WS_MB';Expression={[math]::Round($_.WS/1MB,1)}}
    

Check Results & Measure Improvement

Confirm you fixed the cause, not just the symptom, and that stability holds.

1. Idle Baseline — after sign-in with no foreground UWP activity, Runtime Broker should settle under ~100 MB RAM and near 0% CPU.
2. Event Test — trigger Mail/Calendar/Weather notifications; spikes should be brief and subside quickly.
3. A/B Comparisons — compare before/after Steps 3–8 to identify which change helped.
4. Stability Window — let the system idle 15–30 minutes; there should be no prolonged CPU plateau or steady RAM climb.

Keep It Fixed: Stability & Hygiene

These practices prevent regressions after feature updates or app installs.

1. Update Windows and Store Apps regularly; many spikes trace to specific app builds.
2. Audit Notifications and Background Permissions after major Windows updates—defaults can be re-enabled.
3. Prefer Desktop Equivalents for persistently noisy Store apps.
4. Maintain Integrity — run sfc /scannow after large updates; keep a recent restore point.

Conclusion

High Runtime Broker usage stems from triggers—tips, Spotlight, or chatty apps—not from a broken OS.
By validating the binary, quieting suggestions, limiting background activity, updating or resetting apps, and (if necessary) briefly throttling TimeBrokerSvc, you can return the broker to low overhead and keep Windows responsive.

FAQ