Windows Server 2008 build 4066

Windows Server 2008 build 4066 is a pre-reset build of Windows Server 2008, which was originally described by Grabberslasher in his UX.Unleaked blog entry on 1 May 2008 and was later uploaded to BetaArchive seven months and nineteen days later on 20 December 2008.

This build is the fourth shared build based on the pre-reset code, the others being builds 4028, 4031 and 4038. This build uses the older i386 installation method like in builds 4031 and 4038.

Features
In spite of this build being only available as a server edition, it notably contains many features that are more typical of builds of its client counterpart.


 * Desktop Window Manager
 * Glass - It can be activated by using the keyboard shortcut CTRL + SHIFT + F9.
 * Aurora - Can be activated by using the 3D view option found on the View Options menu.
 * Phodeo - Can be activated by using the Panorama option found on the View Options menu.
 * Sidebar - Contains most of the tiles used in the later build 4074.
 * Windows Media Player - a version that was apparently intended to replace the traditional app bundled with Windows (in this case Windows Media Player 9, which is disabled by default). This build also includes a sidebar tile of said app. Run   to open it.
 * Panorama, Carousel and LVSpy can be enabled by merging these below into the registry.


 * Aero Stars - Identical to what is seen in the later build 4074. Disable the sidebar, unlock the taskbar and then merge these below into the registry.

MILRender

 * MILRender is present in this build. It includes functional Aero Stars and extended Aero.

Notifications
This is the only leaked pre-reset build in which the transparent Aero notifications function.

Safe mode
Windows Explorer crashes in a loop by default under safe mode since the sidebar tiles are added by default. A prompt will appear titled "Desktop" and will ask to proceed to work in safe mode or start System Restore. Clicking either button will not perform any action and will bring up another exact prompt instead. The desktop will not appear with the prompt and Explorer may not launch. The only workaround is to remove all the sidebar tiles from the registry:


 * 1) Open the Registry Editor from Safe Mode with Command Prompt.
 * 2) Navigate to.
 * 3) Collapse the "Tiles" folder, and then remove all the sidebar tiles from the registry.

Additionally, when Windows Explorer is running in Safe Mode, clicking on Log Off from the start menu or initializing the Shut Down dialog box via Alt + F4 on the desktop with Safe Mode, it will bring up another exact prompt. So to log off, shut down, or restart, press the CTRL+ALT+DEL key and then click on "Log Off", "Shut Down", or the ">" button for more options.

Explorer

 * Explorer can randomly crash for no reason under normal use.

Installation

 * On some computers and virtualization software, setup cannot format the drive, as it results in an "Unknown Hard Error" BSOD.
 * A clean install is highly recommended, but it is possible to upgrade to this build.
 * The title for every Setup Wizard's stage freezes at Regional and Language Options, or Installing Devices if the user presses the Shift + F11 keys to invoke the installation progress window.

Upgrade
To upgrade to this build from Windows Server 2008 build 4031 you must edit  in the i386 folder and ensure that. Then you must replace the following files and directories with copies from the RTM build of Windows Server 2003.


 * If upgrading to this build, you will need to ensure that  does not exist in  . Leaving this file will cause a   relating to this file, and rebooting will corrupt the registry, making it impossible to reboot back into setup.


 * On some machines, you will get stuck at the login screen as you are unable to press  To fix this:
 * 1) Boot into Safe Mode.
 * 2) Load up Task Manager.
 * 3) Go to file > New Task.
 * 4) Type in gpedit.msc
 * 5) Go to Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options
 * 6) Find  and change it to enabled.
 * 7) Reboot the machine.

Note: Logging in to this build may take several minutes after an upgrade.


 * There is a chance that setup could fail during an upgrade as  gets corrupted.