Windows Longhorn build 4082

6.0.4082.main.040510-2230
	Build of Windows Longhorn
OS family	Windows NT
Version number	6.0
Build number	4082
Architecture	x86
Build lab	main
Compiled on	2004-05-10
Expiration date
Timebomb	2004-11-06 (+180 days)
SKUs
	Professional
Product key
	TCP8W-T8PQJ-WWRRH-QH76C-99FBW
About dialog

Windows Longhorn build 4082 is a Milestone 8 build of Windows Longhorn. On 23 January 2020, this build was listed on a thread by UX.Unleaked blog founder Grabberslasher to be released to the BetaArchive FTP, and was released in the twelfth and final set of their 33 Longhorn/Vista builds on 4 February 2020 along with the main compile of 4042, build 4087 and build 5492.^[1]

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 0x0000007E 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.

Preinstallation Environment[edit | edit source]

The mouse driver in this build's Preinstallation Environment 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.

Themes[edit | edit source]

The Windows Classic style cannot be applied as there are no color schemes defined in the registry. This can be fixed by using a registry modification.

Explorer[edit | edit source]

CD and DVD drives behave like local disks. As a result of this, the system continuously 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 for this is to create a new user via command-line tool and log in to it.

Control Panel[edit | edit source]

The Hardware and Devices folder does not open.
The Sounds Control Panel applet is missing.
Task Scheduler 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.
Drivers can't be updated in Device Manager as the Hardware Wizard Control Panel applet is missing. To install drivers, use the devcon utility from the Windows XP Driver Development Kit (DDK). Alternatively, copy the hdwwiz.cpl file from another build to the WINDOWS\SYSTEM32 directory in order to get the updating drivers via Device Manager to work.

Creating folders[edit | edit source]

The option to create folders by right-clicking and selecting New doesn't work as the Folder entry is missing. Apply the following registry key to fix this problem:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\.Folder]
@="Folder"

DirectX[edit | edit source]

Although the Desktop Window Manager is present and can be activated by pressing Ctrl+⇧ Shift+F9 as in Windows Server 2008 build 4066, the screen will turn black due to a broken DirectX installation. It can be fixed via the instructions listed on the Windows Aero page.

Graphics[edit | edit source]

Enable VGA Mode after installing video drivers or the system will result in a bugcheck with 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.