Leaderboard

Thanks @Tangy. I would be interested to know your results. Just an update, I spoke again today to Panda's technical support people at AnyTech365. Again, really friendly and helpful people, who knew exactly what I was talking about. They are thinking, as many here do, that Panda have actually withdrawn support for XP. They agree that doing this by just breaking the legacy version of Panda Dome, is not a good way of doing this, especially for paying customers, and they are trying to find out whether this really is the case or whether this has been done accidentally and will be fixed, if indeed it's possible to do that. There has certainly been no change made to the system requirements on Panda's website, and the article trumpeting its XP compatibility claims to have been updated on July 1st. They have given me a number to ring for Watchguard, Panda's parent company, so I will try giving them a ring tomorrow to see what they say about this.

I got a response from Watchguard technical support. "At this time, we have not received any official communication indicating that Windows XP support for Panda Dome has been discontinued. Based on the information currently available, Windows XP continues to be listed as a supported operating system for the legacy Panda Dome version referenced on the Panda website. Based on the information you have provided, this issue appears to be related to **Panda Dome**, which is a consumer (home) product. While we understand your concerns regarding the recent crashes of **PSANHost.exe** on Windows XP, we are unable to investigate or provide support for Panda Dome through WatchGuard Technical Support." So it appears that they only deal with professional business customers at Watchguard support, and they can't help private domestic customers. I would have to use the domestic support channels for Panda support, which I've already done, of course! The guys at AnyTech365 have promised to let me know if they hear anything about the status of XP support from Panda, so all I can do is wait.

Assuming you haven't already uninstalled Panda, could you try excluding from scanning the folders I detailed in my earlier post? I would just be interested to know if this helps the problem on your system. I'm still getting occasional stops and starts of the main Panda service, and I'm trying to find out exactly what is triggering them. Again, not a fix, just a better understanding of where the mechanism is now failing. Incidentally, Panda's online support forms are pretty useless, as once you've submitted one, you are supposed to be able to add new information to it by clicking on the link in the e-mail it sends you. Unfortunately, this doesn't work. When you submit the revised form, you just get an error message that the e-mail and customer number don't match any current user! I've had to submit two further forms from scratch to give them more information.

New build of Serpent/UXP for XP! Test binary: Win32 https://o.rthost.win/basilisk/basilisk52-g4.8.win32-git-20260718-3219d2d-uxp-edd86c9a9d-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk52-g4.8.win64-git-20260718-3219d2d-uxp-edd86c9a9d-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-20260718-3219d2d-uxp-edd86c9a9d-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-20260718-d849524bd-uxp-edd86c9a9d-xpmod.7z Win32 IA32 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260718-d849524bd-uxp-edd86c9a9d-xpmod-ia32.7z Win32 SSE https://o.rthost.win/palemoon/palemoon-28.10.7a1.win32-git-20260718-d849524bd-uxp-edd86c9a9d-xpmod-sse.7z Win64 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260718-d849524bd-uxp-edd86c9a9d-xpmod.7z Win7+ x64 AVX2 https://o.rthost.win/palemoon/palemoon-28.10.7a1.win64-git-20260718-d849524bd-uxp-edd86c9a9d-w7plus-avx2.7z Official UXP changes picked since my last build: - Issue #3122 - Stop using <base> element in json viewer. (25440b453a) - Issue #3129 - Add palette_neon_intrinsics.c to moz.build (6ba6120115) - Issue #3129 - Follow-up: Add aarch64 to platforms enabling Neon in libpng. (97a7730717) - Issue #3134 - Import missing libpng files for loongarch and plug them into moz.build (f3ed8ce4a4) - Revert "Bug 2033848 - Use non-default response ID for GTK file picker accept button. r=stransky" (7e4c152210) - Issue #2829 - Support revert-layer in CSS-wide parsing (cacd5b2d61) - Issue #2829 - Implement CSS revert-layer cascade rollback (07a651cb70) - Issue #2829 - Handle revert-layer variable fallbacks (8a63f0d1e1) - Issue #2829 - Use layer index naming for revert-layer metadata (121fa183a0) - Issue #2829 - Regenerate devtools CSS database for revert-layer (3ad8472edc) - Issue #3140 - implement URL.parse() (a5610624d0) 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.

Long story short, I have revived Comodo Antivirus 12.0.0.6818 (CAV) as part of the Comodo Internet Security suite (CIS) since it was no longer working out of the box. It's one of the last working antimalware programmes with real-time protection, HIPS, VirusScope, secure containmenr, online definition updates, even incremental definition updates, and the possibility of offline updating. This is now my new antimalware programme. And Vir.IT of course. All free of charge.

Sorry for the delay in responding again. Nothing has changed since my last report, the program is working, with my folder exclusions applied, with only occasional stops and restarts of the main Panda service. I can live with that in the short term. I'm still hoping, of course, that a fix will be applied and it will all come good again. Nobody has any definite evidence that Panda have deliberately stopped their XP version from working properly, only speculation. I will wait a while and ring AnyTech365 again if I've heard nothing from them about this. They will be as anxious as I am to get an answer from the Panda developers about this, I'm sure, as they will need to be able to give accurate support information to anyone else asking about this problem! Assuming that they do have a direct channel of communication to them, and it would be pretty stupid if they didn't, hopefully it won't be too long a wait for an answer, one way or the other.

New build of BOC/UXP for XP! Test binary: MailNews Win32 https://o.rthost.win/boc-uxp/mailnews.win32-20260718-40a79c75-uxp-edd86c9a9d-xpmod.7z BNavigator Win32 https://o.rthost.win/boc-uxp/bnavigator.win32-20260718-40a79c75-uxp-edd86c9a9d-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-20260718-id-656ea98-uxp-edd86c9a9d-xpmod.7z IceApe-UXP(suite) https://o.rthost.win/hbl-uxp/iceape.win32-20260718-id-656ea98-ia-c642e3c-uxp-edd86c9a9d-xpmod.7z source repo (excluding UXP): https://github.com/roytam1/icedove-uxp/tree/winbuild https://github.com/roytam1/iceape-uxp/tree/winbuild

FYI, Comodo Internet Security 12.0.0.6818 is not, in fact, the latest version compatible with Windows XP. Furthermore, it contains various bugs that have been fixed in the actual latest version targeting Windows XP. It is Comodo Internet Security 12.0.0.6870: And in fact, even more bugs have been fixed than those listed in the release notes. Here are some screenshots: This version runs smoothly, quickly and light on resources, and the online updates are working again, of course only after fixing myself, without any errors either. Therefore, this will be my final antimalware programme for Windows XP . I do regret not having revived this antimalware programme sooner.

Yes indeed, but if you remember, Malwarebytes did pretty much the same thing. They maintained version 3.5.1 for several years 'as is' for XP users and still provided pattern updates for it. Then they pulled the plug, without any warning, and no longer provided pattern updates, although the program still worked OK. Likewise, Panda keep 22.03.05 as their legacy version for XP users, which can still be downloaded and installed. As long as it still works, I'm not that worried if the program files are old. This is not quite the same scenario, of course, as Panda doesn't use local pattern files for scanning, which makes it even stranger that they would suddenly break XP compatibility. Whatever they do with the daily 'synchronisation' mechanism, it seems that has broken things. No program files have been changed as far as I can see.

It’s clear and obvious that Panda stopped supporting Windows XP for programme updates quite some time ago. The latest version is 22.03.05, nearly one year ago, and that was a long time ago. But to then go and break even that version via the automatic update – that’s a no-go. And in doing so put the user’s partition at risk.

Thanks, no problem! I'm still hoping this will be fixed eventually, especially as I'm a paying customer. I'm still getting messages in my event log that the Panda service has stopped unexpectedly and been restarted, but no actual crash messages. It's usable, but annoying! If nothing has happened soon, I will ring their technical support guys in the UK again and see if they know anything. I won't be wasting my time with any more online forms!

@Dave-H If you absolutely want to stick with Panda – presumably because you still have a valid licence – then I’d uninstall it completely, give everything a thorough clean, then reinstall it, but without allowing any connection to the internet. Then set the cache folder to read-only for everyone, especially for the System account, or if that doesn’t work, delete it completely. Then set all your exclusions and only then connect to the internet. No updates must be carried out locally. Perhaps it will then run stably. But to be honest, this isn’t of course a good workaround, as it unfortunately results in a loss of functionality. Personally, I’m done with Panda and would only go back if an official fix has been released or the update server has been corrected.

This absolutely confirms what I’ve already said here and what many other customers have reported across the web. At first glance, Panda Support seems great, but on closer inspection it’s a joke. For home users, it’s practically non-existent. They probably focus more on enterprise customers. Money makes the world go round.

It is not NT 6.0 incompatible code as otherwise it wouldn't work no matter which compiler was used. This is likely a compiler issue so for now GCC 15 will be more reliable. The GCC 16 compiler hasn't been changed since the previous working build so I haven't been able to isolate the root cause yet. I will continue looking into it.

@VistaLover I reversed this commit which got partial functionality but GCC 16 is still problematic for 32-bit builds. Here is a smaller build using GCC 15 for you to try. https://files.videohelp.com/u/69760/ffmpeg-8.2-2278-a09be9b91e-static-VISTAx86.7z

OK. Patient number 12.0.0.6818 from 2019 has been resuscitated and is eating again. „Oops!... I Did It Again“ ...

There are new Vista builds linked in the previous post. If you can let me know if ffplay is working for you.

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-20260718-99e7fa950-xpmod.7z Win64 https://o.rthost.win/basilisk/basilisk55-win64-git-20260718-99e7fa950-xpmod.7z repo: https://github.com/roytam1/basilisk55 Repo changes: - Revert "import from UXP: Bug 2033848 - Use non-default response ID for GTK file picker accept button. r=stransky (81babad1)" (072bcb2ff) - ported from UXP: Issue #3122 - Stop using <base> element in json viewer. (25440b45) (57690362e) - import from UXP: Issue #3129 - Add palette_neon_intrinsics.c to moz.build (6ba61201) (ff5d3081d) - import from UXP: Issue #3129 - Follow-up: Add aarch64 to platforms enabling Neon in libpng. (97a77307) (fe07f5ff6) - import from UXP: Issue #3134 - Import missing libpng files for loongarch and plug them into moz.build (f3ed8ce4) (38bca147b) - ported from UXP: Issue #2829 - Support revert-layer in CSS-wide parsing (cacd5b2d) (0bb7b6959) - ported from UXP: Issue #2829 - Implement CSS revert-layer cascade rollback (07a651cb) (ebf3fafe2) - import from UXP: Issue #2829 - Handle revert-layer variable fallbacks (8a63f0d1) (5849d68a0) - ported from UXP: Issue #2829 - Use layer index naming for revert-layer metadata (121fa183) (22dac9430) - ported from UXP: Issue #2829 - Regenerate devtools CSS database for revert-layer (3ad8472e) (e49363921) - import from UXP: Issue #3140 - implement URL.parse() (a5610624) (99e7fa950)

As of today, I can see my username right at the bottom of the relevant page, even though I’ve disabled this in my account settings. What on earth is going on now, apart from the MSFN outages that have been going on for over a week? Is this supposed to be a new feature, or has the forum software gone completely haywire?

And it is not Android related. Here is a screenshot taken from New Moon 28 on my beloved, old Windows XP computer:

Ok. You can't see my username but I can as of today. If I open another browser where I'm not logged into my account, I can't see my username, either. So something must have changed.

Steve: I did as instructed and it worked (naturally). Right now my folder has 25h2 as part of the name. when I change it to 26h2 in the fall I guess I'll have to do the same procedure? regards...

@AstroSkipper I mean RAM. I got 8 GBs. MY xp reads around 3 GBs. There is something that my system does not like about it. I have not put any effort to find out what is causing that. Could it be that my xp is 32bits ?

There's a thread in the Vista forum about getting certain versions of VMware Workstation and Player to work beyond the official supported versions. https://msfn.org/board/topic/180052-tutorial-how-to-install-vmware-workstation-11-or-12-in-vista/ Workstation 10 and Player 6 are the last versions officially supported on XP, 2003, and Vista. Early versions of Workstation 11 (and Player 7) won't install on XP/2003/Vista but when inspected the maximum requirement of any of the .sys drivers is NT 6.1 which corresponds to Vista SP1. In previous VMware versions there were additional, separate driver files for XP-based Windows versions (32-bit and 64-bit). Notably the vmx86_64 driver was shared by 64-bit XP/2003 and later versions of Windows, so there weren't separate versions. In VMware 11 it looks like no additional dependencies have been added to the vmx86_64 driver. Its minimum OS requirement has been bumped up from 5.2 to 6.0, but with the lack of new dependencies I'm guessing it would still work in XP if that limitation in the header were removed. Depending on how much the other drivers have changed, there's a small possibility that where the VMware 11 drivers are truly incompatible with XP/2003 64-bit the VMware 10.x 64-bit drivers may be able to replace them. I checked a couple of other drivers (but not all of them) and again noticed no change in dependencies for the Vista-compatible 10.x drivers vs. the Vista-compatible 11.x drivers. This is a good sign, but doesn't necessarily reflect whether the 11.x drivers are providing any new, critical functionality that wouldn't be present if the Vista-compatible 11.x drivers that the 11.x installers include are replaced by XP-compatible 10.x drivers. For example, if critical new functionality related to networking is absent inside the 10.x drivers the Workstation/Player software could potentially run but only if networking is always disabled. As far as the many DLL files that VMware 11 is bundled with, they all still seem to be built targeting NT 5.2 at most, but I'm not certain that I checked 100% of them. I plan to look into this a lot more in the future, but I don't have time now and this will likely get put off for months or longer. If anyone else wants to mess around with this I figured I'd share what I observed so far.

It remains free but after the period of 60 days, the removal of malware is no longer possible. If you need this feature, you have to buy a license. That's ok for me. I personally do not need this feature.

About panda acting up, same as before, but now crappier: service crashes and even on occasions with no service crashes now sistem also becomes very slow while clicking through start menu, e.g. recent documents. Even doing regular tasks, opening e.g. Task Manager I had to wait around 1 minute before it would open. And get this: panda decided it's king of the system somehow and Diskeeper that I use could not even save fragmentation prevented statistics for the current day. The next day it showed as "---------" (none). Unglaublich! Anyhow, applying their panda-b-gone uninstaller things are finally making sense. P.S.: Regarding this about IOBit Malware fighter Its drivers have win7x86 path, and it just makes AppData/Local/Low directories in XP as if it owns the place. Not applicable. Yes, Comodo can be good, though their HIPS system can be quite heavy (but that is with Comodo Firewall). I used both (AV & FW) in the past. Might test it again... They are advertising all over the place "It's Free" and then when wanting to download, you get hit with the remark "for 60 days" when there is a comparison drawn between the two releases. Disgusting!

... I'm trying somehow to understand, but, as a non-coder, I fail to do so ... Your previous working, FULL, FFplay.exe (32-bit) binary from early June, ffplay version N-124841-gb355200263-WINVISTA Copyright (c) 2003-2026 the FFmpeg developers built with gcc 16.1.0 (Rev5, Built by MSYS2 project) configuration: --disable-autodetect --enable-amf --enable-bzlib --enable-d3d11va --enable-dxva2 --enable-iconv --enable-lzma --enable-zlib --enable-sdl2 --enable-gmp --enable-libmp3lame --enable-libopus --enable-libvorbis --enable-libx264 --enable-libx265 --enable-libdav1d --disable-debug --enable-libfdk-aac --enable-fontconfig --enable-libass --enable-libbluray --enable-libfreetype --enable-libmysofa --enable-libopencore-amrnb --enable-libopencore-amrwb --enable-libopenjpeg --enable-libsnappy --enable-libsoxr --enable-libspeex --enable-libtheora --enable-libtwolame --enable-libvidstab --enable-libvo-amrwbenc --enable-libwebp --enable-libxml2 --enable-libzimg --enable-libshine --enable-avisynth --enable-libxvid --enable-libopenmpt --enable-libsrt --enable-libzmq --enable-libgsm --enable-chromaprint --enable-frei0r --enable-libaribb24 --enable-libbs2b --enable-libcaca --enable-libcdio --enable-libflite --enable-libfribidi --enable-libgme --enable-libilbc --enable-libmodplug --enable-librubberband --enable-libzvbi --enable-openal --enable-libcodec2 --enable-ladspa --enable-libuavs3d --enable-libjxl --enable-libxeve --enable-libxevd --enable-libharfbuzz --enable-liblc3 --enable-libaribcaption --enable-lcms2 --enable-libdvdread --enable-libdvdnav --enable-liboapv --enable-libqrencode --enable-libquirc --enable-opengl --enable-gnutls --enable-gpl --enable-version3 libavutil 60. 32.100 / 60. 32.100 libavcodec 62. 36.101 / 62. 36.101 libavformat 62. 19.101 / 62. 19.101 libavdevice 62. 4.100 / 62. 4.100 libavfilter 11. 17.100 / 11. 17.100 libswscale 9. 8.100 / 9. 8.100 libswresample 6. 4.100 / 6. 4.100 was compiled with GCC16, was it not ? However, more recent FFplay (32-bit) builds, when again compiled with GCC16, end up exhibiting the crash-y behaviour I have reported so far; have you changed in some aspect the compiler itself (GCC16) since the start of June or are the recent crashes the result of upstream (FFmpeg) new code, that makes the final binary incompatible with NT 6.0 x86? The GCC15.2 compile launches OK here, ffplay version N-125551-ga09be9b91e Copyright (c) 2003-2026 the FFmpeg developers built with gcc 15.2.0 (Rev14, Built by MSYS2 project) configuration: --prefix=/local32 --bindir=/local32/bin-video --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion --disable-autodetect --enable-zlib --enable-sdl2 --enable-gpl --enable-libmp3lame --disable-debug --enable-libfdk-aac --enable-libass --enable-libxml2 --enable-libshine --enable-gnutls --enable-libx264 --enable-libx265 --extra-cflags=-DLIBXML_STATIC libavutil 61. 4.100 / 61. 4.100 libavcodec 63. 6.100 / 63. 6.100 libavformat 63. 4.100 / 63. 4.100 libavdevice 63. 2.100 / 63. 2.100 libavfilter 12. 2.100 / 12. 2.100 libswscale 10. 2.100 / 10. 2.100 libswresample 7. 2.100 / 7. 2.100 Simple media player usage: ffplay [options] input_file ... and I couldn't help noticing lots of "first-time-to-be-seen" configure flags : --pkg-config=pkgconf --pkg-config-flags='--keep-system-libs --keep-system-cflags --static' --cc=gcc --cxx=g++ --ld=g++ --extra-cxxflags=-fpermissive --extra-cflags=-Wno-int-conversion As for my audio-only MP4 file, it plays there with NO crashes : So, does this mean it's goodbye GCC16.1 and welcome GCC15.2 ? (OT: the appalling forum's code viewer did push my patience to its limits, while trying to send this comment ; will it ever get fixed?)

The Mind-Bending Company That Gets a Million Job Applications—and Rejects 99.9% Getting an offer from Bending Spoons, which owns AOL, has become harder than getting into Harvard https://archive.ph/kY6Th By Ben Cohen / July 10, 2026

Thanks a lot for recompiling ; I've downloaded and tested the new n8.2-dev-2273 VISTA binaries and can confirm the new FFplay.exe files work as expected : If it's not too much to ask , can you share what the issue was with the previous FFplay offering?

Release: WDMHDA Alpha-022 https://github.com/andrew-hoffman/WDMHDA/rele … s/tag/Alpha-022 Changes: Fix choppy playback/silence if stream is paused and resumed near the end of the audio buffer add Mute for the main output (doesn't work on all codecs yet) Fix CORB/RIRB on NForce chipsets Send a power-up command to all Power Widgets on the codec just in case that is needed. Reduced max audio buffer size to 128k again, too much buffer can cause significant lag I should also mention that sdz on VOGONS has released a standalone OPL3 emulator for Win9x which works well in combination with WDMHDA: https://www.vogons.org/viewtopic.php?t=111787

As I already said, it is no longer time to be picky when it comes to real-time protection under Windows XP. And of course, I read such reports about IOBit Malware Fighter. I personally never liked the IOBit company. Their products have never really been any good. And in the case of IOBit Malware Fighter, I can see why. The positives: Easy to install. A clearly structured, very tidy and modern interface. Good usability. Lots of features not usually found in freeware. Excellent uninstallation speed. The negatives: No daily updates as advertised. Today, it’s still installing the version from 9 July. Not really integrated efficiently into Windows XP. When the protection is activated, performance plummets. Version 13 is constantly being promoted, and you’re told to download it, even though it’s not compatible with Windows XP. No self-protection. The scan speed is so poor that I’m lost for words... The scanning speed is the absolute worst I have ever experienced. Smart Scan was cancelled after 123,226 files!!! and 120 minutes!!! with only 5% progress!!! This is no Smart Scan. I then uninstalled it completely. The uninstallation was done in seconds. That just goes to show how poorly the programme was integrated into Windows XP. It was practically just a superficial add-on. And it can even be shut down completely with just two clicks. That’s a goldmine for malware. My conclusion: Looks great on the outside, but a flop on the inside. P.S.: And that’s the good thing about my ancient P4 computer. It mercilessly exposes the weaknesses of software.

@j7n are adamant on NOT using an extension-based adblocker (e.g. uBO) in the browser, because they harbour the conviction that such an extension would considerably impede their browser's performance ; in the past, both myself and other members here have suggested to them the installation and use of uBO, but they still think that their old ways of dealing with ads (blocking "known" ad-serving domains in their HOSTS file) is still sufficient/effective in the web-ecosystem of 2025+ ... Is this on a UXP-based browser (the object of these megathreads) ? Because if you're talking about recent Chromium/Firefox, these now come with built-in ways of dealing with (some of the) unwanted content ...

Thank you for providing the data! Which version have you tested? Free or Pro?

... 12.5 is for XP no doubt. However I already threw it off my box because it's too cut-down. This statement is not really true. Although IOBit Malware Fighter Pro 12.5 can still be installed strangely enough under Windows XP, it says that this version is not compatible with Windows XP, if the user tries to enable real-time malware protection with IObit & Bitdefender engines or advanced protection against ransomware. It also advises to install IOBit Malware Fighter Pro 11.4 as the last XP-compatible version. And so, after all, this is what applies:

@Tangy But the good is VirIT eXplorer Lite is already a perfect offline scanner with a huge local database. And you can send malicious files to C.R.A.M. at any time. And for disinfection you can use, for example, RogueKiller Free. BTW, Adlice has rebranded RogueKiller Anti-Malware to Adlice Protect which is now compatible with Windows 7 and up only. So, hurry up to get the last XP-compatible version!

I already downloaded it yesterday. But I haven't tested it yet.

Back again. I'm cautiously confident that I've found another workaround for the problem with Panda Dome, and this one appears to have stuck. I was puzzled as to why the crashes, although sometimes apparently at random, could be triggered at will, at least on my machine. One thing which nearly always triggered an immediate crash, even if the system had been running for some time without any, was to click the Windows 'Start' button. This led me to think that there was some issue with Windows Explorer which was triggering the crash. One other clue was that one of the first things I noticed was that if I clicked Start, even if it didn't crash, the user-added shortcuts were a blank box, only populating after several seconds. I tried excluding Explorer from scanning, but that made no difference. I then tried excluding my whole system drive from scanning. Hey presto, no more crashes! So, by a process of elimination, I eventually narrowed it down to the folders which were triggering the crashes when they were scanned. I now have three folders excluded from scanning – Documents and Settings\[Username]\Start Menu Documents and Settings\[Username]\SendTo Documents and Settings\[Username]\Recent So far this has stopped the regular crashes, and Panda has updated without them coming back again. This is pure speculation, but what I suspect happened here is that Panda rolled out an update which broke compatibility with the Windows XP Explorer, which is quite different from that on later versions of Windows, of course. When Panda tried to scan those folders, like the 'Recent' folder being scanned when 'Documents' is clicked on the Start Menu, this triggered a crash. This is of course only a workaround, not a fix, and the problem could come back at any time, but at least on my system it seems to have fixed it for now. There is a security issue with excluding system folders from scanning, of course, but as the folders concerned only contain shortcuts, I would think it's pretty minimal. If anyone else still has a malfunctioning installation of Panda Dome installed, I would be interested to know if this works for them.

https://startisback.com/StartAllBack_setup.exe

It was a very old version long time ago. I don't remember what version number it exactly was. But what about 12.2.2 advertised by COMODO? 😜

You’re welcome! It’s rare for me to be this blunt. But what I went through last night was hell. My entire partition was at risk. The BSOD had wiped out various files. Fortunately, most of them were related to Panda. It was a miracle that I was even able to boot the partition at all. And the fact that Panda could be uninstalled despite the damage was another one. Incidentally, the whole drama started straight after the nightly automatic update that Panda had carried out yet again. I’m a bit reluctant to make recommendations these days, but I can tell you what I did a few days ago, in a moment of foresight. It’s really just a coincidence, but take a look at number 7 on the list you posted. That’s what I recently installed: VirIT eXplorer Lite. Here’s my post: https://msfn.org/board/topic/184730-antimalware-firewall-and-other-security-programs-for-windows-xp-working-in-2023-and-hopefully-beyond/page/101/#findComment-1288687 This antimalware programme is very nice. It is fully compatible with Windows XP, even in the latest version!!! The Lite version is free of charge. If you want to have more protection, you have to buy a license for the Pro version. The programme interface isn’t modern; it’s got a bit of a retro feel to it. That’s what programmes looked like in the 1990s: extremely colourful, with lots of bright colours and plenty of colourful buttons. Personally, I think it’s brilliant. It reminds me of those days. VirIT eXplorer Lite requires very little RAM and CPU power. The virus definitions are downloaded locally to the computer and are therefore available offline. That’s the only reason why the programme folder takes up just over 500 MB. And support is available and active. The intrusion detection shield, called VirIT Lite Monitor, had flagged processhacker.exe as malicious and issued a warning every time the computer started up. I then uploaded the file to VirIT or, to be more precise, to C.R.A.M., along with a message. A day later, the warning had disappeared, as they’d complied with my request to whitelist it. I’m completely satisfied with VirIT eXplorer Lite at the moment. Another reassuring point is that this is a programme developed in Europe – specifically in Italy. I will soon be writing a detailed article about VirIT eXplorer Lite/Pro. Old screenshot of my VirIT Lite Monitor with false positive: New screenshot with Process Hacker 2 whitelisted by C.R.A.M.: Cheers, AstroSkipper

FFmpeg update. XP: static shared libfdk-aac VISTAx86: static shared libfdk-aac The following static links will always match the latest uploaded XP archives: https://files.videohelp.com/u/69760/ffmpeg-win32-XP-static-latest.7z https://files.videohelp.com/u/69760/ffmpeg-win32-XP-shared-latest.7z

And that's one more reason to avoid Avast, at least on Windows XP. I’ve had so much trouble with Avast in the past that I’ll probably never use it again, even on other operating systems. Even though I’m not a fan of Avast, it’s quite possible that the lack of an internet connection is the reason why your attempt failed. Try again with an active internet connection!

My screenshot is a PNG file. The text can be well read, and therefore the sceenshot is ok. It’s not about winning a rendering prize. And as for Mypal 78 on Windows 10, it makes absolutely no sense to use that browser there. There are plenty of up-to-date browsers available for Windows 10. Mypal 78 was designed for older operating systems such as Windows XP. On those systems, more modern browsers are urgently needed – particularly on low-spec computers where, for example, Supermium isn’t an option.

@Dave-H I'm guessing you still have Panda Dome 22.03.05 installed and are dealing with that issue. However, since it seems to be running particularly poorly on your system, you might want to consider uninstalling it completely, performing a thorough cleanup, and then installing Panda Dome 21.01.00 with the option Offline Installation enabled. For me, this version vehemently refuses to let PSANHost crash. The cache folder is now also being filled correctly every day. No leftovers from previous days. Here is a screenshot showing the contents of the cache folder: Of course, I can't guarantee that it will work perfectly for you, but it's definitely worth a try. You really don't have anything to lose.

Yes, we need tests and results under Windows XP. Although I never liked IOBit Malware Fighter, we have to consider all possible and still working options in these days. It's no longer time to be picky.

For experimenting with Avast, you should avoid the last XP-compatible version. As far as I can remember, is a previous version associated with fewer problems. I have to look in my archive for the exact version number. As far as I can remember, there were repeated reports on the Avast forums that avast! Free Antivirus 18.5.2342 runs much better than the latest XP-compatible avast! Free Antivirus 18.8.4084.0.

After Us. Genres: Arcade, Third-person, 3D Requires Windows 10/11, at least starting with v1.1 patch I tried. https://store.steampowered.com/app/1406810/After_Us/

No , but you can always check yourself . It's a 5 min. job to cut these out of the res. file. The browser unpacks these hidden extensions each time you launch it.

@ArcticFoxie , @XPerceniolSpeaking of Gurgle IPs, I tend to think 2206 is more "gurgle friendly" , it talks to gurgle more often compared to 1106. I guess it's quite safe to use it for now . But do block those IPs , trind to find them . I still have this list somewhere , can't find right now. Also , I would recommend blocking ALL inbound traffic for 360chrome.exe on all ports with yout firewall. And block outbound for UDP port 5353 and IP 224.0.0.251 – multicast IPv4 address , mDNS multicasts a UDP packet to it. (at least with 1106)

@XPerceniol , thank you for the kind words ! There was an article (I think called "how to force internet suck less" or smth like that) , it had a ton of gurgle/yackoo IPs which are safe to block {they are useless for us} and will not interfere with casual browsing , but it got deleted ! These were the IPs for tracking , the same IPs that every chrome connects to at the start , including 360chrome , the same IPs that chromium browsers use for key logging.