Desktop Window Manager — dwm.exe — is the process that draws everything you see: every window, the taskbar, transparency, and animations. It should sip GPU: 1–5% at idle on integrated graphics. When Task Manager shows it at 30, 50, or even 80% GPU, the whole laptop stutters — mouse movement feels laggy, videos tear, and the chassis gets hot while you are barely doing anything.

On HP laptops, DWM spikes cluster around three triggers. The first is graphics driver problems: HP’s customized Intel, AMD, or NVIDIA drivers falling behind Windows updates, or a Windows update replacing the HP driver with a generic one. The second is the effects stack — transparency, animations, and the widgets board all bill their rendering cost to DWM. The third is a stuck app window forcing constant repaints, like a misbehaving Electron app or a browser tab with runaway animations.

DWM cannot be killed — Windows needs it — so the fix is always about reducing what you ask it to render or repairing the driver underneath it. Work through these in order. For the general step-by-step version, see DWM high GPU step by step .

Why this happens

  • Outdated or mismatched graphics drivers: a driver that lags behind Windows builds makes every compositing operation expensive.
  • Transparency and animation effects: acrylic blur and animations are billed directly to DWM’s GPU usage.
  • Stuck app forcing repaints: a hung or animating window makes DWM recompose the screen continuously.
  • Widgets board rendering: the widgets overlay renders through the compositor at DWM’s expense.
  • Multiple high-refresh or 4K displays: more pixels and higher refresh rates multiply DWM’s per-frame work.
  • Hardware-accelerated GPU scheduling issues: a misconfigured scheduling setting can inflate DWM overhead on some systems.
  • Corrupted DWM state after updates: a feature update can leave the compositor in a degraded state until reset.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Confirm DWM is the problem

Check which GPU engine DWM is using — it tells you whether the load is compositing or something stranger. The GPU engine column also reveals whether copy-engine load is masquerading as 3D load.

  1. Open Task Manager > Details, right-click the column headers, and add GPU and GPU engine columns.
  2. Find dwm.exe and note its GPU % and engine (usually 3D).
  3. Sustained high 3D usage at idle confirms a compositing problem, not a misreport.

Fix 2: Turn off transparency and animations

This is the fastest relief: it directly removes the most expensive things DWM renders. This step alone resolves the majority of DWM complaints on integrated graphics.

  1. Open Settings > Accessibility > Visual effects and turn off Transparency effects and Animation effects.
  2. Close the widgets board (Windows key + W, then close it) and disable it in taskbar settings.
  3. Watch Task Manager for two minutes; DWM GPU should collapse toward idle. Full details: disable transparency effects .

Fix 3: Update graphics drivers from HP

HP validates driver combinations per model, so their graphics driver is the safest first update. Find it at HP support . Prefer HP’s driver first; fall back to the GPU vendor’s only if HP’s is outdated.

  1. Go to HP support , enter your model, and download the latest graphics driver.
  2. Install it, choosing Clean install if the installer offers the option.
  3. Reboot and compare DWM GPU usage at idle before and after.

Fix 4: Find the app forcing repaints

One bad window can keep DWM busy. Isolate it by elimination. A browser tab running a hidden video or animation is the classic invisible culprit.

  1. Close all apps and confirm DWM idles low.
  2. Reopen apps one at a time, watching DWM’s GPU after each.
  3. When usage jumps, update or replace that app — browsers with rogue tabs and Electron apps are frequent offenders.

Fix 5: Toggle Hardware-accelerated GPU scheduling

On some systems this setting reduces DWM overhead; on others it increases it. Test both states. Some systems need two reboots for the scheduling change to fully settle.

  1. Open Settings > System > Display > Graphics > Change default graphics settings.
  2. Toggle Hardware-accelerated GPU scheduling to the opposite of its current state.
  3. Reboot (required) and measure DWM GPU at idle for a few minutes.

Fix 6: Reset the compositor with a clean boot

A clean boot isolates whether a third-party service is driving DWM’s workload. Be patient: halves-of-halves converges on the culprit in about four reboots.

  1. Press Windows key + R, type msconfig, and on the Services tab hide Microsoft services and disable the rest.
  2. In Task Manager’s Startup apps tab, disable all entries, then reboot.
  3. If DWM is calm in the clean boot, re-enable services in halves to find the trigger.

Fix 7: Reinstall the graphics driver cleanly

When updates do not help, a full clean reinstall removes corrupted driver state. DDU is the nuclear option for drivers; use it when normal installs do not stick.

  1. Download Display Driver Uninstaller (DDU) and the latest HP graphics driver.
  2. Boot into Safe Mode, run DDU to remove the graphics driver completely.
  3. Reboot normally, install the HP driver fresh, and verify DWM idles at 1–5% GPU.

Fix 8: Disable Multiplane Overlay (MPO)

Multiplane Overlay lets the GPU compose certain window layers in hardware, but buggy MPO implementations in some drivers cause DWM to work harder, not less — showing up as mysteriously high dwm.exe GPU usage. Disabling MPO via the registry forces the classic composition path, which is often cheaper on affected systems.

  1. Open regedit and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Dwm.
  2. Create a DWORD named OverlayTestMode and set it to 5.
  3. Reboot and measure dwm.exe GPU at the same idle desktop.
  4. If there is no improvement, delete the value to restore default behavior.

Closing

DWM high GPU on an HP laptop is the compositor telling you something is wrong underneath it: an outdated driver, an effects stack the iGPU cannot afford, or one app forcing endless repaints. Cut the effects first for instant relief, then update the HP graphics driver for the permanent fix. A healthy DWM idles at a few percent — anything more deserves investigation.

Frequently asked questions

What does dwm.exe actually do?
Desktop Window Manager is the compositing window manager for Windows. Instead of letting each app draw directly to the screen, DWM has every window render to an off-screen buffer, then composites them together — adding transparency, shadows, animations, and scaling — into the final image. That is why all visual effects costs show up under dwm.exe rather than under individual apps.
Can I end or disable dwm.exe?
No — not on any modern Windows. DWM is a critical system process; Windows 8 and later cannot run the desktop without it, and Task Manager will not even offer an End task option that sticks. Any guide claiming to disable DWM is describing ancient Windows 7 tricks. The correct approach is reducing its workload or fixing the driver underneath it.
Why is DWM GPU usage high when nothing is open?
Because ’nothing open’ still includes the desktop, taskbar, wallpaper engine, widgets, and any background app with a hidden window. Transparency effects, animated wallpapers, the widgets board, and notification animations all render continuously. If usage is high with a truly bare desktop, suspect the graphics driver or a stuck background window forcing repaints.
Does high DWM usage drain battery?
Yes. GPU activity prevents the processor package from entering its deepest idle states, and on laptops the GPU and CPU share a thermal and power budget. Sustained DWM load of 30%+ can visibly shorten battery life and keep fans spinning. Bringing DWM back to its normal 1–5% idle is one of the more effective battery-life fixes on affected laptops.