Desktop Window Manager

The Desktop Composition Engine (or DCE) is a theme rendering engine used in early builds of Windows Longhorn. It is synchronized with WinFS, Avalon, and other internal Windows databases, as well as providing visual effects.

History
The Desktop Composition Engine is first present starting with build 3683, but in a buggy state that only renders windows transparency. Starting from build 3706 through build 4005, a new twirling effect when minimizing or closing windows is added, and a user interface was included to allow the user to enable DCE on boot or via dynamic control.

Throughout Milestone 5, Lab06 builds such as build 4015 and build 4018 were known to have additional DCE effects, including graphical animations and flapping windows while dragging. Despite these animations, other labs used only window transparency effects. Eventually, starting with Milestone 6, the Desktop Composition Engine was reworked to enable a new glass border theme, which would be the forerunner to the Windows Aero theme. While earlier builds have a bug in the DCE which causes it to use CPU processing instead of hardware processing, it wouldn't be until build 4039 to have a working Windows Aero theme.

Desktop Composition Engine remained with most builds until build 4053. Despite that, builds later than build 4039 started to no longer use the Desktop Composition Engine as the desktop compositor's name. Eventually, build 4066 replaced the Desktop Composition Engine with Desktop Window Manager.

Enabling the Desktop Composition Engine
It is to be noted that a compatible Direct3D graphics driver with hardware acceleration has to be installed and running properly prior to starting Desktop Composition Engine, otherwise either nothing happens or the desktop compositor for it will crash or glitch. On some builds, VMware has a bug where there is no alpha masking or multiply support when DCE is enabled.

Windows Longhorn build 3683
There is no user interface to enable DCE in this build. To enable DCE, add the following registry key and reboot: Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\DesktopComposition] "StartupOptions"=dword:00000001

StartupOptions can be set to 0 to disable DCE, 1 to enable it on startup, and 2 to allow dynamic control via the. Unlike other builds, the DCE in this build is only known to work on real hardware.

Milestone 3 builds
This applies to build 3706 up to build 4005. After installing the graphics driver, the user can enable DCE by opening Display Properties to change resolution/color depth and clicking Advanced. There, the will be options to enable DCE on startup or via dynamic control of a button. Enabling DCE for these builds in VMware requires a VMware version in the 6.5 range or it will black screen after starting DCE.

Milestone 5 builds
This applies to build 4011 up to build 4017. It can be enabled via the  command and disabled via. Unlike the Milestone 3 DCE, the DCE in these builds will work on modern versions of VMware given the correct version compatibility.

Milestone 6 builds
This applies to build 4039 up to build 4042 (Lab06_n). It can be started by executing  in   and can be stopped via   in the same directory. The rendering is very buggy, and it often makes the sidebar inoperable for the duration of when the Desktop Composition Engine is enabled. By default, it loads the opaque borders, but glass borders can be enabled. See the Windows Aero page for instructions on enabling glass borders.