Fix Desktop Window Manager (dwm.exe) High GPU Usage

High GPU usage from `dwm.exe` is abnormal when it stays high while the desktop is idle and causes stuttering, heat, fan noise, or rapid battery drain. Restart Windows, then update or roll back the graphics driver and test visual effects, overlays, HDR, browser hardware acceleration, and monitor connections one at a time.

Is dwm.exe really using too much GPU?

First confirm that dwm.exe is the process using the GPU and that Task Manager is not attributing an application's work to the desktop compositor.

Desktop Window Manager (dwm.exe) shows unusually high GPU usage, often with desktop stuttering, heat, fan noise, or reduced battery life.

Open Task Manager with Ctrl + Shift + Esc. On the Processes tab, expand Desktop Window Manager if necessary and check the GPU and GPU engine columns. Sort by GPU usage, then watch the process for a few minutes while no video, game, or animated browser page is running.

A brief rise while opening, moving, resizing, or minimizing windows is normal. GPU use can also rise during video playback, display-mode changes, transparency effects, or use of several monitors. Treat it as abnormal when usage remains high while the desktop is idle, especially if it coincides with stuttering, unusually high temperature, fan noise, flickering, or rapid battery loss.

Open the Performance tab for each GPU. A system with integrated and dedicated graphics can show activity on more than one adapter. The GPU engine column shows whether the work is occurring on GPU 0, GPU 1, or a video-processing engine. If another application is using most of the GPU, troubleshoot that application instead of targeting dwm.exe.

Record the display count, refresh rates, HDR state, recent driver changes, and active overlays before changing anything. You will use the same conditions to verify each fix.

What usually triggers high DWM GPU usage

DWM redraws the desktop when windows, displays, or visual effects change. Common causes include:

• A faulty, outdated, or recently changed graphics driver. It can mishandle composition, power states, HDR, or multiple outputs.
• HDR or a mismatch between HDR-capable displays. HDR conversion and color handling can increase compositor work, particularly when an HDR display is combined with an SDR display.
• High-refresh or mixed-refresh monitors. A 144 Hz or higher display, especially paired with another monitor at a different refresh rate, can expose driver or synchronization problems.
• Browser hardware acceleration. Video, animated pages, and GPU-rendered browser tabs can make the desktop compositor appear busy.
• Game, recording, chat, RGB, and hardware-monitoring overlays. These can inject windows or surfaces into the composition path.
• Several monitors, docks, adapters, or unusual resolutions. USB display adapters and docking stations add another driver layer.
• Transparency, animations, shadows, and other visual effects. These are usually inexpensive, but a driver problem can make them disproportionately costly.
• Malware impersonating the process. The genuine file is a Windows component, but a malicious executable can use a similar name.

This troubleshooting applies to supported Windows 10 and Windows 11 systems using integrated or discrete graphics. Most checks require only a standard account. Changing display, app, and visual-effect settings does not normally require Administrator access. Driver installation, system repair, and some security tools can require Administrator approval. Save open work before restarting, and create a restore point or other backup before major driver changes.

Before changing settings, confirm that the file is genuine. In Task Manager, right-click Desktop Window Manager and choose Open file location. The normal system file is under the Windows system directory, normally C:\Windows\System32\dwm.exe. A copy in a user profile, temporary folder, or downloads folder deserves a malware scan. Do not delete it based only on its name.

Fix dwm.exe high GPU usage safely

Apply these fixes in order. After each change, repeat the same idle or active test so you can identify what changed.

1. Restart Windows. A temporary compositor or driver state can clear after a restart. No special privilege is required. If usage stays normal during the same workload, stop here. If it returns immediately, continue.
2. Update or roll back the graphics driver. Open Settings, select Windows Update, install available updates, and restart. For a laptop, prefer the driver supplied by its manufacturer when available because it can include display-specific components. If the problem began immediately after a driver update, open Device Manager, expand Display adapters, open the adapter's Properties, select the Driver tab, and choose Roll Back Driver when available. Driver changes require Administrator approval.

Settings > Windows Update > Check for updates
Device Manager > Display adapters > [graphics adapter] > Properties > Driver

After restarting, confirm that the adapter has a normal GPU driver version and that idle usage is lower. If the installer fails, the adapter shows a warning icon, or usage is unchanged, continue without repeatedly reinstalling the same package.

3. Test Windows visual effects. Open the Start menu, search for Adjust the appearance and performance of Windows, open it, and select Adjust for best performance. Apply the setting and test again. This disables effects such as animation, shadows, and transparency without removing personal files. If DWM usage falls, re-enable effects one at a time to identify the trigger.

Control Panel > System > Advanced system settings > Performance > Settings > Visual Effects

No Administrator privilege is normally required. If this change has no effect, restore the original visual-effects setting before continuing.

4. Disable overlays and browser hardware acceleration temporarily. Turn off overlays in game launchers, chat clients, recording tools, GPU control panels, and monitor utilities. In your browser's settings, turn off hardware acceleration and restart the browser. Test the same pages or media that caused the problem. If usage drops, re-enable items one at a time. A browser can trigger the problem even when Task Manager highlights DWM instead of the browser.
5. Test HDR and the display arrangement. Open display settings, turn HDR off temporarily, and test. Then disconnect a secondary monitor, dock, adapter, or television and test with one display. If that helps, reconnect displays one at a time and try matching refresh rates and resolutions.

Settings > System > Display > HDR
Settings > System > Display > Advanced display

No Administrator privilege is normally required for these display changes. If usage falls only when HDR or a second monitor is removed, the likely cause is a driver, cable, dock, adapter, refresh-rate, or mixed HDR configuration rather than a damaged dwm.exe file.

How to confirm the fix worked

Use the same conditions before and after each change. If the issue appeared while browsing, reopen the same type of pages. If it appeared during a video, use a similar video. If it appeared with two monitors, test both monitors again. Keep Task Manager open on the Processes and Performance tabs.

A successful fix should produce much lower or intermittent DWM activity while the desktop is idle, without repeated stutter or an unexplained fan surge. GPU usage can still rise during window movement, video playback, HDR changes, or high-refresh animation. The goal is activity that matches the work being done, not zero usage.

Record these observations before and after each change:

• DWM GPU percentage at idle and during the workload that causes the problem.
• Which GPU engine is active.
• GPU temperature and fan behavior.
• Battery drain on a laptop.
• Stutter, flicker, black screens, or delayed window movement.

If disabling an overlay, HDR, a browser setting, or a monitor makes the problem disappear, restore the other settings and reintroduce that feature to confirm the result. If updating the driver changes nothing, test the manufacturer's previous stable driver when rollback is available. If every configuration produces the same high usage and the symptoms include display corruption or crashes, move to the escalation steps instead of repeatedly changing cosmetic settings.

What not to do, and when to escalate

Do not disable, delete, rename, or terminate dwm.exe as a permanent fix. Windows needs Desktop Window Manager to draw the desktop, and forcing it off can cause a blank screen, missing effects, or an automatic restart. Do not download a replacement dwm.exe from the web.

If the file is outside the Windows system directory, or if security software reports suspicious behavior, update Windows Security's security intelligence and run a full scan. A genuine system file should not need to be replaced manually.

Repair Windows only after display-driver and configuration tests have failed. Open an elevated Command Prompt and run these built-in checks in order:

DISM.exe /Online /Cleanup-Image /RestoreHealth
sfc /scannow

DISM should complete successfully, and System File Checker should report that it either found no integrity violations or repaired files. Restart afterward and retest. If either command reports an error, record the exact message instead of deleting system files or resetting Windows immediately.

Seek hardware support when the issue persists across clean driver changes, one-monitor testing, and a clean boot, or when you also see colored blocks, flickering, crashes, driver resets, overheating, or failures in other GPU-accelerated applications. Test another cable, port, display, or dock when practical. A failing GPU, unstable power supply, defective monitor, bad cable, or dock can resemble a DWM problem. For a laptop, use the manufacturer's diagnostics and support process. For a desktop, check cooling and GPU seating only if you are comfortable working inside the case and have disconnected power.

Conclusion

Start with Task Manager, then restart and test the graphics driver, visual effects, overlays, HDR, browser acceleration, and displays one change at a time. If high usage survives those tests or comes with visual corruption and crashes, run the Windows repair checks and arrange hardware diagnosis rather than disabling `dwm.exe`.

Frequently Asked Questions

Is high DWM GPU usage always a sign of malware?

No. Display drivers, HDR, high-refresh monitors, overlays, browsers, and multi-monitor setups are more common explanations. Verify that the file is the copy in the Windows system directory, then run a full security scan if its location or behavior is suspicious.

Can I end Desktop Window Manager in Task Manager?

Do not use that as a fix. DWM is required to compose the Windows desktop, and ending it can make the screen blank or force Windows to restart the process.

Why does DWM use more GPU with two monitors?

DWM must compose and synchronize more display surfaces. Different refresh rates, HDR modes, resolutions, docks, and display adapters can increase the work or expose a driver problem. Test one monitor, then reconnect the other after matching settings where possible.