Windows 2000 build 2020

5.0.2020.1
	Build of Windows 2000
OS family	Windows NT
Version number	5.0
Build number	2020
Build revision	1
Architecture	x86
Compiled on	1999-04-13
Expiration date
Timebomb	+444 days after original install date
SKUs
	Professional
About dialog

Windows 2000 build 2020 is a Beta 3 build of Windows 2000 that was originally leaked by Blackwolf onto the #mswin2k channel of EFNET in 1999 and then found on 23 June 2015.^[1]

This build was copied directly from the build server and includes the typical elements of such builds: CHKFILE.BLD file listing checksums of all compiled binaries; IDW tools; files of the Windows NT 3.51 update engine.

Changes[edit | edit source]

The startup and shutdown sounds have been changed to the ones heard in the released product.
The appearance of the progress bars in setup has been changed.

Bugcheck codes[edit | edit source]

The 0xC5 bugcheck code has been modified to change "system memory pool" to "executive memory pool".
A new bugcheck message ("This driver may be at fault") has been added to allow pointing out the driver file causing the fault. Earlier builds after the transition to using the VGA driver for bugchecks does not point out any information about the problematic drivers, making diagnosing driver-related errors more difficult. This message is named BUGCODE_ID_DRIVER and is inserted in bugcheck code 0xD2.^[2] It was removed during Windows XP's development, but was later readded during Windows 8's development.
New bugcheck codes have been added:
- DRIVER_LEFT_LOCKED_PAGES_IN_PROCESS (0xCB)
- The system is attempting to access memory after it has been freed. This usually indicates a system-driver synchronization issue. (0xCC, later renamed PAGE_FAULT_IN_FREED_SPECIAL_POOL)
- The system is attempting to access memory beyond the end of the allocation. This usually indicates a system-driver synchronization issue. (0xCD, later renamed PAGE_FAULT_BEYOND_END_OF_ALLOCATION)
- DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS (0xCE)
- TERMINAL_SERVER_DRIVER_MADE_INCORRECT_MEMORY_REFERENCE (0xCF)
- A device driver has corrupted the system memory management pool. (0xD0, later renamed DRIVER_CORRUPTED_MMPOOL)
  - This bugcheck includes the same instructions from code 0xC5 after the error message.
- DRIVER_IRQL_NOT_LESS_OR_EQUAL (0xD1)
- The driver mistakenly marked a part of it's image pagable instead of nonpagable. (0xD3, later renamed DRIVER_PORTION_MUST_BE_NONPAGED)
- The driver unloaded without cancelling pending operations. (0xD4, later renamed SYSTEM_SCAN_AT_RAISED_IRQL_CAUGHT_IMPROPER_DRIVER_UNLOAD)
- The driver is attempting to access memory after it has been freed. (0xD5, later renamed DRIVER_PAGE_FAULT_IN_FREED_SPECIAL_POOL)
- The driver is attempting to access memory beyond the end of the allocation. (0xD6, later renamed DRIVER_PAGE_FAULT_BEYOND_END_OF_ALLOCATION)
- The driver is attempting to unmap an invalid memory address. (0xD7, later renamed DRIVER_UNMAPPING_INVALID_VIEW)

Bugs and quirks[edit | edit source]

Installation[edit | edit source]

The unmodified version of this build cannot be normally installed (via CD boot) due to a bugcheck during setup. The user can either use a DOS boot disk to partition and format the drive and then run setup from there, or replace the cdrom.sy_ file in the i386 folder on the CD with a copy from a different build.

Also, sometimes when upgrading from Windows via WINNT32.EXE, Setup asks the user to insert the installation disc during the text-mode part, despite already being inserted. This can also be a fault with the CD-ROM driver. It is recommended to select "Install a new version" instead, go to "Advanced Options..." and select "Copy all Setup files from CD-ROM to the hard disk".

WINNT32.EXE was also modified by the warez group who shared the build to display their NFO file before the actual setup application launches. (VOS.VDB is the NFO, SOC.VDC is an AVI video, and USRV.EXE is the original WINNT32.EXE)