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.

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

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260110-3219d2d-uxp-3e9ca11775-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260110-3219d2d-uxp-3e9ca11775-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-20260110-3219d2d-uxp-3e9ca11775-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-20260110-d849524bd-uxp-3e9ca11775-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260110-d849524bd-uxp-3e9ca11775-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260110-d849524bd-uxp-3e9ca11775-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260110-d849524bd-uxp-3e9ca11775-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260110-d849524bd-uxp-3e9ca11775-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #1791 - Part 1: Un-prefix `-moz-appearance` (a266b9852c) - Issue #1791 - Part 2: Stop force-styling checkboxes/radio buttons. (f303711c59) - Issue #1791 - Part 3: Add manual test for unprefixed `appearance`. (d40256d03f) - Automatically determine current CLDR version when updating langtags. (0471f3bb8c) - Sort replacements per language and per script to ensure the generated file has stable contents. (13b8ede31d) - Issue #2853 - Leverage viewport-only logic to ensure overflow propagation. (0357516199) - Issue #2856 - Make clearing of passwords prefable, and disable by default. (ea25057ec8) - Issue #2887 - Convert use of -moz-appearance to appearance (1782eeb3bd) - Issue #2871 - Restructure `GetEmojiPresentation()` for `Extended_Pictographic` clusters (f13f1bd96e) - Issue #2871 - Addendum - Code Comments (ae2f12c3bc) - Issue #2858 - Hack around the circular calls to `nsPrincipal::Write()` (99c3171426) - Issue #2858 - keep type in line with definition. (ffd00e4056) - Issue #2898 - Don't unroll to large stack probe loops. (628f7cd764) No official Pale-Moon changes picked since my last build. No official Basilisk changes picked since my last build. 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.

I believe in those numbers, as I already stated, I don't trust someone will perform the fake scheme you just described. People have things in life, apart from the forum, you know! Besides, it's easy to check, as I already stated, too! So what? It's my business in what to believe. But at this point, it's too obvious you're very annoyed with someone else's fame. I also think there was a hidden reason to disable topic views. As already stated by @Monroe. Otherwise they would've gotten them back by this time already.

It's my own personal opinion that it was done intentionally so D.Draker's name and maybe a few others, would drop off the 'Popular Contributors' list in time ... which finally happened in the last three weeks, or so. I actually miss his name no longer on the list ... it was interesting watching his 'contributor count' go up and down. I hope I am wrong about the 'topic views' ... but since October nothing, lots of '0s' starting to show up. ...

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.

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.

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:

As part of my work on ytBATCH, I have investigated many ffmpeg releases that are supposed to be compatible with Windows XP. These include, for example, the releases from @Reino, sherpya and @autodidact. The relatively new ones from @Reino and @autodidact work well with YouTube. But when it comes to TV streams, it's a completely different story. Their latest ones in particular have considerable problems with TV stream URLs. On my old Windows XP computer, negative performance changes are immediately apparent. FFmpeg 3.4.1 from 2017 is too old and can no longer access TV stream addresses. The newer releases 7.1 from 2024 and 8.1 from 2025 require much more CPU power than before. They are therefore problematic for older, weak Windows XP computers. That's why I still have been using ffmpeg releases from 2019 for TV stream addresses.

I investigated this myself and the reason appears to be that @Reino's DLLs haven't been "stripped" post successful compilation : https://en.wikipedia.org/wiki/Strip_(Unix) In an MSYS2 environment, $ strip libssl-3.dll will reduce the filesize from 1.22 MiB to just 890 KiB, while $ strip libcrypto-3.dll will reduce the filesize from 5.20 MiB to just 3.88 MiB Finally, as a general observation, different compilers will produce binaries with different filesizes, even when the source code is always the same; and, of course, using different compilation flags between two different compiler invocations will also produce binaries with (slightly?) different filesizes, even when the compiler and source remain unchanged... The DLLs obtained from slproweb were compiled using a "CL" compiler (MSVC C/C++), as you can see by running: openssl version -a => OpenSSL 3.6.1 27 Jan 2026 (Library: OpenSSL 3.6.1 27 Jan 2026) built on: Wed Jan 28 15:01:03 2026 UTC platform: VC-WIN32 options: bn(64,32) compiler: cl /Z7 /Fdossl_static.pdb /Gs0 /GF /Gy /MD /W3 /wd4090 /nologo /O2 -DL_ENDIAN -DOPENSSL_PIC -D"OPENSSL_BUILDING_OPENSSL" -D"OPENSSL_SYS_WIN32" -D"WIN32_LEAN_AND_MEAN" -D"UNICODE" -D"_UNICODE" -D"_CRT_SECURE_NO_DEPRECATE" -D"_WINSOCK_DEPRECATED_NO_WARNINGS" -D"NDEBUG" -D_USE_32BIT_TIME_T -D_WINSOCK_DEPRECATED_NO_WARNINGS -D_WIN32_WINNT=0x0501 OPENSSLDIR: "C:\Program Files (x86)\Common Files\SSL" ENGINESDIR: "C:\Program Files (x86)\OpenSSL\lib\engines-3" MODULESDIR: "C:\Program Files (x86)\OpenSSL\lib\ossl-modules" Seeding source: os-specific CPUINFO: OPENSSL_ia32cap=0x0000e39defebffff:0x0000000000000000:0x0000000000000000:0x0000000000000000:0x0000000000000000 These two are also linked to vcruntime140.dll (external MSVC dependency, thus this further reduces the DLLs's filesize). My educated guess is that Reino's DLLs were compiled with some flavour of MinGW/MSYS2 (as can be deduced from the linked GH issue ), and that compiler is known to produce larger binaries than MS's Visual Studio (but I could be wrong somewhere, without knowing all the finer details ) ...

Edge appears to be the same, so I guess it's a Chromium thing?

For anyone not up to speed; the reason why this is happening has been revealed by one of yt-dlp's major contributors: A lot has changed recently, so I've done some new testing. ios For me personally this player_client still works without a Javascript runtime and a 403 HTTP Error. Compared to me previous post `;formats=missing_pot` is needed though: FOR /F "delims=" %A IN (' yt-dlp.exe --extractor-args "youtube:player_client=ios;formats=missing_pot" -f "(bv[width<=1920]+ba)[protocol^=m3u8]" -O urls "https://www.youtube.com/watch?v=###########" ') DO @IF NOT DEFINED url[0] (SET url[0]=%A) ELSE (SET url[1]=%A) "C:\Program Files\MPC-HC\mpc-hc64.exe" "%url[0]%" /dub "%url[1]%" /close This oldschool method works fine, but as it requires two separate commands I always use my favorite command-line tool Xidel to create the following one-liner: FOR /F "delims=" %A IN ('yt-dlp.exe --extractor-args "youtube:player_client=ios;formats=missing_pot" -f "(bv[width<=1920]+ba)[protocol^=m3u8]" -O urls "https://www.youtube.com/watch?v=###########" ^| xidel -se "let $url:=x:lines($raw) return `\"C:\\Program Files\\MPC-HC\\mpc-hc64.exe\" \"{$url[1]}\" /dub \"{$url[2]}\" /close`"') DO @%A FOR /F "delims=" %A IN (' yt-dlp.exe --extractor-args "youtube:player_client=ios;formats=missing_pot" -f "(bv[width<=1920]+ba)[protocol^=m3u8]" -O urls "https://www.youtube.com/watch?v=###########" ^| xidel -se "let $url:=x:lines($raw) return `\"C:\\Program Files\\MPC-HC\\mpc-hc64.exe\" \"{$url[1]}\" /dub \"{$url[2]}\" /close`" ') DO @%A As an alternative to... -f "(bv[width<=1920]+ba)[protocol^=m3u8]" ...you could also use... -f "bv[width<=1920]+ba" -S "+proto" --format-sort-force web_safari This player_client does require a Javascript runtime (I'm using deno). It only provides the m3u8 protocol formats (audio and video combined), so no filtering is needed, which makes the one-liner very simple: FOR /F "delims=" %A IN (' yt-dlp.exe --extractor-args "youtube:player_client=web_safari" -f "[width<=1920]" -O urls "https://www.youtube.com/watch?v=###########" ') DO @"C:\Program Files\MPC-HC\mpc-hc64.exe" "%A" /close I'm not sure if this player_client provides anything larger than 1080p. If it doesn't, then `-f "[width<=1920]"` isn't needed. As mentioned earlier, most of the time I now use LibreWolf to watch ad-free Youtube videos. I do remember getting the "Sign in to confirm you’re not a bot." message after having watched a dozen Youtube videos through yt-dlp and MPC-HC. Maybe "--impersonate firefox" could prevent that from happening?

I always post on-topic. You should actually know that. And Panda Dome needs Microsoft .NET Framework 4.0 to run at all under Windows XP. My issues could be related to that. So, I need this information to fix issues with my Panda Dome installation. And I had several issues with this anti-malware programme. Thanks for your screenshot but unfortunately, it is not really helpful since there is no complete list of all updates. I need only detailed information about Microsoft .NET Framework 4.0 in terms of Panda Dome. So what could be more on-topic than that? In my thread, all things related to security programmes under Windows XP are definitely on-topic. I am always happy to help others, but now I need some help in the form of detailed information. Strictly according to the principle: manus manum lavat.

@Dave-H Have you installed Revo Uninstaller (Pro) on your Winows XP partition? If so, can you post screenshots of all Microsoft .NET Framework 4.0 updates for comparison taken from Revo Uninstaller? Inside its settings, you can enable to show all system updates. To list all updates, you can enter in the search form the string ".NET Framework 4" I have already repaired my Microsoft .NET Framework 4.0 installation and installed some old updates (before POSReady) which, strangely enough, have somehow disappeared. Here are mine:

As far as I noticed, Panda seems to automatically update the programme only if it is too old. The version 21.01.00 wasn't updated on my system. OTH, the version 18.07.04 was updated to 20.02.01 which, however, isn't the most recent.

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:

Bad news about eScanAV Anti-Virus Toolkit (MWAV)! Their free antimalware scanner can't be updated anymore. I also tried to manually do it with their (weekly) offline virus database updater but this doesn't work either. Here is a quotation from their website https://www.escanav.com/en/mwav-tools/download-free-antivirus-toolkit.asp: And if you update the programme without knowing any better, it will be updated, but rendered unusable with an error message that does not tell the truth.

Huh?

I have no problems to post links that link to the MSFN forum itself. A very fresh example is here. https://msfn.org/board/topic/185045-supermium/?do=findComment&comment=1264614

I was talking about July 2016 Update only , which was re-released in September. "The July 2016 update rollup for Windows 7 Service Pack 1 (SP1) and Windows Server 2008 R2 SP1 was re-released on September 13, 2016 to address an issue in one of the included updates and to improve the overall reliability of the update rollup. Installing this update requires a restart after installation." https://support.microsoft.com/en-us/topic/july-2016-update-rollup-for-windows-7-sp1-and-windows-server-2008-r2-sp1-296220e7-3116-2462-0ed1-fe1198875ad6