it is doooomed :D
Desktop Windows Manager (DWM) memory leakage in Windows 10 (Version 2004).
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Anonymous
The infamous dwm.exe hogging lots of memory. FYI this is not a specific program issue. It just happens with any programs, activities randomly.
I'm getting really tired of killing dwm.exe every so often so that it will release the occupied memory. When is this going to be fixed? Is this ever going to be fixed even?
Windows for home | Windows 10 | Performance and system failures
Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.
156 answers
Sort by: Most helpful
-
Anonymous
2021-07-22T11:48:10+00:00 -
Anonymous
2021-05-24T03:39:12+00:00 Latest 21h2 build, with latest changelogs pretending "We fixed a memory leak that could result in DWM unexpectedly using a lot of memory over time."
And THIS is the result:
Enough is enough!
-
Anonymous
2021-05-12T17:49:26+00:00 can you share this script for restarting dwm.exe ?
There is no magic behind that.... it is just like opening task manager right click on dwm.exe and "kill process". So that is not really a workaround at all. You can kinda just let it leak to 1GB or something, and then kill the process or just restart windows. That is NOT a workaround at all.
@jeriksson82 no, what you described is just the normal madness of Windows 10. windows 10 will try with all might and power to work against you, replacing older drivers. It is possible, but you have to use some "tricks" in fulfilling it.
first you need to disable auto driver updates with gpedit, you need Windows 10 pro for that, and then also use this reg file:
https://www.tenforums.com/tutorials/48277-enable-disable-driver-updates-windows-update-windows-10-a.html You need to use both methods, and then even it is not working at all 100%. You need to also deactivate your LAN/WIFI while youre doing so. And kinda be a bit "lucky" of the timings.
You need to remove the old drivers with DDU: https://www.guru3d.com/files-details/display-driver-uninstaller-download.html (important)
But reverting back to <= 27.20.100.8476 is not really an option. It will prevent dwm.exe memory leak, but I found out why. Because it will break modern standby. I found out by pure luck about this, that my modern standby and C10 states were broken again. And I debugged it back to that it was causing by the Intel driver 27.20.100.8476
So THAT is the reason, why the memory leak is gone with <= 27.20.100.8476, because it will break standby.
Others had also said that disabling the dGPU would prevent the memory to happen, if your laptop has a dGPU. But this also will just break modern standby. So that is the root cause of this.
This brings back the old theory and perfectly sums up, that the leak is triggered by using standby and also hibernate (also fast startup).
-
Anonymous
2021-05-04T10:46:39+00:00 I have a feeling, this might be the right thread for me...
Just saying:
Just downgrade Intel GPU drivers to <= 27.20.100.8476 that will solve the issue.
-
Anonymous
2021-04-14T01:27:57+00:00 You're right! I actually mistook it for an official one. My absolute bad on there...that's probably the reason why their products were on a decline in support.