Leaderboard

Additionally, and predictably, if you set Supermium to use New Moon's default User Agent, then Supermium is sent the tracking link version of the search results. Again, all server-side. The browsers are rendering what they are sent by the server.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260131-3219d2d-uxp-6ee9e34e29-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260131-3219d2d-uxp-6ee9e34e29-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260131-3219d2d-uxp-6ee9e34e29-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260131-d849524bd-uxp-6ee9e34e29-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260131-d849524bd-uxp-6ee9e34e29-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #2914 - Explicitly allow mixed content websockets on localhost. (151ef21890) - Issue #2828 - Follow-up: Simplify rule node tracking and ensure rule walker state isn't reset for the first child processor (226a443c96) - Issue #2916 - Restore the ability to set a default log level when using MOZ_LOG (a8960dc462) - Issue #2889 - Follow-up: Update eventPtr/eventEndPtr for XML_ParseBuffer (4b983c32b0) - Issue #2889 - Follow-up: Add patch for XML_ParseBuffer. (e5497c8425) - Issue #2895 - Implement 32-bit compatible Xoroshiro128++ (0dbad452e6) - MoonchildProductions/UXP#2351 - Fix webrtc video encoding on macos (3224ec7ddd) - MoonchildProductions/UXP#2351 - Fix webrtc for Windows and Linux based on MacOS fix (1d03a05e54) - Whitespace Compatibility for ICU 72+ (20525d238b) - Issue #2403 - Implement SubmitEvent functionality (#2919) (9b3d172a95) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - import from mozilla: Bug 2010411 - CLDR 48 'h' hour format is possibly web incompatible (3b9a3ec8e0) - Revert "Issue #2895 - Replace XorShift128+ with Xoroshiro128++" (75ca0c37f8) - Revert "Revert "Issue #2895 - Replace XorShift128+ with Xoroshiro128++"" (952e3022b8) - js-random: reorder Xoroshiro128++ code flow to reduce intermediate registers (454565b2ac) Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260117-3219d2d-uxp-aace8fa8c0-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260117-3219d2d-uxp-aace8fa8c0-xpmod.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/custom IA32 Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260117-3219d2d-uxp-aace8fa8c0-xpmod-ia32.7z source code that is comparable to my current working tree is available here: https://github.com/roytam1/UXP/commits/ia32 NM28XP build: Win32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260117-d849524bd-uxp-aace8fa8c0-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260117-d849524bd-uxp-aace8fa8c0-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260117-d849524bd-uxp-aace8fa8c0-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260117-d849524bd-uxp-aace8fa8c0-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260117-d849524bd-uxp-aace8fa8c0-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #1636 - Part 1 - Decouple Gio from GConf and always build it with GTK (fc78eec911) - Issue #1636 - Part 2 - Disable Gconf by default (990f256885) - Issue #1636 - Part 3 - Remove Gconf (b04e3d93c9) - Issue #2895 - Part 1: Replace XorShift128+ with Xoroshiro128++ (d4341ea07a) - Issue #2895 - Part 1b: Update license block. (d23afa84e5) - Issue #2895 - Part 2: Remove incorrect debug asserts. (5a0f190104) - Issue #2895 - Part 3: Add manual test. (75ec48bc41) - Issue #2889 - Part 0: Relocate Mozilla-specific files from Expat source. (b81b97ee47) - Issue #2889 - Part 1: Prepare Mozilla's changes and extensions for Expat 2.6.4. (9567601675) - Issue #2889 - Part 2: Import Expat 2.6.4 source. (9ade98b4fc) - Issue #2889 - Part 3: Apply Mozilla's patches to Expat 2.6.4. (0b9e221b14) - Issue #2889 - Part 4: Fix build and runtime issues. (a2f8e66162) - Issue #2889 - Follow-up: Avoid conflicts with system version of libexpat (e0f8acddc7) - Issue #2889 - Follow-up: void methods shouldn't return a value. (8956c61187) - Issue #2889 - Part 5: Rewrite patches for Expat 2.7.3. (a730f838c8) - Issue #2889 - Part 6: Import Expat 2.7.3 source. (d2acec73f7) - Issue #2889 - Part 7: Apply patches to Expat 2.7.3. (ca2ef5184a) - Issue #2889 - Follow-up: Allow generate_hash_secret_salt to be used. (acefed74fe) - Issue #2889 - Follow-up: Adjust Expat 2.7.3 local patches for removal of 3rd patch. (034eeaff97) - Issue #2889 - Follow-up: Remove fix for BZ 569229. (493169e227) - Issue #2895 - Follow-up: Fix JIT code generator for 32-bit targets. (d6e9c4d85b) - [gfx] Be more explicit when converting to cairo formats. (f6d18c7d78) - [gfx] Use better types for cairo image surface manipulations. (6ca8cf782b) - [DOM] Check worker script size (d8f7202951) - [Auth] Only set GSS_C_DELEG_FLAG flag when we confirm server supports delegation. (5321363a1b) - [NSS] Update NSS (464b24c608) - [XPCOM] Add hashkey helper classes for future use. (7b9eda3f69) - [gfx] Add some additional sanity checks to cairo surface creation. (3aff60e443) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. My changes picked since my last build: - application: remove gio from MOZ_EXTENSIONS_DEFAULT (69c17afbe0) - htmlparser: break when infinite loop happens (8201dadf41) Update Notice: - You may delete file named icudt*.dat and icu63.dll inside program folder when updating from old releases. * Notice: From now on, UXP rev will point to `custom` branch of my UXP repo instead of MCP UXP repo, while "official UXP changes" shows only `tracking` branch changes.

All revisions (ALPHA/I386/MIPS/PPC) of Windows NT 4.0 and Windows NT 3.51 has issue with maximum possible total video mode count limit and it is around 296 modes. Any mode provided by driver above 296 will be cutted down. It is not depended on driver issue, this bug is inside Windows NT system itself. Windows 2000 and later does not have such issue. Here it is a binary patch for Windows NT 4.0 (I386, any SP/edition, language) for SYSTEM32\WIN32K.SYS : Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0x6A to 0x68 0xB8 0x00 0xFF 0x03 0x00 0x6A Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0xFF to 0x68 0xB8 0x00 0xFF 0x03 0x00 0xFF Recalculate checksum, f.e. EDITBIN.EXE WIN32K.SYS /RELEASE Here it is a binary patch for Windows NT 3.51 (I386, any SP/edition, language) for SYSTEM32\WINSRV.DLL : Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0xA1 to 0x68 0xB8 0x00 0xFF 0x03 0x00 0xA1 Change 0x68 0xB8 0x00 0xFF 0x00 0x00 0xFF to 0x68 0xB8 0x00 0xFF 0x03 0x00 0xFF Recalculate checksum, f.e. EDITBIN.EXE WINSRV.DLL /RELEASE This will increase total limit to 1190 modes. Below are results in screenshots, before and after.

This thread is technically about Supermium (which is not being sent tracking links BY THE SERVER), your question is more about New Moon (which is being sent tracking links BY THE SERVER). Again, this is all SERVER-SIDE. The browser doing the rendering is rendering exactly what is being sent to that browser BY THE SERVER. And New Moon is being SINGLED OUT. Chrome/Chromium/Supermium/Catsxp/r3dfox - all of these are not being sent tracking links BY THE SERVER. It's all in the USER AGENT (in this case). New Moon without a useragent override (note: you have to hover over a search result link to see the tracking URL, it is not always shown in the address bar): New Moon with a useragent override:

upstream #2895 is fixed with a big help from Mr.Q and better javascript random() will be available on both 32 and 64 bit build later.

And if anyone thinks that there is hardly anything worse to report about SUPERAntiSpyware, I have to disappoint them. We now come to the "official support" for SUPERAntiSpyware, which has since been taken over by the American company USTechSupport. If you want to fill out the online form on the SUPERAntiSpyware homepage, you are required to provide a telephone number. Rejected! An email to support is answered immediately, but of course by a bot. You can write whatever you want, but you won't get any help. Just a recommendation that it's best to use the telephone support. And for this information, the support ticket is then marked as resolved. I've never seen such rubbish. The hotline is probably chargeable. It all smells like a rip-off. That wasn't the case when I contacted SUPERAntiSpyware support the last time years ago before it was acquired by RealDefense LLC in 2023 which is also an American company. But when it comes to America, nothing surprises me anymore.

SUPERAntiSpyware stopped Windows XP support with the version 10.0.0.1254 which was the last working installer version. Until the end of last year, it was still possible to update to version 10.0.0.1266 via automatic updates. Since the beginning of the year, this is no longer possible. Users are constantly being nagged to perform a programme update under Windows XP SP3 32-bit that renders the entire installation unusable after application. This is because it updates to the 64-bit version 10.0.0.1282. The old files are of course overwritten, and anyone who has not created a backup beforehand is lost. Luckily, after hours of searching, I found a Norton Ghost image of my other XP partition with the last changed files when SUPERAntiSpyware was updated to the version 10.0.0.1266. That's why I was able to manually restore the destroyed installaton. Furthermore, the size of the virus definition file that is downloaded has increased significantly. As before, it takes forever to load. The only good thing is that the definitions are still being updated at all. So, nothing is fine. You don't need one. I've had a lifetime licence for the Professional version since 2013. It used to be worth something when Windows XP was still supported. Those days are finally over.

I use Panda 22.03.01 and on a dual or quad core systems PSANHost upon boot up doesn't really waste any cycles, only swells to ~100MB and then goes down to ~15MB from what I observed in TaskManager. It's been a wonderful replacement for Avast and/or AVG and their treachery of the XP systems after all this data we've shared with them throughout the years.

that had to be said. And yes, you were absolutely right. At least, Adlice's support has replied quite quickly. In contrast to that I haven't heard from Panda's support for weeks. Seems to be non-existent.

First of all, thanks for uploading the files! I was surprised to learn that there is supposed to be a .NET Framework version 4.0.30320 for Windows XP. I couldn't find anything about it in any official source. In any case, your installer "Microsoft .NET 4.0.30320 Full" is the same one I have, and it has the number 4.0.30319.1. Presumably, at least for Windows XP, there is no version 4.0.30320. You can find out your current version installed with the following command: reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version The MS Visual C++ 2010 SP1 (10.0.40219.473) installer is indeed the last one you can still get from Microsoft or from abbodi1406. I will try later. In any case, thanks again!

Here you go, enjoy! Installers.zip

I agree as a general off-topic observation that while you do, of course, need to have a general awareness of security and privacy issues when working online, there's really no need to be paranoid about it.

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.

@genieautravail The ungoogled version has the flags #disable-encryption and #disable-machine-id. Enabling them will disable encryption and machine ID creation, allowing you to transfer your profile to another computer. The developer will not transfer them to the regular version, leaving the functionality completely stock. Therefore, for the regular version, use third-party tools to create a portable version.

Well... That's the latest official 'xidel-0.9.9.20230616.8842.e14a96920e01.openssl.win32.zip' on https://sourceforge.net/projects/videlibri/files/Xidel/Xidel development/. Or 'xidel-0.9.9_2025-02-22-git-3e7e88a62307-openssl-win32.7z' on https://rwijnsma.home.xs4all.nl/files/xidel/personal_builds/, which I compiled myself. On Linux Xidel by default requires OpenSSL to open https urls at all. On Windows the normal win32/win64 binary relies on Microsoft's SChannel SSP (Secure Channel Security Service Provider) to do that. On Windows XP SChannel is limited to TLS 1.1, while practically all websites nowadays use TLS 1.2 and newer. So Benito, Xidel's author, created the openssl-win32 build especially for WinXP users. Xidel supports all OpenSSL versions. If you'd like to know what Xidel can do, I suggest you have a look at StackOverflow here or here. Obviously every piece of software that requires the OpenSSL dlls for internet connectivity can use these.

Of course it is! They are different sessions, different cookies. I'm failing to understand the obsession. I'm done here, I really do not need the obsession.

But I feel like the TIME that was spent to demonstrate this PROOF is time WASTED. Because my name doesn't begin with a "D" so answers, despite 100% accurate and true, will never be "liked". Yeah, that was a rib-jab.

Only the official quickjs (32-bit) release natively supports Windows XP SP3 x86: https://bellard.org/quickjs/ https://bellard.org/quickjs/binary_releases/?C=M;O=D https://bellard.org/quickjs/binary_releases/quickjs-win-i686-2025-09-13.zip This fact has been stated earlier in this thread (but am lazy now to find the relevant post). ... And, if you're prepared to use "hacked-binaries" (binaries HexEdited to redirect XP-incompatible kernel functions to OCA/Wine/ReactOS DLLs, then there's this : (the "appeal" of NodeJS vs quickjs is that the former is many times quicker (pun intended) compared to the latter ...)

You can read all about it in the Wiki. Deno can't be used on Windows 7. Node can be used if you use this fork. Take node-v20.19.2-win-x64.zip. extract to e.g. C:\Bin\Node and add that folder to your PATH. Can also be done via CMD as administrator: setx /m PATH "%PATH%;C:\Bin\Node" QuickJS can also be used, but it's rather slow (put qjs.exe and libwinpthread-1.dll next to yt-dlp.exe). Then add to your config file: --js-runtimes quickjs Or: --js-runtimes node

My releases have just been updated.

FFmpeg update. XP: shared static libfdk-aac VISTAx86: shared static libfdk-aac

It used to be (intentionally) broken to burden (very high CPU usage) the csrss.exe service (as seen in Task Mgr). I've installed Avast (from v18 online installer) in my testing XP_VM and will tell you tomorrow. Today everything was calm. Avast and AVG in their new, broken, state begin to burden the system through csrss.exe the next day... EDIT: The results are in and nothing changed: AvastSvc.exe constantly eats up ~25% of (dual-core configured) CPU in VM and csrss.exe eats up the other 20% of (dual-core configured) CPU. So both take up almost 1 whole core! That is outrageous, but Avast got our data, they don't care.

https://drive.proton.me/urls/B1XVQ0VJZ0#UkqYiyCUKuF2

I also tested again the real-time protection module of SUPERAntiSpyware. The CPU usage on my old computer is high and completely unacceptable. Therefore, a Professional licence is not worthwhile at all on low-performance computers.

When I set up my Win 7 notebook two years ago I had wanted to use TinyWall as a firewall ... it was listed as a simple firewall that worked. However, it was listed for only Windows 11 / 10 so I went with an older version of ZoneAlarm that worked with Win 7. It works good as just a firewall, no complaints. Just two days ago I discovered that there was an older TinyWall version that did work with Win 7. https://tinywall.pados.hu/ TinyWall is a lightweight, user-friendly, and secure firewall for Windows. It is also completely free. Under FAQ: The latest version of TinyWall runs on Intel- or AMD-based Windows 11 / 10. An older version, TinyWall 3.2.5, also supports Windows 8.1 / 8 / 7. Just asking if anyone is using TinyWall 3.2.5 on their Win 7 setup and if you have any comments, good or bad? Thanks ...

Today, I have uninstalled Panda Free Antivirus 21.01.00 and installed Panda once again but via their online installer. The version installed by their online installer is 22.03.05. The online installer downloads the legacy installer FREEAV_LGC.exe (117MB) and not the common FREEAV.exe (161MB) under Windows XP. Unfortunately, the version 22.03.05 needs much longer for starting when booting Windows XP. It is round about 5 to 6 minutes on my old machine. The culprit is the process PSANHost.exe which places very high demands on the CPU, up to 99%. The previously installed version 21.01.00 only needed 2 minutes. I'll keep the currently installed version a while just for testing purpose but I think I'll go then back to version 21.01.00. The next days, I'll use to see how this version behaves in my system doing all the things I usually do.

reverting changes in #2895 seems help. now 32bit builds are being compiled and same filename archives will be replaced later. EDIT: all today's 32bit build archives are updated.

The background images are all JPG files and already locally stored while installation.

At the beginning of my Odyssey, I investigated all folders and registry keys belonging to Panda Dome. Therefore, I also found the location of these background images. Additionally, I analyzed the registry accesses of Panda Dome, in particular with regard to the background images. But I have not yet identified the core of the problem. Unfortunately, it is in my nature to solve problems. The pictures are totally unimportant, but I still have to solve the problem. Especially if it works in my other partition. But in any case, thanks for your efforts!

Revo Uninstaller 2.4.5 is the last free version for Windows XP which is offered as an installer and a portable release. You can get it here: https://www.revouninstaller.com/version-history/. Revo Uninstaller Pro 3.2.1 (installer/portable) is the last paid version for Windows XP. It's a very important tool to get rid of remnants regarding antivirus/antimalware programmes.

I got a reply from Adlice to the supprt ticket I filed in terms of RogueKiller: So what was posted here has been confirmed. RogueKiller's real-time protection was never designed for older operating systems such as Windows XP. But at least we have a scanner that still runs on Windows XP in the latest version.

Fair enough, as long as the conversation is kept directly relevant to the use of Panda Dome on XP, or indeed any other AV program. Sorry, I have now realised that the details of the .NET 4 updates on Revo Uninstaller are not with the actual installation records, as they are called 'Security Update for....' so appear in a different place in the list! Here they all are, enjoy! The last two images have duplicated entries. Why they all seem to have the same installation date i'm not sure, I don't remember doing an OS reinstallation in February 2019!

In my main article about Panda Dome, I posted download links to get the most recent installer. Even a link to a legacy installer.

@nicolaasjan I have attempted to make compatible 64-bit OpenSSL shared libraries using MSYS2. If you would like to test them.

Per abbodi1406, https://github.com/abbodi1406/vcredist#windows-xp-notice Direct link: https://download.visualstudio.microsoft.com/download/pr/566435ac-4e1c-434b-b93f-aecc71e8cffc/0D59EC7FDBF05DE813736BF875CEA5C894FFF4769F60E32E87BD48406BBF0A3A/VC_redist.x86.exe MDL forums reference: https://forums.mydigitallife.net/threads/repack-visual-c-redistributable-runtimes-2020-11-10.76588/page-27#post-1630817 I can confirm that the installer is dual-signed (both SHA1+SHA256), thus it can be verified on XP SP3 (which ONLY supports SHA1 file signatures). As for the installer of version 14.29.30139.0 referenced in the "community.pcgamingwiki.com" site, this has the direct link below (courtesy of abbodi1406): https://download.visualstudio.microsoft.com/download/pr/b929b7fe-5c89-4553-9abe-6324631dcc3a/4C6C420CF4CBF2C9C9ED476E96580AE92A97B2822C21329A2E49E8439AC5AD30/VC_redist.x86.exe but it is only SHA256-signed, so I'm not sure if its signature can be verified under XP SP3 : Just my 2c ...

Just running the proxy in the background doesn't mean it is also used by a programme. What I meant is whether you're running ProxHTTPSProxy system-wide or not. In any case, Panda Dome has to use the proxy. Thats why I had to configure Panda Dome to use it, however, for activation only.

I have already provided a solution to activate Panda Dome under Windows XP. Read this post: and this one:

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)".

@VistaLover I have uploaded an updated Vista+ compatible PyInstaller here. Could you test if the yt-dlp built with it works well on your Vista system?

sorry for using that phrasing i wasnt sure how to phrase it just was curious is all

So I was hoping to get a pic of my 95 *upgrade* cd (would be very FIRST version sold at college campus bookstore, there were "A", "B", and "C" releases of 95). I have three prime-suspect locations to search in my "small hoard", but I could not find it Online reading seems to label releases as RTM, Plus, SP1, OSR1, OSR2, OSR2.1, OSR2.5, but I simply *do not remember* them being called that when being sold at the college bookstore, I remember them being called 95a, 95b, and 95c and I know mine would have been the VERY FIRST and that it was an "upgrade" and does *NOT* have the "for sale only with new pc" on its label. Online reading also seem to suggest that the difference between "retail" and "oem" is whether it *includes* Internet Explorer and/or which *version* it includes. From memory, I guess I do not remember it rolling out that way. Here in the USA, the largest (be it "good" or "bad" is a discussion for another day) consumer market, we-in-the-US think of the word "retail" as a distinction of WHO can BUY the item. *Supply Chains* are broken down into classifications like "Tier 1", "Tier 2", and "Tier 3". In the vane of an *OEM* (Microsoft) building/creating Win95 and SELLING it, if Acer, IBM, NEC, HP, Dell, Packard Bell, Texas Instrument, and the like could BUY them to INCLUDE in their manufactured-then-sold computers, that is not (at least here in the US) considered as *RETAIL*. If Amazon, Best Buy, Radio Shack, Tiger Direct, Costco, Walmart *retail stores* were allowed to BUY them and turn around and sell to people like you and me, THAT is considered a *RETAIL* item. I guess I see things that way. But maybe the rest of the world doesn't?

Many thanks, indeed ; but the naysayers/doubters are again back at it, one of them even went as far as to downvote your comment; I posted one last "analysis" there, but, frankly, I'm totally disheartened by all those "experts of today", who leave no room for old-school volunteers like myself ... Well then, I, you, Reino (and possibly others) know that the IOS HLS formats do still work, let the masses on GH's issue tracker stick to their reservations ...

It seems so. I've never had a scenario like this before. But one thing is clear. Panda must have used the proxy connection. No chance without it.

I can't confirm this statement. When I installed Panda Dome 21.01.00, I was only able to activate the Panda account with the help of ProxHTTPSProxy, using the necessary proxy settings in Panda. Connections to Panda's servers were immediately visible in the proxy console.

As a general rule of thumb, I historically REFUSE to download "trusted" content from http, especially "security" software! The version.ini does report v23. I will install into an XP *VM* later this morning. Several extracted-retain-timestamp files are dated from only FIVE DAYS ago.

Are you running ProxHTTPSProxy in the background by default? And if so, in which mode? I had to configure Panda Dome to use the proxy. Which version is your Panda Dome Essential of?

First of all, thanks for uploading the files! I was surprised to learn that there is supposed to be a .NET Framework version 4.0.30320 for Windows XP. I couldn't find anything about it in any official source. In any case, your installer "Microsoft .NET 4.0.30320 Full" is the same one I have, and it has the number 4.0.30319.1. Presumably, at least for Windows XP, there is no version 4.0.30320. You can find out your current version installed with the following command: reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version Although it is actually Microsoft .NET Framework 4.0.30319, I have nevertheless found a reference to version 4.0.30320 in Windows XP. Apparently, the Client Profile and the Extended are assigned exactly this version number:

Hi to all, I have updated the content of my article in first post. Due to the fact that some of you had problems when running ProxHTTPSProxy or HTTPSProxy in older systems I have examined the correlation of crashes with the SSE2 capability of a CPU. The current results can be found in sections Prerequisites and Versions. Furthermore both versions of Root Certificate Updater have been updated and are now of 02/24/2022. Regards, AstroSkipper

Alright, here is the Windows Update Log from my flawlessly MU accessing system: https://www.mediafire.com/file/iflfdi6ncoceop8/Windows_Update_2022_-_AstroSkipper.7z/file @Dave-H Comparing my log file to yours you can see what entries you have to have access MU successfully: 2022-01-27 11:49:29:484 1128 b48 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) =========== 2022-01-27 11:49:29:625 1128 b48 Misc = Process: C:\WINDOWS\System32\svchost.exe 2022-01-27 11:49:29:625 1128 b48 Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2022-01-27 11:49:29:484 1128 b48 Service ************* 2022-01-27 11:49:29:625 1128 b48 Service ** START ** Service: Service startup 2022-01-27 11:49:29:625 1128 b48 Service ********* 2022-01-27 11:49:30:812 1128 b48 Agent * WU client version 7.6.7600.256 2022-01-27 11:49:30:812 1128 b48 Agent * Base directory: C:\WINDOWS\SoftwareDistribution 2022-01-27 11:49:30:843 1128 b48 Agent * Access type: No proxy 2022-01-27 11:49:30:875 1128 b48 Agent * Network state: Connected 2022-01-27 11:50:21:546 1128 b48 Agent *********** Agent: Initializing Windows Update Agent *********** 2022-01-27 11:50:21:546 1128 b48 Agent *********** Agent: Initializing global settings cache *********** 2022-01-27 11:50:21:546 1128 b48 Agent * WSUS server: <NULL> 2022-01-27 11:50:21:546 1128 b48 Agent * WSUS status server: <NULL> 2022-01-27 11:50:21:562 1128 b48 Agent * Target group: (Unassigned Computers) 2022-01-27 11:50:21:562 1128 b48 Agent * Windows Update access disabled: No 2022-01-27 11:50:21:562 1128 b48 DnldMgr Download manager restoring 0 downloads 2022-01-27 11:50:21:593 1128 b48 AU ########### AU: Initializing Automatic Updates ########### 2022-01-27 11:50:21:593 1128 b48 AU AU setting next sqm report timeout to 2022-01-27 10:50:21 2022-01-27 11:50:21:609 1128 b48 AU # AU disabled through User preference 2022-01-27 11:50:21:609 1128 b48 AU Initializing featured updates 2022-01-27 11:50:21:625 1128 b48 AU Found 0 cached featured updates 2022-01-27 11:50:21:625 1128 b48 AU AU finished delayed initialization 2022-01-27 11:50:22:890 1128 b48 Report *********** Report: Initializing static reporting data *********** 2022-01-27 11:50:22:890 1128 b48 Report * OS Version = 5.1.2600.3.0.65792 2022-01-27 11:50:23:078 1128 b48 Report * Computer Brand = MICRO-STAR INTERNATIONAL CO., LTD 2022-01-27 11:50:23:093 1128 b48 Report * Computer Model = AWRDACPI 2022-01-27 11:50:23:109 1128 b48 Report * Bios Revision = 6.00 PG 2022-01-27 11:50:23:109 1128 b48 Report * Bios Name = Award Modular BIOS v6.00PG 2022-01-27 11:50:23:109 1128 b48 Report * Bios Release Date = 2002-10-24T00:00:00 2022-01-27 11:50:23:109 1128 b48 Report * Locale ID = 1031 2022-01-27 12:50:23:968 1128 b48 AU AU received policy change subscription event 2022-01-27 12:50:33:703 1128 b48 AU AU received policy change subscription event There are no "warnings" related to wuident.cab as show in your log file: 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: DownloadFileInternal failed for https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab: error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup FATAL: IsUpdateRequired failed with error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80072EFE 2022-01-27 12:29:26:261 1860 1504 Agent * WARNING: Skipping scan, self-update check returned 0x80072EFE 2022-01-27 12:29:26:339 1860 1504 Agent * WARNING: Exit code = 0x80072EFE 2022-01-27 12:29:26:339 1860 1504 Agent ********* 2022-01-27 12:29:26:339 1860 1504 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2022-01-27 12:29:26:339 1860 1504 Agent ************* 2022-01-27 12:29:26:339 1860 1504 Agent WARNING: WU client failed Searching for update with error 0x80072efe So my first quick conclusion is you have to reset your Windows Update client and install two versions one after another (the order is important). At first WindowsUpdateAgent30-x86.exe and then WindowsUpdateAgent-7.6-x86.exe using the option /WUforce e.g. WindowsUpdateAgent30-x86 /WUforce and WindowsUpdateAgent-7.6-x86 /WUforce. For resetting Windows Update there is a nice tool I used when I had problems with MU. It's called winUpdRestore!v23. If you don't have it or you can't find it I can upload for you. These steps would have been my next suggestions for you in any case. I did these steps definitely when I fixed my system. You should backup your partition by making an image using Norton Ghost for older computers and Aomei, Macrium or Acronis for newer ones if something is going wrong or you have to revert back. Hope we'll get ahead.