Windows 10: BUG dwm.exe Desktop Window Manager

Due to performance issues related to Microsoft Edge, which remains open in the background even after closing and consumes over 1GB of RAM when is not in use, I found that disabling and turning off the following settings:*Startup boost *Continue running background extensions and apps when Microsoft Edge is closed *Use hardware acceleration when availableIt causes *dwm.exe Desktop Window Manager to consume over 5-7GB RAM memory when Microsoft Edge is in useDone: Update drivers, run antivirus scan, run SFC scan... solutions?

:)

 

disabling dwm access denied

I don't know if it is even possible to disable DWM and still have Windows working normally but I found a list of solutions that can solve problems related to DWM:

How to fix Desktop Window Manager notification issues in Windows 10

 

Desktop Windows Manager(DWM) consuming more ram usage

Hey, i have tried all the troubleshooting steps suggested by you to toubleshoot DWM ram usage issue, but still the problem persist and I just close the DWM in task manager, but this is not permant solution I found, because I need to perform same task for every start. Is there any permant solution to this problem apart from the above ?

 

Finding username DWM-1 on the task manager

Hi mik07, Welcome to 10F! *Smile

Out of curiosity I looked at mine and also found a dwm-1 listed under user name:




The next thing I did was run this CMD: C:\Users\(your user name)>tasklist /v in a regular CMD prompt, the /v switch is for verbose, and I came up with:




So I started reading up on this dwm-1 and from what I can tell the desktop windows manager (dwm) has a lot of responsibilities when a computer is being used and it is a way for the dwm to differentiate between the services it provides. DWM.exe is the parent and DWM-1, 2, 3, and so on are the children.

In my case dwm-1 is running the notification window that slides out from the right side of the desktop. From this article:

It looks like as long as you see local or console in the session name your okay, but if you see remote logon via RDP (Remote Desktop Protocol) you'd better check into that especially if you weren't expecting a remote log-on.