Multibooter

OT: I made a preliminary, quick test under Win98. I test-installed under Win98 a slightly earlier version, Kaspersky Anti-Virus v6.0.3.837 Workstation (MP3, 25Feb2009), then attempted to update using this newly-found AutoPatch. It did not work v6.0.3 requires different folder names in the update folder. I also got the error message: "License verification failed" when I tried to update. Maybe v6.0.3 does not have a free 1st update, in contrast to My Ancient Version of Kaspersky, I don't remember. 10+ years ago I had a valid license, now expired long ago, so I didn't have the issue "License verification failed". Summary: it didn't work but maybe I will look into it again, much later.

I did find a site which had links to many downloads of AutoPatches: https://filemood.com/result?q=autopatches Unfortunately, there were no AutoPatches for my Ancient Version of Kaspersky and the download links are dead bittorrent magnet links. Kaspersky Lab has 30+ products with signature updates, with different versions etc, so the chance is exceedingly small that the relevant AutoPatches are still available anywhere in the internet. Maybe in archives of corporate users of Kaspersky of 10+ years ago, although I doubt that corporations archive old stuff that long. OT: When I looked into my own personal archive I have found an AutoPatch containing avp.exe v6.0.3.851 for the last version of Kaspersky Anti-Virus for Windows 98. klif.sys in this newly-found AutoPatch is digitally signed OK 1Apr2009. I had previously thought that Kaspersky Anti-Virus v6.0.3.844 (28Apr2008) was the last version for Windows 98, but this newly-found AutoPatch may update the last Win98-compatible build of Kaspersky Anti-Virus even further. This AutoPatch seems to be a major final update, it contains 27 files. What confuses the matter is that this newly-found AutoPatch was in a sub-folder \6.0.3.830\ with a lower version number than Kaspersky Anti-Virus v6.0.3.844 (28Apr2008) for Windows 98. Eventually I will have to check whether this newly-found AutoPatch can be installed under Win98 and whether the resulting ultimate final build for Win98 can be updated with current signatures.

Unapplicable legal snippets. msfn.org is an international forum, not a USA forum. My Ancient Version of Kaspersky is definitely not an unlawful program for me or for the great majority here at msfn.org. Why don't you wear a head scarf in your msfn.org picture, to obey Iranian Islamic Law, to avoid offending strict Moslems? Maybe you should tell your fellow Canadians to stop travelling to Cuba in winter, because U.S. laws declare tourism to Cuba as illegal. There are good laws and bad laws. Would you have obeyed in 1935, as a good Canadian, the German Nuremburg Laws https://en.wikipedia.org/wiki/Nuremberg_Laws and betrayed Jews to German concentration camps? Would you have obeyed in 1964, as a good Canadian, the United States Jim Crow laws https://en.wikipedia.org/wiki/Jim_Crow_laws ordaining racial segregation and racial discrimination? There is no need to commiserate here with the lack of freedom of U.S. subjects. This is an international technical forum. Hopefully, U.S. subjects will eventually get their freedom back. And no more unapplicable legal advice from a U.S. fifth column in Canada.

To avoid actions by Kaspersky blocking my occasional updates. The size of each update is about 800MB traffic and Kaspersky has to pay for the traffic. I assume that they are already in a difficult financial position because of the US embargo. If they survive I assume that My Ancient Version of Kaspersky will still get free, current signature updates in 2030.

The "AutoPatches" for My Ancient Version of Kaspersky I succeeded in updating both the application modules and the signatures of My Ancient Version of Kaspersky with a single combined update, without a license key and without activation. By installing the final AutoPatches, My Ancient Version of Kaspersky has been updated to the ultimate final version, with the most recent program file digitally signed OK 26May2014. The screenshot above indicates the final AutoPatch "r" next to "Application version" and the Database release date "2/4/2026". Once knowing how-to, preparing future combined updates will be quite easy. The term "AutoPatches" by Kaspersky corresponds roughly to the term "Hotfix" by Microsoft. The screenshot above indicates "Update completed successfully" and "Update application modules: Yes". The signature updates were from a Kaspersky Lab update server, the application updates ("AutoPatches") were from my personal archive. Signature updates and application updates ("AutoPatches") were combined into a single update folder. The screenshot above indicates signatures of 2/4/2026 and the message: "Database status: Reboot is required". This message "Database status: Reboot is required" is displayed by My Ancient Version of Kaspersky when the update of the application modules via AutoPatches is pending. A tiny red square is added to the Kaspersky icon in the System Tray, indicating that AutoPatches are pending. During the reboot after the update, the Kaspersky driver updates and installs the program files contained in the AutoPatches and updates the registry, completely hidden and invisible to the user. StartUp Organizer, for example, which I use as a watch dog, does NOT notice any changes before, during and after the reboot. After rebooting and AutoPatching, the Kaspersky icon in the System Tray looks normal again, without a tiny red square. The successful installation of the AutoPatches is indicated in the About screen above by the display of "r" [=version of the AutoPatches] next to the Version (Note: the About screen is displayed by right-clicking on the Kaspersky icon in the System Tray -> About) and in the Support window (1st screenshot, at the top of this posting). Also, LastSuccessfulUpdate in the registry contains a hex value (Unix timestamp), which confirms that the update was successful. Furthermore, virus-checking with the updated application module and the new signatures works fine. The installation of the final AutoPatches plus a signature update of My Ancient Version of Kaspersky had faced three challenges: 1) The files of the final AutoPatches were removed from the Kaspersky Lab update servers and are most likely not available anywhere in the internet. 2) Kaspersky Lab does not provide license keys for My Ancient Version of Kaspersky anymore, which would permit multiple updates. My Ancient Version of Kaspersky is an unexpiring trial version and can only be updated once. An initial update with the final AutoPatches followed by a second update with current signatures is therefore not possible. Only one update is possible, either an update of the signatures from the Kaspersky Lab server or an update of the application module from my personal archive, but not both.. 3) The digital signature of the .xml file in the subfolder \index\ in the update folder impedes the combining of AutoPatches and current signatures into a single update folder. Before August 2019 the online updates from Kaspersky Lab of My Ancient Version of Kaspersky had consisted of three sub-folders: \AutoPatches\, \bases\ and \index\. After August 2019 no sub-folder \AutoPatches\ is created when downloading updates. The sub-folder \AutoPatches\ contained updates of the installed application modules, \bases\ contained the signature updates and \index\ contained only a .xml file validating \AutoPatches\ and \bases\. The .xml file in \index\ contains at the end a string which is an encoded digital signature generated using the private signing key of Kaspersky Lab. Changing text in the .xml file without updating the signature at the bottom will result in the error message "Invalid file signature" when trying to update. The final release of December 2012 of My Ancient Version of Kaspersky had been updated by several sets of "AutoPatches" supported by Kaspersky until 2017, identified by a letter of the alphabet appended to the build number of Kaspersky Anti-Virus. The last AutoPatch for My Ancient Version of Kaspersky is "r" and contains for example an updated basegui.dll, digitally signed OK 26May2014. The AutoPatches for My Ancient Version of Kaspersky were available from the Kaspersky Lab update servers until about 2018. When I tried to update in August 2019, all files of the AutoPatches for My Ancient Version of Kaspersky had been removed from the Kaspersky Lab update servers and My Ancient Version of Kaspersky could not be updated to release "r" (about 26May2014) anymore. The application modules of My Ancient Version of Kaspersky consequently remained those of the final release of December 2012, without any AutoPatches applied.. In addition Kaspersky Lab removed the text string which identified My Ancient Version of Kaspersky, from the digitally signed .xml file in \index\ downloaded from Kaspersky. Kaspersky Lab must have decided by August 2019 to definitely stop supporting My Ancient Version of Kaspersky, because they removed the application update files from their update servers and made it generally impossible to update the program with AutoPatches by removing the string permitting updates of My Ancient Version of Kaspersky from the digitally signed .xml in \index\. The final AutoPatches, including "r", probably also improve the Protection Components of My Ancient Version of Kaspersky. I have used My Ancient Version of Kaspersky only as an on-demand scanner, I have no need for the Protection Components. Nevertheless, I may eventually add the Protection Components to the installation, for further testing and to see whether activation is required to get the Protection Components to work. According to the User Guide of My Ancient Version of Kaspersky, if you select "Activate later" after installation, "you will have access to all the application's features, except for updates (only one application update will be available)".

in my next attempt to activate Panda under WinXP I have used a genuine gmail email address. After entering the email address in window "Activate Panda Dome", Panda Dome again displayed "Error checking the account. We're sorry but we were unable to access your Panda account. Make sure you have an Internet connection and try again."

Which programs did you revive by updating their OpenSSL components? Do you still use them under WinXP?

MS Visual C++ 2015-2019 Redistributable v14.27.29114 (WinXP, 26Oct2020) can be downloaded from: https://download.visualstudio.microsoft.com/download/pr/c168313d-1754-40d4-8928-18632c2e2a71/D305BAA965C9CD1B44EBCD53635EE9ECC6D85B54210E2764C8836F4E9DEFA345/VC_redist.x86.exe was listed together with many other download links at: https://forum.ru-board.com/topic.cgi?forum=5&topic=24691&start=320 MS Visual C++ 2015-2019 Redistributable v14.28.29213 (WinXP, 13Aug2020) can be downloaded from: http://download.visualstudio.microsoft.com/download/pr/566435ac-4e1c-434b-b93f-aecc71e8cffc/0D59EC7FDBF05DE813736BF875CEA5C894FFF4769F60E32E87BD48406BBF0A3A/VC_redist.x86.exe was listed together with many good comments at: https://www.vogons.org/viewtopic.php?t=84578&start=80 MS Visual C++ 2015-2019 Redistributable v14.29.30139 (WinXP, 10Dec2021) can be downloaded from: http://download.visualstudio.microsoft.com/download/pr/b929b7fe-5c89-4553-9abe-6324631dcc3a/4C6C420CF4CBF2C9C9ED476E96580AE92A97B2822C21329A2E49E8439AC5AD30/VC_redist.x86.exe emberedison in his posting on 1Dec2025 warns against v14.29.30139, "14.28.29213.0 is work", https://community.pcgamingwiki.com/files/file/2883-microsoft-visual-c-redist-2015-2019-for-windows-xp/ Unfortunately, builds 14.27.29114 and 14.28.29213 do NOT install under WinXP on my SSE-only Inspiron 7500 (Pentium III), they seem to require SSE2. The excellent "MS Visual C++ Runtime Packs 2005-2015 (Kurt_Aust, RyanVM)", however, contains vcredist2015_x86.exe v14.0.24215.1 which installs OK on my Inspiron 7500 with SSE-only. OpenSSL v3.6.0 (32bit, Light, 8Oct2025), in turn, installs OK under WinXP on my SSE-only Pentium III laptop after having installed vcredist2015_x86.exe v14.0.24215.1 from Kurt Aust. "MS Visual C++ Runtime Packs 2005-2015 (Kurt_Aust, RyanVM)" can be downloaded from https://www.mediafire.com/file/03xebkxhpvlpep8/Visual_C_redist_32-bit_05_08_10_12_13_15.7z/file BIG QUESTION: Is there any benefit for a non-programmer to install OpenSSL under WinXP?

Besides speed, system stability could be another criteria for deciding between fltmgr.sys build 5107 and build 6912 under WinXP. eMule could be used for comparing system stability/uptime when running with fltmgr.sys build 2180 [WinXP SP2] vs build 5107 vs build 6912. eMule, installed under WinXP SP2 and running 24/7 on a dedicated old Inspiron laptop (500MHz, SSE-only, 512MB RAM), tends to crash with the original fltmgr.sys build 2180 after downloading for 7-14 days. Build 5107 has been installed to see whether it can increase eMule uptime, i.e. system stability.

We finally agree on something!

https://www.virustotal.com/gui/file/767b877e735c425bf05c34683356abfde4070b092f17a4741ea5ac490611f3de https://www.virustotal.com/gui/file/9f805311953057a944567d9a2e45ee4d65ffb7804925115b3b05bf02d3ff7821

Thanks, AstroSkipper. But pw-protected "ProxHTTPSProxy_TLS_1_3_1_5_220717_PopMenu_3V3_CheckedByAstroSkipper.7z", containing your software package, has still the same issue (false positives by Kaspersky) which I posted on 14Jan2025, https://msfn.org/board/topic/183352-proxhttpsproxy-and-httpsproxy-in-windows-xp-for-future-use/page/61/ cacert_updater.exe and cmdow.exe inside your package still get flagged as Trojan and riskware by Kaspersky. mediafire: "This file was uploaded from Germany on January 14, 2025 at 9:50 AM" I surely want to believe that your package is clean. Maybe you can make these two files look clean or replace them, not just password-protect them? Many good little files have disappeared into oblivion because they were flagged.

Owned 100% by a U.S. company with U.S. government contracts? On the other side of the globe: Eugene Kaspersky's background? Searching with the Yandex search engine for: Kaspersky Putin lists interesting articles, for example the 2012 article https://www.brookings.edu/articles/russias-top-cyber-sleuth-foils-us-spies-helps-kremlin-pals/

That looks too tricky to me, at least for testing Panda. Do you have simple instructions for installing the TLS stuff under WinXP? In contrast, updating the various versions and editions of My ancient version of Kaspersky in one swoop is quite simple. I just use a little corporate utility, Kaspersky Updater, to create/update a single update distribution folder from which 30+ Kaspersky programs can be updated off-line. Below is a screenshot of this little corporate utility, which I used for updating 3 different Kaspersky programs, the normal workstation edition, the specced-down workstation edition and the server edition. This screenshot shows the signature update of 10Dec2025 for my posting "My ancient version of Kaspersky under Windows 10" of 15Dec2025. https://msfn.org/board/topic/184730-antimalware-firewall-and-other-security-programs-for-windows-xp-working-in-2023-and-hopefully-beyond/page/82/#comments The message "... Retranslation successful" means that the update was successful and that the update distribution folder was filled OK. No idea what the part "and update is not requested" refers to. Kaspersky Updater here was run under Windows Server 2003 (blue window title) and updating under WinXP and Win10 from the update distribution folder worked OK. No need to register with an email address and to fiddle around with TLS stuff under WinXP.

Using different emails does NOT protect your privacy. United States spy agencies identify people by name, email address(es), phone numbers, IP numbers assigned etc. OT: the header of a Jeffrey Eppstein FBI file recently released indicates also the IP number as a personal identification trait, together with the date of birth. https://web.archive.org/web/20251227130144/https://www.miamiherald.com/public/latest-news/2wwvfa/picture313924496/alternates/FREE_1140/Screenshot 2025-12-23 115102.png In many countries the router IP number assigned by Internet providers is nearly impossible to change. You can pull the power plug of the router and reconnect it, but still the same router IP number.