Windows Longhorn build 4038

6.0.4038.main.030813-1852
	Build of Windows Longhorn
OS family	Windows NT
Version number	6.0
Build number	4038
Architecture	x86
Build lab	main
Compiled on	2003-08-13
Expiration date
Timebomb	2004-02-09 (+180 days)
SKUs
	Professional
Product key
	TCP8W-T8PQJ-WWRRH-QH76C-99FBW
About dialog

Windows Longhorn build 4038 is a Milestone 6 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. It was uploaded on 30 January 2020 in the seventh set of his 33 Longhorn/Vista builds, along with its server counterpart.

Setup[edit | edit source]

Although setup is mostly similar to previous builds of Longhorn, the cancel and back buttons have been removed, now making the top-left back and top-right exit buttons the only choices. Upon hovering over buttons, the cursor now changes as well. The upgrade page has also been updated, now having the buttons organized vertically, rather than horizontally.

However, this is the first build of Longhorn to contain the complete setup inside the install.wim image, and setup will boot off the setup located inside the image.

Setup
Product key entry
EULA
Upgrade page
Setup is copying files

New features and changes[edit | edit source]

The 3D views have been improved in usability when compared to 4033.main. The spinning icons have returned and the 3D views are interactable. However, it is still not possible to use Panorama to open files or folders.
It is now possible to move an Explorer window by clicking and dragging on free space within the upper navigation pane. In addition, double-clicking empty space on that pane also minimizes the window.
Replaced Help and Support by Assistance. However, it is almost nonfunctional since the links in its home screen only take to blank pages.
The settings page of Windows Explorer has been updated with bigger XP-style buttons for OK, Cancel and Apply.

DCE[edit | edit source]

The Desktop Compositing Engine now enables Direct3D shaders on capable hardware. Since DCE now has working Direct3D shaders, the new borders are now shown, which weren't found in earlier builds containing a working DCE. Although by default the borders will be opaque, the transparent borders can be enabled by tricking desksrv.dll into believing that the user has access to the private, unleaked Aero theme. To enable DCE, run the sbctl start command, although it requires a compatible graphics driver. Alternatively, the user can use the rundll32.exe user32.dll,DceStartup to start the DCE.

Bugs[edit | edit source]

The preview pane may not show the common task options.

Installation[edit | edit source]

On VMware, this build can't be installed, booting from the CD as it will get stuck on the boot screen. To prevent this bug, a Windows Preinstallation Environment from another build is required. This bug persisted until build 4050.
On some computers, the hardware portion of setup will crash just after the second reboot and the user will be instantly taken to the desktop.

Upgrade[edit | edit source]

It is currently not possible to upgrade to this build. After the second reboot, Windows will corrupt the registry and will fail to boot, causing the error Windows could not start because the following file is missing or corrupt: \WINDOWS\system32\config\SYSTEM when upgrading from most builds prior to this one.
When upgrading from build 4029 ~ build 4033, lsass.exe terminates with a critical error, and the system will become stuck in a bootloop. The only workaround is to reinstall Windows. This bug persisted until build 4050.

Desktop Compositing Engine[edit | edit source]

While this build's Desktop Compositing Engine can render the DWM window frames, it suffers from rendering glitches that fail to refresh a window's graphical content unless the window is resized.

Safe mode[edit | edit source]

Trying to log in after booting into safe mode results in an error due to the User Profiles Service and Group Policy Service being disabled.

The services can be manually enabled in safe mode by adding the following entries to the service whitelists in the registry:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\ProfSvc]
@="Service"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Minimal\GPSvc]
@="Service"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\ProfSvc]
@="Service"

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SafeBoot\Network\GPSvc]
@="Service"