Welcome to Windows XP Service Pack 4

[harkaz]

@Kurt_Aust What is the error you get with KTD, exactly?
The driver cabinet is still named sp3.cab, so I don't think this has to do with anything.

Happy and prosperous 2016 to everyone!
I may be able to start working on the v3 soon.

[Kurt_Aust]

The DriverPacks Finisher starts, runs for a few seconds, throws up an error box stating that it "could not delete DSPdsblr.exe" and then quits (also closing the error box), leaving several files in %SystemDrive%.

It doesn't run for anywhere near long enough to indicate an otherwise successful execution as running it without keeping the drivers takes much longer.

Here's a copy of the failing settings file.

Code: Select all

[General]
; preferred language
prefLang	= "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform	= "disc"
; trailing backslash is allowed, but not necessary
location	= "C:\Virtual_Machines\nLite\WinXP_x32_Prof_SP4 - Copy"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "all"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "custom"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "all"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "no"


; this section is optional!
[OptionalSettingsOther]
; CCC/CCP/None, use ATI Catalyst Control Center or ATI Catalyst Control Panel (only relevant when slipstreaming Graphics DriverPack)
; 1/2/3/None, use Nvidia Control Panel - 1 = Old, 2 = New, 3 = Both, None
ATI_cpl		= "CCC"
Nvidia_cpl	= "3"

[GH0st]

Happy and Prosperous 2016 to Everyone!

Same to you Harkaz! Happy New Year to all the uSP4 lovers!!

[Dibya]

@harkaz , same to you .happy new year.

[Kurt_Aust]

Two other minor quirks while I'm at it, as I noted earlier in this thread

KB2918614 has been replaced by KB3072630, perhaps the first post should be updated to reflect this.

and there's a glitch in the taskbar caused by IE8, you'll notice that the show desktop icon is missing. This is easily fixed by making sure the directories exist before account initialisation, I use the following commands in nLite's RunOnce to achieve this:

Code: Select all

rem fix Quick Launch toolbar (broken by IE8)
MkDir "%UserProfile%\Application Data\Microsoft\Internet Explorer\Quick Launch"
MkDir "%AllUsersProfile%\..\Default User\Application Data\Microsoft\Internet Explorer\Quick Launch"

[ChiefZeke]

SP4 and Driver Packs - see here for info: http://forum.driverpacks.net/viewtopic. ... 824#p58824

[Kurt_Aust]

You probably know about it already, but it might be viable to include a final version of .NET 4.0 in any v3 of SP4 as support ends on 12th January 2016
http://www.infoq.com/news/2014/08/NET40-EOL

[Mirza]

I have XP SP3 and wanted to update but it failed . After the setup inspect it suddenly stop .I would include screenshot later .

[harkaz]

This KTD bug is weird. I will have to run it in VM.

@Mirza In 99% of cases it is "Failed to install catalog files".

If this is the case:

Type net stop cryptsvc at cmd prompt
Delete the \WINDOWS\SYSTEM32\catroot2 folder
Type net start cryptsvc at cmd prompt.
Restart SP4 installer.

[harkaz]

The v3 will be the final version of SP4, so it will include all updates until its release and I'll take the time needed to include all .NET FW updates as well.
It's difficult to fix everything you report to me, but I'll try to address most of these issues.

[GH0st]

Sounds awesome Harkaz!!

[Mirza]

Also the cloud include iso file.How to use them?They only extract i386 folder with alot of stuff.

[Mirza]

@harkaz The error is 'An internal error occured' and when I click ok 'SP4 installation not complete'. The solution does not working.

[harkaz]

Please send me the svcpack.log located in %systemroot%
The ISO file is used alternatively of the self-extracting installer by copying the ISO contents to a local folder of your hard drive and launching the i386\update\update.exe program.

[Kurt_Aust]

Wrote a guide on how to use SP4v2 with the DriverPacks

http://www.msfn.org/board/topic/174973- ... some-apps/

[GH0st]

http://www.majorgeeks.com/news/story/r_ ... neral.html

Guess along with .Net packs ending support, comes this as well!! Would be good to have their final release of IE in final uSP4 pack

[Kurt_Aust]

What Microsoft is actually doing is changing to only supporting the most recent version of IE to work on a supported OS, so IE8 on XP PoS is safe for now.

https://support.microsoft.com/en-us/lif ... t-Explorer

[Mirza]

Forget it . I've installed SP4 successly ! Do I need post sp4 update ? I dont install Sp4 v1 , just v2.

[GH0st]

Just use the v2, slip stream into your media, do install, get updates from Microsoft

[Mirza]

How and what is slipstreaming?

[GH0st]

ahh, this is the best way to deploy either SP3 or uSP4.

You can use the tools named "nLite" or "RyanVM Integrator". These tools will allow you to SLIPSTREAM either service pack, into your original XP, than make a new ISO (Image file) and burn this to a blank disc, in the end making a new Windows XP install disc, which has the latest service pack integrated/Slipstreamed!

nLite Forums

[MrMaguire]

The v3 will be the final version of SP4, so it will include all updates until its release and I'll take the time needed to include all .NET FW updates as well.
It's difficult to fix everything you report to me, but I'll try to address most of these issues.

Would you consider releasing a vanilla version of Unofficial SP4? i.e. not including updated components, such as Internet Explorer and Windows Media Player.

[Mirza]

Oh i got it...thanks ! Looking forward for any update.

[harkaz]

@MrMaguire I won't create any customized SP4 versions. What I'm thinking about is creating a video on how to create a generic WIM file for Windows XP, like the one included with POSReady 2009 setup ISO. You could then easily create a WIM starting from SP3 and performing any customizations you'd like, then reseal and deploy with a POSReady-like setup procedure or with just imagex.

[GH0st]

@MrMaguire I won't create any customized SP4 versions. What I'm thinking about is creating a video on how to create a generic WIM file for Windows XP, like the one included with POSReady 2009 setup ISO. You could then easily create a WIM starting from SP3 and performing any customizations you'd like, then reseal and deploy with a POSReady-like setup procedure or with just imagex.

This sounds like a very cool thing ...

[harkaz]

Well, it seems that the 16-bit error is finally fixed. So I'll just need to integrate the updated files, remove some Firewall-related stuff (as suggested by GH0ST) and finalize V3.

I will also try to prepare a generic WIM file with .NET FW 1.1, 3.5, 4.0 preinstalled.
Language-specific WIMs (SP4+MUIs) may be available as well.

[harkaz]

I had noticed a bug with Start Menu icons after applying a POSReady update. Has the issue been fixed yet? If not, I will reconsider the inclusion of POSReady updates in the SP4 and make them available in the WIM only.

[GH0st]

Well, it seems that the 16-bit error is finally fixed. So I'll just need to integrate the updated files, remove some Firewall-related stuff (as suggested by GH0ST) and finalize V3.

Sound great!

Have you considered adding more of the changes I have on my Enhanced Security Options? Have you considered renaming the "Administrator" account to "Admin"?

[GH0st]

Harkaz: Regarding FireWall ...

When using "Auslogics Registry Cleaner", it finds problems in the "Firewall Policy" shared access ... blah blah blah. This may not be an important issue, but it may be something you can address while making changes in FW policies.

Code: Select all

Key=HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List
Value=%SystemRoot%\System32\TFTPD.EXE
ValueType=1
ValueData=2500530079007300740065006D0052006F006F00740025005C00530079007300740065006D00330032005C00540046005400500044002E004500580045003A004C006F00630061006C005300750062004E00650074003A0045006E00610062006C00650064003A00570069006E0064006F0077007300AE0020005400720069007600690061006C002000460069006C00650020005400720061006E007300660065007200200053006500720076006900630065000000

Key=HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Services\SharedAccess\Parameters\FirewallPolicy\DomainProfile\AuthorizedApplications\List
Value=%SystemRoot%\System32\TFTPD.EXE
ValueType=1
ValueData=2500530079007300740065006D0052006F006F00740025005C00530079007300740065006D00330032005C00540046005400500044002E004500580045003A004C006F00630061006C005300750062004E00650074003A0045006E00610062006C00650064003A00570069006E0064006F0077007300AE0020005400720069007600690061006C002000460069006C00650020005400720061006E007300660065007200200053006500720076006900630065000000

Auslogics Registry Cleaner When installing don't allow it to do regular install, must chose custom, so as to NOT download and NOT install the "BoostSpeed".

I decided to try this after falling in love with their Auslogics Disk Defrag!

[harkaz]

I will remove these 2 keys, but I won't add any further customizations. I want to keep the SP4 as generic as possible.

It seems they couldn't care less about fixing shlwapi.dll. Server 2003 support has ended, so there won't be any fixes about it in the future.
If was a software engineer I would have fixed the shlwapi.dll myself, the bug is ludicrous.

Creating a WIM is difficult because it requires customizing the POSReady binaries to suit your needs. Fortunately, these are .NET 1.1 binaries and can be easily decompiled.

[GH0st]

10-4, Thanks again!!

-I have never had a problem with the Shell Lightweight api. Is this a problem showing with the next version? Or is there issues I'm not yet aware of? My current version installed is 6.0.2900.6540

-regarding the whole WMI thing, I personally don't have a problem with just cotinuing to run the final uSP4 ... then just get the current POS's from MS.

[maxtorix]

@harkaz can you re-consider adding Microsoft Private Folder feature in the final version of Unofficial SP4?
http://www.softpedia.com/get/Security/L ... lder.shtml

[Dibya]

@Kurt_Aust What is the error you get with KTD, exactly?
The driver cabinet is still named sp3.cab, so I don't think this has to do with anything.

Happy and prosperous 2016 to everyone!
I may be able to start working on the v3 soon.

Hi, I donot know Driverpack forum user are taking about.
Thanks again.
I have intrigated usp4 and mastorage pack without a single problem.
Happy New year

[harkaz]

4 GB Geoff Chappel's patch IDA code:

Code: Select all

4GB RAM patch

1. KERNEL

a- Patch 1

PAGELK:0056A724 loc_56A724:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+C1j
PAGELK:0056A724                 cmp     edi, ebx
PAGELK:0056A726                 jnb     short loc_56A701
PAGELK:0056A728                 push    7               ; SuiteType
PAGELK:0056A72A                 call    _ExVerifySuite@4 ; ExVerifySuite(x)
PAGELK:0056A72F                 cmp     al, 1
PAGELK:0056A731                 jnz     short loc_56A73A
PAGELK:0056A733                 mov     eax, 1000000h
PAGELK:0056A738                 jmp     short loc_56A75B

Change 0056A731 75 07 to 90 90 (nop)

b- Patch 2
PAGELK:0056B68B
PAGELK:0056B68B                         loc_56B68B:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+ABj
PAGELK:0056B68B A1 C0 1B 48 00                          mov     eax, _MmHighestPossiblePhysicalPage
PAGELK:0056B690 8D 4B FF                                lea     ecx, [ebx-1]
PAGELK:0056B693 3B C8                                   cmp     ecx, eax
PAGELK:0056B695 76 0D                                   jbe     short loc_56B6A4
PAGELK:0056B697 8D 58 01                                lea     ebx, [eax+1]
PAGELK:0056B69A 8B F3                                   mov     esi, ebx
PAGELK:0056B69C 2B F7                                   sub     esi, edi
PAGELK:0056B69E 89 5D EC                                mov     [ebp+var_14], ebx
PAGELK:0056B6A1 89 75 F4                                mov     [ebp+var_C], esi
PAGELK:0056B6A4
PAGELK:0056B6A4                         loc_56B6A4:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+C1j
PAGELK:0056B6A4 3B FB                                   cmp     edi, ebx
PAGELK:0056B6A6 73 D9                                   jnb     short loc_56B681
PAGELK:0056B6A8 6A 07                                   push    7               ; SuiteType
PAGELK:0056B6AA E8 A3 24 EF FF                          call    _ExVerifySuite@4 ; ExVerifySuite(x)
PAGELK:0056B6AF 3C 01                                   cmp     al, 1
PAGELK:0056B6B1 75 07                                   jnz     short loc_56B6BA
PAGELK:0056B6B3 B8 00 00 00 01                          mov     eax, 1000000h
PAGELK:0056B6B8 EB 21                                   jmp     short loc_56B6DB
PAGELK:0056B6BA                         ; ---------------------------------------------------------------------------
PAGELK:0056B6BA
PAGELK:0056B6BA                         loc_56B6BA:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+DDj
PAGELK:0056B6BA 81 3D 98 D0 47 00 57 00+                cmp     _MmProductType, 690057h
PAGELK:0056B6C4 74 10                                   jz      short loc_56B6D6
PAGELK:0056B6C6 6A 01                                   push    1               ; SuiteType
PAGELK:0056B6C8 E8 85 24 EF FF                          call    _ExVerifySuite@4 ; ExVerifySuite(x)
PAGELK:0056B6CD 3C 01                                   cmp     al, 1
PAGELK:0056B6CF B8 00 00 80 00                          mov     eax, 800000h
PAGELK:0056B6D4 74 05                                   jz      short loc_56B6DB


Change 0056B6B1 75 07    to 90 90 (nop)



2 - HAL patch

PAGE:8001C5DD                         loc_8001C5DD:                           ; CODE XREF: HalGetAdapter(x,x)+A1j
PAGE:8001C5DD                                                                 ; HalGetAdapter(x,x)+A7j ...
PAGE:8001C5DD 8A 4F 08                                mov     cl, [edi+8]
PAGE:8001C5E0 88 4D EC                                mov     byte ptr [ebp+var_14], cl
PAGE:8001C5E3 8A 4F 05                                mov     cl, [edi+5]
PAGE:8001C5E6 84 C9                                   test    cl, cl
PAGE:8001C5E8 53                                      push    ebx
PAGE:8001C5E9 74 17                                   jz      short loc_8001C602
PAGE:8001C5EB 80 3D B8 97 01 80 00                    cmp     _LessThan16Mb, 0
PAGE:8001C5F2 75 0A                                   jnz     short loc_8001C5FE
PAGE:8001C5F4 83 FA 02                                cmp     edx, 2
PAGE:8001C5F7 74 05                                   jz      short loc_8001C5FE
PAGE:8001C5F9 83 FA 05                                cmp     edx, 5
PAGE:8001C5FC 75 04                                   jnz     short loc_8001C602
PAGE:8001C5FE
PAGE:8001C5FE                         loc_8001C5FE:                           ; CODE XREF: HalGetAdapter(x,x)+C8j
PAGE:8001C5FE                                                                 ; HalGetAdapter(x,x)+CDj
PAGE:8001C5FE 33 DB                                   xor     ebx, ebx
PAGE:8001C600 EB 40                                   jmp     short loc_8001C642

Patch: 8001C5E9 74 17 to 8001C5E9 EB 17

The new v3 will fully tested and fixed for the 4GB patch.
All hal/kernel files that can be patched will be patched.

[harkaz]

The shlwapi.dll bug is that it does not allow changing the Internel and E-mail clieant shown in the start menu from Start menu properties.

As for DP, may I recommend customizing the ISO even further:

Use Type 1 integration for the basic drivers (SCSI, Network, Chipset). Type 1 has a size limit but it works in all scenarios, including repair installs.

Run a dp scanner at T13 or later to find all hardware from infs located on the DVD-ROM drive (uncompressed files).

KTD may have a perfomance impact anyway, so I recommend against using it.

No further customizations/features will be added in v3

Only bug fixes will be included.

[GH0st]

Thank you Harkaz!

I am prepared to BETA test, do a live install, asap. Takes me 10 or so minutes to back stuff, then I can start slipstream process, then load it to a USB stick (rufus).

I still have my last ISO (current install) on USB, so can format and install back, if something goes wrong.

[Dibya]

4 GB Geoff Chappel's patch IDA code:

Code: Select all

4GB RAM patch

1. KERNEL

a- Patch 1

PAGELK:0056A724 loc_56A724:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+C1j
PAGELK:0056A724                 cmp     edi, ebx
PAGELK:0056A726                 jnb     short loc_56A701
PAGELK:0056A728                 push    7               ; SuiteType
PAGELK:0056A72A                 call    _ExVerifySuite@4 ; ExVerifySuite(x)
PAGELK:0056A72F                 cmp     al, 1
PAGELK:0056A731                 jnz     short loc_56A73A
PAGELK:0056A733                 mov     eax, 1000000h
PAGELK:0056A738                 jmp     short loc_56A75B

Change 0056A731 75 07 to 90 90 (nop)

b- Patch 2
PAGELK:0056B68B
PAGELK:0056B68B                         loc_56B68B:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+ABj
PAGELK:0056B68B A1 C0 1B 48 00                          mov     eax, _MmHighestPossiblePhysicalPage
PAGELK:0056B690 8D 4B FF                                lea     ecx, [ebx-1]
PAGELK:0056B693 3B C8                                   cmp     ecx, eax
PAGELK:0056B695 76 0D                                   jbe     short loc_56B6A4
PAGELK:0056B697 8D 58 01                                lea     ebx, [eax+1]
PAGELK:0056B69A 8B F3                                   mov     esi, ebx
PAGELK:0056B69C 2B F7                                   sub     esi, edi
PAGELK:0056B69E 89 5D EC                                mov     [ebp+var_14], ebx
PAGELK:0056B6A1 89 75 F4                                mov     [ebp+var_C], esi
PAGELK:0056B6A4
PAGELK:0056B6A4                         loc_56B6A4:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+C1j
PAGELK:0056B6A4 3B FB                                   cmp     edi, ebx
PAGELK:0056B6A6 73 D9                                   jnb     short loc_56B681
PAGELK:0056B6A8 6A 07                                   push    7               ; SuiteType
PAGELK:0056B6AA E8 A3 24 EF FF                          call    _ExVerifySuite@4 ; ExVerifySuite(x)
PAGELK:0056B6AF 3C 01                                   cmp     al, 1
PAGELK:0056B6B1 75 07                                   jnz     short loc_56B6BA
PAGELK:0056B6B3 B8 00 00 00 01                          mov     eax, 1000000h
PAGELK:0056B6B8 EB 21                                   jmp     short loc_56B6DB
PAGELK:0056B6BA                         ; ---------------------------------------------------------------------------
PAGELK:0056B6BA
PAGELK:0056B6BA                         loc_56B6BA:                             ; CODE XREF: MmAddPhysicalMemoryEx(x,x,x)+DDj
PAGELK:0056B6BA 81 3D 98 D0 47 00 57 00+                cmp     _MmProductType, 690057h
PAGELK:0056B6C4 74 10                                   jz      short loc_56B6D6
PAGELK:0056B6C6 6A 01                                   push    1               ; SuiteType
PAGELK:0056B6C8 E8 85 24 EF FF                          call    _ExVerifySuite@4 ; ExVerifySuite(x)
PAGELK:0056B6CD 3C 01                                   cmp     al, 1
PAGELK:0056B6CF B8 00 00 80 00                          mov     eax, 800000h
PAGELK:0056B6D4 74 05                                   jz      short loc_56B6DB


Change 0056B6B1 75 07    to 90 90 (nop)



2 - HAL patch

PAGE:8001C

Hi ,harkaz please how to use IDA.
Does it is better than hexediting.Please tell me
please please Can I use it for RAM Limit removal addon

[=[FEAR]=JIGSAW]

@ GH0st

Your link to "CryptoPreventSetup" is not working anymore in your post for Security Enhancements > http://www.ryanvm.net/forum/viewtopic.p ... 610#138610

[GH0st]

@ GH0st: Your link to "CryptoPreventSetup" is not working anymore

Fixxed, thank you!

[harkaz]

@Dibya The IDA Pro will not patch the file, it will give you the offset where the file should be patched.

I have been able to test the 4GB patch on SP4 v3 for the first time and it's working!
It may feel a bit slower though.

Remember you will lose the patch if a future hal/kernel update is installed.

SP4 v3 is being tested and will be released soon.

[GH0st]

SP4 v3 is being tested and will be released soon.

Awesome, I am ready as soon as you are! Yeah, I even went to store and got two 2-liters of Pepsi ... so I'm up all night long now!

[GH0st]

PSSSSssss <--- Pepsi bottle opening

[harkaz]

Legacy (v2) version information:

All these files are available under the Legacy folder.

1. Verification info and description

1. WindowsXP-USP4-v2-x86-ENU.exe (recommended)
Description: Windows XP SP4 Installer with POSReady Update support
Version: 2.0
MD5: CF07D21FFFF544283AEB455CBEBAFF8C
SHA1: 95AE364CE2CB39D9ED022E84F8829C883F43AB5F
Date/Time Stamp: 15 November 2014 00:00:00 UTC
Size: 992 MB (1040456589 bytes)

2. WindowsXP-USP4-NOPOS-x86-ENU.exe
Description: Windows XP SP4 Installer (no POSReady Update support)
Version: 2.0
MD5: 965E47FCBCDF5800E7783AE02B0DC8C2
SHA1: 088BBC0E8279607062202DC00C2E1D51896BDF1F
Date/Time Stamp: 15 November 2014 00:00:00 UTC
Size: 992 MB (1040461739 bytes)

Tools to create 6 Bootable Floppy Disks for older systems:

3. WindowsXP-USP4-Floppy-ic.exe
Description: Windows XP Home Edition SP4 Floppy Disk Utility
MD5: A55815299706C1F4A84FBD6DAA0CF3F0
SHA1: B6AF4F46ECAF3DE958887F361DDC15B1A659A327
Date/Time Stamp: 15 November 2014 00:00:00 UTC
Size: 4.46 MB (4677668 bytes)

4. WindowsXP-USP4-Floppy-ip.exe
Description: Windows XP Professional SP4 Floppy Disk Utility
MD5: A8BD830A91C1C3C39DF124D75C59FB07
SHA1: 0F0D23DB590C09171340D6EAC0CB772FF8EFB765
Date/Time Stamp: 15 November 2014 00:00:00 UTC
Size: 4.46 MB (4678008 bytes)

These two ISOs can be used to install WindowsXP-USP4-V2-x86-ENU.exe on older systems without DVD/USB support. These ISOs can be found in the ISO for SP4 installer Cloud folder:

5. SP4CD1-v2.iso
Description: Windows XP SP4 Installer CD-ROM #1
Version: 2.0
MD5: 19A42A10229113215448F72BEC2C9B04
SHA1: 8BE6BC4E1D15E4092F72C64599F8232D194AD1AD
Date/Time Stamp: 15 November 2014 00:00:00 UTC
Size: 640 MB (671336448 bytes)

6. SP4CD2-v2.iso
Description: Windows XP SP4 Installer CD-ROM #2
Version: 2.0
MD5: 8A3DA247B696C02F54B59DE794A232AF
SHA1: 7D16C64D5DAC4D4D4CB095F5D3D7D681790EC2F8
Date/Time Stamp: 15 November 2014 00:00:00 UTC
Size: 359 MB (376602624 bytes)
[/list]
This is SP4 Final OS Version: 5.1.2600.6532

2. Patches Cloud folder includes a number of patched files. These files, when used with SP4 media, should be digitally signed. Some of these can be used to enable installation on systems with 4 GB of RAM (or greater) while others will help you changing the default set of components to be installed during CD-ROM installations.

3. nLite and Windows XP Professional SP4: nLite will detect all Windows XP SP4 Professional media as "Media Center" ones. Ignore any Media Center-related messages, this behaviour is a result of the way nLite checks whether Media Center is present. Media Center will be available only if SP4 is slipsteamed in a media Center installation source.

4. A note about POST-SP4 Hotfixes. The post-sp4 update KB2918614 updates MSI 4.5. It is imperative that you install this update seperately. After installing it RUN THIS COMMAND: msiexec.exe /regserver
Also, if you're using .NET Framework 4.0 make sure you run:
%systemroot%\Microsoft.NET\Framework\v4.0.30319\ngen.exe executequeueditems
every time you install a new update or application for .NET Framework. This will boost system's performance and ensure reliability.

5. There is an issue with post-sp4 .NET updates I would like to report, which is not caused by the SP4 itself.

Scenario: Install SP4 -> Enable .NET Framework 4.0-> Run Windows Update Manual Check. -> Install Updates -> reboot (twice) -> Installed all updates successfully -> Run Windows Update Manual Check.

You will get the .NET Framework 4 GDR update (KB2468871) in the optional updates.
Reason: This happens because one of the newest updates deletes the:
HKLM, "SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Client Profile\KB2468871" and
HKLM, "SOFTWARE\Microsoft\Updates\Microsoft .NET Framework 4 Extended Profile\KB2468871"registry keys.

SOLUTION: You can either let Windows Update download and install the update automatically (it must not be removed afterwards) or apply a reg file to satisfy Windows Update: http://www.mediafire.com/view/p8jibcgq6 ... 468871.reg

6. You can install SP4 v2 on top of SP4 version 1.0. Before installing, howewer, delete the HKLM,"System\CurrentControlSet\Control\Session Manager\Environment","TZ",0,"MEZ-1MESZ-2" key.

7. Post-SP4 Update Pack: An update pack, which can be slipstreamed into any SP4-integrated installation disk, is now available. You can find it in the Post-SP4 Update Pack Cloud folder.
This update pack must be used with Windows XP SP4 Version 2- integrated media to Clean install Windows XP SP4 + all post-SP4 updates until the date specified below.

Latest Version: 24 November 2014

READ BEFORE DOWNLOADING: UNLIKE ALL OTHER UPDATE PACKS its integration is done in these 3 steps. It must be done BEFORE USING nlite or RyanVM integrator, on a clean SP4 v2 source:

1. Copy the I386 folder from the ZIP FILE to the installation directory.
2. Copy the CMPNENTS folder from the ZIP FILE to the installation directory.
3A. If you're using HOME Edition copy the HIVESFT\HOME\I386\hivesft.inf file from the ZIP FILE to the I386 subfolder of the installation folder. OR:
3B. If you're using PROFESSIONAL Edition copy the HIVESFT\PRO\I386\hivesft.inf file from the ZIP FILE to the I386 subfolder of the installation folder.
4. Copy the updated sysoc.in_ from the SYSOC directoroy to the I386 directory in the installation folder depending on your CD-ROM edition:
- If you're using Home Edition copy SYSOC\HOME\sysoc.in_
- If you're using Home Edition K copy SYSOC\HOMEK\sysoc.in_
- If you're using Home Edition KN copy SYSOC\HOMEKN\sysoc.in_
- If you're using Home Edition N copy SYSOC\HOMEN\sysoc.in_
- If you're using Profssional Edition (not Media Center Edition) copy SYSOC\PRO\sysoc.in_
- If you're using Professional Edition K copy SYSOC\PROK\sysoc.in_
- If you're using Professional Edition KN copy SYSOC\PROKN\sysoc.in_
- If you're using Professional Edition N copy SYSOC\PRON\sysoc.in_
- If you're using Profssional Edition (Media Center Edition) copy SYSOC\PROMCE\sysoc.in_
5. The PATCHES folder contains the updated versions of modified netfx11.inf, netfx35.inf, netfx40.inf and allows to OPTIONALLY change the default configuration of components.

After integrating the post-sp4 update pack you can perform any tweaks you desire.

WARNING: The post-sp4 update pack, unlike Windows XP Service Pack 4 v2, has undergone limited testing! It's designed primarily for Clean, CD-ROM/DVD-ROM-based installations

This update pack is based on Onepiece's .NET Framework addons and 5eraph's POSReady addon.

Verification Information for the UPDATE PACK:
SP4addon-241114.zip (49806998 bytes, reuploaded) MD5: 6C722FC5F90583D4B5BF8393D13E73FB

8. POSReady 2009 updates easily ported to Windows XP post-EOL
I have easily "ported" all updates to Windows XP. I upload the sfx installers for testing on a monthly basis. You can find these in the Post-SP4 Update repository Cloud folder.

NOTE: The .NET Framework 3.0 updates are not offered via Windows Update even if you apply the POSReady update hack. They can be found in the update repository as well as the latest post-sp4 update pack.

[harkaz]

What's new in version 3.0:

1. POSReady updates until January 2016 have been included
2. 16-bit app emulation issue when installing from slipstreamed CD-ROM has been fixed
3. Fixed the 4GB+ PAE patch
4. Some other minor fixes
5. Fixed the "FP" (false positive) "malware" files in SP4 v2.

[harkaz]

And that's it, the final SP4 version has been released.

I thank you all for your support all these years. I hope you enjoy Windows XP in the years to come.

[Dibya]

hi harkaz, can i please use your ram patch files from PATCHES-V3.ZIP for my pae addon please.
Thanks a lot for your usp4 new version
my addon link::http://www.ryanvm.net/forum/viewtopic.php?t=10547

[harkaz]

Yes, of course, you may use the files for your addon.

[GH0st]

Thank you Harkaz, for all your wonderful work, will start working with v3 now!

Edit to add: I'm slow today, but I am burning the ISO to USB Thumb Drive now, via Rufus v2.6

I did choose to do the MINIMAL when using nLite v1.4.93, just used Task Selection: Service Pack, Drivers, Bootable ISO.

My past experience has been to allow uSP4 to just do what it wants, with the least amount of tweaks or remove component options. So, all I did was Slipstream uSP4v3 into my XP Pro sp0, add my Intel Inf Drivers, make an ISO. Burn ISO to USB Thumb Drive.

Be back later ....

Edit to add: Took 55 minutes to burn to Thumb drive, not SP4's fault, slow druve

[tipoole]

We all thank you Harkaz for what u have done for xp.Couple of questions:
most probably post SP4 update pack doesnt apply to v3 anymore right?
v3 integration can also be done via nlite or only cmd integration?

[GH0st]

ok, setup as stated above ...

Install took 33 minutes, went with out flaw and upon first boot the Event Viewer had only a few warnings (yellow marks) which were related to .NET stuff. This was similar to uSP4v2, but less then v2!

I used nLite to just slipstream, add drivers and make ISO. No other option used, no tweak deployed!

Going to MS Update, it did offer two updates, one was Malicious File Removal Tool Jan2016. Other was KB2926765. I looked this up, seems to be related to SHLwapi.dll (26Mar14). This was recently mentioned by Harkaz as a problem, guessing he did not include this in current version, due to issues surrounding it! (Harkaz: Should we avoid this?)

I did have to install .NET 4.0, 2.0 and 3.5 were already present. It optimizes itself when reboot, so all is well!

note: .Net 2.0, does NOT show up in "Add or Remove Programs" nor "Add/Remove Windows Components" sections. Not sure if this is by design or if this is a desired trait. Not sure if people would want to remove 2.0 for some reason.

It does feel super fast, the underbelly is quick. Though I do have a Intel C2Q@2500mhz, 4gb ram, G33/ICH9DO chipset and a Velociraptor (10,000rpm) HD.

Continuing to work with it!