OK, found the problem ... was seated behind the keyboard. I was trying to install a driver which was for W7 or newer, which is why the installer was making a call for a newer SHELL32 (v6). The site showed it was good for WinXP ... but ...

Working further, I found a way to get it to work, thru their driver section ... just was not easy at all and NOT clearly marked!!

So there was no tie between this problem and kb4494528 ... thanks to all who were willing to participate in finding the cure!

OK, I have updated the GH0stPak post here, check it out. I can't see any need for changes, or updates. I am suspecting that MS will not offer any more updates for it. So unless there are more CUSTOM patches that should be added ... this may be the end!

Will there be a final XP SP, SP5 or whatever it may be called? At the moment it seems like GhostPak is the only up2date SP for XP. It would be nice to have a final SP for other languages like e.g. German, too (I'm German). Is there a script or something else to download the XP KBs, which seem to have been language-specific until Windows XP?

I'm running a few Windows XPs, they hardly get connected to the internet, but sometimes it's inevitable, and even though I followed the MS security advisory for XP (but not going the PosReady route), I'm a bit afraid, thinking of the latest RDP security hole. Obviously there are tons of security holes in Windows, no matter what version, and fwik it seems like these holes are closed only when even countries like Iran are able to use them. Then you'll see a MS update even for outdated Windows versions like XP. MS or the three-letter-agencies probably knew about these holes for years, but they keep silent, until third-world-countries are able to exploit these security holes, then they come with their "help". Isn't that nice?

Ok, but apart from politics, are there plans for some kind of (really) final XP Service Pack?

Will there be a final XP SP, SP5 or whatever it may be called? At the moment it seems like GhostPak is the only up2date SP for XP .... are there plans for some kind of (really) final XP Service Pack?

There may be one more GHostPak ... but I suspect nothing more ... unless MS decides it needs to put more updates out there! We have hoped that Harkaz, would consider putting all the updates together into another release of "uSP4", at which point there is no need for GH0stPak. We shall see! As far as someone making a German pack, I suspect NOT, unless your going to do it!

I chose to shutdown/reboot at end. re-ordered some to get them in order. put the FORCE tag on kb2564958, hoping it would force this to install, but I suspect it doesn't update (sometimes) due to its main component not being installed during OS install. But does become installed shortly there after.

kb2564958 is related to "Microsoft Active Accessibility", not sure why this (sometimes) can't be applied on a fresh install, but later after the install of dotnet's and hardware driver install, then it can be installed. It's probably related to the dotnet's

This final update pack should be applied to Windows XP installation media immediately after slipstreaming SP4 v3.1b to a Windows XP RTM/SP1/SP2/SP3 source. This will update installation media to May 2019, including every single update released until the POSReady 2009 end-of-life in May 2019.

To integrate this update pack:

1. Download PostSP4-May19-UpdatePack-harkaz-070619.zip from the "Post-SP4 Update Pack" Cloud folder, link: https://drive.google.com/open?id=1UvRI6 ... j7Zw4S29Tq
2. Extract zip contents
3. Double click slipstream.bat and follow on-screen instructions (you need to provide the path to the directory containing both CMPNENTS and I386 folders).
4. If you want .NET Framework 3.5 not to be installed by default, after completing steps 1-3: copy and overwrite the netfx35.in_ file in the I386 folder of Windows XP installation media from the PostSP4-May19-UpdatePack-harkaz-070619-NETFX35-OFF.zip file in the "Post-SP4 Update Pack" Cloud directory (download link: https://drive.google.com/open?id=1qqx7s ... Yw_YVD9v7c ), OR the istart\netfx35.in_ from the same zip archive only if you are slipstreaming to Windows XP Starter installation source.

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

You can get it to work by applying the update once nLite has already analysed the source folder.

Other than that the update seems to work without issue once this error is bypassed. Is there any particular reason that the final update was done in this manner rather than the more typical addon pack for integration via nLite or the RVM integrator?

I started with my XPpro sp0, then using nLite slipstreamed uSP4, immediately after that slipstream process was done, I reduced the nLite screen so I could then apply the Harkas's post sp4 update. Once it was done, I then continued with nLite as I normally would.

I have another problem, the legal VL serial number is not accepted
I will try tomorrow again.

XP SP4 must be slipstreamed in a Windows XP environment (known issue with official SP3).

I can reproduce the nLite issue but the exact cause is not clear to me. Sp4 update packs come with all important INFs digital signed so nLite is not an option for update pack creation because it tampers those files.

UPDATE: Regarding the nLite issue: it is somehow triggered by the timezone update registry entries in hivesft.inf. So it is an nLite bug, and there is no urgent need for me to address it, since nLite is incompatible with SP4 anyway.

harkaz thank you for the information that "XP SP4 must be slipstreamed in a Windows XP environment".

I installed WinXP on VMWare without any .Net.
As soon as I finished installing WinXP I installed .Net 3.5, PowerShell 2.0 and .Net 4.0 (from Control Panel)
and everything went good.
MU shows zero useful updates.
The .NET Framework 4 GDR update (KB2468871) does not appear in the optional updates.

UPDATE: XP SP4 MUI has been re-upload.
Search the term 'MUI' (without quotes) in the first post and follow the link for details and download.

Can't describe in words how much thanks/gratitude is owed to @harkaz for this amazing contribution!!! I haven't been here in a long while, and was super excited to see the recent update!

A few questions for @harkaz or anyone else who knows:

(a) I read the instructions for applying the updated MUI pack, but am still not sure if I need to (1) start with an English clean Windows SP3 ISO, slipstream or install the latest June 2019, then apply the MUI packs (in other words, everything stays in English until the end); or (2) start with my desired language's clean SP3 ISO from the very beginning and apply all the SP4 files including the MUI???

I suspect the correct method is (1), can anyone confirm?

(b) Going into the future, should the general order be: clean SP3 ISO -> apply all SP4 files up through June 2019 (slipstream or post-install) -> apply any GH0stPaks released on or after June 2019???

(c) The SP4 files are super valuable, have them been archived to a safe repository like the Internet Archive for safekeeping? Google Drive probably shouldn't be the only place to store them!

I have never used the MUI pack, so can't offer any advice there, but, it sounds like you got it!

Since MS just pulled the June update, being a TIMEZONE update, looks like they were not supposed to release it to XP. Makes me thing there will not being any more updates, at least not official. This means GH0stPak is done! Since Harkaz's most recent work is of a newer date. So was a fun project to have done for the past year. I will keep the GHostPak's archived on Google drive, but move them all to the older folder, keeping Harkaz's recent work, up front.

EDIT: To say I just updated my GH0stPak page and Google Drive, take a looks see!

I've been trying to get the latest post-SP4 update pack (released this month) from @Harkaz to work, but unsuccessfully.

I used nLite 1.4.9.3 (which is itself running in a Windows XP SP3 virtual machine) to slipstream version 3.1b of the SP4 pack into a folder containing clean Windows XP SP3 installation files (I tried both Win XP Professional SP3 and Win XP Professional N SP3, all in English). After the slipstreaming step, while nLite is still open and waiting, I used the `slipstream.bat` file in the post-SP4 update to put the recent updates into the installation files folder. Lastly, I let nLite create an ISO with those files.

This ISO fails to install on a VirtualBox virtual machine. Every time, the installation fails (the virtual machine would freeze) at this exact step:

BTW, I tried to slipstream version 3.1b into the same installation files, and installing that into a virtual machine was fine. So it's got something to do with the latest update.

Also, in the first post of this thread, @harkaz linked to a 4GB+ RAM patch file by someone called Dibya. I found @Dibya's thread on this forum, but I still can't figure out how to apply this 4GB patch and at what step in the installation I should apply it. Can someone give some instructions?

I have never used the MUI pack, so can't offer any advice there, but, it sounds like you got it!

Since MS just pulled the June update, being a TIMEZONE update, looks like they were not supposed to release it to XP. Makes me thing there will not being any more updates, at least not official. This means GH0stPak is done! Since Harkaz's most recent work is of a newer date. So was a fun project to have done for the past year. I will keep the GHostPak's archived on Google drive, but move them all to the older folder, keeping Harkaz's recent work, up front.

EDIT: To say I just updated my GH0stPak page and Google Drive, take a looks see!

Thank you very much GH0st. Even if the latest post SP4 update by @harkaz supersedes your pack, you still did a great job helping everyone stay updated!

I think your problem stems from the VM ... do you have the ability to do this all on an actual install of XP?

Unfortunately there is no bare metal machine I can install Windows XP on...

Can someone confirm if the slipstream steps I noted above (two posts above) are the correct and canonical way to get the latest June 2019 post-SP4 updates into an ISO? I'd appreciate any tips to get it to install in a VirtualBox virtual machine, thanks!!

I am glad to see that there are people who still care about Windows XP. Before I came across this pack I used "WSUS Offline Update" but they themselves ceased support for XP and don't provide updates after year 2014. I still have plenty of old hardware, not buff enough to run newer Windows systems, but too stubborn to finally rest in computer Valhalla.

If you happen to still have any plans for this I have a few suggestions:

1) As far as I understand the latest post-update pack is meant to be included as part of bootable installation CD only. Could you make an executable package out of it, just like the WindowsXP-USP4-v3.1b-x86-ENU.exe file? Or better upgrade WindowsXP-USP4-v3.1b-x86-ENU with these updates?

The reason I am asking is that I am not sure that making a bootable installation CD would work for some of my laptops. They have Windows XP preinstalled with laptop-specific drivers and other software. Reinstallation of OS is done via accessing a special recovery partition, not a CD.

Or should I just use GH0stPak for that matter?

2) My Windows version is non-English. Doing the registry trick and using MUI pack to change language back after installing SP4 worked fine. But I am wondering that given the source of this pack would that be possible to replace the English update files with other language files? Do you mind giving some hints or writing a tutorial on how to do that?

I would like to eliminate all these extra steps and just have one final update package that I just click and be done with it, just like with Service Pack 3.