Windows Longhorn build 4093 (main)

6.0.4093.main.040819-1215
Build of Windows Longhorn
6.0.4093.main.040819-1215
OS family
Architecturex86
Compiled2004-08-19
Timebomb+180 days after original install date
Works in
About
LH4093 Winver.png
SKUs
Professional
Key
TCP8W-T8PQJ-WWRRH-QH76C-99FBW
TCB.png TCBGallery.png

Windows Longhorn build 4093 (main) is the last main branch compile of the original Longhorn project (based on the Server 2003 RC1 codebase) before development was reset with build 3790.1232. This build was leaked on 28 August 2006, shortly after the closure of the original OSBetaArchive.com, and was labeled as a farewell release. The build is largely unstable; a hallmark of which was typical of most Longhorn builds found in the late 40xx range. It was also the last pre-reset Longhorn build to be available, and one of the final builds to be compiled by Microsoft under the old codebase.

Many applications and features are unstable works-in-progress, and might not function as intended. The development reset began sometime within four hours and fourteen minutes after the compilation of this build, at 16:29. Development transitioned over to a new codebase (which prior to the reset was already in the works from as early as 3 August 2004) and was based on a work-in-progress version of Windows Server 2003 Service Pack 1. The codebase would later evolve to become Windows Vista.

While this build is only available in the Professional SKU, a Home edition is mentioned in the Activation Wizard discussed later in the article. It is currently unknown if this build was ever compiled under the Home SKU.

Setup[edit | edit source]

Although setup is mostly similar to previous builds of Windows Longhorn, a few minor adjustments were made across a number of pages.

Features[edit | edit source]

UAC[edit | edit source]

The User Account Control functionality has received a few uplifts in this build, which now features a checkmark that controls whether a local user account can open a specific application in the Properties menu. The unknown application dialog has also recieved a small design uplift.

MXPlayer[edit | edit source]

A version of Windows Media Player intended to replace the traditional app (first seen in Windows Server 2008 build 4066) is present in this build under a different file name; however, it is less stable than what was originally envisioned in the aforementioned build. The redesigned application can be run from the Windows installation directory, under C:\Windows\MXPlayer.exe.

Avalon Applications[edit | edit source]

This build includes an Avalon-based Windows Movie Maker application. However, the application is largely unfinished and the debug prompts/assertion error messages that plague it make the application nearly unusable. The Avalon Movie Maker can be found in C:\Program Files\Movie Maker 3\MovieMaker.exe.

The overhauled Display Properties dialog first seen in build 3683 also marks a return in this build; however, most of the links found in the application simply redirect to the older control panel applet found in Windows XP. A power dialog and a Wireless Presentation application based on the Avalon framework are also present in this build. The applets are named as LHDesk.exe, PowerCpl.exe, and WPWizard.exe, all of which are found respectively in the SYSTEM32 folder.

A prototype Color Management control panel (based on Avalon) can be found in this build as well. During the componentization procedure, the accidental omission of a specific Control Panel library in the manifest led to the executable not being present in the component store and its main DLL component becoming duplicated; the affected component in question is microsoft.windows.controlpanel.colormanagement. However, it is believed that the missing executable was a stub, as the main application code is found through another component named system.windows.explorer.controlpanel.colormanagement.dll. The launcher stub for the former can be reproduced using an IDE. The applet itself is largely unfinished, as shown by the other pages accessible on the right either crashing or doing nothing due to the lack of functions found within the DLL file.

Prototype Windows Product Activation[edit | edit source]

The .NET Framework library folder (C:\Windows\Microsoft.NET\Windows\v6.0.4030\) contains an exectuable file named LicenseUI.exe, which includes dialogs for a prototype design of the Windows Product Activation functionalities; however, most dialogs do not load and those that remain are lacking in terms of design and functionality and have a chance of crashing. The remaining dialogs can be run via C:\Windows\Microsoft.NET\Windows\v6.0.4030\LicenseUI.exe -type=w -dlg=Y, where Y is a number from 1 through 10. Only dialog options 2, 3 and 6 load correctly.

The sixth dialog contains options which refer to both the Home and Premium SKUs, indicating that at some point in development, the SKUs would be included in a commercial release of the Longhorn project; these SKUs would later respectively turn into the Home Basic/Premium and Ultimate editions in the final release of Windows Vista. A full list of LicenseUI pages can be found here.

Miscellaneous[edit | edit source]

  • A new sound tray icon, which directs the user to the Sound and Devices Control Panel, has been added to the taskbar.
  • The Games library has recieved a few minor design uplifts. As a side effect of componentization, all shortcuts to the inbox games have been removed from the Library; although the executable files for the games themselves are still present in the operating system.
  • The shutdown/restart/stand by choices have been uplifted, now including an entirely revamped shutdown screen, prompting the user if they want to carry out said action.

Fixes[edit | edit source]

  • The ability to use the Windows Classic theme has been restored in this build.
  • The Hardware and Devices folder in the Control Panel has been made functional again.
  • The video driver can properly initialize again without having to manually enable VGA mode after driver installation.

Bugs and quirks[edit | edit source]

Installation[edit | edit source]

  • As typically seen in componentized builds, installation can take a long time and may often fail.
  • Installation can hang for extended periods of time if is started on the current date, even with a non-functional timebomb.
  • The hardware portion of setup has issues with MUI handling, and may fail to copy certain files. It is advised to skip file copying if the user is prompted to point to a specific file location. This issue largely depends on the hardware being used, regardless of what copy the build was installed from.
  • On first logon and after completion of the hardware detection phase of setup, the Windows Explorer application may fail to launch. A workaround is to use the Task Manager to start the Explorer application.
  • The screen color depth is set to 16-bit by default, rather than 32-bit.

Upgrade[edit | edit source]

Attempting to upgrade from other builds is not possible as one of two outcomes may occur:

  1. A bugcheck with error code 0x7E after the second reboot. This is commonly observed when trying to upgrade from non-componentized builds, such as 4074 (through a registry tweak that reports it as a componentized build).
  2. An error during the file copy phase.

WinPE mouse drivers[edit | edit source]

The mouse driver in this build's WinPE does not function on specific hardware configurations or hypervisors, and may require a keyboard to navigate through the installation procedure. This issue appears to be largely related to using a PS/2 mouse, as most ordinary USB mice appear to function properly in setup.

Timebomb[edit | edit source]

Unlike other Longhorn builds, this build contains a mostly non-functional timebomb and as a result can be installed on the current date.

Outlook Express[edit | edit source]

Outlook Express does not start due to issues with registry access and missing WinFS dependencies.

Explorer[edit | edit source]

  • CD and DVD drives behave like local disks. Floppy drives behave like local disks only if a CD is inserted in the system.
  • Help and Support crashes Explorer.
  • Explorer will crash after adding the display tile in sidebar and will not launch again. A workaround is to create a new account via the Command Prompt or by removing the affected tile through a registry modification.
  • Text may overlap certain visual elements in the Game Library.
  • Sometimes, icons may not show correctly on the desktop and Start menu unless Explorer is restarted.
  • Viewing large folders might cause Explorer not to properly load all directories (which is true for the System32 directory). Refreshing Explorer several times fixes this.

Themes[edit | edit source]

Changing the theme will leave the taskbar without a visual style, reminiscent of build 4074's theming service bug. This can be fixed by restarting explorer.exe or changing to another theme (except Windows Classic).

The navigation buttons of Windows Explorer, Internet Explorer and other Avalon-based applications will disappear if the application is in use.

Control Panel[edit | edit source]

  • By default, the Phone and Modem Options Control Panel applet name is empty.
  • Sometimes, Computer Management will display script errors due to missing registry entries.

Drivers[edit | edit source]

  • This build does not install the default monitor driver by default and may need to be installed manually. As a result, changing the display resolution will not ask for confirmation.
  • The Hardware Abstraction Layer device may show up as an unrecognized device.
  • Many driver categories lack their respective icons.

Compatibility[edit | edit source]

The VMware sound drivers have a large chance of ceasing to function for no specific reason, regardless of whether hardware-based sound acceleration is enabled or not.

Safe mode[edit | edit source]

The Safe Mode functionality does not work in this build and results in an INACCESSIBLE_BOOT_DEVICE bugcheck with code 0x7B. This is because the SafeBoot key, located at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control, is largely incomplete and lacks most entries necessary for Safe Mode to work. Restoring the key from an earlier build with working safe mode allows this build to boot properly, but the video driver will not initialize properly. As a result, the operating system will freeze as it transitions into graphical mode.

Other bugs[edit | edit source]

Gallery[edit | edit source]

External links[edit | edit source]