locked
[Question] How can I close "DWM" on Windows 8?

    Question

  • Hi,guys

    Here is problem about DWM on Windows8. The DWM is different on Windows8, it can't be closed - but on Win7 we can close it (as,Ctrl+Shift+F9). It's seems DWM become a "very basic" service on Windows8, it's need running anytime when system launched.

    Has any solution to close it?

    Thanks,

    Infil


    • Edited by iNfil Tuesday, October 11, 2011 3:57 AM
    Tuesday, October 11, 2011 3:56 AM

Answers

All replies

  • Hi iNfil,

    It is the intention that DWM always stays on on Windows 8. May I ask why you are trying to turn it off?

    Thanks

    Tuesday, October 11, 2011 5:42 PM
  • I want to know too...

    Here I have a software "iz3d" may make 3D games to Anaglyph images

    But it has no effect in Windows Developer Preview.

    I guess it may cause by DWM

    I try to end it for diagnose. But it always restart by winlogon = =

    If you have any suggest?

    Thanks~ Sorry for my poor English...

    Saturday, October 22, 2011 1:05 PM
  • You can't disable DWM:

     

    In the Developer Preview version of Windows, Desktop Window Manager (DWM) is always ON and cannot be disabled by end users and apps. As in Windows 7, DWM is used to compose the desktop. In addition to experiences enabled in Windows 7, now DWM desktop composition enables desktop composition for all themes, support for Stereoscopic 3D, and management, separation, and protection of the experience with Metro style apps.

    Desktop composition for all themes

    In Windows Vista and Windows 7, desktop composition is enabled only with the AERO Glass Theme. Hence users of Windows Classic and high contrast themes cannot use experiences enabled by desktop composition such as Windows Flip, automatic scaling for high resolution (DPI) scaling, thumbnail Preview and full screen magnifier. In addition, in these earlier versions of Windows, app developers must write and maintain multiple code paths – one where desktop composition is enabled and another where desktop composition is disabled.

    With Windows Developer Preview, desktop composition is enabled for all themes. Users of Windows Classic and high contrast themes can use the experiences enabled by desktop composition such as Windows Flip, automatic scaling for high resolution (DPI) scaling, thumbnail previews, and full screen magnifier. In addition, developers don’t need to write and maintain multiple code paths, thereby simplifying development.

    Support for Stereoscopic 3D

    DWM desktop composition supports rendering and presentation of windowed and full-screen stereoscopic 3D app content.

    Management, Separation and Protection of the Experience with Metro style apps

    DWM desktop composition enables separation and protection of desktop app windows from the new Metro style app windows by managing and separating the desktop app windows from the Metro style app windows. Since desktop composition is responsible for managing all app windows, disabling desktop composition can result in unexpected behavior. In addition desktop composition is responsible for composing the new Start menu as well as additional window animations that form the core personality of the new Windows operating system.

    Controlling Desktop Composition

    In Windows Vista and Windows 7, desktop composition is disabled in a number of scenarios. In Windows Developer Preview, DWM desktop composition is a core operating system component and cannot be disabled. With a few exceptions, desktop composition is always on; it’s started before the user logon and remains active for the duration of a session. This section describes how Windows Developer Preview treats the scenarios in Windows 7 where desktop composition is disabled.

    Server SKU and certain client SKUs

    In Windows Developer Preview, all server and client SKUs have desktop composition enabled. This ensures that server admins and users can benefit from the experiences enabled by desktop composition.

    Fundamental requirements for desktop composition

    Windows Developer Preview ensures that graphics adapter and system color depth requirements are met through WDDM driver support and system color depth.

    WDDM Driver Support

    If a system does not have a WDDM-compliant graphics driver, Windows Developer Preview uses Microsoft Basic Display Adapter as the default adapter. Since DWM always runs on the default adapter, it will choose Microsoft Basic Display Adapter to compose the desktop when a WDDM-compliant graphics driver is not available (whether not installed or disabled) on the system.

    Microsoft Basic Display Adapter is a software rasterizer that uses the CPU rather than the GPU to perform all the drawing. Note that the performance of desktop composition on Microsoft Basic Display Adapter (especially animations) may not be as smooth as when running desktop composition on a GPU.

    System Color Depth

    Desktop Composition cannot run unless the color depth is set to 32 bits per pixel. In Windows 7 the color depth of the system can be changed in one of the following scenarios:

    ·         An end user uses the Windows Display control panel or a 3<sup>rd</sup> party control panel to change the system color

    ·         An end user runs an app that changes the color depth of the system through a public API

    Unlike Windows 7, Windows Developer Preview does not support color depth other than 32 bits per pixel. The user can no longer change the color depth of the system by using the control panel.

    In addition, app developers cannot use APIs to change the color depth of the system. Windows Developer Preview will detect apps that try to change the color depth of the system to less than 32 bits per pixel, and inform the user that an app compatibility shim must be applied to run the apps. After confirmation from the user, the app compatibility shim is applied and the shim virtualizes the low color mode to the app while keeping the system running at 32 bits per pixel. 

    WinSAT

    In Windows Developer Preview, desktop composition does not depend on WinSAT scores. Moreover, WinSAT no longer includes DWM assessment.  

    App Compatibility and User Action

    In Windows Developer Preview:

    ·         All of the options for disabling desktop composition that exist in Window 7 are removed

    ·         Desktop composition is responsible for composing all themes

    ·         Apps cannot use DwmEnableComposition to disable desktop composition. In order to maintain backward compatibility, a call to this API will return success; however, desktop composition is not disabled

    ·         The "Disable desktop composition" shim is removed

    ·         The option to "Disable desktop composition" from the compatibility tab of the Application Properties dialogue box is removed

     

    An App Uses a Mirroring Driver for Remoting

    In Windows Developer Preview:

    ·         Does not support mirror drivers for remoting scenarios; while most of the existing apps that use mirror drivers should continue to work, due to the infrastructural change required to support existing mirror drivers in Windows Developer Preview with DWM ON, some features or apps that use mirror drivers may not work

    ·         Does support Desktop Duplication APIs for app developers who use mirror drivers for remoting scenarios.

     

    ·         Does not support existing Accessibility Mirror Drivers

    ·         Existing Mirror Drivers must be updated to ensure that they are compatible with Windows Developer Preview

     

    Remote Desktop Connection

    In Windows Developer Preview, desktop composition is always enabled for a remote desktop connection. A client computer connecting to a Windows Developer Preview remote computer will always get desktop composition enabled for the remote desktop session irrespective of the Windows client version. Desktop composition is supported for multiple monitors on the client machine as well as for the remote app session.

    In addition, when connecting to a Windows Developer Preview remote computer, the following settings in the Remote Desktop Connection client do not take effect:

    ·         Color depth

    ·         "Enable composition” checkbox

     

    The color depth of the connection is always set to 32 bits per pixel and desktop composition is always enabled.

     


    "A programmer is just a tool which converts caffeine into code"

    Saturday, October 22, 2011 4:05 PM