The Windows 11 Widgets Board is the panel that slides out when you press Win+W, full of news headlines, weather, stocks, and sports scores. It is powered by a background process called Widgets.exe, and on some laptops that process develops an unhealthy appetite, consuming 10 to 25 percent CPU around the clock even if you have never opened the board in your life.
The mechanism is simple: the board refreshes its content on a schedule so it feels instant when opened. When a feed gets stuck or the board’s cache corrupts, that polite scheduled refresh turns into a frantic loop. Because the taskbar weather widget keeps the service alive, the CPU burn continues through your entire session, warming the laptop and draining the battery.
The fixes range from a simple cache clear to removing the taskbar widget to disabling the board entirely. Start with the lightest option and escalate only if CPU stays high.
Why this happens
- A stuck news or weather feed: A feed that fails to complete its refresh retries aggressively, looping CPU usage.
- Corrupted widgets cache: Damaged cached content makes the board re-download and re-render continuously.
- Taskbar weather widget keeping it alive: The taskbar widget pins the Widgets.exe process in memory for the whole session.
- Too many pinned widgets: Each pinned widget adds its own refresh timer and rendering cost.
- WebView2 rendering issues: The board renders in Edge’s WebView2 runtime; a broken runtime install causes excessive CPU.
- Aggressive refresh after sleep: Waking from sleep can trigger a backlog of missed refreshes all firing at once.
- Personalized content churn: Tailored news and ads refresh more frequently than a static weather widget would.
How to fix it
Work through these in order — diagnose first, then act.
Fix 1: Confirm Widgets.exe is the offender
Verify the process name and its CPU pattern before changing settings, so you know the fix actually worked.
- Press Ctrl+Shift+Esc to open Task Manager.
- Sort by CPU and look for Widgets.exe near the top.
- Watch for three minutes; the board should be mostly idle between refreshes.
- If it sustains double-digit CPU, proceed with the fixes below.
- Note the baseline so you can compare after each change.
Fix 2: Remove the taskbar widgets button
Removing the taskbar entry stops the always-on widget host that keeps Widgets.exe running all session.
- Right-click an empty area of the taskbar and choose Taskbar settings.
- Find the Widgets toggle near the top of the list.
- Switch Widgets to Off.
- The weather icon disappears from the taskbar immediately.
- Check Task Manager to see if Widgets.exe exits or calms down.
Fix 3: Clear the widgets board cache
A corrupted cache is a common cause of refresh loops. Clearing it forces the board to rebuild cleanly.
- Close the widgets board if it is open with Win+W toggling.
- Press Win+R, type %localappdata%\Microsoft\Windows, and press Enter.
- Look for widgets-related cache folders and rename rather than delete them as a safety step.
- Alternatively, sign out and back in, which clears in-memory board state.
- Re-check CPU after 15 minutes of normal use.
Fix 4: Repair the WebView2 runtime
The board renders its content through Microsoft Edge WebView2. A damaged runtime makes rendering far more CPU-intensive than it should be.
- Open Settings, Apps, Installed apps.
- Search for Microsoft Edge WebView2 Runtime.
- Click the three dots and choose Modify, then Repair.
- Let the repair complete and restart the laptop.
- Test Widgets.exe CPU with the board both closed and open.
Fix 5: Disable the Widgets Board with Group Policy
On Windows 11 Pro, Group Policy can disable the board entirely, which is cleaner than just hiding the taskbar button.
- Press Win+R, type gpedit.msc, and press Enter.
- Navigate to Computer Configuration, Administrative Templates, Windows Components, Widgets.
- Double-click Allow widgets and set it to Disabled.
- Click Apply and OK, then restart.
- Widgets.exe should no longer launch at all.
Fix 6: Uninstall the Web Experience Pack
The Widgets Board ships as the Windows Web Experience Pack. Removing it is the most thorough option on any edition.
- Open Terminal as administrator with Win+X.
- Type winget list web experience to confirm the package name.
- Run winget uninstall MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy carefully.
- Restart the laptop after removal.
- Verify Widgets.exe no longer appears in Task Manager.
Fix 7: Reinstall the Web Experience Pack
When repair does not help, a clean reinstall of the package that hosts the board replaces every corrupted file. Your pinned widgets reset to defaults, which is a small price for a quiet CPU.
- Open Terminal as administrator with Win+X.
- Run winget uninstall MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy to remove it.
- Restart the laptop after removal.
- Run winget install MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy to reinstall.
- Open the board once with Win+W, close it, and monitor CPU for an hour.
Fix 8: Reinstall the Web Experience Pack
When repair does not help, a clean reinstall of the package that hosts the board replaces every corrupted file. Your pinned widgets reset to defaults, which is a small price for a quiet CPU.
- Open Terminal as administrator with Win+X.
- Run winget uninstall MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy to remove it.
- Restart the laptop after removal.
- Run winget install MicrosoftWindows.Client.WebExperience_cw5n1h2txyewy to reinstall.
- Open the board once with Win+W, close it, and monitor CPU for an hour.
Closing
The Widgets Board is a nice-to-have that should never cost you double-digit CPU. For most people, removing the taskbar button or repairing WebView2 settles it; for those who never glance at widgets anyway, disabling the board entirely is the clean answer. Either way, verify with Task Manager that Widgets.exe is actually quiet afterward. Background CPU hogs rarely travel alone, so if the fans are still busy, check whether Teams autostart is also dragging down your boot. Background refresh loops rarely travel alone, so if the fans stay busy, audit your other startup consumers too. Microsoft documents background app controls in its Windows support hub . Background refresh loops rarely travel alone, so if the fans stay busy, audit your other startup consumers too. Microsoft documents background app controls in its Windows support hub . If the board is quiet but boot is still slow, disabling unnecessary startup apps is the next step worth taking.
