Windows 2000 в 2020 году

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.

NFO file[edit | edit source]

                     Brought to you by #Mswin2k on EFnet.

                                                                          
╔═══════════════════════════════════════════════════════════════════════════╗
║ [ Microsoft Windows 2000 Professional Build 2020 ]   April 14,1999        ║
║ [ Beta 3 RC1 ]                                                            ║
╟───────────────────────────────────────────────────────────────────────────╢
║ Type..........: OS                   │ Provider..: Jolly Ole' Saint Nick  ║                    ║      ║
║ Cracker ......: N/A                  │ Video ....: N/A                    ║   ║
║ Packager .....: Willy Gates          │ Audio ....: N/A                    ║   ║
║ Protection ...: N/A                  │ # Disks ..: 14X 25MB (1x 13.8MB    ║
╚═══════════════════════════════════════════════════════════════════════════╝


┌─────────────────────────────┤Release NoteZ├──────────────────────────────┐
│This is an internel release of Win2k, it was not released to testers.     │
│It includes a dump dir full of goodies for the developers.                │
│Still not beta3, but close. It grows more stable every build.             │
│Well... almost every build.. =P                                           │
│                                                                          │
└──────────────────────────────────────────────────────────────────────────┘

                                 
┌──────────────────────────────┤Shout OutZ├────────────────────────────────┐
│ AcktiveX, Phreeze, Blackwolf, [[, Twk-B, Invy, BillGatez, PsYbErJaK,     │
│ Violent|J, ^Techie^                                                      │
└──────────────────────────────────────────────────────────────────────────┘


props to my niggas - caldude, office9, aba, nailbomb, and the man BJM

THESE ARE NOT THE FUCKING BLACKWOLF BUILDS 

THESE ARE #MSWIN2K BUILDS :)

UNTIL NEXT BUILD...REMEMBER...WHO'S YER DADDY

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)

Gallery[edit | edit source]

Setup[edit | edit source]

• Preparing setup

• GUI setup

• Installing devices

• Installing network

Interface[edit | edit source]

• System Properties

• Safe to shutdown screen

References[edit | edit source]

Hi, I’d like to say thank you all for the help. Certainly the name «Use personalized menus» for this option doesn’t make sense at all but it worked.

It’s great to see the Windows 2000 still working so well, even with @blackwingcat’s amazing kernel extender, I’m using the latest SeaMonkey (2.49.5) to post this here. Although this is not Windows 98 (Which I loved much more) it is almost the exact same thing, so I have a similar experience like I had when I was a kid.

Just FYI, The screenshot I posted shows two Netscapes, but they aren’t real Netscape; It’s just SeaMonkey and Pale Moon 28.x skinned to look like old (v4 and v9, respectively) Netscape, which was my browser of choice back in late 90’s.

Thank you all!

IMPORTANT NOTICE: This method no longer works. Microsoft dropped support for SHA-1 updates at the end of July 2020, just under three months after I wrote this article, and as such decommissioned Windows Update for older Windows operating systems in the process. I’m leaving the article here for historical reasons as all the links in it currently still work.

If you need to update Windows 2000 Pro for whatever reason I recommend you use a third party tool like Legacy Update. Or you could just download an archive (link below) I made shortly after writing this article (as I suspected that Windows Update wouldn’t last forever, though I had no idea it was only going last another few months). As far as I know it contains every available update for a Windows 2000 Pro SP4 installation and even has some handy batch scripts to install most of them for you.

🗜️Windows 2000 Pro Updates (432MB)
— SHA256 Hash: dfa446c26ddb64d3fdc272d9c66b6beb84a7b8f4b96bb7713be5dba1d9657973

Recently I had need to reinstall Windows 2000 Professional, which I did in a Virtual Machine (I used VMWare’s Workstation Player, which is free for non-commercial use). Now, although my usage of Win2K Pro was itself going to be relatively restricted and I had installed a version that came with Service Pack 4, I decided it’d probably be best if I did update it, but when I ran Windows Update I unsurprisingly found it just didn’t work. It wasn’t surprising because of how old the OS is now and also because its extended support period ended almost ten years ago. I did find out though that it is possible to fix, which was surprising.

There’s a lot of misinformation out there about how to actually get it working again, mostly because it appears lots of people that explain how to do it did so years ago when perhaps certain software requirements were different and various websites still existed. After a bit of trial and error though I did figure out how to get it working by myself and it’s not all that difficult either, all you may have trouble with is obtaining one or two of the files you need as old resources pointing to them either don’t exist or are outdated. Anyway without further ado, you need the following files and to install them in this order:

• Service Pack 4
• Microsoft Internet Explorer 6 Service Pack 1 (Windows 2000)
• Root Certificates Update
• Microsoft Windows Installer 3.1
• Update for Background Intelligent Transfer Service (BITS) 2.0 and WinHTTP 5.1 (KB842773)
• Windows Update Agent
• Enable & Use TLS 1.0 in Internet Options

Firstly telling you to install SP4 is a given, but I highly recommend you install 2K Pro from a source that already includes it for the sake of ease, I only mention the service pack in case you forgot and are installing Windows from an older source that didn’t include it. Secondly the Root Certificates Update is a silent install; once you run it nothing will appear to happen but it has in fact installed as expected in the background. Thirdly I’m not entirely sure if it’s necessary to install Windows Update 3.1 for this process but even if it isn’t you might as well update it while you’re at it. Lastly that ‘Use TLS 1.0’ option you need to change is fairly simple to do; it’s located under the security heading on the advanced tab of the Internet Options control panel:

Картинка с сайта: www.xenodyne.co.uk

You may have already discovered to your annoyance that I haven’t actually linked to any direct downloads but have instead linked to pages that have links to the downloads. The 3rd and 5th links simply point to search results in the Microsoft Update Catalogue website, which is not particularly helpful on my part I know and I apologise if that’s pissed you off, but I am unsure of Microsoft’s hotlinking policy for the catalogue website and besides which it seems a bit buggy and somewhat dynamic in the way it generates results, so direct linking probably wouldn’t work anyway.

If you click one of these two links, it will direct you to the website with a search query in place to bring up results that hopefully include the ones you need to download. However this website has a frequent tendency to do one of three things; either show you the result you need in amongst a bunch of other results that you don’t, show you a bunch a results that do not include the result you need even though it should (see picture below), or just not show you anything at all.

Картинка с сайта: www.xenodyne.co.uk

It’s clearly a bit beta in nature, or just badly coded. Either way what you want to do when searching the catalogue is to make sure the update listed has «Windows 2000» in the Products field (bare in mind some updates apply to more than one Windows OS too). If you search for an update and it brings up results for other operating systems but not for Windows 2000 (common for the BITS update as shown above), keep refreshing the page or clicking the search button on the top right and eventually it’ll show you the update you’re actually looking for… Well it should do anyway. While refreshing the page two or three times usually gets it to work, I have found on occasions that I had to wait a while before searching again so it would list the updates I wanted.

That’s not the end of it though, as once you click on the download button for an update it’ll open a new window with the actual links to the files. There’s usually one or two, but sometimes several (oft for different languages if the update needed to be localised). However even this doesn’t always work properly and you may get weird file links or an error, but again reloading it usually works and this may be required several times. It’s less glitchy than the search function though so it does seem to work as expected most of the time. However for the sake of making things easier for you, once you’ve downloaded the files you can compare them to this list of filenames to make sure you got the right ones:

ie6setup.exe

rootsupd_fe44934fd80dd11fec2f0f9b24431658a4f6d589.exe

WindowsInstaller-KB893803-v2-x86.exe

windows2000-kb842773-x86-enu_e676d47e065a314bbf1d15b096a67aede6b0539a.exe

windowsupdateagent30-x86.exe

On the positive side though, it does seem Microsoft have almost every update they ever released for older operating systems on this catalogue website, so if you for instance wanted to download every update for Windows 2000 Pro yourself and store them somewhere for safe keeping you can for the most part. If however you run into trouble and cannot find anything on the catalogue, the Internet Archive does tend to have pages from Microsoft’s old download websites and even the files saved, but I’ll leave that up to you to figure out.

Windows 2000 Pro
Windows Update
Workaround