Desktop Window Manager

By on June 1, 2012 12:33:57 AM from Stardock Forums Stardock Forums


Join Date 05/2012


     I have just started to use the stuff in Object Desktop. Blinds and FX were fine, but as soon as I applied a package using the iconpackager, my disk started thrashing and everything went real slow. Task manager showed that a process called dwm.exe or Desktop Windows manager and explorer were the culprits. is this a known issue?



Locked Post 4 Replies
Search this post
Subscription Options

Reason for Karma (Optional)
Successfully updated karma reason!
June 1, 2012 8:14:14 AM from WinCustomize Forums WinCustomize Forums


 What is dwm.exe And Why Is It Running?

You are no doubt reading this article because you are wondering why this dwm.exe process is taking more memory than you think it should, and you are curious what it does. Thankfully for you, we have the answer.

So What Is It Anyway?

Desktop Window Manager (dwm.exe) is the compositing window manager that gives you all those pretty effects in Windows Vista: Transparent windows, live taskbar thumbnails (that you can resize now), and even the Flip3D switcher that you can disable and replace with Switcher.


What happens in Vista is that applications write the picture of their window to a specific place in memory, and then Windows creates one “composite” view of all the windows on the screen before sending it to your monitor. Because Vista is keeping track of the contents of each window, it can add effects when layering the windows such as the transparency we’re all used to, as well as the live preview thumbnails.

The benefit to using this approach is that Windows Vista can utilize the hardware acceleration features in your video card to create very smooth animations for minimizing and restoring, and even for the transparent effects.

What about Memory Usage? 

If you open up Task Manager, you can see the dwm.exe process in the list, typically taking somewhere between 30-50MB of memory in my testing:


The size of the DWM process is controlled by the number of windows that you have open, since each window requires a buffer in memory to store the contents of the window. If you have a large number of very large windows open, DWM will use more memory.

The benefits of using a compositing window manager are worth that relatively small amount of memory under most circumstances.


IconPackager doesn't usually cause a significant issue.  If it's the first time using it you may get some high usage as it's being applied . . but everything should level out quickly.

Reason for Karma (Optional)
Successfully updated karma reason!
October 17, 2012 10:10:27 PM from Stardock Forums Stardock Forums

Its running but why is still says not enabled?

Reason for Karma (Optional)
Successfully updated karma reason!
October 18, 2012 7:39:26 AM from WinCustomize Forums WinCustomize Forums

Go ahead and run through this:


Reason for Karma (Optional)
Successfully updated karma reason!
Sign Up or Login and this ad disappears!
There are many great features available to you once you register. Sign Up for a free account and browse the forums without ads.
Stardock Forums v1.0.0.0    #101114  walnut1   Server Load Time: 00:00:00.0000422   Page Render Time:

Home | About | Privacy | Upload Guidelines | Terms of Service | Help
WinCustomize © 2016 Stardock Corporation. All Rights Reserved.