XPSP3_QFE_UpdatePack for Windows XP Post-SP3 20180109
- =[FEAR]=JIGSAW
- Posts: 400
- Joined: Mon Feb 18, 2008 11:54 am
- Location: Cape Town, South Africa
August 2015 cumulative time zone update available.
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- =[FEAR]=JIGSAW
- Posts: 400
- Joined: Mon Feb 18, 2008 11:54 am
- Location: Cape Town, South Africa
I've noticed a few times installing XP that POSReady does not get enabled. Even though I am using the EnablePOSReadyMU_Addon, the necessary reg entry does not get created. Sometimes it's created and sometimes not. On my last install the reg entry was missing. I checked the qfeUpPck.in_ and it contains the following, but it doesn't look like it's always being applied:
Anyone have any ideas why enabling sometimes fails?
Code: Select all
[POS.AddReg]
; will allow MU to offer POSReady2009/Embedded updates
HKLM,"SYSTEM\CurrentControlSet\Control\WindowsEmbedded\ProductVersion","FeaturePackVersion",0x00000000,"SP3"
HKLM,"SYSTEM\WPA\PosReady","Installed",0x10001,01,00,00,00
; will allow installation of Microsoft Security Essentials on POSReady 2009
HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Microsoft Security Client",,0x10
XPSP3_QFE_EnablePOSReadyMU_Addon_20141111.7z5eraph wrote:What version of "EnablePOSReadyMU_Addon" do you have, adric?
I'm just wondering why the [POS.AddReg] section in the qfeUpPck.inf isn't always applied during install.
Last edited by adric on Wed Sep 16, 2015 7:36 pm, edited 3 times in total.
Update Packs
Many thanks to you user_hindden for your pack and 5eraph for the POS Ready addon. 

- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
adric wrote:XPSP3_QFE_EnablePOSReadyMU_Addon_20141111.7z5eraph wrote:What version of "EnablePOSReadyMU_Addon" do you have, adric?
I'm just wondering why the [POS.AddReg] section in the qfeUpPck.inf isn't always applied during install.
replace:
Code: Select all
qfeUpPck.inf|,SA3009008|,SA3009008,POS.AddReg|1
Code: Select all
qfeUpPck.inf|,MU.Addreg|,MU.Addreg,POS.AddReg|1
You did not miss an update, adric. The original addon still works.
this addon won't work with nlite i tried integrating just this addon and it throws this error http://postimg.org/image/vtkupqj47/ , this did not happen with earlier versions of this addon
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
must be one of YOUR addons creating the error.Adrian wrote:this addon won't work with nlite i tried integrating just this addon and it throws this error http://postimg.org/image/vtkupqj47/ , this did not happen with earlier versions of this addon
the update pack is not generating the msg
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
No rush, user_hidden. Flash will need updating again within a week. There should be a time zone update at around the same time.
Take whatever time you need.
Take whatever time you need.

I am getting file-copy error/s during the txt-mode-setup phase, when using 5eraph's "Remove Nasty Net Locater protocol addon:
"5er_KB922120-v6_user_hidden_Removal_Addon_v20120814.7z".
The errors are
the "entries_KB922120_Removal.ini" file inside the above addon has following section.
Can some one throw light on what is the problem I am having?
Is it due to the incorrect order (sequence) of the addons?
My order of addons as below:-
rgds bhishmar
"5er_KB922120-v6_user_hidden_Removal_Addon_v20120814.7z".
The errors are
My limited investigation shows that TXTSETUP.SIF still has entries for the above 4 files, even thoughfile missing reports for rspndr.adm, exe, inf, & sys files.
the "entries_KB922120_Removal.ini" file inside the above addon has following section.
This section is supposed to remove these files from TXTSETUP.SIF, is it not?[obsolete_files] ;RVMi and nLite code
rspndr.adm
rspndr.exe
rspndr.inf
rspndr.sys
Can some one throw light on what is the problem I am having?
Is it due to the incorrect order (sequence) of the addons?
My order of addons as below:-
Can somebody also suggest a better order?UpdatePack=C:\C_SAVE\SAVE\RyanVM\XPSP3_QFE_UpdatePack_20150908.7z
[AddonPacks]
RVMAddons_2.0.1_UH.7z
Ricks-YumeYao_MicrosoftVC7891012RuntimeLibraries_MixedAddon_2_2_3.7z
CmdOpenInstallSilent-2.1.0.exe
Addon_DirectX32_9.0c_Runtimes_201006.7z
Addon_Java_Runtime_7_update_72.7z
np2-mod_4225_954_addon.7z
5er_KB893056_Hibernate_SP3_Addon.7z
5er_KB922120-v6_user_hidden_Removal_Addon_v20120814.7z
5er_Win7CMDToolsForNT5x_Addon_v2012-01_3_x86.7z
XPSP3_QFE_POSReady_Addon_20150908_5er.7z
Ricks-YumeYao_WMP11_Addon_ENU_V3_4_7.7z
YumeYao_IE8_Addon_Nosetuperr_ENU_1.5.12.7z
RogueSpearAddonsM2-XPSP3-NoKtD_8.09.7z
MassStorageAddons_IaStor_8.9.0.1023.7z
rgds bhishmar
BLUF: Integrate the update pack and all of your other addons first. Then, when that has been completed, integrate your removal addon. Running the removal addon a second time will not remove the entries that cause the copy errors, as described in 2.a. below.
Sadly, Bhishmar, it has nothing to do with your order. It has to do with how RVMi seems to work: (v1.6 and 1.6.1beta2.1)
As a workaround for your existing modified source you can add 0 byte text files with the following names to I386, then run the removal addon again on the source. It should then work.
DOSNet.inf
TxtSetup.sif
Sadly, Bhishmar, it has nothing to do with your order. It has to do with how RVMi seems to work: (v1.6 and 1.6.1beta2.1)
- Files in update pack, then addons, are compressed and added to the source. Addon files will always overwrite update pack files with the same name.
- Files are removed per [Obsolete_Files] directive:
- If entries for those files exist in DOSNet.inf and TxtSetup.sif then those entries are removed with the files. But if the files don't exist in the source then no entries are removed from DOSNet.inf or TxtSetup.sif.
- Entries are added to DOSNet.inf and TxtSetup.sif per [Dosnet_Files] and [Txtsetup_Files] directives.
As a workaround for your existing modified source you can add 0 byte text files with the following names to I386, then run the removal addon again on the source. It should then work.
- rspndr.ad_, rspndr.ex_, rspndr.in_ and rspndr.sy_
DOSNet.inf
Code: Select all
d1,rspndr.adm
d1,rspndr.exe
d1,rspndr.inf
d1,rspndr.sys
Code: Select all
rspndr.adm= 100,,,,,,,20,0,0
rspndr.exe= 100,,,,,,,2,0,0
rspndr.inf= 100,,,,,,,20,0,0
rspndr.sys= 100,,,,,,,4,0,0
"5eraph",
Many thanks for your detailed explanation & reasoning, and especially taking time for a quick response.
I was other wise engaged, so could not see ur reply earlier.
I prefer your last suggested method (alternate workaround), of editing & removing the respective file entries from TXTSETUP.sif & DOSNET.sif, before running the final ISO creation, for convenience, & lesser number of intervening steps.
Only I have a question : After editing these two files (TXTSETUP.sif & DOSNET.sif), any file digital-signature setting tool has to be run on them, before the ISO creation ? I have a faint memory this was required in earlier days, May be I am wrong!
Also a final suggestion, for the purpose of clarity & full correctness in your excellent post for others benefit.
I think your 2nd line in the post should be changed: (i.e. if I understood it correctly.)
from:
Thanks & rgds Bhishmar
Many thanks for your detailed explanation & reasoning, and especially taking time for a quick response.
I was other wise engaged, so could not see ur reply earlier.
I prefer your last suggested method (alternate workaround), of editing & removing the respective file entries from TXTSETUP.sif & DOSNET.sif, before running the final ISO creation, for convenience, & lesser number of intervening steps.
Only I have a question : After editing these two files (TXTSETUP.sif & DOSNET.sif), any file digital-signature setting tool has to be run on them, before the ISO creation ? I have a faint memory this was required in earlier days, May be I am wrong!
Also a final suggestion, for the purpose of clarity & full correctness in your excellent post for others benefit.
I think your 2nd line in the post should be changed: (i.e. if I understood it correctly.)
from:
to:Running the removal addon a second time will not remove the entries that cause the copy errors, as described in 2.a. below.
i.e either "not" should be deleted from first line, OR use the changed line.Running the removal addon first time (along with other addons) will not remove the entries that cause the copy errors, as described in 2.a. below.
Thanks & rgds Bhishmar
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- =[FEAR]=JIGSAW
- Posts: 400
- Joined: Mon Feb 18, 2008 11:54 am
- Location: Cape Town, South Africa
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
Microsoft seems to have stopped writing Knowledge Base articles for certificate updates and other updates that don't involve files end-users can choose to download from the Microsoft Update or Microsoft Download sites. Some examples:
- SA3009008 (KB3009008) - Instructions on disabling SSL 3.0. The Knowledge Base article didn't exist until the Fixit solution was available, but the Security Advisory was up 15 days before then.
SA3119884 (KB3119884) - November 30th certificate revocations. Still no Knowledge Base article.
SA3123040 (KB3123040) - December 8th certificate revocation. No KB article here either.
- =[FEAR]=JIGSAW
- Posts: 400
- Joined: Mon Feb 18, 2008 11:54 am
- Location: Cape Town, South Africa
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- dumpydooby
- Posts: 530
- Joined: Sun Jan 15, 2006 6:09 am
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!
- =[FEAR]=JIGSAW
- Posts: 400
- Joined: Mon Feb 18, 2008 11:54 am
- Location: Cape Town, South Africa
- user_hidden
- Posts: 1924
- Joined: Thu Dec 06, 2007 7:52 am
- Location: Canada eh!