Introducing - Unofficial Windows XP SP4

[harkaz]

Probably a registry key thing. I had managed to satisfy official WU, except in some scenarios when some later .NET updates deleted keys and made WU request updates again. Refer to Windows Update logs.

SP4 was originally released in 2014, more than 10 years ago, and is no longer supported.

Edited February 8 by harkaz

[user57]

On 10/17/2021 at 11:51 PM, harkaz said:

That's normal apart from the freeze. .NET 2.0-3.5 appear due to necessary Windows Installer baseline configuration.

Try optimizing the .NET Framework 4.0 (refer to XP SP4 first post at RyanVM.net, see my signature). Otherwise, start from scratch in that order:

SP2 -> SP4 directly, no .NET -> Install post-SP4 -> install .NET 3.5 and .NET 1.1 -> reboot -> Install .NET 4.0 -> reboot  -> Install all .NET apps -> Optimize  .NET Framework 4.0

i readed me a bit into this by far not done yet

first it´s impressiv much and a very big collection, good job 

the problem that you need sp1 to sp2 to sp3 or such things is solveable

what these installer scripts use is that /.msu/.msi./.inf files for a installer script (some convert all files together like reg to inf ect.)
the problem with that installer script however is that is is kinda slow, and it cant install in 1 step

there is a thing before that installer script
its the "install maker" ? such as InstallShield or Visual Studio Installer (those are very common to create a installer script)
those are rather "build-together-ish" and make those scripts

there 3 ways to collect that informations
1: from the raw/source file (for example InstallShield, Visual Studio Installer)
2: extracting the information from the .msi/msu or .inf files 
3: debugging the installer and the next (non script) functions after the script installer (such as createfile, regopenkey ect.)

one way for the files to do it in 1 step would be to use the MoveFileEx function with PendingFileRenameOperations
the registry can be changed with the common registry functions

then everything dont depent to go through the installer script 
i remember i once did that with a installer script in like 1998 and it speeded up the installer from like 10 min to 10 seconds

a own installer then just dont need .net 1.0 .net 4.0, it simple can install what it wants

those installer scripts have a next deeper set of functions those are the registry and file functions - kinda reminds me the discussions about engines and engines for a engine