Windows Longhorn build 4093

6.0.4093.main.040819-1215
	Build of Windows Longhorn
OS family
Architecture	x86
Compiled	2004-08-19
Timebomb	2005-02-16 (+181 days)
Works in
About
SKUs
	Professional
Key
	TCP8W-T8PQJ-WWRRH-QH76C-99FBW

Windows "Longhorn" build 4093 is the last 'main' compile of the original "Longhorn" project (based on the Server 2003 RC1 code-base) before development was reset with build 3790.1232. This build was leaked on 28 August 2006, shortly after the closure of the original OSBetaArchive, and was labeled a farewell release. It is highly unstable; which was typical of most later "Longhorn" builds.

It can login on the current date without activation.

It was the last pre-reset "Longhorn" build to be leaked, and one of the last to be compiled. This build's installation media cannot be booted up normally; this can be done using build 4033's Preinstallation Environment, and even then installation does take a long time to complete.

Many applications and features are unstable works-in-progress, and might not function as intended. However, most working features and applications can be launched using the Run command and certain features like WordPad and the Windows Classic theme has been fixed. However, Safe Mode does not work properly and displays a BSOD before it could be launched. The development reset began a mere four hours and fifteen minutes after the compilation of this build, at 16:29 (although many teams had already been working with the new codebase since at least 3 August 2004). Development moved to a new code base, which eventually became Windows Vista.

Features[edit | edit source]

MXPlayer[edit | edit source]

It has a new version of Media Player called MXPlayer. It can be accessed by running MXPlayer.exe in the installation directory, but it is incomplete and a lot of the options don't work or result in assertion errors.

Avalon Applications[edit | edit source]

It includes an Avalon-based Windows Movie Maker application. However, this version is highly unstable, and the debug prompts and assertion error messages that plague it make it nearly unusable. The Movie Maker can be found in C:\Windows\Program Files\Movie Maker 3\MovieMaker.exe.

It also marks the return of the Avalon-based Display Properties dialog first seen in build 3683. However, most of the links simply redirect you back to the XP-style dialog. An Avalon-based Power dialog can be found in this build as well, though it is unstable. Likewise, there is also an Avalon Wireless Presentation application in this build. The applets are LHDesk.exe, PowerCpl.exe, and WPWizard.exe in SYSTEM32, respectively.

It also includes a prototype Color Management Avalon-based control panel. However during componentization of the build, a mistake was made in the manifest for the main executable of the control panel, leading in the executable not being present in the component store, and its main DLL component duplicated. The component in question is microsoft.windows.controlpanel.colormanagement. However it is believed that the missing executable was just a stub, starting the main application code in the duplicated system.windows.explorer.controlpanel.colormanagement.dll file. It is thus easy to recreate the stub executable using an IDE like SharpDevelop. The control panel applet is extremely unfinished, as shown by the other pages accessible on the right either crashing or doing nothing.

Prototype Windows Product Application[edit | edit source]

Inside C:\Windows\Microsoft.NET\Windows\v6.0.4030\ is a file named LicenseUI.exe. It contains dialogs for a prototype version of Windows Product Activation, however most of the dialogs don't load and those that remain are highly unstable and incomplete. Some of the dialogs can be run via C:\Windows\Microsoft.NET\Windows\v6.0.4030\LicenseUI.exe -type=w -dlg=?, where ? is a number from 1 to 10, but only 2 and 3 load correctly.

Miscellaneous features[edit | edit source]

It is the last build to include the original Windows Sidebar. It would be reintegrated into Vista, but only starting in build 5212 and as its own process instead of being integrated with explorer.exe. It is also among the last to include WinFS.