Build list legend
Available build 
Confirmed build 
Unconfirmed build 
Fake build Existing page
Non-existent page
Non-existent page
Windows NT 4.0
| Version of Microsoft Windows | |
.svg){kind=logo} | |
 | |
| OS family | Windows NT |
|---|---|
| Version | 4.0 |
| Codename | Shell Update Release |
| Architecture | x86 (PC/AT, PC-98), DEC Alpha, MIPS, PowerPC |
| Latest build | 4.0.1381.7097 (Service Pack 6a Security Rollup update) |
| Release date | 1996-08-24 |
| Support end | 2004-06-30 (Workstation) 2004-12-31 (Server) 2006-07-11 (Embedded) 2006-12-31 (with Extended Security Updates) |
| Replaces | |
| Windows NT 3.5x | |
| Replaced by | |
| Windows 2000 | |
Windows NT 4.0 (codenamed Shell Update Release or Tukwila)[a] is a major version of Windows NT, which was released on 24 August 1996 as the successor to Windows NT 3.51 released a year before. It introduces the Windows 95 user interface to the Windows NT line, as well as includes major architectural changes to the operating system such as moving a large part of the graphics subsystem to kernel mode.
At launch, Windows NT 4.0 supported 486 and newer processors as well as MIPS, DEC Alpha and PowerPC. However, most of the ports were ultimately deprecated in the following years, with support for the last surviving non-x86 version for the DEC Alpha being dropped in August 1999.
This version originally launched in Workstation and Server editions. An Enterprise Edition of Windows NT Server 4.0 was released in 1997 and is designed for high-demand, high-traffic networks. The Terminal Server Edition (codenamed Hydra), introduced in 1998, allows users to log-in via a remote desktop client. Finally, Windows NT Embedded 4.0 (codenamed Impala) was launched in 1999, which allows developers to pick individual system components to build a custom version of Windows NT.
The Server and Workstation editions were succeeded by Windows 2000 on 17 February 2000. Windows NT 4.0 continued to be supported up to 2006 in various forms. A total of six Service Packs and a Security Rollup Package were released during its lifetime.
Editions[edit | edit source]
There are several editions of Windows NT 4.0:
- Workstation
- Server
- Enterprise Edition
- Terminal Server Edition
- Embedded
Service Packs[edit | edit source]
There were 6 service packs released for Windows NT 4.0. Only Service Pack 1 was made available for the MIPS architecture, and Service Pack 2 was the final release for the PowerPC architecture. The last had been pulled by Microsoft due to a severe bug, which results in the revised Service Pack 6a. Microsoft had originally intended to release a seventh service pack for Windows NT 4.0, but eventually canceled it, and instead released an update rollup in 2001.[1][2]
| Architecture | SP1 | SP2 | SP3 | SP4 | SP5 | SP6 | SRP |
|---|---|---|---|---|---|---|---|
| x86 | Yes | Yes | Yes | Yes | Yes | Yes | Yes |
| DEC Alpha | Yes | Yes | Yes | Yes | Yes | Yes | No |
| PowerPC | Yes | Yes | No | No | No | No | No |
| MIPS | Yes | No | No | No | No | No | No |
Option Pack[edit | edit source]
The Windows NT 4.0 Optional Pack was released in 1997 and includes server solutions and clients for Windows NT 4.0 Workstation, Server and Windows 95, including Personal Web Server, Transaction Server, Message Queue Client, FrontPage 98 Server Extensions, Management Console, Script Debugger, Windows Scripting Host, Data Access Components and Internet Information Services 4.0.
Installing the Option Pack requires Service Pack 3 to be installed. Installing it on Service Pack 4 and later will cause setup to show an information that the option pack was not tested on Service Pack 4 yet, but lets the user continue.
System requirements[edit | edit source]
The x86 version of Windows NT 4.0 requires a 486 processor, at least 16 MB of RAM, 110 MB of hard drive space (varies depending on components being installed), and a VGA or better display.[3] Windows NT 4.0 drops support for 80386 processors. Windows NT 4.0 allows installation to be possible without a floppy drive via CD-ROM media, although a floppy drive is required if one wants to make an Emergency Repair Disk or if not booting directly from the CD.
Hardware compatibility[edit | edit source]
Earlier releases of Windows NT 4.0 do not support processors with a CPUID higher than 3.[4] The system will crash during setup or boot if run without limiting the CPUID to less than 3. Service Pack 6 fixes this kernel issue.
Product Team credits Easter egg[edit | edit source]
Windows NT 4.0 contains the Product Team credits Easter egg from Windows 95. Like in Windows 95, it is implemented in SHELL32.DLL, and the steps to show it are much the same as in Windows 95; create a new folder and renaming it to each of the following names in order:
- and now, the moment you've all been waiting for
- we proudly present for your viewing pleasure
- The Microsoft Windows NT Product Team!
The only main difference from the one in Windows 95 is that any references to "95" are replaced with "NT".
The text is in SHELL32.DLL's resource BIN and XORed with 0x95 as an obfuscation measure. For similar reasons, the Easter egg folder names are stored in the .text section of SHELL32.DLL as custom hashes of the old folder name concatenated with the new folder name. This was implemented by build 1175 and there shows the "SUR Shell Team" and "SUR Shell Test Team"; at some point after that the text was replaced by a message informing that "you won't find the credits here".
Source code leak[edit | edit source]
In early 2004, the source code for Windows NT 4.0 Service Pack 2 leaked online, together with a partial copy of the Windows 2000 source code.[5] The source of the leak was traced to Mainsoft, the developer of MainWin, an application that allowed developers to port existing Windows programs to Unix systems, whose development required access to selected portions of Windows source code under Windows Interface Source Environment program.[6] In response, Microsoft released the following statement:
On Thursday, February 12, Microsoft became aware that portions of the Microsoft Windows 2000 and Windows NT 4.0 source code were illegally made available on the Internet. Subsequent investigation has shown this was not the result of any breach of Microsoft's corporate network or internal security, nor is it related to Microsoft's Shared Source Initiative or its Government Security Program, which enable our customers and partners, as well as governments, to legally access Microsoft source code. Microsoft reaffirms its support for both the Shared Source Initiative and the Government Security Program.
Microsoft continues to work closely with the U.S. Federal Bureau of Investigation and other law enforcement authorities on this matter. Microsoft source code is both copyrighted and protected as a trade secret. As such, it is illegal to post it, make it available to others, download it or use it. Microsoft will take all appropriate legal actions to protect its intellectual property. These actions include communicating both directly and indirectly with those who possess or seek to possess, post, download or share the illegally disclosed source code.
Specifically, Microsoft is sending letters explaining to individuals who have already downloaded the source code that such actions are in violation of the law. Additionally, Microsoft has instituted the use of alerts on several peer-to-peer clients where such illegal sharing of the source code has taken place. These alerts are designed to inform any user who conducts specific searches on these networks to locate and download the source code that such activity is illegal.
Questions about the ongoing investigation should be referred to the FBI.
— Microsoft Corporation[7]
Despite the warnings, the archive containing the leaked code spread widely on the file-sharing networks and, even later, on open-source repository websites. On 16 February 2004, an exploit allegedly discovered by an individual studying the leaked source code for certain versions of Microsoft Internet Explorer was reported. On 15 April 2015, a repository containing the leaked NT 4.0 source code was removed from GitHub at Microsoft's request,[8] although other repositories hosting the Windows 2000 source code continued to exist in the same website; most of them were taken down by Microsoft's request on 9 April 2021.[9]
List of known builds[edit | edit source]
Available build Confirmed build Unconfirmed build Fake build Beta 1[edit | edit source]
Beta 2[edit | edit source]
Release Candidate 1[edit | edit source]
Release Candidate 2[edit | edit source]
Pre-RTM[edit | edit source]
RTM[edit | edit source]
International Beta[edit | edit source]
Service Pack 1[edit | edit source]
Service Pack 2[edit | edit source]
Service Pack 3[edit | edit source]
Service Pack 4[edit | edit source]
Service Pack 5[edit | edit source]
Service Pack 6[edit | edit source]
Service Pack 6a[edit | edit source]
Security Rollup[edit | edit source]
Notes[edit | edit source]
- ↑ Most official documentation uses Shell Update Release or SUR. Tukwila is an internal name coined by Dave Cutler.
References[edit | edit source]
- ↑ Update on Windows NT 4.0 Service Pack 7, Windows NT Server. 19 April 2001. Archived from the original on 28 April 2001.
- ↑ Kerr, Rob. MS ditches Service Packs for Windows NT 4.0, The Register. 18 April 2001.
- ↑ ARCHIVED: What is Microsoft Windows NT?, University Information Technology Services. 18 January 2018.
- ↑ CPU Identification by the 32-Bit Windows Kernel, Geoff Chappell - Software Analyst. 22 January 2008.
- ↑ https://archive.org/download/NFO_Collection_2000-2004_Compilation/NFO_COLLECTION_UNPACKED/2004/02-2004/NF_DAILY_NFO_COLLECTION-13-02-2004.zip/_NUKED_MICROSOFT.WINDOWS.2000.AND.NT4.SOURCE.CODE-SCENELEADER.nfo
- ↑ Mook, Nate. Windows Source Leak Traces Back to Mainsoft, BetaNews. 13 February 2004.
- ↑ Microsoft. Statement from Microsoft Regarding Illegal Posting of Windows 2000 Source Code, Microsoft PressPass. 12 February 2004.
- ↑ Van der Sar, Ernesto. Microsoft Takes Pirated Windows NT 4.0 Source Code Offline, TorrentFreak. 15 April 2015.
- ↑ Microsoft. DMCA takedown request filed on behalf of Microsoft Corporation, GitHub. 9 April 2021.
.svg){kind=logo}