Leaderboard

@dencorso : Methinks the above two posts are just outright "plug" attempts for the referenced payware software manufacturer ; new MSFN user @rryan22 has just subscribed 6 hours ago with the (apparent) sole intent of making those two posts... And while the country of origin has been declared as the UK, the quality of the English language used points more to a translation machine/web bot, e.g.: Just to be on the clear, I have nothing personal against payware (coders certainly have to make a living) or people without an adequate command of the English language (which is the default in these forums...). However, unless @rryan22 has personally tested every individual piece of payware software he has mentioned as the last one working on Vista/Win2k, then I'll continue to treat his posts as disguised advertisement attempts... BTW, should any of the claims made be true, why isn't a transparent approach of accessing those older, still payware, software versions offered?

First, before making the registry change below, you should download and install Microsoft's updated Windows Installer 4.5 (KB942288-v3) from THIS LINK for Windows XP 32-bit, which is what we assume you have. (The MS article that explains this updated installer is HERE.) Next, copy the text given by @Sebijk (below) to notepad and save it as POSReady.txt Make sure what you copy starts with the "Windows..." line and has two blank lines after the line that ends in "00000001" Rename the file POSReady.txt to POSReady.reg, right-click on it, select "Merge", then "Yes". Reboot the system. =================######================= Direct Links to WU/MU (just in case...): for Windows Update http://update.microsoft.com/windowsupdate for Microsoft Update http://update.microsoft.com/microsoftupdate =================######================= NOW, sometimes Microsoft Update (MU) takes a long time to get anywhere - sometimes a LONG LONG time. Sometimes even longer than that. When MU takes ages to find anything, stop it, install by hand the Office 2007 Comparability Pack and all Office 2003 updates (they usually don't require rebooting), then the latest IE8 update, then reboot. After that, MU will find all remaining relevant updates fast. If using Windows Update (WU) instead, then the latest IE8 update and a reboot should be enough. Moreover, as both Office 2003 and 2007 are now EoS, the latest IE8 update and a reboot may be enough for both MU and WU. See: <link> , <link> , <link> , and <link> . =================######================= THEN, after you've installed the initial truck-load of updates for POS since 2014, if you want to skip ahead and enable TLS 1.1 and 1.2 in your Internet Options - Advanced, go to this < LINK > and follow Heinoganda's instructions. And then you might UNcheck TLS 1.0. But please promise to come back here and slowly and carefully read every page of this thread and take notes because there'll be a test later and it's only 568 pages at this point. =================######================= 'Nuff said!

Hi Mcinwwl :), thanks for replying, I appreciate it. So only the first 6 files are needed to make WU work? And the rest are just vulnerability and incompatibility hotfixes? In that case it makes it easier to keep track of only these 6 files. Initially I thought all 15 files are needed to make it work, I didn’t read the whole topic I admit. I think the UpdateAgent-7.6 file is safe, I guess it is normal for it to show “Microsoft Update” instead of “Microsoft Corporation”. And a big thanks to dencorso, glnz and all the others who helped to make this possible.

Interesting. The link worked for me. I uploaded the file to my own website here. http://ximonite.com/ethernet/intel/w2k/PRO2Kv3.zip

You need to add a registry key, then they can be installed.

Well, since you asked me, here are my 2¢: KB2898785 *is superseded* by later updates. The important files there are browseui.dll & shdocvw.dll (both v. 6.0.2900.6740). KB3124275 IE6 *is not superseded* by later updates. The important files there are browseui.dll & shdocvw.dll (both v. 6.0.2900.6985), and the latter is the last shdocvw.dll ever released. As for browseui.dll, the last version ever released of it (v. 6.0.2900.7288) is in KB4025497, from 2017. The much older 2014 KB2962872-IE6 for x86 POSReady 2009 does, however, contain *non superseded* browsewm.dll v. 6.0.2900.6576, which is the last version of it ever released. It won't install on a system already having IE8 installed, but may be replaced by hand on a non-booted XP using, say, a linux-live CD to boot the machine, first in %windir%/system32/dllcache, then in %windir%/system32. Since those 3 files are not used by IE8 they're not updated by IE8 cumulative updates, but other XP SP3 modules do use them, so it's relatively easy not to have the last browsewm.dll & shdocvw.dll in one's installation, because the updates they are in require IE6 to install, and most users had already moved on to IE8 when they were released. HTH

1. You need to remove nothing, although patches 7 to 14 are not mandatory to make WU work. BTW I realised, that both my VMs installed in 2019 go away without KB2898785 - @dencorso, is this something included in KB3124275 IE6 Cumulative Update? also, I remember I've been starting with IE8, so that might also did the trick. 2. I do not know if NDP20SP2-KB2932079-x86.exe was included in later cumulative updates or not, but chances that you are really vulnerable for this are near zero in home reality. Install for sake of completeness if needed 3. Microsoft might have used different certificates, it's a beeeg corpo start from running heinoganda's cert updater and if installer will not throw prompt that certificate looks invalid, you are safe. If you're still worried, we might compare file checksums, or you might throw it to virustotal or jotti for scan. 4. Should work no matter if you install reg tweak first or the last, but personally I always updated registry as a late step (when all XP updates were installed, and I needed POSReady ones), so that's the only way I swear on 5. No, you can't, due to board rules and Microsoft redistributable license, but you might do a script that downloads them all from Microsoft catalog or, if worried it will die, from Wayback machine... Actually, I can do one myself

For all who are interested in an independent Update Root Certificates and revoked certificates, I want to offer a small downloader and updater (available now) without version confusion. Download Download 2 Archive Password: S4QH5TIefi7m9n1XLyTIZ3V5hSv4se1XB6jJZpH5TfB6vkJ8hfRxU7DWB2p Eliminates misspellings, change from "Continue updating?" to "Do you want to update certificates?" thanks @hmuellers update 10/05/2018 Version 1.6 Corrected several bugs, optimized the program, improved some features, an additional function implemented and download URL's updated. update 09/29/2018 Version 1.5 Corrected several bugs, optimized the program and improved some features. update 09/25/2018 Version 1.4 Various features implemented so that no obsolete sst files are installed. It is now possible to use additional download sources for existing download sources (up to 5), one another download source has already been added. Further information can be found in the file "Info Version 1.4.txt". update 06/29/2018 Version 1.3 Added feature, more information in "Info Version 1.3.txt" in the download. update 02/16/2016 Version 1.2 Due Country-specific formats of date display, partly the creation date of sst files was not correctly displayed. update 12/18/2015 Version 1.1 The creation date of the downloaded sst files appears.

I've later found out that there are even newer hal.dlls (v. 5.1.2600.5687), but just for multicore processors (and not needed unless one's machne has more than 8 logical processors). They're found in KB958244 and, as above, the KB article is gone, but the hotfix remains available by request from MS. Long live, XP!