Leaderboard

I would like for you to replace the links for RogueKiller last XP compatible versions from generic web-site links to archived links with v15 and portable v16 on 32bit and 64bit. It's a shame that Panda is placing XP on guillotine right now, but to be honest, XP had a good run, 25 years of anti-malware support from various programmes. I am still using Avast on XP VMs and i feel relatively secure with COMODO Firewall Pro from 2007 version, and i have no complaints. I do not recommend the last version of COMODO Internet Security however, because it choked my old Celeron to the core when i tested 4 years ago...

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260725-3219d2d-uxp-30427c0213-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260725-3219d2d-uxp-30427c0213-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-20260725-3219d2d-uxp-30427c0213-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-20260725-d849524bd-uxp-30427c0213-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260725-d849524bd-uxp-30427c0213-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260725-d849524bd-uxp-30427c0213-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260725-d849524bd-uxp-30427c0213-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260725-d849524bd-uxp-30427c0213-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #1803 - Convert std::*<T>::value/::type to _v and _t suffixes. (1dd094e90b) - Issue #3061 - Remove network tickler. (3312ebb226) - No issue - Exclude some files from the preprocessor that don't have directives in them. (4b77043d11) - Issue #3144 - Implement CSSStyleSheet replaceSync (05467e9db6) - [js] Guard against OOB string sizes in internal Printf (90952505ec) - [gfx] Add bounds checks and limit reverse scanning of ligature data. (07271921c9) - [gfx] Hold a strong ref during GetFontAt lookup. (0b8fd38fb3) - [DOM] Make parser update form owner properly (0cd2c3acf7) - [js] Initialize BaselineFrame return value slot in OnLeaveBaselineFrame. (a809f575d1) - [js] Clamp length of regexp captures array for dollar substitution. (f8982ebd3f) 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: - devtools: restore preprocessor usage (30427c0213) 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 BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260725-40a79c75-uxp-30427c0213-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260725-40a79c75-uxp-30427c0213-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/boc-uxp/tree/custom * Notice: the profile prefix (i.e. parent folder names) are also changed since 2020-08-15 build, you may rename their names before using new binaries when updating from builds before 2020-08-15. -- New build of HBL-UXP for XP! Test binary: IceDove-UXP(mail) https://o.rthost.win/hbl-uxp/icedove.win32-20260725-id-656ea98-uxp-30427c0213-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260725-id-656ea98-ia-c642e3c-uxp-30427c0213-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

Ok. Forget about this version! It still can be started under Windows XP but it no longer works properly. I reverted back to the last good one I could find. And that is Malware Hunter 1.210.0.841 (Dec 29, 2025). I will edit my article accordingly. And BTW, I said tests could be done by the users but I’ve never seen any like that.

The links are still available on Adlice servers after editing to suit the users’ needs. I do not use COMODO Internet Security but COMODO Antivirus. This works fine with no impact on CPU. And my CPU is a single-core P4. I wouldn't recommend the complete suite COMODO Internet Security, either. You must always focus on the pearls and throw the by-catch overboard.

This time on time :-) - the latest update is online: The mirror of latest ArcticFox 44, BNavigator 0.9, Firefox 28/45ESR, IceApe 52, IceDove 52, K-Meleon 1.5.x/74/76, MailNews 52, New Moon 26.5/27/28, RetroZilla, RZ browser and Serpent 52/55 builds by @roytam1 has been updated -> soggi.org - tools. changelog: - added latest BNavigator 0.9 20260725 build - added latest IceApe 52 20260725 build - added latest IceDove 52 20260725 build - added latest MailNews 52 20260725 build - added latest New Moon 28 20260725 builds - added latest Serpent 52 20260725 builds - added latest Serpent 55 20260725 builds To don't lose track of things I want to update too someday... todo: - add various flash player versions - add FlashFix for WinXP - add VLC 2.2.8 (WinXP non-SSE2) done! - add polyfill addons Kind regards soggi

Don’t be misled! Quoting from old, already closed and resolved at the time issues serves no purpose and is misleading. I’ve opened a new issue on GitHub today: https://github.com/Feodor2/Mypal68/issues/723 One thing is clear. If you use a browser that doesn’t support Cloudflare’s security nonsense, you won’t get very far in these days, and it’ll be useless. Indeed, Cloudflare = Cauldron Filthcare.

New build of post-deprecated Serpent/moebius for XP! * Notice: This repo will not be built on regular schedule, and changes are experimental as usual. ** Current moebius patch level should be on par with 52.9, but some security patches can not be applied/ported due to source milestone differences between versions. Test binary: Win32 https://o.rthost.win/basilisk/basilisk55-win32-git-20260725-94e741a46-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20260725-94e741a46-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - ported from UXP: Issue #1803 - Convert std::*<T>::value/::type to _v and _t suffixes. (1dd094e9) (200256195) - ported from UXP: Issue #3061 - Remove network tickler. (3312ebb2) (5cb455841) - ported from UXP: Issue #3144 - Implement CSSStyleSheet replaceSync (05467e9d) (de7f8267f) - import from UXP: [js] Guard against OOB string sizes in internal Printf (90952505) (604ade209) - import from UXP: [gfx] Add bounds checks and limit reverse scanning of ligature data. (07271921) (6c05b903c) - import from UXP: [gfx] Hold a strong ref during GetFontAt lookup. (0b8fd38f) (a3d9936ff) - import from UXP: [DOM] Make parser update form owner properly (0cd2c3ac) (443fd3272) - import from UXP: [js] Initialize BaselineFrame return value slot in OnLeaveBaselineFrame. (a809f575) (df19befd2) - import from UXP: [js] Clamp length of regexp captures array for dollar substitution. (f8982ebd) (94e741a46)

# [Windows 8.1 x64] Cyberpunk 2077 2.31 Steam compatibility patch I am publishing an experimental compatibility package for **Cyberpunk 2077 2.31 on Windows 8.1 x64**, tested against the Steam public build `20383525`. ** Download has been taken down **ZIP SHA-256:** `5D8543335269D86B7456B60B6E6A3908C6C296B186DB93F8EF25EA38D371745E` > This release was tested only on **Windows 8.1 x64**, so that is the only > operating system for which it is currently recommended. The installer rejects > other Windows versions and unsupported game files. ## What it fixes The package provides a D3D12On7 raster path for the tested Steam build and fixes the known presentation problem where Cyberpunk appears frozen and updates only when another window is dragged over it. The game can be launched normally with Steam's **Play** button after adding the launch option printed by the installer. ## Performance On my tested machine, performance is close to running the game on Windows 10. It is dramatically better than my older Cyberpunk 1.63 compatibility setup, which delivered roughly half performance on the same machine. This is an observed real-world comparison, **not a controlled or standardized benchmark**. Results will vary with GPU, driver, settings and system setup. ## Tested setup - Windows 8.1 x64 - Cyberpunk 2077 2.31, Steam build `20383525` - GeForce RTX 2060 - NVIDIA driver `474.11` - 1920 x 1080 - Raster rendering only Other GPUs and drivers, GOG/Epic releases, hybrid graphics and other operating systems have not been tested. ## Required: official D3D12On7 1.1.0 package Download Microsoft's official [`Microsoft.Direct3D.D3D12On7` 1.1.0 NuGet package](https://www.nuget.org/packages/Microsoft.Direct3D.D3D12On7/1.1.0) separately and save the unchanged file next to `Install.cmd` as: `Microsoft.Direct3D.D3D12On7.1.1.0.nupkg` Expected package SHA-256: `C0C4D597537ECC1C777FA3B5523E5CCDE0B9984B88FB9F37B2385E1D687BF536` The Microsoft package is not bundled with this patch. ## Required: SecondSystem SecondSystem must already be installed and active. **It is not bundled with the patch.** Obtain it separately here: [SecondSystem from win32's Patreon](https://patreon.com/win32?utm_medium=clipboard_copy&utm_source=copyLink&utm_campaign=creatorshare_fan&utm_content=join_link) Please support its developer and follow the terms provided with it. ## Installation 1. Extract the complete ZIP. 2. Download the official D3D12On7 package above and place it beside `Install.cmd`. 3. Install and activate SecondSystem. 4. Exit both Cyberpunk 2077 and Steam completely. 5. Run `Install.cmd`. 6. Copy the exact Steam Launch Options value printed at the end. 7. Paste it into **Steam > Cyberpunk 2077 > Properties > General > Launch Options**. 8. Start the game with Steam's **Play** button. Do not append custom arguments; the included launcher intentionally uses only the fixed, validated command line. The installer validates the exact game/runtime hashes and stops before changing anything if the files are unsupported. It keeps all compatibility files local to the game directory and creates a verified uninstall record. ## Important limitations The following features must remain disabled: - Ray tracing and path tracing - DLSS - NVIDIA Reflex - Frame Generation, including XeSS Frame Generation This release is for raster rendering. Cyberpunk 2.31's newer Agility SDK path is not a Windows 8.1 target, so modern features that depend on it are outside this patch's scope. ## Removal and game updates Close the game and Steam, run `Uninstall.cmd`, then clear Steam Launch Options. The uninstaller restores any files it backed up and reverses its SecondSystem mappings. The package is locked to Steam build `20383525`. The launcher compares the full contents of the current executable with its validated local copy and refuses a mismatch. After a Steam update, uninstall this release and wait for a version explicitly validated for the new build; do not remove the version/hash safety checks. ## What is and is not included The ZIP contains the original open-source proxy, launcher, installer scripts, source code, documentation and notices. It does **not** include: - Cyberpunk 2077 files - Microsoft D3D12On7 or D3D11On12 binaries - SecondSystem - Steam files - any DRM bypass A legal Steam copy of the game is required. The installer extracts the runtime inputs from the official NuGet package separately supplied by the user and creates a local working copy. Microsoft terms still apply and may restrict this use or modification; this is not legal advice. Full installation, troubleshooting, technical and checksum information is in the included `README.md`.

How to secure Windows XP in 2026 - A multi-layered security strategy It is now July 2026. Since Panda Security – either unintentionally or perhaps deliberately – rendered its Panda Dome programme unusable on Windows XP from 2 July onwards due to faulty automatic updates, there are, in practical terms, hardly any anti-malware programmes with real-time protection left for this operating system supported by both programme and definition updates. Almost all well-known manufacturers of antivirus and antimalware programmes have discontinued support for Windows XP over the years. It is therefore of the utmost importance, first and foremost, to persuade Panda to correct its update routine on the server side. Windows XP enthusiasts can exert considerable influence here by reporting all issues with Panda Dome to the support team. Only if many people do this is there a realistic chance that anything might change in this regard yet. I really shouldn’t care, since I'm actually done with Panda. In any case, Windows XP users must realise that comprehensive security suites, as they used to be, practically no longer exist. System protection must therefore be organised differently. You have to build and organise it yourself using various tools that must work together harmoniously. Layer by layer, so to speak. What do you need for a secure Windows XP system? Windows XP SP3 with all essential components and available updates. Backup system: A fully functional backup system that regularly creates partition images. Firewall: A very good firewall that monitors all network traffic, including all incoming and outgoing connections, even those from Windows XP system components. Real-time protection: A programme that runs in memory, detects and reports threats. Process manager: Located in the taskbar. Startup manager: A good startup manager. On-demand scanners: One, or better still several, good on-demand scanners with a disinfection feature. Browser: An up-to-date browser with an ad blocker. Certificates: Up-to-date root certificates. And, of course, common sense. And if anyone now claims that this is impossible, I’ll respond directly: I’ve configured my Windows XP system exactly like this and haven’t had a single infection in 25 years. Windows XP is still my main operating system alongside Android. Cheers, AstroSkipper

You are a Super Moderator and you know a lot of members here in this forum. Is there anyone in MSFN with such skills?

Hi @Dave-H, try this site to see all ciphers classified due to its TLS version: https://browserleaks.com/ssl Here is a screenshot of Iceape-UXP accessing browserleaks.com using its native TLS protocol (max. TLS 1.3): There you can see which TLS version is currently used and its ciphers. You can clearly realize that exactly three ciphers are relating to TLS 1.3: - TLS_AES_128_GCM_SHA256 (0x1301) - TLS_CHACHA20_POLY1305_SHA256 (0x1303) - TLS_AES_256_GCM_SHA384 (0x1302) Here is a screenshot of Iceape-UXP accessing browserleaks.com using ProxHTTPSProxy REV3e: And these three mentioned TLS 1.3 related ciphers are obviously not present in ProxHTTPSProxy REV3e. @heinoganda added a lot of TLS 1.2 ciphers I have never seen before, but unfortunately no ciphers relating to TLS 1.3 protocol. My conclusion: ProxHTTPSProxy REV3e contains openssl-1.1.1d including support for TLS 1.3, but the TLS 1.3 related ciphers have to be added or implemented by a person with Python programming skills yet. So we need a programmer as it was @heinoganda in the past. Cheers, AstroSkipper

I had never seen a SSE release of Mypal in the past. I used it and it was my favourite browser until development was dropped. Feodor provided only a 32 and a 64 Bit release of each version. And I would know of it whether such a SSE release existed in the past or not.

I can't open https://web.whatsapp.com/. It is immediately redirected to https://www.whatsapp.com/.

Mypal 68 is portable. Therefore you can try to modify whatever you want without any tragic consequences. If it doesn't work, simply delete it! I do have a main profile and one for testing purpose only.

I think he meant a release supporting CPUs with SSE instructions set only, lacking of SSE2 or higher.

When I think about Feodor's old Mypal releases, I don't believe that there'll be any SSE builds. But just an assumption! Nevertheless, an additional SSE build would be great, of course!