Leaderboard

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

For the time being I am trying to avoid going back to a full build which may contain many libraries that nobody uses. It will expand as fixes and requests are added to it. Here is a build for you to test with added support for https. The next release can include it in all builds. https://files.videohelp.com/u/69760/ffmpeg-8.2-2237-b4b30ff8fd-win32-shared-xpmod-P4.7z

Thank you once more for these new releases ; however, I have to report that the latest ffplay.exe compiles for Vista x86, BOTH the static+shared binaries, are completely broken under Vista SP2 x86 (with ALL MS updates until EoS, and then some ); whatever media file you throw at FFplay.exe (e.g., via drag-n-drop) results in the app instantly crashing; below, an instance of a plain MP4 file containing h264 video + aac audio: Your previous VISTA release works as expected with that same MP4 file: FWIW, your latest FFplay.exe static compile for WINXP doesn't suffer from this issue and plays the MP4 file without any problem: You'll probably need a Vista SP2 x86 VM to troubleshoot this, as I have no clue as to what might have gone wrong; perhaps an updated third-party lib has in the interim (n8.2-dev-1568...n8.2-dev-2232) removed support for NT 6.0? We know it's not caused by upstream (FFmpeg source code), because your n8.2-dev-2232 compile for XP works OK; in addition, when I probe the MP4 file with latest FFmpeg for VISTA, it doesn't crash: ffmpeg version N-125505-gc57660fb18-WINVISTA Copyright (c) 2000-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 61. 2.100 / 61. 2.100 libavcodec 63. 5.100 / 63. 5.100 libavformat 63. 3.100 / 63. 3.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 Input #0, mov,mp4,m4a,3gp,3g2,mj2, from 'Mastermind_Se8Ep12[2494504515559].mp4': Metadata: major_brand : isom minor_version : 512 compatible_brands: isomiso2avc1mp41 encoder : Lavf62.13.101 Duration: 00:25:41.93, start: 0.000000, bitrate: 968 kb/s Stream #0:0[0x1](und): Video: h264 (Main) (avc1 / 0x31637661), yuv420p(progressive), 768x432 [SAR 1:1 DAR 16:9], 837 kb/s, 25 fps, 25 tbr, 90k tbn (default) Metadata: handler_name : VideoHandler Stream #0:1[0x2](eng): Audio: aac (LC) (mp4a / 0x6134706D), 48000 Hz, stereo, fltp, 125 kb/s (default) Metadata: handler_name : SoundHandler At least one output file must be specified Hopefully you'll be able to get to the bottom of this, as I do use FFplay.exe myself under Vista SP2 (32-bit) ; thanks for all your hard efforts already!

Versions for XP. All full versions work fine. The lighter, stripped-down versions, including the latest one, do not support HTTPS. For example: ffplay.exe -i “https://paranormalium.waw.pl/radio/8000/mp3_48” ffplay returns this error: https or dtls protocol not found, recompile FFmpeg with openssl, gnutls, or securetransport enabled. https://paranormalium.waw.pl/radio/8000/mp3_48: Protocol not found So here’s my question: Could you release the full version for XP at least once in a while? The lightweight versions are great, but there are always unexpected issues with them, just like in this case.

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

Yeah, that's what they're doing to us. Anyhow - a few pieces of news: a) with Panda installed going into WinXP SafeMode takes about 1 minute or maybe more (feature?) b) Panda 21.01 hasn't worked here either - same problems c) Avast 18.5.2342 - now I know why it wants internet - because even if you choose manual update in "Program update" it will do it in the background (instup: their setup) and update to 18.8.2356 (18.8.4084.0 internally) and then wants you to restart. But then again we come to the csrss overloading, so - a non starter. d) IOBit Malware fighter 11.4 works well and updates to july 2026 definitions. e) Today I punched into Serpent search engine iobit malware fighter xp and there was also a find of sourceforge, so went there, downloaded it and it's a 12.5.0.1545 and it installs and works merrily on WinXP. I believe it's a keeper.

Well, folks, things are about to get tough. After restarting my Windows XP partition with Panda Dome 21.01.00, the PSANHost.exe process crashed again immediately - and this time it was a major crash. The main process, PSUAMain.exe, then froze completely. Nothing was working anymore. Here's some log and dump data: And then things got even worse. A BSOD, caused by the Panda Network Filter Driver psinknc.sys. This was the first BSOD for years. Here is the message and part of the dump file analysis: After that, I tried to boot into safe mode, but I couldn't get in. Somehow, after three partitions were scanned by scandisk, I managed to boot into the partition normally again, and I immediately uninstalled Panda Dome completely, including an additional deep clean. Forget about Panda Dome entirely, whether it's version 21.01.00 or 22.03.05! Since the 2. of July, Panda has destroyed compatibility with Windows XP and compromised it by faulty, incompatible updates. Currently, the following applies: Stay away from Panda on Windows XP! Nothing works anymore without an official fix or patch. That’s it for Panda as far as I’m concerned. I’m absolutely livid. P.S.: The minidump content is incomplete due to the totally faulty forum editor. One can’t post sensibly here anymore.

Long time ago, I used COMODO Antivirus for a short time. It didn't convince me even back then and I uninstalled it. But COMODO Internet Security Premium 12.0.0.6818 was, in fact, the last version that was claimed in some forums to run flawlessly on Windows XP. So if this version doesn't work properly anymore, you can forget about COMODO as antivirus protection. P.S.: I found this one here advertising the use under Windows XP: https://antivirus.comodo.com/security/free-antivirus-xp.php

@VistaLover Thank you for reporting the problem. I will investigate and make new builds.

FYI, today I contacted Panda Security by telephone via AnyTech365 and informed them of the problems with Panda Dome's PSANHost process on Windows XP, which have been ongoing since 2 July. There are indeed free of charge helpline numbers for all sorts of countries, and as many users as possible should get in touch. Here is the page with the telephone numbers: https://www.pandasecurity.com/en/homeusers/free-antivirus/support/ So please leave a message there. Call them! The more people who get in touch, the better.

... But the author has already mentioned that : The community of XP-using members here has to reach a consensus as to what should be the minimal configuration of the FFmpeg/XP compiles, so that autodidact doesn't have to jump through hoops to try and satisfy each and every one of you ; remember, this most kind person is offering an invaluable service out of the goodness of their heart ; compiling binaries is a time and CPU (read: electricity) consuming convoluted process...

Here it is: https://sourceforge.net/app/iobit-malware-fighter/

Somehow, I have a sixth sense. The PSANHost.exe process just crashed after running without errors for three days. Here is the error message and the contents of the PSANHost.exe.mdmp dump file extracted with WinDbg: As I said, you shouldn't get your hopes up too soon. This time, it also has to do with the DLL file PSANModProcMon.dll. Maybe try turning off Process Monitor . I'm glad there's no Panda Dome on my primary Windows XP partition at the moment.

Panda Dome 22.03.05 has been significantly more unstable on my primary Windows XP partition – which has all the POSReady 2009 updates installed – since 2 July than Panda Dome 21.01.00 on my secondary Windows XP partition, which does not have the POSReady 2009 updates installed. As the crashes were all related to the important system file ntdll.dll, I am now wondering whether the version of ntdll.dll also plays a role. This system file was installed with the POSReady update KB4493563 in March 2019, of course only on my primary Windows XP partition. Today, during a test of Glarysoft Malware Hunter, this programme also caused an error related to the ntdll.dll file. Coincidence?

It’s best not to celebrate just yet; wait until the PSANHost.exe process has been running stably again over the next few days or weeks. It may be stubbornly refusing to crash, but as we’ve learnt the hard way, this monster is capable of behaving quite differently. Please report here if it crashes again!

@Tangy Perhaps you can try Panda Dome 21.01.00. I am under the impression that this version is working better on Windows XP. It's definitely worth a try. @Dave-H That's what I replied to @Tangy.

Panda 22 is still warning me about dodgy website links embedded in other sites, so I guess the protection is still OK at the moment. Do you have a link to the offline installer for 21, should I need to use it?

I assume that these updates are for offline protection. So blocking them may lead to fail detecting malicoius threads when disconnected to the internet. But as long as you are connected to the internet, Panda Dome should actually use the cloud engine for scanning files. That's the right attitude.

That’s, of course, the ultimate way to block incompatible updates. But that wasn’t what I suggested. Not keen on Panda Dome 21.01.00? It’s running without any problems for me at the moment.

If I wanted to, I could switch to other fonts that look much nicer and more professional in a matter of seconds. It’s really simple to do this in the Mypal 78 settings or using a CSS stylesheet, which I can load on the fly at any time via my forked UserCSSLoader script. But as long as I can read everything clearly, I couldn’t care less about the font used.