Welcome to Windows XP Service Pack 4

[harkaz]

setupapi.dll performs the layout.inf check.

I found this in a Microsoft's document :

5.7 Verifying Files and Pruning the File Queue
During the verifying-and-pruning stage of driver installation, SetupAPI logs messages that pertain to verifying and pruning (in other words, deleting) file-copy operations from the file queue. SetupAPI performs these tasks before it commits the file queue.
SetupAPI logs messages for this stage only if an error occurs or if one of the verbose logging levels is set.
If SetupAPI verifies a file, it deletes the file’s corresponding copy operation from the file queue; when SetupAPI subsequently commits the file queue, it does not copy the file to the system.
SetupAPI verifies a file if and only if the following conditions are true:
• The driver package has a Windows Hardware Quality Labs (WHQL) catalog, a Microsoft Authenticode® catalog, or a test catalog.
• All the INF files that are associated with the file’s driver package are installed in the default system INF file directory, and the catalog files that are associated with these INF files are installed in the crypto catalog store.
• The signatures of all the INF files that are associated with the file’s driver package are validated by their respective catalog files.
• The signature of the file is validated by the catalog file that is associated with a particular INF file—the one that specifies the source media layout for the file. (This INF file is the one containing the SourceDisksFiles and SourceDisksNames sections that identify the source media and the source file for the file to be verified.)
• The file exists in a particular destination directory—the one specified by the DestinationDirs section in the INF file that specifies the source media layout for the file.

If SetupAPI does not verify a file, it leaves the file’s copy operation in the file queue. When SetupAPI subsequently commits the file queue, it copies the file to the system—unless the existing file on the system is in use and a reboot is not required. In this case, SetupAPI compares the file in the driver package with the existing file. If they are identical, SetupAPI does not copy the file, and it logs the following type of message:
#I193 File "…\SET87.tmp" is identical to existing "…\Some_File_Name_And_Extension", delayed copy skipped.
5.7.1 Verifying Files and Pruning the File Queue: Verbose Logging
The following example illustrates what the verifying-and-pruning subsection in a SetupAPI log file looks like for a Blender device—if the most verbose logging level is set.
@ 10:18:25.843 #V286 Verification using alternate platform (Platform = 2, High Version = 5.1, Low Version = 5.0).
@ 10:18:25.890 #V132 File "e:\windows\inf\Blender_INF_File_Name.inf" (key "Blender_INF_File_Name.inf") is signed in catalog "Blender_Catalog_File_Path\Blender_Catalog_File_Name.cat".
@ 10:18:25.890 #V286 Verification using alternate platform (Platform = 2, High Version = 5.1, Low Version = 5.0).
@ 10:18:25.906 #V132 File "e:\windows\inf\layout.inf" (key "layout.inf") is signed in catalog "E:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\NT5INF.CAT".
@ 10:18:25.906 #T185 Pruning Files: Verifying catalogs/INFs.
@ 10:18:25.906 #T186 Pruning Files: Verifying catalogs/INFs completed.
@ 10:18:25.906 #V286 Verification using alternate platform (Platform = 2, High Version = 5.1, Low Version = 5.0).
@ 10:18:25.921 #V132 File "E:\WINDOWS\System32\DRIVERS\blender.sys" (key "blender.sys") is signed in catalog "Blender_Catalog_File_Path\Blender_Catalog_File_Name.cat".
@ 10:18:25.921 #V191 File "E:\WINDOWS\System32\DRIVERS\blender.sys" pruned from copy.

Let's see which commands are involved in these checks. WinVerifytrust call seems to be the way to verify a file with a catalog.

UPDATE: The setupapi.log shows this error message:

[2013/09/26 10:45:55 2176.664 Driver Install]
#-019 Searching for hardware ID(s): acpi\genuineintel_-_x86_family_6_model_23,*genuineintel_-_x86_family_6_model_23,acpi\genuineintel_-_x86_family_6,*genuineintel_-_x86_family_6,acpi\genuineintel_-_x86,*genuineintel_-_x86
#-018 Searching for compatible ID(s): acpi\processor
#-198 Command line processed: "C:\SP3\i386\update\update.exe"
#I022 Found "ACPI\GenuineIntel_-_x86" in C:\WINDOWS\INF\cpu.inf; Device: "Intel Processor"; Driver: "Intel Processor"; Provider: "Microsoft"; Mfg: "Intel"; Section name: "IntelPPM_Inst".
#I023 Actual install section: [IntelPPM_Inst.NT]. Rank: 0x00000004. Effective driver date: 04/01/2004.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [IntelPPM_Inst] in "c:\windows\inf\cpu.inf".
#I320 Class GUID of device remains: {50127DC3-0F36-415E-A6CC-4CB3BE910B65}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-124 Doing copy-only install of "ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0".
#E358 An unsigned or incorrectly signed file "c:\windows\inf\layout.inf" for driver "Intel Processor" blocked (server install). Error 1168: Element not found.
#W187 Install failed, attempting to restore original files.

[harkaz]

The patch region of setupapi.dll 5.1.2600.5512 seems to be here:

Code: Select all

77973CA2                    loc_77973CA2:               ; Xref 77973A4C 77973A5A
77973CA2 899D40F7FFFF           mov     [ebp-8C0h],ebx
77973CA8 8D8540F7FFFF           lea     eax,[ebp-8C0h]
77973CAE 50                     push    eax
77973CAF 53                     push    ebx
77973CB0 FFB54CF7FFFF           push    dword ptr [ebp-8B4h]
77973CB6 56                     push    esi
77973CB7                    loc_77973CB7:               ; Xref 7797409A
77973CB7 FFB57CF7FFFF           push    dword ptr [ebp-884h]
;===================
77973CBD E80E6D0200             call    jmp_CryptCATAdminEnumCatalogFromHash ; @ 530BD
;===== sos! this function enumerates the catalogs that contain a specified hash.

77973CC2 898564F7FFFF           mov     [ebp-89Ch],eax
77973CC8 3BC3                   cmp     eax,ebx
77973CCA 0F8405030000           je      loc_77973FD5 ; Error (530CA)
;=== offset: 530CA - main patch!
;=== We need to patch this to jump somewhere else.
;=== The loc_7797407A is at offset: 5347A

77973CD0 C78590F7FFFF0C020000   mov     dword ptr [ebp-870h],20Ch
77973CDA 53                     push    ebx
77973CDB 8D8590F7FFFF           lea     eax,[ebp-870h]
77973CE1 50                     push    eax
77973CE2 FFB564F7FFFF           push    dword ptr [ebp-89Ch]
77973CE8 E8616C0200             call    jmp_CryptCATCatalogInfoFromContext
;======================== 
77973CED 85C0                   test    eax,eax
77973CEF 0F8485030000           je      loc_7797407A ;fails - offset 
77973CF5 399D80F7FFFF           cmp     [ebp-880h],ebx
77973CFB 7420                   jz      loc_77973D1D (530FB) 

77973CFD FFB580F7FFFF           push    dword ptr [ebp-880h]
77973D03 8D8594F7FFFF           lea     eax,[ebp-86Ch]
77973D09 50                     push    eax
77973D0A E894C7FBFF             call    pSetupGetFileTitle
77973D0F 50                     push    eax
77973D10 FF15E8119277           call    dword ptr [lstrcmpiW]
77973D16 F7D8                   neg     eax
77973D18 1BC0                   sbb     eax,eax
77973D1A 40                     inc     eax
77973D1B EB23                   jmp     loc_77973D40

77973D1D                    loc_77973D1D:               ; Xref 77973CFB
77973D1D F6453802               test    byte ptr [ebp+38h],2
77973D21 751A                   jnz     loc_77973D3D
77973D23 8D8594F7FFFF           lea     eax,[ebp-86Ch]
77973D29 50                     push    eax
77973D2A E874C7FBFF             call    pSetupGetFileTitle
77973D2F 50                     push    eax
77973D30 E8ABF0FFFF             call    fn_77972DE0 ; does some catalog checks
77973D35 85C0                   test    eax,eax
77973D37 7404                   jz      loc_77973D3D
77973D39 33C0                   xor     eax,eax
77973D3B EB03                   jmp     loc_77973D40

77973D3D                    loc_77973D3D:               ; Xref 77973D21 77973D37
77973D3D 33C0                   xor     eax,eax
77973D3F 40                     inc     eax
77973D40                    loc_77973D40:               ; Xref 77973D1B 77973D3B
77973D40 3BC3                   cmp     eax,ebx
77973D42 0F8432030000           je      loc_7797407A ; fails
77973D48 8B852CF7FFFF           mov     eax,[ebp-8D4h]
77973D4E 3BC3                   cmp     eax,ebx
77973D50 7402                   jz      loc_77973D54 ; SOS! Second jump!
77973D52 FF00                   inc     dword ptr [eax]
77973D54                    loc_77973D54:               ; Xref 77973D50
77973D54 395D18                 cmp     [ebp+18h],ebx
77973D57 0F84B6000000           je      loc_77973E13
77973D5D 8D8584F6FFFF           lea     eax,[ebp-97Ch]
77973D63 50                     push    eax
77973D64 53                     push    ebx
77973D65 8D8594F7FFFF           lea     eax,[ebp-86Ch]
77973D6B 50                     push    eax
77973D6C FF15B8129277           call    dword ptr [GetFileAttributesExW]
77973D72 8BF0                   mov     esi,eax
77973D74 3BF3                   cmp     esi,ebx
77973D76 0F84FE020000           je      loc_7797407A ;fails - SOS!
77973D7C 8B451C                 mov     eax,[ebp+1Ch]
77973D7F 3985A4F6FFFF           cmp     [ebp-95Ch],eax
77973D85 7402                   jz      loc_77973D89
77973D87 33F6                   xor     esi,esi
77973D89                    loc_77973D89:               ; Xref 77973D85
77973D89 3BF3                   cmp     esi,ebx
77973D8B 0F84E9020000           je      loc_7797407A
77973D91 8D8530F7FFFF           lea     eax,[ebp-8D0h]
77973D97 50                     push    eax
77973D98 8D8524F7FFFF           lea     eax,[ebp-8DCh]
77973D9E 50                     push    eax
77973D9F 8D8518F7FFFF           lea     eax,[ebp-8E8h]
77973DA5 50                     push    eax
77973DA6 8D85E0F6FFFF           lea     eax,[ebp-920h]
77973DAC 50                     push    eax
77973DAD 8D8594F7FFFF           lea     eax,[ebp-86Ch]
77973DB3 50                     push    eax
77973DB4 E898D4FBFF             call    pSetupOpenAndMapFileForRead
77973DB9 85C0                   test    eax,eax
77973DBB 7552                   jnz     loc_77973E0F
77973DBD 895DFC                 mov     [ebp-4],ebx
77973DC0 8B4D1C                 mov     ecx,[ebp+1Ch]
77973DC3 8BBD30F7FFFF           mov     edi,[ebp-8D0h]
77973DC9 8B7518                 mov     esi,[ebp+18h]
77973DCC 33C0                   xor     eax,eax
77973DCE F3A6                   rep     cmpsb
77973DD0 0F94C0                 sete    al
77973DD3 8BF0                   mov     esi,eax
77973DD5 89B5CCF6FFFF           mov     [ebp-934h],esi
77973DDB EB15                   jmp     loc_77973DF2

77973DDD 9090909090             db      5 dup (090h)

77973DE2                    off_77973DE2:               ; Xref 7797439C
77973DE2 33C0                   xor     eax,eax
77973DE4 40                     inc     eax
77973DE5 C3                     ret

77973DE6 9090909090             db      5 dup (090h)

77973DEB                    off_77973DEB:               ; Xref 779743A0
77973DEB 8B65E8                 mov     esp,[ebp-18h]
77973DEE 33DB                   xor     ebx,ebx
77973DF0 33F6                   xor     esi,esi
77973DF2                    loc_77973DF2:               ; Xref 77973DDB
77973DF2 834DFCFF               or      dword ptr [ebp-4],0FFFFFFFFh
77973DF6 FFB530F7FFFF           push    dword ptr [ebp-8D0h]
77973DFC FFB524F7FFFF           push    dword ptr [ebp-8DCh]
77973E02 FFB518F7FFFF           push    dword ptr [ebp-8E8h]
77973E08 E856B40100             call    pSetupUnmapAndCloseFile
77973E0D EB07                   jmp     loc_77973E16 ;next step

77973E0F                    loc_77973E0F:               ; Xref 77973DBB
77973E0F 33F6                   xor     esi,esi
77973E11 EB03                   jmp     loc_77973E16

77973E13                    loc_77973E13:               ; Xref 77973D57
77973E13 33F6                   xor     esi,esi
77973E15 46                     inc     esi

I tried to patch the 77973CCA to jump to different line, with no success. Program execution always fails (update.exe hangs). I'm trying to find a solution.

[harkaz]

Although I didn't patch the setupapi.dll, I've found another way to overcome the issue. I used the original layout.inf for the INF directory only and no problems were reported.

So, after some updating of the Service pack 4 package, I will present you with Windows XP Service Pack 4 Milestone 1 very soon.

[tomasz86]

Just one comment - when adding new files to the source you can just create a second layout.inf file, ex. layout2.inf following the structure of the original one.

[harkaz]

Now I tested it on live CD-ROM installation - it fails to verify assemblies. Will try to use the original layout.inf and specify an alternative layout.inf file for syssetup.inf - probably it will work.

UPDATE: Issue is not releated with the modified layout.inf, i retried with the original layout.inf..
I'll start working on CD-ROM to see what causes this.

[harkaz]

I found that the assemblies issue was caused by a patched setupapi.dll I had previously created. I used the original setupapi.dll and the problem was fixed.

However, using a modified layout.inf file gave me the familiar "Windows XP Professional setup is not valid. No signature was present in the subject" error message.

I have two or three options:

1- Patch the syssetup.dll to accept a modified layout.inf file. However, this could cause future problems with driver installation, as we've seen in Service Pack install.
2 - Sign the layout.inf file using a self-signed certificate and preinstall the certificate in Trusted Root Certificates store during text-mode setup.
3- Use a modified layout.inf file only for GUI-mode setup - not really an option.

Option #2 causes less problems, in my opinion.

[harkaz]

Success! I just managed to install a modified layout.inf on live system with a catalog I have signed with a certificate I created (I am the CA as well).

Now, some final steps are left to complete XP SP4 Milestone 1.

[=[FEAR]=JIGSAW]

Cool

[harkaz]

Windows XP Unofficial SP4 Milestone 1 is ready!

What's changed since SP3 package (most important changes):

- Windows Messenger 4.7 is completely removed from all Windows editions.
- Changed the Service Pack version to number 4 (not in OS itself- which will still be SP3 for compatibilty reasons, but in OS installers - EXE and CD-ROM).
- Updated update.exe and setupapi.dll files for the SP installer.

The new version will be available for testing in a couple of minutes.

UPDATE: Download link available (copy-paste to your address bar):

https://mega.co.nz/#F!RZQlEAzC!GyCnB2pUJBcNgYP4R2ndVg

[ChiefZeke]

Tried link - file is no longer available

[harkaz]

That's strange, because when I copy it to my address bar it shows up normally. I get the error you mention only when I click on the link on the post

I will reupload it somewhere else.

UPDATE: I'm updating MSN Explorer and making some changes to ensure that Messenger will be removed even when Windows is upgraded. I will upload the new version very soon.

[ricktendo64]

You think you could publish a source so that other language updatepack makers could give making a localized sp4 a shot?

I do the spanish xp updatepack and am pretty good at repacking

[user_hidden]

Code: Select all

The file you are trying to download is no longer available.

This could be due to the following reasons: 
The file has been removed because of a ToS/AUP violation.
Invalid URL - the link you are trying to access does not exist
The file has been deleted by the user.

[shiner]

I would like to test this out, but I can only get to 35% of the DL before it stalls and I can't get it to resume.

Alternative site and md5 would be nice.

Update:
Just tried again and got to 42% of the download before it wimped out. I will keep the download alive for an hour to see if it kicks back in and can complete the file.

Update 2:
No go again. Remains stuck at 42%. I will have to wait for a different link maybe because I am on a data cap and don't want to waste my data on multiple failed downloads.

[harkaz]

OK, I've reuploadied the original Milestone 1 EXE to Google Drive.

I will include the Messenger's "Upgrade installation fix", MSN Explorer 10.5 and IE8 RTM in the next milestone (it's coming soon...).

This is the new Milestone 1 link: https://drive.google.com/folderview?id= ... sp=sharing

MD5: 35AA0429A2000E50FE8FC3A948750173

Note for repackaging: The sp4inf.cat catalog file used to verify layout.inf and syssetup.inf is temporary. In final builds, I will rebuild the nt5inf.cat file, which is normally used to verify all Setup INF files.

[shiner]

The gdrive link worked straightaway.

[ChiefZeke]

Click on the link > Goes to Google drive. Click on the file > error message: Sorry, no preview is available > click again > back to Google drive with one file: XPSP4. In upper right corner is a Sign in box - required to sign in?

[harkaz]

Click the arrow at the lower right corner.

[bphlpt]

Yeah, it's kind of weird. The arrow at the bottom right is not visible until you first click on the file. The download arrow is then visible while the error message - "Sorry, no preview is available" is also visible.

Cheers and Regards

[tomasz86]

It's probably better to use Google Drive links like this:

https://docs.google.com/file/d/0B7k-l_4 ... lNUbjhrQmM

[ChiefZeke]

Got it this time- took a few clicks through three pages to get it.

I saw the comments above about only using Ryan - any know if AutoStreamer works - figured I'd try to slipstream the SP4 M1 with an SP3 source to see what happens. Will report back later (today or tomorrow).

AutoStreaner did not recognize SP4 M1 as valid - probable becaus eof no KB number (my guess).

[harkaz]

Interesting... I've tested it with nLite, without problems.
I'll test it with Autostreamer as well.

[harkaz]

It's weird that Autostreamer cannot recognise the original SP3 package as well. I tried it with a Windows XP "Gold" disk.

[harkaz]

Updating the update.ver file manually is such a pain. I need a program to automate the process of updating the update.ver file with the latest file information.

Each line has the following general structure:

filename = MD5, Version_in_hex, Size, SP3QFE, CRC32

For example, iexplore.exe (IE8 RTM v 8.0.6001.18702) is referenced as:

iexplore.exe=B60DDDD2D63CE41CB8C487FCFBB6419E,000800001771490E,638816,SP3QFE,A69929E9

I need your help generating such a file for a given set of files.

NOTE: Not all files accept a version parameter. For example, binaries and information files accept versions, while wav files don't. In the second case, the parameter has to be omitted with a comma (,).

Thanks in advance.

[tomasz86]

Here you are:

https://dl.dropboxusercontent.com/u/153 ... DATEVER.7z

This isn't the newest version but it's the only one I can share now (the other one is part of a larger script and it's impossible to use it alone). This one is pretty slow so you'll have to be patient

You'll need to modify it though in order to process only single files as at the moment it's supposed to recreate update.ver for all files (just put your SP sfxcab archive or folder in HF). It also doesn't generate the last two values (SP**** and CRC32). I don't think they're really necessary but it wouldn't be difficult to edit the script in order to create them.

The script has been tested only in Windows 2000 and XP.

EDIT

By the way, there are some minor bugs in the original XP SP3.

[shiner]

feedback,

After integrating M1 into the source setup directory (SP2), if I use RVMi to add some T13 addons followed by my standard nLite run -- setup fails in VBox with a message that Windows cannot be installed. I tried twice, with and without "Optimize system files" checked in RVMi.

OTOH, when I skip RVMi altogether and use just the nLite run on the setup directory, setup succeeds in VBox and everything appears OK. (no addons though)

So it appears RVMi is breaking something (maybe).

[harkaz]

Can you give me more information about the error? Attach the setup log files for example.

[shiner]

I have done a few more tests and investigation.
My source setup + M1 with nLite integrated addons and other tweaks works just fine. No problems.

My source setup + M1 with RVMi integrated addons doesn't work. I did a folder compare of the result directory using only nLite and the result directory using RVMi. RVMi is removing SP3.cab AND the SP3.cat from the source. This is most likely the culprit. nLite doesn't do that.

If that is not the reason for the issue, then here is the text of the Setup error window in VBox:

Windows XP Professional Setup

Setup cannot access the CD containing the Windows XP installation files.

To retry, press ENTER. If you are not successful after several tries, quit Setup.
Then, to restart Setup, copy the Windows XP installation files to your hard disk.

To quit Setup, press F3.

This occurs just after formatting the system partition. No files are copied to that partition because this error occurs.

[harkaz]

@shiner, I''l take a look at it. What addon did you use?

@tomasz86 Thanks a lot for the tool. I wish there was such a tool for editing dosnet.inf and txtsetup.sif files...

I'm trying to integrate IE8 in the Service Pack 3 but I'm facing a very STRANGE problem.
I install the service pack without problems. I manually install install.ins file before reboot.
Then Windows restarts, oobe shows up, etc. But after completing the reboot, I can't launch IE8.

The only way to start the browser is to open an htm file in the ServicePackFiles folder. This is the only place from where it will open files. After that, the browser seems to work normally. However, the Developer Tools are not functional!

I'm trying to understand what causes these issues.

UPDATE: About the RyanVMi issue, probably the SP3.CAT is deleted because the integrator thinks it's superseded. Because the SP version number is 4, the catalog file for the SP would normally be SP4.CAT, but I haven't changed that yet. The integrator probably cleans up SP3.CAT for this reason.

UPDATE#2: Fixed the IE8 installer! Installed on top of XP SP3. Now I need to check the uninstallation process. Then I will test it on XP SP1 (IE8 cannot be updated on top of SP1 normally, so it's interesting to check for special errors) and prepare the CD-ROM files.

[tomasz86]

@tomasz86 Thanks a lot for the tool. I wish there was such a tool for editing dosnet.inf and txtsetup.sif files...

There is but it's a part of a larger script, precisely the script which I started writing long time ago (more info on MSFN: How to merge two text files?). The script is still unfinished - that's why I haven't made it publicly available yet. Yet, I've been using it to prepare all my unofficial packages such as UURollup, Update Rollup 2, .NET Framework merged installer, etc. so it's quite usable even in this state. Unfortunately the part responsible for handling Service Packs it's still only half-baked as for now.

At the moment you can use the script for merging updates into update rollups but the main goal is to also be able to add new updates to service packs. Merging INF files is the main part of the script (but not the only one since apart from that you also need to merge files, add new files, add addons, etc.).

Due to lack of time I haven't been able to go on with the development for a while but I'm going to resume it sometime later this year. Still, feel free to send me a PM if you're interested in trying it out. Anyone else interested in testing is also welcomed to contact me but please remember that the script is still very experimental and should be used very carefully, especially for creating unofficial packages which would be later distributed around the Internet. Creating such packages without proper knowledge of their construction will cause more harm rather than do any good.

[harkaz]

Tested IE8 on XP SP1/SP2/SP3, it works fine.

I also tried to force the installer run on top of XP RTM, but it fails to verify product key.

[harkaz]

I'm now working on IE8 CD-ROM installations.
I have some problems here:

- Ieframe.dll registration fails (shdocvw.dll related?)
- Some IE8-related files fail to register.
- runonce -r takes too long to complete.

[ricktendo64]

occache.dll also fails to self reg, these other files I remove from syssetup.inf so they dont register

syssetup.inf|11,,mshtml.dll,3||1
syssetup.inf|11,,msrating.dll,1||1
syssetup.inf|11,,inseng.dll,1||1
syssetup.inf|11,,occache.dll,3||1
syssetup.inf|11,,webcheck.dll,1||1
syssetup.inf|11,,imgutil.dll,1||1
syssetup.inf|11,,pngfilt.dll,1||1
;IE8
syssetup.inf|11,,browsewm.dll,1||1
syssetup.inf|11,,cdfview.dll,1||1
syssetup.inf|11,,danim.dll,1||1
syssetup.inf|11,,datime.dll,1||1
syssetup.inf|11,,extmgr.dll,1||1
syssetup.inf|11,,lmrt.dll,1||1

[harkaz]

Thanks for the tip ricktendo64. Intead of removing these entries completely, I preferred to change the registration parameter to number 2 and this caused no issues.
Now I need to fix one thing in CD-ROM installations: the Downloaded Program Files folder icon is not properly shown.

I have also fixed many bugs of SP4 uninstallation, when installed on top of IE8.

I decided to include the latest Windows Update Agent as well in the M2, so it will longer to release it.

[harkaz]

All IE8 issues fixed. Tested on clean, upgrade and live installations on top of IE6/IE7/IE8.

Some final touches to complete IE8 integration and move on with Windows Update Agent.

M2 will be available right after Windows Update Agent is integrated to Windows XP SP4.

[harkaz]

In order to integrate the Windows Update Agent I have replaced the original files and registered the new ones.

Is there something else I need to do?

For some reason the Windows Update site hangs and svchost shows 99% CPU usage.

[bphlpt]

@harkaz,

Please keep working and keep posting your progress and any questions you might have. I, for one just don't respond because you are doing things I never have, so I don't have any idea what to tell you when you ask a question -- but I do read every post and I wish you well. I'm sure many others do the same thing.

Cheers and Regards

[harkaz]

@ bphlpt: Thanks a lot for your support!

I've examined these addons: http://www.ryanvm.net/forum/viewtopic.php?p=78735 and I noticed I haven't registered the wuweb.cat catalog.

I'll try later to see if that's the problem.

[harkaz]

Unfortunately, the prblem persists. However, I have discovered somethingf interesting: even the Windows Update Agent installer doesn't work.

Is this a bug in registry, or this is due to IE8 RTM? I'll have to check this out.

UPDATE: I can't believe this. I just installed IE8 RTM with Windows Update Agent 3.0 on top of clean XP SP3 installation. The problem persists...

Next attempt: update IE with the latest cumulative update.

update #2: The latest IE8 cumulative update seems to do the trick, but I haven't confirmed that yet on SP4 configuration. I'll keep you updated.

[harkaz]

Success! Updating IE8 with the latest cumulative update after installing SP4 fixed the issue.

Some final fixes now: SP3.CAT deleted by RyanVMi and fix installation failure on top of a previously installed Service Pack (using the SP installer, for example: upgrade from XP Gold to XP SP2 and then trying to upgrade to SP4 fails).

After these fixes and some final testing, XP SP4 M2 will be available for download.

[Atari800xl]

When this is finished, can somebody please make a little writeup on how "ordinary users" van use this? I've read all the messages in this thread (very exciting to follow this thread, thanks Harry Kazmanski), but I'm still figuring out how I should use this for a Dutch SP4?
Thank you for all your hard work!!

[harkaz]

I've been working on M2 final these days. I have just made it possible to follow the update path: XP RTM -> XP SP2 -> XP SP4.

I still have a problem with SP4 uninstallation in that scenario, which is something I'm working on right now.

@Atari800xl: You're welcome Your guess about my name was wrong however (I'm from Greece).
A tutorial would be rather difficult to create, but I'll give it a try. You see, it's a great project with so many things to take care of.

[harkaz]

Windows XP Unofficial SP4 Milestone 2 is now available!

At last I have finalised the Milestone 2 installation package. This package fixes many bugs found in M1 installer and adds new features.

I. Bug fixes:

You will be able to follow these update paths as well (it triggered an error in M1):

- RTM->SP2->SP4
- RTM->SP1->SP4
- RTM->SP1->SP2->SP4

However, you'll be unable to uninstall XP SP4 from control panel after installing it following one of the above update paths.
There might be more update scenarios which will disable uninstallation. Please report such cases.

You won't be able to change the default backup directory (\WINDOWS\$NtServicePackUninstall$). For this reason, the "Browse" button has been disabled.

XP SP4 M2 installer requires SP1 at minimum. To upgrade from RTM, the recommended update path is: RTM->SP2->SP4, although you can also use any other possible update path flawlessly.

Some other bugs fixed: Messenger is completely removed from the system even when you run Upgrade installation from SP4 slipstreamed installation media. SP3.CAT was renamed to SP4.CAT to prevent its deletion from addon integrators.

NOTE: After installing XP SP4 on a real system, Automatic Updates oobe window may show up with the text: "Thank you for installing Service Pack 3". Don't be puzled by this: SP4 is basically SP3+post-sp3 updates.

II. What's new in SP4 M2:

- Internet Explorer 8 RTM: IE8 will be installed always with SP4. Tested installation/uninstallation on top of IE6/IE7/IE8 on live, clean and upgrade installations.
- Windows Update Agent 7.6.7600.256: SP4 will not include Microsoft Update. You should update IE8 with the latest cumulative update to use Windows Update website. If you use Automatic updates, it may cause high svchost usage, but it will show later some basic updates for WU to function properly. I don't recommend using Automatic Updates with this SP4 version.
NOTE: After uninstalling SP4, you may be unable to launch Windows Update from the Start menu. This happens if you had IE6 installed on your system before applying SP4 M2. This is not a problem, because WU site requires IE8 to function properly. I have checked this, and does not happen if you've upgraded on top of IE8.
- MSN Explorer 10.5: The latest version of MSN Explorer is available out of the box in CD-ROM installations. If you're updating a running system, it will keep the previously installed MSN Explorer version.

DOWNLOAD LINK: https://docs.google.com/file/d/0B7k-l_4 ... sp=sharing[/b]

MD5: 078A540DFAECCE513E7CAD28165C1165

Disclaimer: This is beta, unofficial Microsoft software and requires testing before applying to real hardware.

Looking ahead: Windows Installer 4.5 and WMP11 will be the first components to integrate in SP4 M3.

A technical note: @tomasz86: Cabarc failed BIG TIME creating the cab today. I used this excellent tool (and XVI32) to create the SFX EXE: http://www.softpedia.com/progDownload/S ... 31564.html.
It will work only in English, but I think it's easy to change the sfx header for a different langugae. It compresses all files without problems, and that's what matters (cabarc wouldn't compress after some point).

UPDATE: Download link updated with XP SP4 M2 final.[/b]

[bphlpt]

Your Google Drive folder link shows as "Empty folder"?????

Cheers and Regards

[harkaz]

I'm fixing a final bug right now. I will reupload the file ASAP.

[tomasz86]

Windows Update website works with IE6 SP1 in Windows 2000. Are you 100% sure that it requires IE8 in XP?

As for cabarc, I haven't really encountered any problems when using it in my system (both 2000 and XP) so no reason for me not to use it (at least for now)... Could you explain in details what exactly happened?

[user_hidden]

WU/MU works just fine with IE6 under XP-SP3

[harkaz]

I've fixed some other 3 issues:

-Offline Web pages folder text not shown properly in CD-ROM installations.
-New Tab page bug after enabling IEAccess fixed.
-update.exe did not create uninstaller after patching it to work in the RTM->SP2->SP4 etc. path.

About the WU issue: I'm uploading the M2 EXE right now, so that you can give me a hint about what's going wrong.

@tomasz86: cabarc failed to compress files after some point. It throwed a 'FCIAddFile error code 8' message and stopped execution. Probably the SP4 folder is too big for old cabarc (1997 version) because it showed no issues with M1 build.

UPDATE: Link is now available!

Happy testing!

[Din5dale]

Subscribing, thank you!

[harkaz]

MSI45 (RTM) integrated in live installs. Moving on to integrate MSI45 in CD-ROM installs.