Desktop Windows Manager (DWM) memory leakage in Windows 10 (Version 2004).

I've been experiencing the same issue, with DWM having a huge memory leak and grinding my laptop to a halt a few hours after a hibernation. The problem went away when I downgraded my Intel UHD 630 driver from version 27.20.100.8935 to version 26.20.100.8141, but I'd really rather have the latest drivers for security and compatibility purposes. I'm on Windows 10 Pro Version 10.0.18363 Build 18363 on a Dell G5 5587 with Dell BIOS 1.14.0,

Unfortunately, yes that's the only viable solution, at the expense of possibly unpatched security vulnerabilities, and reduced performance.

I've done a lot of extensive testing. It seems that hybrid sleep/hibernation is the root cause of this. It's a massive shame that Microsoft/Intel aren't seriously looking at this "resource wastage" problem, leaving it to the consumers at their own in circles.

One moderator in Intel forums mentioned that we had to bring up the issue to Microsoft forums for their attention, since they couldn't get the same issue as many of us are facing, replicated one-for-one. And Microsoft forums doesn't seem to be looking into this matter. What a huge cul-de-sac dilemma we have...

Another method is to disable hibernation or sleep, and perform a full shut down (Shift + Shut down). Hybrid shut down will also result in DWM.exe leaking badly too.

Actually, in my experience, the bloat happens when using the computer normally. The only thing that resolves for now is downgrading the Intel driver.

Update to this issue:

Apparently when the system goes to sleep/hibernate, the DWM process would massively inflate into the gigabyte region. This also applies to hybrid shutdown as compared to full shutdown. Running on Windows 10 build 19042.844, with the graphics driver as 27.20.100.9313 for Intel HD and 461.51 for Nvidia.

It's clear cut that there are more users facing this issue and Microsoft and Intel aren't looking into it. Apart from restarting DWM process via Task Manager for a short term resolution, there is no other way to resolve this. The issue would either return to bloat even more, or it's some issue with sleep/hibernation that's causing an excessive waste of onboard resources leading to performance and inefficiency.

PLEASE CREATE ANOTHER THREAD! This is not a chat place where you simply get solutions. This problem is different, and yours is different too. To create a new thread/question, click 'Ask a question' above this site.