[REQ] Windows Server 2003 build 3676 corrupt copy
Forum rules
Please read the following rules before posting a download request in this area:
1. Don't post a request if you have under 10 posts as stated in the rules. If you do anyway, it will be deleted without further notice.
2. Requests for anything against our rules will not be entertained and you will be warned.
3. Check that we don't already have the file on our FTP servers by using the database linked in the navigation.
Please read the following rules before posting a download request in this area:
1. Don't post a request if you have under 10 posts as stated in the rules. If you do anyway, it will be deleted without further notice.
2. Requests for anything against our rules will not be entertained and you will be warned.
3. Check that we don't already have the file on our FTP servers by using the database linked in the navigation.
-
captainlinux8880
- Posts: 373
- Joined: Sat Jul 27, 2019 10:11 am
- Location: Somewhere on planet Earth.
[REQ] Windows Server 2003 build 3676 corrupt copy
Hello. On June 12, 2022, a corrupted copy of Windows Server 2003 build 3676 was leaked. Source. Who has the download link? I want to look at the ISO and try to fix it. Thanks.
-
Windows Thunderstruck
- Posts: 583
- Joined: Tue Aug 08, 2017 2:11 pm
-
captainlinux8880
- Posts: 373
- Joined: Sat Jul 27, 2019 10:11 am
- Location: Somewhere on planet Earth.
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
Can't fix... The kernel is corrupted. The file NTDLL.DLL (kernel) located in I386/System32 is also broken, so this build cannot be repaired. Only text files in ISO survived...
-
PivotGuy246
- Posts: 115
- Joined: Wed Dec 30, 2015 4:32 pm
- Location: The Void
- Contact:
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
The ISO may be thoroughly screwed, but the NT kernel surely isn't given that DRIVER.CAB is almost entirely recoverable:captainlinux8880 wrote: ↑Mon Jun 13, 2022 12:33 pmCan't fix... The kernel is corrupted. The file NTDLL.DLL (kernel) located in I386/System32 is also broken, so this build cannot be repaired. Only text files in ISO survived...
-
captainlinux8880
- Posts: 373
- Joined: Sat Jul 27, 2019 10:11 am
- Location: Somewhere on planet Earth.
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
DRIVER.CAB is not such an important file, it can be replaced with other versions, and it seems that the system will install normally without it... If someone manages to restore the kernel, then it will be great!PivotGuy246 wrote: ↑Mon Jun 13, 2022 1:11 pmThe ISO may be thoroughly screwed, but the NT kernel surely isn't given that DRIVER.CAB is almost entirely recoverable:captainlinux8880 wrote: ↑Mon Jun 13, 2022 12:33 pmCan't fix... The kernel is corrupted. The file NTDLL.DLL (kernel) located in I386/System32 is also broken, so this build cannot be repaired. Only text files in ISO survived...
-
PivotGuy246
- Posts: 115
- Joined: Wed Dec 30, 2015 4:32 pm
- Location: The Void
- Contact:
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
You... do realize that DRIVER.CAB does contain the NT kernel, right?captainlinux8880 wrote: ↑Mon Jun 13, 2022 1:15 pmDRIVER.CAB is not such an important file, it can be replaced with other versions, and it seems that the system will install normally without it... If someone manages to restore the kernel, then it will be great!
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
This is probably the same corrupted copy that sat on an old OSBA member's ftp server around the time it went offline.
-
captainlinux8880
- Posts: 373
- Joined: Sat Jul 27, 2019 10:11 am
- Location: Somewhere on planet Earth.
-
captainlinux8880
- Posts: 373
- Joined: Sat Jul 27, 2019 10:11 am
- Location: Somewhere on planet Earth.
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
As far as I know, nLite cuts out the DRIVER.CAB in Lite versions, as well as this file can be replaced with other versions, I remember this when I restored the Windows XP build 2600.1078PivotGuy246 wrote: ↑Mon Jun 13, 2022 1:17 pmYou... do realize that DRIVER.CAB does contain the NT kernel, right?captainlinux8880 wrote: ↑Mon Jun 13, 2022 1:15 pmDRIVER.CAB is not such an important file, it can be replaced with other versions, and it seems that the system will install normally without it... If someone manages to restore the kernel, then it will be great!
-
oscareczek
- Posts: 700
- Joined: Fri Apr 25, 2014 5:37 pm
- Location: Poland
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
And how is that relevant to DRIVER.CAB containing the copy of NTOSKRNL.EXE?
-
whistler2442
- Posts: 9
- Joined: Mon Mar 14, 2022 9:41 am
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
Yes. It refers to the file DRIVER.CABoscareczek wrote: ↑Mon Jun 13, 2022 1:57 pmAnd how is that relevant to DRIVER.CAB containing the copy of NTOSKRNL.EXE?
-
captainlinux8880
- Posts: 373
- Joined: Sat Jul 27, 2019 10:11 am
- Location: Somewhere on planet Earth.
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
oscareczek wrote: ↑Mon Jun 13, 2022 1:57 pmAnd how is that relevant to DRIVER.CAB containing the copy of NTOSKRNL.EXE?
in 1078 it is also contained there, lol. however, when replacing DRIVER.CAB from SP1, build 1078 still identifies itself as 1078 and not SP1. Driver.cab just stores drivers...
-
qazmko1029
- Posts: 213
- Joined: Sun Mar 31, 2013 2:36 am
Re: [REQ] Windows Server 2003 build 3676 corrupt copy
With service pack installer integrated, some files wouldn't get updated including driver.cab. This does not happen in official integrated version.captainlinux8880 wrote: ↑Mon Jun 13, 2022 2:33 pmin 1078 it is also contained there, lol. however, when replacing DRIVER.CAB from SP1, build 1078 still identifies itself as 1078 and not SP1. Driver.cab just stores drivers...