5eraph's post-SP2 Update Pack v2017-06_2
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
Here's an odd update:
https://support.microsoft.com/en-us/kb/3063858
It lists Server 2003 x64 (hence XP x64) as being affected, but there is no download for it.
Maybe because extended support ends in a month.
"Hey, are we gonna do this update for 2003?"
"Nah. It's too complicated, and we fired the only guy who remembers how this was coded 10 years ago".
Other updates for today:
KB3057839
KB3033890
I'll miss XP x64 getting updates after next month. Ironically, regular XP will still be supported through POSReady. Still gonna keep using it on my main computer though. Works better than anything newer out there for my purposes.
https://support.microsoft.com/en-us/kb/3063858
It lists Server 2003 x64 (hence XP x64) as being affected, but there is no download for it.
Maybe because extended support ends in a month.
"Hey, are we gonna do this update for 2003?"
"Nah. It's too complicated, and we fired the only guy who remembers how this was coded 10 years ago".
Other updates for today:
KB3057839
KB3033890
I'll miss XP x64 getting updates after next month. Ironically, regular XP will still be supported through POSReady. Still gonna keep using it on my main computer though. Works better than anything newer out there for my purposes.
Agreed, mockingbird. I'll be using XPx64 for a while yet.
Updated to 2015-06_1. Please read the Changelog for full details.
_________________
Relevant post-XP-EoS executable update packages that need the patched update.exe file to update an existing XPx64 installation:
Updated to 2015-06_1. Please read the Changelog for full details.
_________________
Relevant post-XP-EoS executable update packages that need the patched update.exe file to update an existing XPx64 installation:
I tried integrating the various update packs using a Windows XP x64 virtual machine (found that easier than using real hardware), and all has been successful. Aside from one small hiccup.
I integrated Service Pack 2 and this update pack into the same Dell OEM SP1 source. This time installation completes successfully, but the text portion of setup says it can't load "atiixpag.inf". An ATi driver? Why would it want that. VMware doesn't emulate any ATi hardware, I'm pretty sure.
I integrated Service Pack 2 and this update pack into the same Dell OEM SP1 source. This time installation completes successfully, but the text portion of setup says it can't load "atiixpag.inf". An ATi driver? Why would it want that. VMware doesn't emulate any ATi hardware, I'm pretty sure.
That file is included on all XP discs. None of my releases modify it or its metadata in other files.
I don't recall what actual hardware VMware emulates. It's usually some standardized device that uses generic drivers. XP/2003 x64 in my VirtualBox clients load the driver for "Standard VGA Graphics Adapter". The Microsoft Update website does not offer any driver updates for it.
I'd assume Dell modifies its OEM discs. Many large manufacturers include drivers and updates for their specific hardware. Dell has done it before.
I don't recall what actual hardware VMware emulates. It's usually some standardized device that uses generic drivers. XP/2003 x64 in my VirtualBox clients load the driver for "Standard VGA Graphics Adapter". The Microsoft Update website does not offer any driver updates for it.
I'd assume Dell modifies its OEM discs. Many large manufacturers include drivers and updates for their specific hardware. Dell has done it before.
I have one problem and can't figure out how to fix it.
My problem is windows media player 11.
When i have Integrate 5eraph's Windows XP x64 post-SP2 Update Pack + 5er IE8 Addon
(to clean source win xp pro sp2 x64) I have integrated wmp11 (+ hotfixes ) by using WMP11 Slipstreamer by boooggy.
So everything is OK but after installation win xp x64 to my computer i launched
FastStone Capture to record some video and i get the following error:
---------------
Unexpected error!
To record the video you need "windows media player".
Make sure that the application has been installed.
---------------
But wmp11 is already in my computer...
When i install again wmp11 on live system by overwriting all files the problem is fixed.
I think that problem is in registry entries.
Maybe some registry keys not made correctly by wmp11 slipstreamer.
I don't know wich registry keys exactly i need to apply in registry and fix this problem.
My problem is windows media player 11.
When i have Integrate 5eraph's Windows XP x64 post-SP2 Update Pack + 5er IE8 Addon
(to clean source win xp pro sp2 x64) I have integrated wmp11 (+ hotfixes ) by using WMP11 Slipstreamer by boooggy.
So everything is OK but after installation win xp x64 to my computer i launched
FastStone Capture to record some video and i get the following error:
---------------
Unexpected error!
To record the video you need "windows media player".
Make sure that the application has been installed.
---------------
But wmp11 is already in my computer...
When i install again wmp11 on live system by overwriting all files the problem is fixed.
I think that problem is in registry entries.
Maybe some registry keys not made correctly by wmp11 slipstreamer.
I don't know wich registry keys exactly i need to apply in registry and fix this problem.
We Don't Call 911
I ran RegShot in an attempt to see how I can help, minutka15. There are a great many registry entries to sort through. Don't have FastStone Capture installed on my system, but I'll see what I can do in VM. It may take me a while.
Haven't forgotten about you, MrMaguire. Been away from keyboard a lot lately. It'll take about 2 hours of time for me to reconfigure my machine and test an ISO. It may be a couple more days before I can do it.
Haven't forgotten about you, MrMaguire. Been away from keyboard a lot lately. It'll take about 2 hours of time for me to reconfigure my machine and test an ISO. It may be a couple more days before I can do it.
MrMaguire, I finally found time to reconfigure my main machine to test install Win2003. But I am still unable to reproduce any of your symptoms using update pack and IE8 addon v2015-05_1 and Win2003 addon v2015-04_1, including your atiixpag.inf issue. Bear in mind that I have an nVidia GTX 650 card, so that particular issue may be beyond my ability to troubleshoot.
Updated to 2015-06_2:
Relevant post-XP-EoS executable update packages that need the patched update.exe file to update an existing XPx64 installation:
- Updated Adobe Flash to v18.0.0.194 from v18.0.0.160.
Relevant post-XP-EoS executable update packages that need the patched update.exe file to update an existing XPx64 installation:
Updated to 2015-06_3:_________________
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
- High priority update KB2926765, released 2014/05/13.
Updated to 2015-06_4:
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
- Updated Adobe Flash to v18.0.0.203 from v18.0.0.194.
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
- High priority update KB2926765, released 2014/05/13.
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
Updated to 2015-07_1. Please read the Changelog for full details.
_________________
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
_________________
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
- High priority update KB2926765, released 2014/05/13.
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
It was good idea to remove Adobe Flash Player and Malicious Software Removal from this UP.
I wanted to say it before but i thought you could get me wrong.
Otherwise now we won the place about 20 mb than before and now we can make updated CD version and add some usefull addons too.
Thanks 5eraph
I wanted to say it before but i thought you could get me wrong.
Otherwise now we won the place about 20 mb than before and now we can make updated CD version and add some usefull addons too.
Thanks 5eraph
We Don't Call 911
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
I installed WSS03 in VMWare last night and am now just finishing up all the updates from Microsoft Update for it.Svyat wrote:I just have preinstalled WSS03 with all current updates deployed for this moment. I can provide you with direct links for updates that appear in Windows update each month.5eraph wrote:Don't know where to find updates for Windows Storage Server 2003 yet. Any ideas?
I had to recreate the ISO with a boot sector, as the ISO I downloaded didn't have one.
All said and done, it's almost 1GB of updates

Eventhough all the logos and the description in Computer Properties specifically defines it as "Windows Storage Server" or "Windows Storage Server 2003 R2", it still concerns me that I see no special provision for "Storage Server" in Microsoft Update. It just treats it like ordinary Windows Server, so we'll see if Microsoft really does keep releasing updates for it, but I won't be holding my breath.
I'm also very much interested in any downloadable Windows Storage Server 2003 x64 updates for my XP x64 machine.
If anyone knows a download source please let me know. Thanks!
I used to download the Windows Server 2003 x64 updates from xin.at but now the extended support for Server 2003 has ended this is no longer an option.
If anyone knows a download source please let me know. Thanks!
I used to download the Windows Server 2003 x64 updates from xin.at but now the extended support for Server 2003 has ended this is no longer an option.
Alter your reality...forever.
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
I am currently trying to find a copy of WSS03 for myself for the prospect of updates. While looking around I came across this in an article about WSS03:
"Like Windows 2003, Web Edition (but unlike other Windows 2003 products), Windows Storage Server is available only when
purchased with new NAS devices from vendors such as Dell, HP, and Iomega. As a result and because NAS products constitute an
unusual product category, hardware OEMs, not Microsoft, service Windows Storage Server. You must obtain bug fixes, security fixes,
and other product updates from OEM Web sites, not from Windows Update. Microsoft says it will work directly with its hardware partners
to ensure that they receive security updates as quickly as possible. However, responsibility for communicating and providing those updates
to customers will lie with the vendors."
Perhaps someone could clarify for me; but to me this sounds like WSS03 should include some software from which ever OEM
provided the hardware you should be using. With that software, you connect to the OEM's website to get the updates. Is this correct?
"Like Windows 2003, Web Edition (but unlike other Windows 2003 products), Windows Storage Server is available only when
purchased with new NAS devices from vendors such as Dell, HP, and Iomega. As a result and because NAS products constitute an
unusual product category, hardware OEMs, not Microsoft, service Windows Storage Server. You must obtain bug fixes, security fixes,
and other product updates from OEM Web sites, not from Windows Update. Microsoft says it will work directly with its hardware partners
to ensure that they receive security updates as quickly as possible. However, responsibility for communicating and providing those updates
to customers will lie with the vendors."
Perhaps someone could clarify for me; but to me this sounds like WSS03 should include some software from which ever OEM
provided the hardware you should be using. With that software, you connect to the OEM's website to get the updates. Is this correct?
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
Here's a nice big update:
https://support.microsoft.com/en-us/kb/3078601
The problem is that the download link is redirecting to KB3045685, which is an older update from April. Looking at the file details for KB3078601, it looks like they had to redo the kitchen sink. Since it's GDI+ and DDRAW, maybe they finally did something with Vsync?
The update isn't showing up in Microsoft Update for my WSS 2003 x64 VM.
https://support.microsoft.com/en-us/kb/3078601
The problem is that the download link is redirecting to KB3045685, which is an older update from April. Looking at the file details for KB3078601, it looks like they had to redo the kitchen sink. Since it's GDI+ and DDRAW, maybe they finally did something with Vsync?

The update isn't showing up in Microsoft Update for my WSS 2003 x64 VM.
Sorry 5eraph,
as you have been so kind to fix the Version Number Problem I posted in the MSFN Forum...
i came to notice by using the WSUSOffline Installer to find out about the installed roots* Version that within the Logfile of the Offline Updater some KBs where also installed [I post 'em at the end of this post]. All 8 ones are of the group where only registry entries where/should have been set to stop WU from showing them.
I tried the nlited DVD (damned be it that I have no more 800'er CD-Rs and no one is manufacturing them anymore) on the target machine and a Windows Update Run was also asking for those 8 KBs....
Then I tried (my 1st Time) a RVMI iso (Base Update Pack/IE8/Win2003/Delta) and WSUSOffline afterwards - and the KBs in question were not installed. But if I go on with nlite from that base (to deselect stuff like the tour and set service parameters/etc. [No Unattented]) the KBs are again installed by WSUSOffline....
As this may be one of the fundamental differences between RVMI and NLite I am not aksing you to fix that nlite problem within your packs - but as I am not sure what are the exact registry parameters to stop those KBs from being recognized as missing (if that is the problem)- would you be so kind to list the full reg-hive-tree-entry for them?
Or maybe some other Users have an Idea about that?
But Ok, here is the List of the KBs in Question [WSUSOffline Log/Iso Names]:
as you have been so kind to fix the Version Number Problem I posted in the MSFN Forum...
i came to notice by using the WSUSOffline Installer to find out about the installed roots* Version that within the Logfile of the Offline Updater some KBs where also installed [I post 'em at the end of this post]. All 8 ones are of the group where only registry entries where/should have been set to stop WU from showing them.
I tried the nlited DVD (damned be it that I have no more 800'er CD-Rs and no one is manufacturing them anymore) on the target machine and a Windows Update Run was also asking for those 8 KBs....
Then I tried (my 1st Time) a RVMI iso (Base Update Pack/IE8/Win2003/Delta) and WSUSOffline afterwards - and the KBs in question were not installed. But if I go on with nlite from that base (to deselect stuff like the tour and set service parameters/etc. [No Unattented]) the KBs are again installed by WSUSOffline....
As this may be one of the fundamental differences between RVMI and NLite I am not aksing you to fix that nlite problem within your packs - but as I am not sure what are the exact registry parameters to stop those KBs from being recognized as missing (if that is the problem)- would you be so kind to list the full reg-hive-tree-entry for them?
Or maybe some other Users have an Idea about that?
But Ok, here is the List of the KBs in Question [WSUSOffline Log/Iso Names]:
Code: Select all
windowsserver2003.windowsxp-kb960803-x64-enu_24a0bf0784ddd84e4039346c879a6a4345fa016a.exe
windowsserver2003.windowsxp-kb2570947-x64-enu_2c335e2756fe753bdc57706b659cc702cb946e46.exe
windowsserver2003.windowsxp-kb2584146-x64-enu_0669a06e16a21ad798240ca52b2454bf7780bf7a.exe
windowsserver2003.windowsxp-kb2638806-x64-enu_0f0d9300da2ff12634da8076ddfdc7d21bea8e7b.exe
windowsserver2003.windowsxp-kb2603381-x64-enu_7048c039de35fae6716631629138b6f3693696c0.exe
windowsserver2003.windowsxp-kb2659262-x64-enu_04fcf1e30a06d64905a6deb5ebcdd5c03dfec3f3.exe
windowsserver2003.windowsxp-kb2686509-x64-enu_345be187191d6ee8c4e78a47cc0906753202e32e.exe
windowsserver2003.windowsxp-kb2834886-x64-enu_b1721c3315f1614ee1525f4cf231b90bad1ba309.exe
Sorry for the delay, Ashpool. Wanted to be thorough.
Most of the registry entries I add--and all the ones you're looking for--are in 5erUpPck.inf on your source after integration. Just search the file for the KB numbers.
I don't know the criteria "WSUSOffline Installer" checks when searching for missing updates, or what exactly nLite removes when prompted, but QFECheck and the Windows Update website are happy with the following registry entries.
Most of the registry entries I add--and all the ones you're looking for--are in 5erUpPck.inf on your source after integration. Just search the file for the KB numbers.
I don't know the criteria "WSUSOffline Installer" checks when searching for missing updates, or what exactly nLite removes when prompted, but QFECheck and the Windows Update website are happy with the following registry entries.
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB960803","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2570947","Description",0,"Security Update for Windows Server 2003 (KB2570947)"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2570947","InstalledBy",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2570947","InstalledDate",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2570947","Type",0,"Update"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2570947\Filelist",,0x10
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Backup Dir",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Comments",0,"Security Update for Windows Server 2003 (KB2570947)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Fix Description",0,"Security Update for Windows Server 2003 (KB2570947)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Installed By",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Installed On",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Service Pack",0x10001,3
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947","Valid",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947\File 1","Flags",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947\File 1","New File",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947\File 1","New Link Date",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2570947\File 1","Old Link Date",0,""
HKLM,"SOFTWARE\Classes\CLSID\{1B53F360-9A1B-1069-930C-00AA0030EBC8}\InprocServer32",,0x00020000,"%systemroot%\system32\hypertrm.dll"
HKLM,"SOFTWARE\Classes\CLSID\{88895560-9AA2-1069-930E-00AA0030EBC8}\InprocServer32",,0x00020000,"%systemroot%\system32\hticons.dll"
HKLM,"SOFTWARE\Classes\CLSID\{D5AB5662-131D-453D-88C8-9BBA87502ADE}\InProcServer32",,0x00020000,"%systemroot%\system32\mscoree.dll"
HKLM,"SOFTWARE\Classes\Wow6432Node\CLSID\{1B53F360-9A1B-1069-930C-00AA0030EBC8}\InprocServer32",,0x00020000,"%systemroot%\SysWOW64\hypertrm.dll"
HKLM,"SOFTWARE\Classes\Wow6432Node\CLSID\{88895560-9AA2-1069-930E-00AA0030EBC8}\InprocServer32",,0x00020000,"%systemroot%\SysWOW64\hticons.dll"
HKLM,"SOFTWARE\Classes\Wow6432Node\CLSID\{D5AB5662-131D-453D-88C8-9BBA87502ADE}\InProcServer32",,0x00020000,"%systemroot%\sysWoW64\mscoree.dll"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146","Description",0,"Security Update for Windows Server 2003 (KB2584146)"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146","InstalledBy",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146","InstalledDate",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146","Type",0,"Update"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\0","BuildCheckSum",0,"1ad31"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\0","BuildDate",0,"Fri Nov 18 08:31:04 2011"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\0","FileName",0,"packager.exe"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\0","Location",0,"%11%"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\0","Version",0,"5.2.3790.4936"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\1","BuildCheckSum",0,"1073e"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\1","BuildDate",0,"Fri Nov 18 07:48:17 2011"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\1","FileName",0,"packager.exe"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\1","Location",0,"%16425%"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2584146\Filelist\1","Version",0,"5.2.3790.4936"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Backup Dir",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Comments",0,"Security Update for Windows Server 2003 (KB2584146)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Fix Description",0,"Security Update for Windows Server 2003 (KB2584146)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Installed By",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Installed On",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Service Pack",0x10001,3
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146","Valid",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146\File 1","Flags",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146\File 1","New File",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146\File 1","New Link Date",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2584146\File 1","Old Link Date",0,""
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2603381","Description",0,"Security Update for Windows Server 2003 (KB2603381)"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2603381","InstalledBy",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2603381","InstalledDate",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2603381","Type",0,"Update"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2603381\Filelist",,0x10
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Backup Dir",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Comments",0,"Security Update for Windows Server 2003 (KB2603381)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Fix Description",0,"Security Update for Windows Server 2003 (KB2603381)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Installed By",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Installed On",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Service Pack",0x10001,3
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381","Valid",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381\File 1","Flags",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381\File 1","New File",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381\File 1","New Link Date",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2603381\File 1","Old Link Date",0,""
HKLM,"SOFTWARE\Classes\Package\protocol\StdFileEditing\server",,0,"%11%\Packager.exe"
HKLM,"SOFTWARE\Classes\Wow6432Node\Package\protocol\StdFileEditing\server",,0,"%11%\Packager.exe"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2638806","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2659262","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509","Description",0,"Security Update for Windows Server 2003 (KB2686509)"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509","InstalledBy",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509","InstalledDate",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509","Type",0,"Update"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509\Filelist\0","BuildCheckSum",0,"ecc5"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509\Filelist\0","BuildDate",0,"Thu Apr 19 07:39:27 2012"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509\Filelist\0","FileName",0,"kblChecker.dll"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509\Filelist\0","Location",0,"%10%\$hf_mig$\KB2686509\update"
HKLM,"SOFTWARE\Microsoft\Updates\Windows Server 2003\SP3\KB2686509\Filelist\0","Version",0,"5.2.3790.4985"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Backup Dir",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Comments",0,"Security Update for Windows Server 2003 (KB2686509)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Fix Description",0,"Security Update for Windows Server 2003 (KB2686509)"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Installed",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Installed By",0,"5eraph's XPx64 post-SP2 Update Pack"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Installed On",0,"v2015-07_1"
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Service Pack",0x10001,3
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509","Valid",0x10001,1
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509\File 1","Flags",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509\File 1","New File",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509\File 1","New Link Date",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2686509\File 1","Old Link Date",0,""
HKLM,"SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix\KB2834886","Installed",0x10001,1

5eraph: Nothing to be sorry about.... I think at the moment I am suffering from some serious form of "Betriebsblindheit" (Sorry, don't know a translation here from german to english and dict.cc's "routine-blinded" doesn't make up to its full meaning IMHO).
To have the option of accessing the regular windows update side (without a further activation used) I was using an activated VM Install and have done repair installs over that (AFAIR it was just my XPx64 SP1 CD either slipstreamed with SP2 or with later installed SP2) - my test with the RVI Installer was on a fresh VM using M$ generic key for the Install... now I've also installed the nlited isos on a fresh VM... and well.... My Fault... There ain't no problems, all registry entries there and WSUSOffline doesn't install anything - as that one's not activated I can't test WindowsUpdate, but there shouldn't be any differences to WSUSOffline (besides superseded ones which shouldn't be a problem here).
I don't know what's actually done during a repair install (kept from the old install) - but for installers like rootsupd.ex_ within the AMD64 folder - they seem to work, registry entries and other stuff within an "updated iso" seem to be problematic... Ok, nothing I want to investigate further - it simply was my fault not thinking about it thoroughly... (But something people who really do need a repair install may want to investigate further)
Please explain:
There is not a Server 2003 x64 post-SP2 Update pack, still there ware a talks for using that one intended for x86 to be used on x64, and beside this there is a Win2003 Addon for the Update Pack which obviously it is intended to be used with post-sp2 update pack for XP x64 on Server 2003 x64. because they share the same kernel base.
So please make this clear, which update pack(s) can be used on Server 2003 SP2 x64?
There is not a Server 2003 x64 post-SP2 Update pack, still there ware a talks for using that one intended for x86 to be used on x64, and beside this there is a Win2003 Addon for the Update Pack which obviously it is intended to be used with post-sp2 update pack for XP x64 on Server 2003 x64. because they share the same kernel base.
So please make this clear, which update pack(s) can be used on Server 2003 SP2 x64?
That discussion took place before I created the 2003x64 addon in 2014. It has received considerably more testing since then.
Use both for 2003x64. The XPx64 pack is needed for the common files. And the 2003x64 addon is needed for the additional files 2003 needs.
Use both for 2003x64. The XPx64 pack is needed for the common files. And the 2003x64 addon is needed for the additional files 2003 needs.
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
Hi 5eraph,
I thought it was time to finally do a final compilation CD. So I have it with the last pack, plus the delta, flash and IE6 add-ons, but after running Microsoft Update after an in-place upgrade, it shows these updates as being available:

(I'll list the text here, for posterity's sake)
(KB2834886)
(KB2686509)
(KB2659262)
(KB2638806)
(KB2603381)
(KB2570947)
(KB960803)
(KB961118)
Thanks, and great work.
I thought it was time to finally do a final compilation CD. So I have it with the last pack, plus the delta, flash and IE6 add-ons, but after running Microsoft Update after an in-place upgrade, it shows these updates as being available:

(I'll list the text here, for posterity's sake)
(KB2834886)
(KB2686509)
(KB2659262)
(KB2638806)
(KB2603381)
(KB2570947)
(KB960803)
(KB961118)
Thanks, and great work.
The in-place upgrade is preferred by many. I think it is easier and more convenient, for the end user, IF it works correctly. That way no reinstalling applications, etc. That's one of the reasons that I also think that SP are easier than update packs, and switchless installers are easier than addons. They can all be applied in-place to a live running system.
But, applying things in-place can create many more issues to potentially have to deal with, since each end user's system can be different. I'm sure it is far easier, from the update/addon author's perspective, to start from a clean slate. It is also much more likely to end up with clean, tight, faster, and reliable system that way. So there are definite advantages to the user to install that way, but it usually takes more time and effort, especially if you have a lot of applications installed.
There are ways to deal with the above complications, such as separating the OS and applications as much as possible, preferably on different drives/partitions, and using applications that are designed to be portable so that little or no info is written to the registry. But that requires thought ahead of time to accomplish, and not all applications are available in that format. More headaches are created if you want to dual/triple boot, and there is more aggravation to be sure that each application is set up so that any data is stored separately from the app and the OS for ease of access and backup. All of that is way more complicated for the vast majority of users to deal with, and the OS and application authors all know that, so they just let everything end up on C:, which leads us right back to the original issue.
Cheers and Regards
But, applying things in-place can create many more issues to potentially have to deal with, since each end user's system can be different. I'm sure it is far easier, from the update/addon author's perspective, to start from a clean slate. It is also much more likely to end up with clean, tight, faster, and reliable system that way. So there are definite advantages to the user to install that way, but it usually takes more time and effort, especially if you have a lot of applications installed.
There are ways to deal with the above complications, such as separating the OS and applications as much as possible, preferably on different drives/partitions, and using applications that are designed to be portable so that little or no info is written to the registry. But that requires thought ahead of time to accomplish, and not all applications are available in that format. More headaches are created if you want to dual/triple boot, and there is more aggravation to be sure that each application is set up so that any data is stored separately from the app and the OS for ease of access and backup. All of that is way more complicated for the vast majority of users to deal with, and the OS and application authors all know that, so they just let everything end up on C:, which leads us right back to the original issue.
Cheers and Regards
- mockingbird
- Posts: 102
- Joined: Wed Oct 17, 2012 4:28 pm
I intentionally DID NOT DO "Repair Install" because it's now known that Repair Install only applies file updates but not registry updates...Dibya wrote:we can do repair by booting xp cd.
Thats i do every 3months.
If you want to repair a broken installation, go ahead and do "Repair Install", and then do an in-place upgrade. That way, you get the best of both worlds. The Repair Install will allow you to boot into a functioning XP X64 installation, and then the in-place upgrade will properly apply all the updates, especially those that you wouldn't get with Microsoft Update.
My goal was only to bring up to date my XP x64 install that was done with a circa 2012 update pack slipstreamed disk.
Here's how my scenario played out:
1) Did the in-place upgrade
2) Microsoft Update was broken. This was probably caused by an improper transition back to IE6. Before I did the in-place upgrade, I uninstalled IE8 in anticipation of replacing it with the updated IE6 add-on. (I don't need IE8 since I'll never use it for web browsing, and IE8 offers no security advantage to a fully-updated IE6 AFAIK). Ran the Microsoft Update Fixit several times, did not help
3) Re-installed the in-place upgrade, fixed Microsoft Update, it's working perfectly from IE6
4) Installed those updates from my post above
If they ever get that >4GB memory hack for 32-bit XP working properly, might switch over, seeing as how XP 32 is still getting security updates (Until April 2019 or so), while XP x64 is completely EOL in every respect.
I shall test my slipstreamed disk on vmware to see if everything is indeed up to date.
Re: 5eraph's post-SP2 Update Pack v2015-07_1
can you italianize these packs and addon?
5er_UpdatePack_XPx64SP2_2015-07_1.7z
5er_Win2003_Addon_2015-07_1_x64.7z
I would use them to Windows Server 2003 Standard and Enterprise in Italian
Thank you
5er_UpdatePack_XPx64SP2_2015-07_1.7z
5er_Win2003_Addon_2015-07_1_x64.7z
I would use them to Windows Server 2003 Standard and Enterprise in Italian
Thank you
Re: 5eraph's post-SP2 Update Pack v2015-07_1
Don't know how I would do that. I don't have Italian versions.
Re: 5eraph's post-SP2 Update Pack v2015-07_1
what about using language pack over English version?
Just my 2Cents
Re: 5eraph's post-SP2 Update Pack v2015-07_1
5eraph,
I just used your Update Pack and Add-on with nLite for my first-ever install of 64-bit XP. The installation went smoothly, including my usual softwares, as well as access to Microsoft Update. The Avast anti-virus online installer worked perfectly, and I will be experimenting with this “Opera 64-bit” browser:
https://www.opera64bit.com/
I didn’t know what I was missing all this time. Great work 5eraph! And thank you.
I just used your Update Pack and Add-on with nLite for my first-ever install of 64-bit XP. The installation went smoothly, including my usual softwares, as well as access to Microsoft Update. The Avast anti-virus online installer worked perfectly, and I will be experimenting with this “Opera 64-bit” browser:
https://www.opera64bit.com/
I didn’t know what I was missing all this time. Great work 5eraph! And thank you.
Re: 5eraph's post-SP2 Update Pack v2015-07_1
I'm not sure, so I put "Opera 64-bit" browser in quotes. A third party offshoot? I was hoping for feedback from experienced XP x64 users before I install it on my final build, because I had never heard of it before. I mentioned it over on msfn, too, but no one has picked up on it yet.
I thought it might be a neat find--but yeah, maybe too good to be true. If no one else posts about having used it, I will probably go back to my practice install and experiment with it myself before committing further.
I thought it might be a neat find--but yeah, maybe too good to be true. If no one else posts about having used it, I will probably go back to my practice install and experiment with it myself before committing further.
Re: 5eraph's post-SP2 Update Pack v2015-07_1
some thing for your pack 5eraph
download.windowsupdate.com/d/csa/csa/secu/2017/02/windowsserver2003-kb4012598-x64-custom-enu_f24d8723f246145524b9030e4752c96430981211.exe
download.windowsupdate.com/d/csa/csa/secu/2017/02/windowsserver2003-kb4012598-x64-custom-enu_f24d8723f246145524b9030e4752c96430981211.exe
Re: 5eraph's post-SP2 Update Pack v2015-07_1
It will be in the Delta addon when I make time this weekend, Dibya.
Re: 5eraph's post-SP2 Update Pack v2015-07_1
thanks a lot 5eraph
Re: 5eraph's post-SP2 Update Pack v2015-07_1
And some more this week:
See here
https://support.microsoft.com/en-us/hel ... -platforms
For x64 Windows XP SP2
KB958644 - 2008
KB2347290 - 2010
KB3011780 - 2013
KB4012598 - 2017
KB4012583 - 2017
KB4022747 - 2017
KB4018466 - 2017
KB3197835 - 2017
KB4024323 - 2017
KB4025218 - 2017
KB4024402 - 2017
KB4019204 - 2017
For x64 Internet Explorer 8
KB4018271 - 2017
Additional information available here:
https://www.askwoody.com/2017/xp-sp3ser ... june-2017/
See here
https://support.microsoft.com/en-us/hel ... -platforms
For x64 Windows XP SP2
KB958644 - 2008
KB2347290 - 2010
KB3011780 - 2013
KB4012598 - 2017
KB4012583 - 2017
KB4022747 - 2017
KB4018466 - 2017
KB3197835 - 2017
KB4024323 - 2017
KB4025218 - 2017
KB4024402 - 2017
KB4019204 - 2017
For x64 Internet Explorer 8
KB4018271 - 2017
Additional information available here:
https://www.askwoody.com/2017/xp-sp3ser ... june-2017/
Last edited by motokiume on Tue Jun 20, 2017 1:56 pm, edited 1 time in total.
Re: 5eraph's post-SP2 Update Pack v2015-07_1
I've also seen KB4025687.

- KB958644 - Originally added to update pack 2008-10_2.
- KB2347290 - Originally added to update pack 2010-09_1.
- KB3011780 - Originally added to update pack 2014-11_2.
- KB4012598 - Originally added to Delta addon 2017-05_1.

Re: 5eraph's post-SP2 Update Pack v2017-06_1
Updated to 2017-06_1. Please read the Changelog for full details.
_________________
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
_________________
The only relevant post-XP-EoS executable update package that needs the patched update.exe file to update an existing XPx64 installation:
- High priority update KB2926765, released 2014/05/13.