Windows Aero

Aero is a transparent Windows visual style used from Milestone 6 Longhorn builds to Windows 7 (window transparency was removed in 8). The first build to have working Aero is Windows Longhorn build 4038, and the last build to use Aero (with window transparency) is Windows 8 build 8424 (fbl woa drop). In Windows Longhorn, Aero effects relied on the Desktop Composition Engine (or Desktop Window Manager in newer builds), which only worked in a few builds such as 4039, 4042, 4066, and 4074. In Windows Vista and 7, it relies on a WDDM driver due to the use of hardware acceleration, otherwise the Windows Basic theme would be used. This requirement was dropped since at least Windows 8 build 7880 with the introduction of a software rendering fallback to the Desktop Window Manager.

Windows Longhorn build 4038 to build 4042 (Lab06_n)
First, install a compatible Direct3D driver and ensure it works via. While you can run  in   to enable the borders, they will be opaque. In order to enable transparent borders, you need to go into  and copy the Plex folder. Paste back into the Themes folder and the new folder should automatically rename itself to "Plex - Copy". Rename the pasted folder to "Aero" and rename the msstyles file inside the folder to. After that, restart the Theming service (either running  and   or logging off and back on will work). At this point, you can run  again to enable the glass borders.

Windows Longhorn builds 4074 to 4082
This is a guide on how to enable Aero in Longhorn build 4074 to 4082, adapted from the tutorial at the Experience Longhorn Project. The patched ISO known as 'Longhorn The Way It Was Meant To Be' (Longhorn TWIWMTB) has all these features in place. If you have a standard copy of this build, here's how to get Aero working:

Note: This guide won't work on the x64 version of build 4074, except for basic DWM effects.

Video Drivers and Theme Files
You should use the SVGA driver pack if you have VMware 7.1. Installing this driver is fairly simple: go to the Device Manager, and under 'Graphics' click 'Update Driver' with the mounted or burned driver pack ISO (Device Manager is buggy in build 4081 and 4082, so command-line tools may need to be used instead). Builds 4081 and 4082 requires booting into VGA display mode after updating the driver, otherwise it will result in a 0xB4 BSOD.

Builds 4081 and 4082 ship with an incomplete DirectX, which will cause a black screen when enabling DWM (see below). The missing components can be obtained from the DirectX 9.0b installer for Windows XP (9.0c may also work, but not tested). The installer itself will refuse to install on Longhorn, but this can be bypassed by manually extracting the contents of dxnt.cab and installing all of the .inf files found within from their right-click menus (answer no to all overwrite prompts), and copying any remaining files from dxnt.cab into System32. Verify successful installation by running the Direct3D tests in dxdiag (it may complain about DirectShow not being registered, but the spinning 3D cube animation can still confirm DirectX is functional).

Now we need to reconstruct the Aero theme files. This is done by using the Jade theme files and copying these to the desktop. The 'Jade' folder and the files 'Jade.theme' and 'Jade.msstyles' should be renamed, respectively, to 'Aero' (folder), 'Aero.theme' and 'Aero.msstyles'. Now, open 'Aero.theme' as a text file and change: [email protected],-203 to DisplayName=Aero. Replace all instances of 'Jade' with 'Aero' then in the text file. Save the theme and put the theme files back into the directory.

The Transparency and Desktop Window Manager
Now we need to go to the registry. Navigate in the registry to  and create 2 DWORDs. Call the first DWORD MILExplorer and set the value to 1. The second is optional (setting it enables Aero stars on the Desktop): call it MILDesktop and set the value to 1. Save the registry. Go to Control Panel → Display → Themes and choose the Aero theme. After some seconds, you will see a lovely transparent taskbar and sidebar. If you added the MILDesktop key and if you have the drivers, you will also see the Aero Stars (animating stars on the desktop).

At this moment we run into a problem. Trying to open a window will do nothing. That's because the window is completely transparent. Even though we enabled Aero transparency, we haven't yet enabled the Desktop Window Manager. In build 4081 or 4082, this can be done easily by just pressing Ctrl + Shift + F9, but this is broken in build 4074.

To start DWM in build 4074, create a Notepad text file and paste in the following code. Save it as a '.bat' (batch file). Then run it, and the DWM should be on. @echo off %systemdrive%\windows\i386\sbctl.exe start rundll32 %systemdrive%\windows\system32\uxdesk.dll,DwmStartComposition %systemdrive%\windows\i386\sbctl.exe stop tskill explorer.exe %systemdrive%\windows\i386\sbctl.exe start

Alternatively, copy desksrv.dll from build 4081 or 4082 to make Ctrl + Shift + F9 work.

Please note that if you don't install the drivers, DWM will likely not load. Also, if you restart, the transparency will disappear by default. This can be avoided by adding a shortcut to your DWM-starting batch file to the Startup folder.

Do note that by default, Explorer borders will be green on an unmodifed copy of the build. TWIWMTB and patched Aero themes can add transparent borders to the build.

Windows Vista pre-Beta 2 builds
This is a guide to enable Windows Aero (i.e. Desktop Window Manager) in Windows Vista build 5212 to build 5284 in VMware Workstation and Player. It is recommended to use the version 11 (Workstation) or 7 (Player) or older, as newer versions starting from 12 has rendering problems in which the display would flicker and only active window or part of it will render properly. This is likely due to changes in display engine to support DirectX 10 and OpenGL 3.3.

Video Drivers
First, the SVGA driver pack must be used and installed via Device Manager. Any SVGA driver from VMware version 6.0-7.1 will work, however VMware 6.0 compatibility must be used on build 5231 due to the BSOD bug.

Enabling Aero

 * 1) After you installed the drivers, open  . If you're running build 5048 to 5231.2, browse to   (if the DWM key does not exist, create it). If you're running build 5259 to 5284, then browse to   instead (create the DWM key if it's not there).
 * 2) Create a DWORD key named  (UseMachineCheck for 5259-5284) and set its value to 0. Log off and back on and Aero should automatically be enabled.

Optional Keys
You can also use these DWORDs in the DWM key you created to get various effects.


 * Blur - set it to 0 to disable blur, else set it to 1.
 * BlurSigma (build 5212-5270 only) - set it to a decimal value between 1 and 30, depending on the value it will control the blur intensity. If set to a value out of the 1-30 range, it will disable transparency and make borders black.
 * Animations- if set at 1, the Aero animation effects will be enabled. It can be disabled by setting the key to 0.
 * AnimationsShiftKey - set it to 1 to be able to press Shift key during animations to slow them down.
 * RenderClientAreaOnly - setting it to 1 will cause the window borders and title bars to disappear, use with caution!

Bugs and quirks

 * Since these builds uses LDDM instead of the WDDM used in newer builds, Vista drivers will not work. Windows XP drivers are required to enable Aero in these builds.
 * Aero is not known to work on builds 5098 and 5112 outside of real hardware.
 * When Aero is enabled on build 5212, the borders becomes transparent, but the taskbar doesn't.
 * Before build 5259, there is a bug that causes Aero animations to lag. It is possible to work-around this by ending and restarting the  process.
 * Flip3D is activated via the Windows Key + Spacebar in build 5212 and build 5219, rather than Windows Key + Tab in later builds.
 * The Vista WDDM driver can be installed starting from beta 2 to RC1 builds (tested on 5384 and 5600) with a replaced msvcrt.dll from an RC2 or RTM build, but this results in triggering a license error.

Aero in Windows 8/8.1
Early builds of Windows 8 use the same Aero theme as Windows 7. It was later modified to have a bigger, centered title bar caption in build 7850, then a smaller close button on dialogs in build 7880 (which also no longer requires a WDDM driver to be installed, as the DWM can now run in software-rendering mode), and remained the same until Windows 8 Developer Preview, which now has sharp corners instead of rounded in most elements.

In Windows 8 Developer Preview, it's possible to enable the glass effects in the Aero Lite theme (referred to as Windows Basic) by running.

While Windows 8 build 8432 and later builds (including the RTM and Windows 8.1) removed the glass effects, it is possible to get it back, though not fully functional as it was more of a bug than a workaround. To do so, right click the desktop and open up Personalization. Select any of the high contrast themes to apply it. Once applied, click on Window color to open it up. Leave the page open and minimize it. Open a separate personalization window and apply the theme you used before applying high contrast and close out of the personalization window you just opened. Go back to the other personalization window that you minimized and click save changes to save the high contrast colors. To disable, reselect your current theme. This also works on Windows 10 as well, but it changes the Aero theme to Aero Lite (except for applets like volume control)

The same bug can also be used to enable transparency when using the Aero Lite theme on Windows 8 Consumer Preview and Release Preview, albeit being more stable with full colorization.

Bugs and quirks

 * In Windows 8 Developer Preview, the Aero theme does have bugs. For instance, the lower half of the window background of some applications which use Aero for the entire window (e.g. Desktop Gadget Gallery or Mozilla Firefox), have a gray square.
 * In Windows 8 RTM and Windows 8.1, if the "glass" effects were enabled using a bug described above, a broken "glass" effect will be enabled that results in the border to draw contents of menu, icons, or other window above it to itself. Moving or resizing the window will also leave the trails of the title bar and cursor. Maximizing the windows will temporarily clear out those.