Windows Vista build 3790.1232

Windows Vista build 3790.1232 is one of the first builds of Windows Vista compiled after the development reset, and the first to be built by the new  build lab. It is essentially a recompile of a contemporary Windows Server 2003 Service Pack 1 build with the same number, and therefore not functionally a Longhorn build. However, as it was compiled from a branch that was only introduced by post-reset Longhorn and was distributed with the Longhorn EULA, it is still usually considered to be one.

The build was first described by Grabberslasher on his UX.Unleaked blog on 2 May 2008. The Professional version of this build was uploaded to BetaArchive on 14 August 2011, while the Home Edition version of this build was shared by Grabberslasher in the second set of his 33 Longhorn/Vista builds on 25 January 2020.

As the build is virtually unchanged from Windows Server 2003, it is possible to install most updates for it with little to no workarounds, including Service Pack 2 and Internet Explorer 8. However, Windows Update will not work as Microsoft never officially released a client x86 build based on the newer Windows Server 2003 codebase.

This is the client counterpart of Windows Server 2008 build 3790.1232.

Background
Microsoft had numerous problems with earlier Longhorn builds, including stability issues and memory leaks due to the use of relatively new technologies such as .NET, Avalon and Managed C++, as well as organizational issues and feature creep. Because of this, the Longhorn project was reset to the latest codebase of Windows Server 2003 Service Pack 1, which was still in the works at the time. In addition, its planned feature set was reconsidered and a ban on .NET was instituted in the Windows source tree, with the exception of certain components. This build is virtually unchanged from its base build, aside from it being compiled in the new  branch.

Zero-day activation
The build must be activated before log-on. Most versions online have a way to remove this activation method, although the copy on BetaArchive's FTP server has these methods removed.

Missing files
During setup, you will encounter a prompt that asks you where to look for some files. The default answer is the root directory of your CD-ROM drive, but you must use the i386 directory to copy those files. If not followed, a lot of applications will be missing. Note that this only applies to the original leak.

Missing files in the original images
The original copies of this build are completely unfixed, meaning that the above instructions will not work, since the files do not exist anywhere. You must provide the following files to setup in some way for it to finish correctly. They can be stubs, or the real files from a period-correct build that has them. File list Blank.txt Empty.txt Sample1.jpg Sample2.jpg filters.xml moviemk.chm moviemk.exe news.png paint.png (Files below are on the installation media, but the file names omit the leading w) wWMalert.wav wWMemail.wav wWMonline.wav wlogowin.gif wlvback.gif wmsgsc.dll wmsgslang.dll wmsmsgs.exe wtype.wav wxpmsgr.chm

Leak
The Professional version of this build was released with the following note from the original leaker. According to mrpijey, it was provided by an anonymous source.

"Build: Windows Server 2003 ".NET Server" (5.2.3790.1232 Professional Beta)

Compiled: 2004-08-19

This build is a pain in the neck. It should really be called 'Windows Server 2003 "We have no clue what this thing is called because Microsoft are lazy people and don't give proper names to a lot of their project reset builds" (5.2.3790.1232) (Professional Beta)'. This 3790.1232 can be considered a Windows Server 2003 Post-RTM but this particular build was built by the Winmain lab, odd for a server build. What really happened was the Winmain lab taking .NET Server 5.2.3790.1232 when Microsoft were resetting the Longhorn project and decided to toy around with it. You could call this pre-Longhorn Omega-13 if you really wanted, but there isn't really a name for this build, except for "Windows Pain in the neck". While the Longhorn EULA is in there, it isn't necessarily a Longhorn build. It was merely a test build for Microsoft to play with before they moved to Longhorn post-reset pre-beta.

Let's put this on a timeline to make it understandable.

Build 4093 declared a mess, Microsoft decides to reset the project

While Microsoft decides to reset the project, it just so happens 5.2.3790.1232 happens to be the latest code

Microsoft take it and tell the Winmain lab to compile it for the sole reason of playing with it

Microsoft decide to use this as base and move on to begin Longhorn development

I bet you did not understand a word of that whatsoever. Basically, this build is what Longhorn is based on, but it is not strictly Longhorn. It's basically a Server 2003 RTM with SP1 Release Candidate slipstreamed and given a Professional client SKU. This means all the server goodies were removed."

Another thread about the build containing an NFO claiming that the original leak was a "RELEASE BY "KiTTY"" was discussed on the BetaArchive forum. The NFO contained comments possibly directed at BetaArchive staff, due to similar criticism also used (with explicit mention of said site) in the NFO of Windows 8 build 8888 (win8_gdr_soc_intel).

NOTE: The NFO is provided for historical purposes only. NFO contents

''