Ok nothing fixed on Windows 11 22000.194 with 30.0.100.9922.
Just perfect.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
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?
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.
Just updating everyone on my experience :
On May (5 months ago) I reverted my Intel graphics driver (UHD 600) to 26.20.100.7985 version (as recommended here by @TurboTacho on February 23 2021 - https://answers.microsoft.com/en-us/windows/forum/all/desktop-windows-manager-dwm-memory-leakage-in/c2968fb0-ee26-4483-9f08-dfa19149cd24?page=2 )
Since then no leakage of dwm.exe (steady on about 100MB) even after hibernation.
Windows 10, 21H1
OS Build 19043.1237
8GB RAM
256GB SSD
Intel has already assured several times that they have fixed the leak on new versions of the drivers, but the problem is directly on the Windows OS side.
In May MS stated that they had fixed this problem in test build 21382, but even on the insider build these problems were observed, although not as often or the leakage stopped at 800 mb.
yesterday i have also installed intel driver (not HP driver) 30.0.100.9864 .. lets see what will happen.. dwm is currently eating ~200MB
I am testing Windows 11 since yesterday with Intel iGPU driver 30.0.100.9922 and it seems to not leak so far. I noticed some spiking in memory up to 250MB of DWM.exe but after some random time, it "reset" back down to 50mb, and then spiked again to 150MB and reset back. Seems maybe they implemented a workaround which will reset the memory in Windows 11? So far it behaves correctly. But I also had a week of no leak under Windows 10, so that could just be "luck" so far.
Intel also claimed they implemented a "fix" in 30.0.100.9922, but I already had tested 30.0.100.9922 under Windows 10 and it still leaked.