Windows Longhorn build 4053

Build of Windows Longhorn
Version number6.0
Build number4053
Build labmain
Compiled on2003-10-22
Expiration date
Timebomb+180 days after original install date
Product key
About dialog
TCB.png TCBGallery.png

Windows Longhorn build 4053 is a Milestone 7 build of Windows Longhorn, which is reported to have been shared online on 1 March 2004.[1] Overall, this build is very similar to build 4051, but with networking bugs patched.

Although the watermark shows that this build was test-signed, it was compiled in evaluation mode and can be installed on the current date. Attempting to log onto the desktop once the timebomb has been triggered will return the user to the login screen.

Setup[edit | edit source]

Setup is mostly similar to previous builds of Longhorn. This build can also be upgraded from previous builds too.

Changes[edit | edit source]

This is the earliest available build of Windows to support disabling upgrades via an empty noupgrade.txt placed in the sources folder.

Bugs and quirks[edit | edit source]

Theming[edit | edit source]

If any application handled by Explorer like Windows Explorer or Internet Explorer stops responding, the theming of these applications will bug out and show the classic theme title bar.

Control Panel[edit | edit source]

The normal method of creating user accounts does not work in this build. However, accounts can still be created by going to run and typing in either control userpasswords2 or netplwiz.exe. An alternative method is porting nusrmgr.cpl from another build to replace the one in the \WINDOWS\SYSTEM32 directory in order to get it to work or using the Local Users and Groups MMC snap-in can be used (lusrmgr.msc).

Start menu[edit | edit source]

The most frequently used items list of the Start menu resets itself after every reboot.

Notifications[edit | edit source]

Notifications tend to reappear quite a lot. Fully closing the notifications may take several attempts.

Upgrade[edit | edit source]

On some machines, after the first reboot during an upgrade, an "Unknown problem in upgrade happened" error will appear, and clicking OK will cause the machine to restart. After restarting, setup will continue normally until another reboot takes place, in which "The file WinSetup.dll could not be loaded or is corrupt. Setup cannot continue." will appear. Clicking OK will restart the computer and on some machines, there will be no mouse and keyboard support (since the hardware detection phase of setup did not start), and the only workaround is to reinstall Windows and does not occur on some machines. This bug persists until build 4093.

Gallery[edit | edit source]

References[edit | edit source]