Quick fix: Runtime Broker (RuntimeBroker.exe) manages permissions for UWP apps. High RAM means an app is requesting many permissions. Open Task Manager → identify which UWP apps are running → close unnecessary ones. For chronic: Settings → System → Notifications → toggle off “Get tips and suggestions.” If specific app keeps Runtime Broker high: reinstall that app.
Runtime Broker is a system process. Normally uses 10-30MB RAM. Spikes to several hundred MB or 1GB+ mean an app is misbehaving. Identify the offending UWP app and reset / reinstall.
Affects: Windows 11 (and Windows 10).
Fix time: ~15 minutes.
What causes this
Runtime Broker mediates permissions between UWP apps and system resources. Each running UWP app maintains a permission session. High RAM happens when:
- Many UWP apps running simultaneously.
- A UWP app has a memory leak.
- Toast notifications, suggestions, telemetry overloading.
- Specific apps (Outlook UWP, Calendar, OneDrive) misbehaving.
Method 1: Identify and close offending apps
The standard route.
- Open Task Manager (Ctrl+Shift+Esc).
- Sort by Memory descending.
- Look for Runtime Broker entry. Click to expand if multiple instances.
- Right-click Runtime Broker → Go to details. Or End task for specific process.
- If you can’t identify which app is causing it: open Settings → Apps → Installed apps. Look at recently used / Microsoft Store apps.
- Close unused UWP apps:
- Settings, Calendar, Mail, Photos: close if not needed.
- OneDrive (if heavy): pause sync.
- Cortana: disabled in Win11 by default.
- Restart PC. Recheck Task Manager.
- If specific app keeps Runtime Broker high: reset / reinstall that app.
This is the standard fix.
Method 2: Disable tips and suggestions
For reducing telemetry-driven Runtime Broker activity.
- Open Settings → System → Notifications.
- Scroll. Untick:
- Show me the Windows welcome experience after updates and when signed in to show what’s new and suggested.
- Get tips and suggestions when using Windows.
- Open Settings → System → Notifications → Additional settings. Untick:
- Same options.
- Open Settings → Privacy & security → General. Untick all options including Show me suggested content in the Settings app.
- Open Settings → Personalization → Lock screen. Untick Get fun facts, tips, and more from Windows and Cortana on your lock screen.
- Reboot. Runtime Broker should be calmer.
- For chronic high RAM: continue to Method 3.
This is the telemetry reduction.
Method 3: Reset specific UWP apps
For chronic offender.
- Identify suspect app from Task Manager (Method 1).
- Open Settings → Apps → Installed apps.
- Find suspect app. Click three-dot menu → Advanced options.
- Click Reset. Clears app data and settings.
- If Reset insufficient: click Uninstall → reinstall from Microsoft Store.
- For Cortana: PowerShell removal:
Get-AppxPackage *Cortana* | Remove-AppxPackage - For OneDrive: pause sync (icon in tray → Pause syncing).
- For Outlook UWP: uninstall and use Outlook desktop.
- For all suspects: bulk reset / reinstall.
- For underlying Windows issue:
sfc /scannow+dism /online /cleanup-image /restorehealth.
This is the per-app reset.
How to verify the fix worked
- Runtime Broker in Task Manager: 10-50MB at idle.
- System feels less sluggish.
- Available RAM increased.
- No specific app spiking it.
If none of these work
If Runtime Broker still high: Driver issue: outdated driver triggering permission requests. Update GPU, Bluetooth, audio. Windows Update bug: known specific build issues. Install latest cumulative. For chronic background apps: Settings → Apps → per-app → Background apps permissions → Never. For Telemetry / Diagnostic Data: Settings → Privacy & security → Diagnostics & feedback → Required only. For Insider builds: known higher RAM use. Stay on Stable. For PCs with 8GB RAM: Win11 is tight on 8GB. Consider RAM upgrade. For specific apps that need permissions: live with the cost. Or replace with desktop equivalents.
Bottom line: Task Manager → identify which UWP app keeps Runtime Broker high. Close / reset / reinstall that app. Disable tips, suggestions, telemetry to reduce baseline. sfc /scannow for system-level fixes.