free up some more ram by stopping certain exes from being called to start & stop

Discussion in 'Windows 7' started by RanCorX2, Feb 5, 2011.

  1. RanCorX2

    RanCorX2 MDL Addicted

    Jul 19, 2009
    674
    191
    30
    #1 RanCorX2, Feb 5, 2011
    Last edited by a moderator: Apr 20, 2017
  2. NiHiLisT

    NiHiLisT MDL Member

    Jul 29, 2009
    214
    14
    10
    Thank you! Always trying to squeeze some ram out of my box!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Enigma256

    Enigma256 MDL Senior Member

    Jan 17, 2011
    354
    300
    10
    #4 Enigma256, Feb 5, 2011
    Last edited: Feb 5, 2011
    :rolleyes: This is what happens when people sip from the Pierian Spring.

    WMI processes are on-demand. They start up only when something requests information from or otherwise interacts with the WMI. Once that is done, the WMI processes will stay in memory for a short period of time, in case there are other requests. If there are none, they will terminate on their own. All you're doing here is preventing applications from interacting with WMI properly. Maybe you don't have any that need WMI in a critical way, but whatever. If you want to needlessly cripple a component that's on-demand anyway, be my guest.

    As for dllhost, disabling that is truly idiotic. That's a generic COM host. It's not just for thumbnails. It just so happens that the thumbnails mechanism uses it. This has the potential for breaking a lot of things, both Microsoft and third-party. If you don't like the shell using memory and CPU cycles doing thumbnails, you should disable the feature in Group Policy (there are a whole bunch of features controlling this feature there, and you can disable it entirely). That's the correct way to do it. Another way to do it is to unregister the thumbnail-related COM object(s), but that's the wrong way to do it--though, since it doesn't involve crippling the COM host, even that is significantly better than telling someone to mess with dllhost!
     
  4. RanCorX2

    RanCorX2 MDL Addicted

    Jul 19, 2009
    674
    191
    30
    #5 RanCorX2, Feb 5, 2011
    Last edited: Feb 5, 2011
    (OP)
    Never had any issue disabling them before both on xp, vista. I do know what they used for, I'm just a minimalist when it comes to what I like running in the background. I've yet to find something that uses the COM+ features of windows so I keep both COM services disabled as well.