Windows Longhorn build 4083

Windows Longhorn build 4083 is a Milestone 7 build of the Microsoft Windows Longhorn operating system. Originally, only the x64 version of this build leaked on 10 November 2004. On 1 February 2020, the x86 version of this build was leaked by Grabberslasher, founder of the UX.Unleaked blog.

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 is only solid colors by default. It contains the new tree wallpaper that would be used on subsequent builds.

Fixes and removed features

 * The folder creation bug from build 4074, build 4081, and build 4082 has been fixed in this build.
 * Removed unmanaged-DWM ( &  ).

Bugs and quirks

 * Safe mode is broken and displays a BSOD.
 * CD and DVD drives behave like local disks.
 * The Windows Classic theme will not function due to a broken  file.
 * On some computers and virtualizers, the WinPE doesn't support the mouse, so you must use the keyboard to navigate the WinPE.
 * 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.
 * The Phone and Modem Options Control Panel applet name is empty.
 * The fans will automatically run at max speed.
 * WordPad and Outlook Express won't start due to bugs.
 * Help and Support causes an  restart.
 * Computer Management displays script errors.
 * Device Manager has a bug and as such, you cannot update drivers. You can install drivers by using devcon from the Windows XP DDK, and booting with the "Enable VGA Mode" option in the Advanced Options menu during startup.

x64 build specifics

 * Help and Support does not open.
 * Opening Device Manager will result in huge CPU usage.

Timebomb
It is one of the notable Longhorn builds that has a broken timebomb and can be installed on the current date.

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

No mouse driver in WinPE
On some computers and virtualizers, the WinPE doesn't support the mouse, so you must use the keyboard to navigate the WinPE. This seems to be related to using a PS/2 mouse, as USB mice seems to work fine for the setup.