Leaderboard

@D.Draker wrote ClamWin still works and without the need for any addons. Not sure how big is the company behind ClamWin. https://clamwin.com/

I have the same issue on Windows 8.1.

@Leokids123, for Windows 7 and 8.1, there's r3dFox from @K4sum1. He has compiled ESR v128.9 releases.

There was a patch released for 7 and Vista to fully support 4K, as in the ability to boot from them, but it got deleted very soon, probably they also made one for XP? https://news.softpedia.com/news/Improve-Windows-7-SP1-and-Vista-SP2-Compatibility-with-Advanced-Format-Disks-216563.shtml Nothing about 4Kn though.

So we may safely assume, no support for XP was ever inttended. Look here, https://aidanfinn.com/?p=13179 "Why Windows Server 2012 Hyper-V VHDX 4K Alignment Is So Important The current VHD driver assumes a physical sector size of 512 bytes and issues 512-byte I/Os, which makes it incompatible with these disks. As a result, the current VHD driver cannot open VHD files on physical 4 KB sector disks. Hyper-V makes it possible to store VHDs on 4 KB disks by implementing a software RMW algorithm in the VHD layer to convert the 512-byte access and update request to the VHD file to corresponding 4 KB accesses and updates."

AI answer.

WSUS Offline Update 9.2.6 does not do anything good from scratch under Windows XP in these days. So, I modified the DownloadUpdates.cmd file in line 206 located in the sub folder cmd where I added an additional option to the downloader wget.exe: set DLDR_PATH=..\bin\wget.exe --no-check-certificate Furthermore, I replaced the wget.exe file by the last XP-compatible version 1.19.4. Then, I configured WSUS Offline Update 9.2.6 to use ProxHTTPSProxy to avoid any possible connection problems, especially certificate related. But one can also try to download all updates without it, of course. And I inserted the last XP-compatible version Sigcheck 2.30 to avoid any verification problems although I didn't enable the option "Verify downloaded updates". And what shall I say? WSUS Offline Update 9.2.6 still works under Windows XP even today. Of course, only if such modifications were done I listed above. Here is my log generated after a successful download of German Windows XP updates under the OS Windows XP : TBH, I did all that here to show that even today these updates can be downloaded under Windows XP. Personally, I do not need to download those updates anymore as I already did it in 2014, 2019 and 2022. And I archived all installed updates I got from Windows Update from the very first including all POSReady updates. Cheers, AstroSkipper

You should use New Moon 28 or Serpent 52 in combination with uBlock Origin Legacy and suitable filter lists enabled. A more recent user agent can't hurt, either. Mypal 29 and Firefox 52 are much too old.

Yep, a bit strange. But as I have already described, my 360Chrome 13.5 Build 1030 Redux initially also reported no secure connection to the website https://chi.uk2.net/ using ProxHTTPSProxy, i.e. no green padlock. Only after I had deleted all certificates in the Certs folder and updated the cacert.pem certificate inside the ProxHTTPSProxy installation, 360Chrome immediately reported a secure connection after a restart and showed the green padlock. However, recognising valid certificates has always been a problem in almost all 360Chrome versions for Windows XP. TBH, I very rarely use 360Chrome only to check sites for browser compatibility. I generally surf with Mypal 68 (is now running great ) and New Moon 28, and I try to open the more modern, very bloated sites with Thorium. If all else fails, I use my Android tablet.

Hi @TheLeftOldComputer! Many antimalware programmes are no longer compatible with Windows XP but ClamWin has always been. Unfortunately, it does not have a real-time protection. Only an additional tool called Clam Sentinel which has no longer been developed for years and never was a good one. It could only use ClamWin to scan downloaded files. So what about a programme based on the open source ClamAV with its virus definition databases which offers real-time protection? Or a fork of ClamWin with real-time protection and still compatible with CPU's only having the instruction set SSE? Kind regards, AstroSkipper

That's good. But in your original screenshot there wasn't a green padlock.

@Multibooter And if eScanAV 22.x does not run with your SSE only CPU, you can try the previous version eScanAV 14.x which is still available on their homepage. But one thing is clear. The air for systems with an SSE only CPU is now very thin, especially when it comes to antimalware programmes that still receive the latest virus definitions.

Then --enable-low-end-device-mode would better suit your needs, in theory it should combine many, including these. Don't throw stones at me, if not. Just try. *use without quotes.

Use in conjunction with --component-updater=url-source=0.0.0.0 Otherwise it would still check for available updates at certain intervals. It won't update them, but these checking connections is better to avoid.

I believe that updating Chrome components in the background on Windows XP may now be more of a problem than a benefit. It's been so many years since support for Chrome on Windows XP was discontinued that components for this operating system are no longer being developed, let alone checked for compatibility. Thus, using the flag --disable-component-update seems to me a logical consequence.

As I already wrote, no components were installed in my Thorium installation. The list is simply empty. It was just an idea. Personally, I use the flag --disable-component-update.

Stem

Star

Flop

Clam

But people, like Dave-H, are grateful these ports exist.

It's because some write they are, but no one gives a link.

Predictable, playing with local sharks is dangerous, and not surprising, considering the fact you lost to @D.Draker.