Windows Longhorn build 4083

6.0.4083.main.040516-1537
	Build of Windows Longhorn
Version number	6.0
Build number	4083
Architecture	x86, x64
Build lab	main
Compiled on	2004-05-16
Expiration date
Timebomb	2004-11-12 (+180 days)
SKUs
	Professional
Product key
	TCP8W-T8PQJ-WWRRH-QH76C-99FBW
About dialog

Windows Longhorn build 4083 is a Milestone 7 build of Windows Longhorn. The x64 version of this build was shared on 10 November 2004, and an x86 version of this build was later uploaded on 1 February 2020 by Grabberslasher, the founder of the UX.Unleaked blog.

x64 build[edit | edit source]

The x64 version of this build is a test for the use of the Preinstallation Environment under the x64 architecture. The x64 version has no default wallpapers (besides the bitmap backgrounds), which is why there are only solid colors by default. It contains the new "Tree" wallpaper that would be used in subsequent builds.

As of 2023, this is the only available pre-reset x64 build which uses the WIM-based setup, as all earlier builds used the amd64-based setup.

Also, this is the only available pre-reset x64 build to have .NET Framework and Avalon. However, the .NET and Avalon installation is 32-bit, thus the Avalon part of the shell does not get loaded.

Fixes and removed features[edit | edit source]

The folder creation bug from build 4074, build 4081 and build 4082 has been fixed in this build.
The unmanaged-DWM and Flip3D have been removed in this build. A version of DWM rewritten in .NET-managed code would be reintroduced in build 4088.

"Tree" wallpaper for the x64 version[edit | edit source]

It is impossible to set wallpapers in JPG format as background in the x64 version. To use the "Tree" wallpaper for the x64 version, navigate to C:\WINDOWS\Web\wallpaper and locate the Longhorn.jpeg, open it with Paint, save it as Bliss.bmp on the same location, and then right-click on the desktop, click on Properties to open the Display Properties Control Panel Applet, select any theme, and then click on Apply and OK.

Bugs and quirks[edit | edit source]

Installation[edit | edit source]

As typical of builds in this build range, it tends to take a long time to install and can be unstable.

Upgrade[edit | edit source]

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

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 (via a registry tweak that reports it as a componentized build).
An error during the file copy phase.

WinPE[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.

WordPad[edit | edit source]

WordPad does not start, as it will display with Failed to create empty document instead.

Outlook Express[edit | edit source]

Outlook Express does not start due to registry errors and certain dependencies on WinFS.

Display Properties[edit | edit source]

The Windows Classic theme does not function due to a broken Windows Classic.theme file.
The wallpapers, which are in JPG format, cannot be seen by default. However, if you browse one, the wallpaper will be shown.

Explorer[edit | edit source]

CD and DVD drives behave like local disks.
- As a result of this, the system continously throws out notifications about low disk space.
Help and Support crashes Explorer.
Explorer will crash after adding the display tile in sidebar and won't launch again. A workaround is to create a new account via cmd.
When the Aero taskbar and sidebar are enabled (32-bit version only), the Taskbar erroneously uses the Sidebar background.

Control Panel[edit | edit source]

Hardware and Devices folder does not open.
Sounds Control Panel applet is missing.
Task Scheduler folder from Control Panel shows a nameless folder and generic folder icon.
By default, the Phone and Modem Options Control Panel applet name is empty.
Computer Management displays script errors due to missing registry entries.
Device Manager has a bug in which drivers can't be updated due to the Hardware Wizard Control Panel applet being missing. The user can install drivers by using devcon utility from the Windows XP or Windows Server 2003 Driver Development Kit (DDK), or copy the hdwwiz.cpl from another build to the WINDOWS\SYSTEM32 directory in order to get the updating drivers via Device Manager to work.

Graphics[edit | edit source]

Enable VGA Mode after installing video drivers or the system will result in a blue screen of death with a error code 0x000000B4.

Windows Product Activation[edit | edit source]

The Windows Product Activation component is missing due to the componentization. An incomplete rewritten one in .NET-managed code and Avalon would be reintroduced in build 4093.

Safe mode[edit | edit source]

The Safe mode is completely broken and results in a bugcheck with code 0x0000007B. This is because the Safeboot key, located in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control is largely incomplete and missing a lot of entries. 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, so Safe Mode is currently not known to work on these pre-reset Longhorn componentized builds.

DirectX[edit | edit source]

DirectX, just like 4081 and 4082, is not completely installed. It can be fixed by following the instructions on the Windows Aero page.

Additional issues for x64 build[edit | edit source]

Display Properties[edit | edit source]

As the "Tree" wallpaper mentioned above, it is impossible to use JPG pictures as desktop background in the x64 build. A workground is to save a JPG picture as a BMP picture and set as desktop background.

Device Manager[edit | edit source]

Opening Device Manager will result in huge CPU usage.

Timebomb[edit | edit source]

Unlike the x86 version of this build, the x64 version of this build has a broken timebomb and can be installed on the current date. Even if the x64 version's timebomb expires if it was installed on the current date, the user can still log in without trouble, although it will trigger a bugcheck with error code 0x00000098 after a while.