Some have also been replaced with newer ones.
Here are some examples:
High Priority Update KB4014793 replaced high priority updates KB979687 and KB3126593.
High priority update KB3178034 replaced high priority update KB3145739.

Finally I do not understand why you are aggressive, here we are to help each other.

Some have also been replaced with newer ones.
Here are some examples:
High Priority Update KB4014793 replaced high priority updates KB979687 and KB3126593.
High priority update KB3178034 replaced high priority update KB3145739.

Thank you for showing me these problems!

I worked very hard to find these to make sure To have only whats needed. So thank you for showing me these. I will make the corrects in the next release!

I have been installing the updates manually after 2018-Sep-17 and have 52 updates (only the last IE8 is included, no .NET or MS Office updates). Some of them have probably been superseded by newer versions, which would explain the discrepancy with the number of 42 updates mentioned in your post. Here are my updates, listed in the same order as in Microsoft Update Catalog (which is the order they are installed by Windows Updates):

when oneadds hotfixes using nlite, is it normal that the iso grows considerably in size? Theres an option called Direct hotfix Integraton one would assume newer files replace older ones without adding weight to the ISO?

XPSP3_QFE_UpdatePack_20180109.7z
XPSP3_QFE_POSReady_Addon_20180917_5er.7z
XPSP3_QFE_EnablePOSReadyMU_Addon_20160311.7z
YumeYao_IE8_Addon_Clean_ENU_1.5.42.7z
YumeYao_WMP11_Addon_ENU_v3.5.1.7z
OnePiece_Microsoft_Silverlight_v5.1.50907.0_True_AddOn_INTL.cab
Kels_TweakUI_v2.10_CPL_addon_build2.cab
Addon_DirectX32_9.0c_Runtimes_201006.7z
WinRAR_AddOn_x86_5.71-en.zip40 new updates
* The 84493435 can not be integrated.
* It is advisable not to integrate the 4494528, but to install it manually.

Nikos Lots of your updates replaces each other .
Anyone can kindly make a iso with last update pack from 5eraph and make list of updates ? I am willing to try to update this addon.
I already updated existing IE8 addon .

You will find the complete list of updates released after 2018-Sep-17 in my post above with the date stamp of 2019-Jun-09--07:58. There are total of 52 updates. Two updates which were excluded are listed below the main list. It seems that Nikos agreed with that number in the subsequent post. However, I would still suggest checking the description of each update, in case I missed something. The list would only need to be modified for computers with processors which do not support SSE2. In that case there is some more information available on MSFN (please refer to the link below).

I have been updating two machines running the updates manually every month after 2018-Sep-17 and monitoring the following thread on MSFN:

[quote=Stormit post_id=144449 time=1526068027 user_id=19443]
[b]Hi 5eraph: I uploaded your new file 05/11/18. Thank You Again for all that you do.[/b]
[/quote]

Hey Stormit, thanks for uploading the treasure trove of files to your GDrive however the following files appear to be corrupted somehow as they will not unrar. Could you please refresh them as I would like to collect all that I can before Ryan shuts this board down. Long story short my storage got corrupted and I'm tring to replenish a new one will those files that are now forever lost. much appreciation in advance.

ALSO if is not too much trouble to compile a list of files and to whom they belong so I can sort them by creator thus extending credit for them whenever asked. Your a lifesaver at least for my XP network

I intend to finish 5ereph's great work by building the last XPSP3 QFE POSReady Addon myself after having given entries_POSUpdates.ini and 5erPOSUp.inf a thorough analysis which I will post here. First I have made a list of files and updates for the addon using the updates offered by Automatic Updates on a PC with XP SP3 installed from an ISO in which the QFE SP3 Update pack had been integrated. I received a list 0f 99 updates and after having downloaded them and extracted their contents I reduced the number of updates required to 81 by eliminating duplicates. Please note that these are supposed to be critical updates only with a few non security updates included. I have provided the update list I have compiled as an attachment, and invite comments and suggestions.

Thanks for pointing out the existence of this security update for Remote Desktop released 5/10/2019. Microsoft offer this update for XP and POSREADY 2009, so I think that it would be more appropriate to add it to the XPSP3_QFE_UpdatePack_20180109 which I intend to update some day.

Thanks for pointing out the existence of this security update for Remote Desktop released 5/10/2019. Microsoft offer this update for XP and POSREADY 2009, so I think that it would be more appropriate to add it to the XPSP3_QFE_UpdatePack_20180109 which I intend to update some day.

I am not sure about the logic of that. If Microsoft offered it for both operating systems then surely it should be in updates available to both OSes. I know this causes a duplication, so perhaps it would be best if it is only in the POSready update. In any case, leaving out such an important update would be wrong even if including it violates a strict taxonomy of the operating systems.

I am not sure about the logic of that. If Microsoft offered it for both operating systems then surely it should be in updates available to both OSes. I know this causes a duplication, so perhaps it would be best if it is only in the POSready update. In any case, leaving out such an important update would be wrong even if including it violates a strict taxonomy of the operating systems.

Bob

After giving this some consideration I decided that it would be prudent to add the Remote Desktop security update KB4500331 to my list of updates for a new XPSP3 QFE POSReady addon because it is possible that someone might integrate it into an ISO that has not been updated with the XPSP3_QFE_UpdatePack for Windows XP Post-SP3.

I assume that the those updates that caused problems when integrated individually using nlite will not be a problem when included in an update pack addon. I noticed that the dastardly KB4134651-v2 is not being offered by Automatic Updates so it is not in my list.

KB4500331 dated May-10
File: … 741e.exe
Size: 532,000 bytes
Security update for WES09 and POSReady 2009. POSR must be enabled, otherwise the update won’t get installed. The update is skipped by WU and must be installed manually.

KB4500331 dated May-10
File: … 741e.exe
Size: 532,000 bytes
Security update for WES09 and POSReady 2009. POSR must be enabled, otherwise the update won’t get installed. The update is skipped by WU and must be installed manually.

When KB4500331 is included with the addon I do not anticipate that the PC on which it is installed needs to have the HKEY_LOCAL_MACHINE\SYSTEM\WPA\PosReady key because the registry settings for successful installation of this update will be imported into the registry from the integrated install CD.

In order to list and download all the POSReady 2009 updates you could use the shareware utility Wuinstall. Obtain a fully functional trial of wuinstall here. An alternative is the Powershell scripts PSWindowsUpdate which can be downloaded fromhere. It requires Powershell 2.0 downloaded from here. Instructions for using PSWindowsUpdate can be found here. Note that modules have to be copied to %SYSTEMROOT%\System32\WindowsPowerShell\v1.0\Modules\PSWindowsUpdate. Wuinstall has the advantage that it includes the severity rating for each update in it's list.

Some of the listed updates detected with the WUA are duplicates including these updates for gdiplus.dll replaced with KB4495022:

I compared my list of POSReady updates with the list I compiled from 5ereph's POSReady addon to obtain a list of updates from his addon not detected by WUA using the nifty Microsoft utility WinDiff. Here is the list that I obtained:

1) My favourite WU scanning application is Windows Update MiniTool. It is free, it doesn't require .Net Framework and it can be run in offline mode. I have just run it on one of my XP installations which doesn't even have .Net v1.1 installed, with network connection disabled. WUMT v12/20/2016 is compatible with Windows XP and can be downloaded from the page shown below.

Until recently that version had also been available on Major Geeks but it has now been replaced with v07.01.2020, which only supports Windows 10.

Offline Mode allows checking updates on a machine without internet connection. To get it working the file "wsusscn2.cab" must be downloaded from Microsoft and placed in the same directory as WUMT file:

2) I have noticed that both MS WU and WUMT will often flag an update which has already been included in "XPSP3_QFE_UpdatePack" or "XPSP3_QFE_POSReady_Addon_20180917_5er". Here is an example from my latest scan:

1) My favourite WU scanning application is Windows Update MiniTool. It is free, it doesn't require .Net Framework and it can be run in offline mode. I have just run it on one of my XP installations which doesn't even have .Net v1.1 installed, with network connection disabled. WUMT v12/20/2016 is compatible with Windows XP and can be downloaded from the page shown below.

Thanks for drawing my attention to this cool Windows Update tool. I tried it and it after scanning for updates it provided notifications of available updates in a format similar to the Microsoft Update website. However, if you use it to download updates it will download those from the GDR service branch rather than the QFE service branch which is of no use to us. The same is probably true with Wuinstall and PSWindowsUpdate. Here is Microsoft's definition of GDR and QFE:

GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes.

What they mean is that the QFE updates are cumulative hotfixes based on customer feedback as well as security fixes and major bugfixes. The QFE updates can only be obtained from the Microsoft Update Catalogue.

A cool feature of the Windows Update MiniTool is the facility to select available updates from the gui and copy their title and URL location to the clipboard so it can be pasted into Notepad. If you remove the update titles and leave only the URLs and save the file as download.txt, you can download the updates with wget using this command:

wget -i download.txt

The alternative is to download selected updates from the Windows Update MiniTool's GUI which will download them to \Windows\SoftwareDistribution\Download\ with cryptic folder names like ba067eab1593c32b446232564b5e0ae0. However, Wuinstall and PSWindowsUpdate are command line tools for power users with a long list of options.

I kept a printout of my scan with Wuinstall and It does not contain the KB2479943 and KB2619339 included with the XPSP3_QFE_UpdatePack.

I kept a printout of my scan with Wuinstall and It does not contain the KB2479943 and KB2619339 included with the XPSP3_QFE_UpdatePack.

The reason why those two updates are flagged on my system might be because my XP SP3 source was trimmed with nLite and lots of components were removed (all .Net, WMP, and some more). So I wouldn't worry about it too much. What is more important when you look at the screenshots from my previous post is that WUMT flagged exactly the same updates as MS WU, so the tool seems to be reliable, even if used in offline mode.

Zephyr:

GDR service branches contain only those fixes that are widely released to address widespread, critical issues. QFE service branches contain hotfixes in addition to widely released fixes. What they mean is that the QFE updates are cumulative hotfixes based on customer feedback as well as security fixes and major bugfixes. The QFE updates can only be obtained from the Microsoft Update Catalogue.

However, if you use [WUMT] to download updates it will download those from the GDR service branch rather than the QFE service branch which is of no use to us.

Are you sure about that? This would mean that the only way to get QFE updates is to download them manually from Microsoft Update Catalogue. This is not a big deal with a basic setup like mine (listed below, for the record) but becomes more time consuming if there are some more components installed (.Net, MS Office, WMP, etc.).

Zephyr:
However, if you use [WUMT] to download updates it will download those from the GDR service branch rather than the QFE service branch which is of no use to us.

Are you sure about that? This would mean that the only way to get QFE updates is to download them manually from Microsoft Update Catalogue. This is not a big deal with a basic setup like mine (listed below, for the record) but becomes more time consuming if there are some more components installed (.Net, MS Office, WMP, etc.).

I am not 100% sure That QFE updates cannot be obtained using Windows Automatic Updates, because I am not an expert like 5ereph, but whenever I consult the Microsoft Automatic Update catalogue and go to the KB article referenced for each update the file list always gives the service branch as SP3QFE.

As I stated earlier I intend to build the final XPSP3 QFE POSReady Updates addon myself, because 5ereph has clearly abandoned the project. The first step is to obtain a list of of current updates for POSReady 2009 by running Winstall, PSWindowsUpdate or WUMT on a PC with a fully updated installation of Windows XP SP3, and piping the output to a text file. Using this list download all the updates from the Microsoft Update Catalogue and extract them into the folder in which they were supplied using the /X: switch. You then make a printout of the directory in which the updates were saved using this command:

This file is then edited so that all the files in each update is listed as a column with the KB number of the update from which it was extracted beside them in another column. This will reveal that many modules are found in several updates, but with different version numbers. We require to save only the modules with the highest version number, which corresponds to the the update that contains that module with the highest KB number. Here is a sample of the list that results:

You now need to copy the column with the KB numbers to another files and sort them in ascending order to obtain a list of required list of updates. Notepad2 makes this easy because it supports editing of columns. and sorting lines. This is a more reliable way of eliminating duplicates than visual inspection. Using this technique I was able to eliminate some more duplicates in my revised list which I present her as an attachment.

The next step for building the final XPSP3 QFE POSReady addon is to make a file list for every module that is included in the 7z archive that is the addon, including the path for folders. It is easy to make a mistake and omit to copy a required module into the folder where the addon is being assembled. The answer to this problem is to use a script to automate the process. Such a script is DX's Universal UpdatePack-Addon Creator. This is basically a batch file which has been preconfigured to automate the building of a limited number of addons which does not include this addon. However, if you do try to use it with the WinXP Post-SP3 Update Pack setting it will extract all the files from the POSReady updates and select those with the highest version number to be included with the addon, while copying them into the required folders where necessary. There are some alterations to be made to the resulting assembly so that it is suitable for our addon. These are listed below:

The next step in making the final build of the XPSP3 QFE POSReady Update is to analyze entries_POSUdates.ini from the the last build from 2018, and revise it to support the current POSReady 2009 updates. It would be helpful if you could make suggestions or attempt some of the procedures suggested here to confirm that we are getting consistent results, as I am bound to have made some mistakes on the way.

Having studied entries_POSUdates.ini it seems to me that the XPSP3 QFE Update Pack Post-SP3 and the XPSP3 QFE POSReady Addon are supposed to be integrated at the same time. I assume that the integrator reads the instructions in entries_POSUdates.ini first, and then modifies qfeUpPck.inf in the rvtemp directory so as to remove registry entries for XPSP3 updates that have been replaced by POSReady 2009 updates along with their associated security catalogues. Actually identifying which updates in the XPSP3 QFE Update Pack are going to be obsolete requires an enormous amount of time and intense concentration, which makes me think that 5ereph must have had a script to automate the task. You could examine the entries for 243 updates at the Microsoft Update Catalogue which does show the POSReady 2009 updates that replace XPSP3 updates, but this would take forever, and not every update included in the XPSP3 QFE Update Pack is shown at the Microsoft Update Catalogue, and even when they are it is not reliable guide for replacements. What I did was search qfeUpPck.inf for the modules for each POSReady 2009 update in my Revised list of POSREADY 2009 Updates to identify the XPSP3 updates that contain the same module which makes them obsolete. Sometimes a module is bundled with other modules, so you have to do a reverse search in the Revised list of POSREADY 2009 Updates to ensure that all of these modules have been replaced by a current POSReady 2009 update. Here is my analysis of entries_POSUdates.ini that should provide a guide to updating it:

[ExtraFileEdits]
Edits qfeUpPck.inf from the XPSP3_QFE_UpdatePack for Windows XP Post-SP3 to remove registry entries for updates that have been replaced by POSREADY 2009 updates. The text in the [QFEUpdatePack] section before the seperator is replaced by the text after the seperator, which in this example is a space. The number after the second seperator determines how often this operation is carried out.

The line "RunPostSetupCommands =" is altered to enable automatic update of the Adobe Flash Player after install.

The next entry copies a line from [KB2510581] to a new section [KB971961]. I cannot understand the point of this, so I would leave it unaltered.

[sysoc]
This section contains entries that need to go into the [Components] section of sysoc.inf. This section is left unaltered.

[dosnet_files]
Lines to write inside dosnet.inf. This section is left unaltered.

[txtsetup_files]
This section contains entries that need to go into the [SourceDisksFiles] section of txtsetup.sif. This section needs to be edited to show the correct file names for the latest Adobe Flash Player.

[i386_compress]
This section compresses files in @winroot or the subdirectories of @winroot. Otherwise provide path. This section is left unaltered.

[obsolete]
This section contains all the updates referenced in [ExtraFileEdits]. This section tells the integrator to remove entries in the svcpack.inf file that include these KB numbers and remove any files that include these KB numbers from the svcpack directory. It is mainly security catalogues and their entries in svcpack.inf that are removed.

I attach lists of all the obsolete XPSP3 from the XPSP3 QFE Update Pack that I can identify.

I took a pickaxe to the RyanVM repository of PostSP3 kb's (megaupload) and now have a folder of .exe of updates which I felt were the only ones I needed (by reading their descriptions listed in the QFE POST SP3 Update pack thread). IIRC few months ago I attempted to craft a 7z with DXUPack using these refined set of select updates and subsequently integrated the .7z with nlite to XP SP2 source (prior to which SP3 was also integrated to). I ensured everything was listed chronologically.
Upon booting after install there were some serious errors which made OS inoperable, deviating from my usual unintended install***. My 'base' unattended (custom registry entries, OEM apps etc) install is finalized already and has been for years. Only these updates are giving me a headache. Also I did a little test: Took whole RyanVM repository of English kb-xxxxxx.exe's and put them into a folder, and using DXUPACK, made alternative PostSP3 addon with those. No modifications. The resultant file was 77.2Mb, whereas the QFE_PostSP3 update pack is 58Mb. Very perlexing.

***Edit Upon re-reading the tutorial on the download page for DXUPACK here on ryanVM.net, its likely that I am not using DXUPACK right. Its more complicated than just putting files in a folder - I read something about addtion of some weird .net 3 and .net4 files (????? this addon creator is definately not for faint of hearted!!) - regardless I loath ANY inclusion of .NET as I prefer to manually install/un these, after unnatended install, at leisure / per requirement. So I guess this rules out using Addon Creator altogether.

So now what? I can either ignore Post SP3 and POS2009 updates altogether, (custom selection pack or the 'full' QFEupdate packs) altogether and stick with my vanilla unintended install, (which is final minus Post SP3 updates).

In any case I'd appreciate it if someone could make a modular update E8 addon.
Any takers?
note: Whether or not the TLS update (which I believe is a POS2009 update) can be included in a IE8 addon I'm unsure..

I'd also like to confirm if its possible to make an addon with select updates from complete Post SP3 list.

Apparently 5ereph thinks that the unpatched Spectre/Meltdown vulnerability in Windows XP is so catastrophic that there is no longer a necessity for further builds of his POSReady 2009 addon. Therefore I am volunteering to release the final build. Below is my revision of entries_POSUpdates.ini. After going to all the trouble to identify obsolete updates in user_hidden's XPSP3 QFE Update Pack I discovered that my revision of entries_POSUpdates.ini is almost the same as the original except that I have removed one incorrect entry and several spurious entries. I have also updated the file names for the Adobe Flash modules to the current version in [txtsetup_files].

[T-13.SetRunOnce.AddReg]
This registry entry is written to launch the the next INF section [T-13] using rundll32.exe. It does not need to be altered.

[T-13]
The entries at the beginning add the registry entries for the flash player and it's update service, and so need to be retained. The next entries are not altered because they refer to updates to IE6, and there have been no further cumulative security updates for IE6 since KB3124275. KB4316682.AddReg adds the registry entries for the cumulative security update for IE8 for WES09 and POSReady 2009 from 5/30/2018 and needs to be replaced with KB4493435.AddReg

[1st_Logon.SetRunOnce.AddReg]
This section adds a registry entry to launch the next INF section [1st_UserStart] using rundll32.exe at first time the user logs in. It does not need to be altered.

[SourceDisksNames]
Identifies the disks that contain the source files being installed, and their location on the disk. It does not need to be altered.

[SourceDisksFiles]
The source files that are used during installation. Only includes Microsoft Jet Expression Service for some reason. It does not need to be altered.

[DestinationDirs]
Specifies the target destination directory for copy operations on files referenced by name in the next section. It does not need to be altered.

[CopyAlways.DLLCache.Files]
Defines the files to be copied to the target directory defined in the previous section. It does not need to be altered.

[DelayedFileReplace.Commands]
KB4034775 has not beeen superceded, so this section should be retained unaltered.

[KBxxxxxxx.AddReg}
As these registration entries are different from the registration entries shown in the update's inf file I assum that each update has to be installed while using a utility like SysTracer to log changes to the system that are presented as reg files. These need to be converted to the inf format using a utility like Reg2INF.

Note that %SP4REG% is a variable for SOFTWARE\Microsoft\Updates\Windows XP\SP4 and %HFREG% is a variable for SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix

[KB3081320.AddReg]
This entry appears to be incomplete because it contains no file information, so it must be generated again.. This security update has not been superseded, so retain this entry with the new information.

[KB4316682.AddReg]
Adds the ability to Internet Explorer to utilize TLS 1.1 and 1.2 support. This section is retained unaltered.

[FlashService.AddReg]
This section is retained unaltered.

[Flash32.AddReg]
Change the version number from 31.0.0.108 to the number of the latest version which is 32.0.0.303. Change the file names to the names of the latest version which is Flash32_32_0_0_303.ocx and FlashUtil32_32_0_0_303_ActiveX.exe. Otherwise this entry remains unchanged.

[Flash.RegSvr]
Change the file name to the latest name which is Flash32_32_0_0_303.ocx

[T-13.SetRunOnce.AddReg]
This registry entry is written to launch the the next INF section [T-13] using rundll32.exe. It does not need to be altered.

[T-13]
The entries at the beginning add the registry entries for the flash player and it's update service, and so need to be retained. The next entries are not altered because they refer to updates to IE6, and there have been no further cumulative security updates for IE6 since KB3124275. KB4316682.AddReg adds the registry entries for the cumulative security update for IE8 for WES09 and POSReady 2009 from 5/30/2018 and needs to be replaced with KB4493435.AddReg

[1st_Logon.SetRunOnce.AddReg]
This section adds a registry entry to launch the next INF section [1st_UserStart] using rundll32.exe at first time the user logs in. It does not need to be altered.

[SourceDisksNames]
Identifies the disks that contain the source files being installed, and their location on the disk. It does not need to be altered.

[SourceDisksFiles]
The source files that are used during installation. Only includes Microsoft Jet Expression Service for some reason. It does not need to be altered.

[DestinationDirs]
Specifies the target destination directory for copy operations on files referenced by name in the next section. It does not need to be altered.

[CopyAlways.DLLCache.Files]
Defines the files to be copied to the target directory defined in the previous section. It does not need to be altered.

[DelayedFileReplace.Commands]
KB4034775 has not beeen superceded, so this section should be retained unaltered.

[KBxxxxxxx.AddReg}
As these registration entries are different from the registration entries shown in the update's inf file I assum that each update has to be installed while using a utility like SysTracer to log changes to the system that are presented as reg files. These need to be converted to the inf format using a utility like Reg2INF.

Note that %SP4REG% is a variable for SOFTWARE\Microsoft\Updates\Windows XP\SP4 and %HFREG% is a variable for SOFTWARE\Microsoft\Windows NT\CurrentVersion\HotFix

[KB3081320.AddReg]
This entry appears to be incomplete because it contains no file information, so it must be generated again.. This security update has not been superseded, so retain this entry with the new information.

[KB4316682.AddReg]
Adds the ability to Internet Explorer to utilize TLS 1.1 and 1.2 support. This section is retained unaltered.

[FlashService.AddReg]
This section is retained unaltered.

[Flash32.AddReg]
Change the version number from 31.0.0.108 to the number of the latest version which is 32.0.0.303. Change the file names to the names of the latest version which is Flash32_32_0_0_303.ocx and FlashUtil32_32_0_0_303_ActiveX.exe. Otherwise this entry remains unchanged.

[Flash.RegSvr]
Change the file name to the latest name which is Flash32_32_0_0_303.ocx

Don't worry I have not given up. I have been struggling with Systracer Pro which has quite a steep learning curve. Apart from finding a serial that works the main problem is filtering out all the spurious registry entries that Windows makes every time something changes on the PC. Not being an expert like 5ereph I cannot be certain which entries are made by the installer and which are made by Windows.

Do we need flash integrated? that deadmeat eat lot of space, and actually I was glad when mrt.exe was gone too. After all we could use smaller flash debugger to play swf.

@Zephyr are you plan to merge with PostSP3 UP or just Posready UP?

I am glad you brought up the issue of flash, because I cannot see the point of including the ActiveX version of flash in the update pack when no-one watches video on IE8 anymore, and you no longer need IE to use the Microsoft Update site. If anyone can think of a good reason to retain flash I would be interested to hear what they say.

I plan to merge the new updates with the POSReady update pack. The postSP3 update pack only requires KB4500331 (remote code execution vulnerability in Remote Desktop Services) to be fully updated.

Last edited by Zephyr on Tue Apr 28, 2020 5:51 am, edited 1 time in total.

Guys, I've been suspicious about why odbc (mdac) doesn't work in my slipstreamed XP for months, so I tried to locate the problem once again
note: you could test it with freeware "mdb plus" to open any access mdb file

Guys, I've been suspicious about why odbc (mdac) doesn't work in my slipstreamed XP for months, so I tried to locate the problem once again
note: you could test it with freeware "mdb plus" to open any access mdb file

I tried opening an mdb sample file with MDB Viewer Plus and received the following error message "Provider cannot be found. It may not be properly installed." I opened odbcad32.exe (ODBC Data Source Administrator) and under the Drivers tab I see that the Microsoft Access Driver (ODBCJT32.DLL) supports mdb files. I attempted to open a mdb sample file with MDB Viewer Plus while Microsoft Process Monitor is running with a filter for MDBPlus.exe, but I found that the program successfully accesses Microsoft database modules like msdart.dll, msader15.dll, and msdao15.dll. Shortly before exiting the thread MDBPlus.exe could not find the following registry entries:

HKCR\CLSID\{00000542-0000-0010-8000-00AA006D2EA4} is a key for the in process server msdao15.dll.

The ProgID is ADODB.ErrorLookup.2.8

KB4034044 included in the last XPSP3 QFE POSReady update pack updated msado15.dll and msado28.dll with a large number of registry entries under the KEY_CLASSES_ROOT\Interface. My revision of the update pack will install KB4489973 which will update these modules to version 2.81.3016.0. There are a couple of new registry entries in HKEY_CLASSES_ROOT\TypeLib which might make a difference. We shall see.

I am clueless about this sort of thing, so in this situation I might be tempted to install the 2007 0r 2010 Microsoft Access Database Engine

@Zephyr the problem is many apps that still use mdb will bypass Access db engine and use older windows bundled driver unless they tried to open the newer accdb file. I have tried myself installing 2007 or 2010 version and mdbplus still not working.

I have finally built an inf file of the new POSReady 2009 updates that will be merged with 5erPOSUp.inf from the original addon built by 5ereph. It is presented as an attachment with this post, and if there are any code wizards who would like to study it I would be glad to hear any comments and suggestions.

When 5ereph built the addon he installed each update and recorded the new registry settings by taking a snapshot of the system before and after the updates were installed. This is a superior approach to nLite which integrates a bunch of update installers by copying the inf file that each one contains. 5ereph's approach means the registry will be updated with new internet settings, for instance, but it is VERY labour intensive.

The two tools that I have found most useful for this is the freeware Regshot 2 Unicode, and the shareware Systracer Pro. They both do the same thing, like recording and comparing snapshots and producing reports, but the GUI of Systracer is more polished and elegant. Regshot 2 Unicode has the advantage that once a comparison has been made a screen will show all the registry keys recorded as a tree view, with tick boxes so that you can deselect the keys that are irrelevant. This means that you can incorporate keys from various parts pf the registry in a single reg file, rather than having to combine reg files as you do with SysTracer. Also for our purposes it has the added bonus of outputting a INF file which eliminates the need for a REG to INF conversion. However, Regshot 2 Unicode requires the regshot.ini file to be edited to build a custom filter of unwanted registry settings. SysTracer will allow you to build a filter through the GUI with the usual Explorer type view and tick boxes.

I made most of the reg files with Systracer, and I did a batch conversion using Reg2inf, but this tool is rather unreliable and repeated some entries with the first few lines or truncated others at the last few lines. The format of INF files was too different from 5erPOSUp.inf, which required a lot of search and replace operations. Neither Regshot 2 Unicode or Reg2inf could create the standard INF destination directories variables for paths, which required more search and replace operations.

I found the culprit of the odbc errors it is kb4034775 which basically MDAC update. If I slipstream all post SP3 updates until kb4500331 except kb4034775 I can open mdb file just fine.
Whats weird is I can install kb4034775 manually afterward and ODBC still works! I check what happen through regshot and found nothing special with registry just KB entries, no self registering, no CLSID.. nothing. So something might be wrong with the way kb4034775 slipstreming, kb4034775 also has no superseded updates.

The problem is that qfecheck has revealed that Windows setup has not copied the updated ks.sys and termdd.sys to %SYSTEMROOT%\System32\drivers, but has instead copied the versions from SP3 in driver.cab. This means that once XP is installed we have ks.sys version 5.3.2600.5512 instead of version 5.3.2600.7562 and termdd.sys version 5.1.2600.5512 instead of 5.1.2600.7701.

Here are the entries for ks.sys and termdd.sys in the setup files after integration which might offer a clue:

I suppose you could manually copy ks.sys and termdd.sys to the Drivers, Drivers Cache, and DllCache folders, or I could add a RunPostSetupCommands at [T13] to copy the files to their correct locations, but I am not sure how to do that.

DONT USE 4SHARED .I cannot dowload rather i got hijacked to Advertisement pages after pages.
Use https://www.filedropper.com/
I can 'provide you mediafire mirror
We can manually add that hotfix .
Cheers

DONT USE 4SHARED .I cannot dowload rather i got hijacked to Advertisement pages after pages.

I did get bombed with adverts recently with 4shared, but they seem to have gone away today. I tried logging out of my 4shared account and downloading my revision of the addon by logging in through my Google account and I succeeded in downloading the file with no problem. However Mediafire would be a better option for this forum because they don't require temporary registration through Google, Facebook or Twitter.