How to Fix Desktop Window Manager High GPU Usage in Windows

What DWM does and what its GPU use should look like

Since Windows 8 the whole desktop is drawn through dwm.exe: every window is rendered into a texture, and DWM combines them into the frame your monitor receives, adding transparency, rounded corners, shadows and animations along the way. There is no supported way to turn it off, and its idle footprint is tiny — on a healthy machine DWM shows single-digit GPU percentages and only spikes during video playback, window dragging or heavy animation work.

A constant 20–50% GPU on an idle desktop means something is feeding DWM constant dirty work. The prime suspects: a browser or Electron app playing video or running WebGL, live wallpapers, an overlay from a chat or GPU utility, a second monitor with a mismatched refresh rate, and last but not least the display driver itself. Add the GPU column in Task Manager (right-click the column headers) to confirm DWM is really the consumer — often the actual work belongs to another process, and DWM only presents the result.

• Update the graphics driver first — Intel, NVIDIA and AMD each fix DWM bugs in every other release
• Turn off transparency: Settings > Personalization > Colors > Transparency effects
• Match refresh rates on a multi-monitor setup, or at least test identical values
• Close browsers playing video and Electron apps (Teams, Discord, Slack) and watch DWM drop
• Toggle Hardware-accelerated GPU scheduling in Settings > System > Display > Graphics > Default graphics settings
• If Task Manager shows dwm.exe running from anywhere but C:\Windows\System32, scan for malware

The fixes in the order that pays off

Start with the display driver: update through Windows Update, or better through the vendor's own tool — NVIDIA App or GeForce Experience, AMD Software: Adrenalin Edition, or the Intel Driver & Support Assistant. A surprising share of constant-DWM-load reports ends with a driver update, and rolling back helps just as often when a brand-new release is the culprit. Reboot after installing, since the driver and DWM re-negotiate their contract only at boot.

Then reduce the visual load: Settings > Personalization > Colors turns off Transparency effects, and Settings > Accessibility > Visual effects tames animations — both cut the per-frame work DWM has to do, which matters most on integrated GPUs. If the load only appears with a specific app, disable hardware acceleration inside that app (browsers and Electron apps all have the switch) instead of blaming the compositor. Finally test HAGS: Settings > System > Display > Graphics > Change default graphics settings — flip Hardware-accelerated GPU scheduling, reboot, and keep whichever state calms DWM down.

When it is not DWM's fault at all

The GPU column in Task Manager tells you who owns the engine: if Video Decode or Video Processing runs hot while DWM shows low values, a browser stream is the real client, not the compositor. A dwm.exe crash-restart loop — the screen flickers black for a second — usually means an unstable GPU overclock or a failing driver rather than a Windows setting. On multi-monitor mixed-refresh setups, dragging a video window across screens makes DWM scale and convert every frame, which reads as high GPU on a chart but is honest work; the clean fix is matching refresh rates or upgrading to a cable that carries the full signal. If nothing helps, create a new local user account and check DWM there — a per-profile app is then the trigger.

Questions and Answers

Read next

All articles · FAQ