Windows XP/Server 2003 source code revisited

Hi everyone. As you may know, lots of people aren’t interested much of compilation & further development of Windows XP/Server 2003 source code. By referring to guides from 2020/21, I succeed of compilation. Also I will share a simple guide of how to do that (based on Windows Server 2003 (NT 5.2.3790.0) build guide). Here’s a screenshot to prove that it’s a real compiled build.


  • Create and install Windows 10’s latest version virtual machine, with minimum 120GB disk space and 4GB memory and processor cores
  • Allocate D:\ disk drive for entire source code (min. 60GB)
  • Change CD-ROM drive to G:\ (for getting missing files if neccesary)
  • Disable User Account Control - needs for avoid screens of confirmation
  • Download source code from link below
  • Important! Disable Real-Time Protection from Windows Security
  • Extract source code to D:\srv03rtm
  • Uncheck read-only from srv03rtm folder
  • Install driver.pfx from “tools” folder for Local Machine & Current User
  • Run Command Prompt as Administrator, and switch to D:\srv03rtm.
  • Run tools\prebuild for prepare to building
  • Type “build /cZP -M 4” (-M 4 for using all 4 cores of processor)
  • Extract missing binaries to D:\binaries.x86fre (link will be uploaded later)
  • Type on CMD “tools\postbuild -full”
  • Then, write “tools\oscdimg pro|per|srv” for generating ISO file for XP Professional/Home Edition/Server 2003 Standard Edition

Serial key located at srv03rtm\base\ntsetup\pidgen\pidgen\spidgen.cpp, and it’s HB9CF-JTKJF-722HV-VPBRF-9VKVM

Missing instructions I will write here. You can use guide at top as quick reference to get all missing things. Link to missing binaries of source I will upload later.

Download Links

Source code: srv03rtm.7z - Google Drive
Missing files: misbin.7z - Google Drive

1 Like

Link to missing binaries: misbin.7z - Google Drive

i’m never even able to find a download

and when i ask for one i get ignored

I already provided link for downloading
Click to link below

is this the files of the leak or on a fixed up version of the leak done in 2021

edit: there’s a readme file claiming this is prepatched 10a. good.

these files are contains all patches and modifications of v10a.

did you tamper with code related to windows registry installation?

the error message id is SP_SCRN_REGISTRY_CONFIG_FAILED.

nope. did you edited some config files or don’t follow instructions properly?

I’m 4 months trying to make a build and I can’t do it at all… I’m using Windows XP Pro x86 sp3, I get about 8 errors in a build, and I don’t even know how many in the postbuild… I already I’m discouraged

I used every rentry co guide but it didn’t work

Some questions here:
Can I use Windows 10 x64?
Do I need to change the date? Or create new certificates?

u can iirc

(late oops) seemed to be an issue with certificates as generating new ones fixed the issue

nothing need to change. I regenerated certificates in November, 2022. they will be valid for additional 100 years thankfully to guide Win2K3 test certificates utility.

and use minimum Windows 10 1809 (2018 year release), because started from 1809 exists support for newer encryptions of certificates. I recommend you use latest Windows 10 x64 release.

please send errors screenshots or descriptions here

the slightly different certificates might be why setup ends up failing on some build setups. regenerating them to be more accurate to the original ones fixed my setup problem and also let me fully build srv03rtm on windows 7 (which builds it faster due to less background tasks using the hard drive)

maybe, but I don’t know how to generate them for older Windows versions. it seems in some parts needs to turn on -legacy switch for OpenSSL. anyways, in source code exists additional instruction of generation (D:\srv03rtm\tools\openssl.txt). maybe that will help. otherwise, you can use guide for Linux only

it isn’t “linux only” as the two requirements are installable on windows.

i did have a problem where a build would refuse to install afterwards but removing the code regarding this fixed it.

where and which code did you removed?

it was somewhere in cmdline.c inside of ntsetup. it should be near the code to check if someone is trying to install a timebombed build after expiration.