Talk:Windows Server 2003 build 3615

OK. I copied the file 3615 build driver.cab to build 3604 from the file driver.cab copied the file only ntkrpamp.exe, ntkrnlmp.exe, and ntoskrnl.exe. The ntdll.dll file from driver.cab I can not find. If ntdll.dll is missing from driver.cab. I can first delete from 3604 build files ntkrnlmp.ex_ and ntoskrnl.ex_. I can copy the driver.cab and ntdll.dll files from this build 3615 to the 3604 build and then from the driver.cab 3615 file I copy ntkrpamp.exe, ntkrnlmp.exe, and ntoskrnl.exe. I will be grateful in advance.
 * NTDLL.DLL is in DRIVER.CAB, maybe your copy is broken.--Winins (talk) 16:49, 10 October 2019 (UTC)


 * OK. I copied the driver.cab and ntdll.dll files from this build 3615 to build 3604, then copied the files from dirver.cab 3615, ntkrnlmp.exe, ntoskrnl.exe, ntkrpamp.exe. and the build should be installed.

Hey releaked
I found uncorrupted copy build 3615. please see https://archive.org/download/windows-.net-whistler-server 16:15, 6 May 2020 (UTC)
 * I had a look. There are the same corrupt copies. For all three editions: Enterprise, standard and web server. BenjiMadden7850 (talk) 16:45, 6 May 2020 (UTC)
 * I checked one file from build 3615. 100% full ISO-image. 195.191.235.159 16:49, 6 May 2020 (UTC)
 * We need an uncorrupted copy of build 3615. 195.191.235.159 16:55, 6 May 2020 (UTC)
 * In case you haven't got the idea. Check I386/EULA.TXT in web server, and VALUEADD/VALUEADD.HTM in all three editions. Then take a look in 3621's (uncorrupted) VALUEADD/VALUEADD.HTM. These are just the same corrupted 3615 isos we have seen before...
 * BenjiMadden7850 (talk) 16:59, 6 May 2020 (UTC)
 * Just take these files and start the installation? 195.191.235.159 17:00, 6 May 2020 (UTC)
 * That will not work. I tried to setup Web Server, but it didn't work because eula was corrupt. Enterprise Server didn't work. Winnt32.exe was corrupted too. I haven't tried standard server, but i'm pretty sure all three of these iso's are the same old corrupt iso's that you can find elsewhere on the internet. BenjiMadden7850 (talk) 17:11, 6 May 2020 (UTC)
 * If the iso's are corrupted, there is nothing to solve. ToMi (talk) 17:16, 6 May 2020 (UTC)
 * Nice try, Rain Ocampo. BF10 (talk) 17:17, 6 May 2020 (UTC)

Releaked?
This build releaked??? 5.149.255.178 11:50, 27 May 2020 (UTC)
 * no BenjiMadden7850 (talk) 11:52, 27 May 2020 (UTC)

About installing Windows Server 2003 build 3615
Does there is a way to install Windows Server 2003 build 3615 by replacing files that actually corrupted with uncorrupted ones from build 3604? User:WindowsServerFan (talk) 12:11, 18 December 2021 (UTC)


 * You can try to replace with the uncorrupted files from build 3604 in the this build. Bubblebeam (talk) 12:13, 18 December 2021 (UTC)


 * And also which files are corrupted? Yes, I am going to try replacing the corrupted files with 3604 uncorrupted ones, but idk which files are corrupted. And yes, rescuing Windows Server 2003 build 3615 is possible/easier than Windows Longhorn build 4048. And yes, replacing driver.cab, ntdll.dll, ntoskrnl.exe, ntkrnlmp.exe, ntkrnlpa.exe, ntkrpamp.exe is not enough, as it is techically Windows Server 2003 build 3604, which identifies itself as 3615. No, we need all uncorrupted files from 3615, and then replacing 3604's files with 3615's uncorrupted ones in 3604 iso or replacing 3615's corrupted ones with 3604's uncorrupted ones in 3615 iso. User:WindowsServerFan (talk) 14:29, 18 December 2021 (UTC)


 * 4048 is nearly irrecoverable, since it uses the WIM installation method and the install.wim of this build is mostly corrupt. 3615 is easier to rescue since the system files are still directly on the i386 folder, though they are compressed.


 * BTW, 4048 is also recently rescued by lucasm User:WindowsServerFan (talk) 15:22, 10 January 2022 (UTC)