Leaderboard

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.

... 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!

For example Eset : Here is how to get it for XP: Click on link https://www.eset.com/us/home/online-scanner/ >Towards bottom of web page click 'Choose language version' >Under 'Download Options' click 'Choose other product version' >Under 'Configure download' click the down arrow of 'Version' and select Version 2 ('Operating system' window will show XP)>click 'DOWNLOAD'. Hope that still works. It did about a year ago.

About the 60 days , we could always use an on/off line scanner. Let us also no forget, beggars can't be choosers. Could you please elaborate on panda. thank you.

Interesting, indeed. But unfortunately, I can't test that at the moment. As I already reported, I uninstalled and removed all related to Panda Dome. And due to the serious crash I had I really don't know if I want to give it a try at the moment. But what about your support ticket? It's nearly one week ago. Surely they must have replied at least once to let the customer know what the status of the support ticket is.

The best would be to look for a new email provider!

And again a single sentence statement. Which crucial features do you miss in the free edition of IOBit Malware Fighter? And why don’t you get a 6-month licence for the Pro version? You can find them everywhere, and they’re even available at regular intervals. IOBit runs lots of promotions. I managed to get hold of some yesterday. This gives you the opportunity to test the programme thoroughly, exploring all its features, and then report on it in detail here. Here is a feature comparison: https://www.iobit.com/en/malware-fighter-pro.php Or take this one: Use this to clarify your point!

And what exacty does that mean? The problem with one-sentence statements that contain no information is always the same. They’re of no use to anyone. And the reader is then left to guess, interpret or make assumptions, which only lead to rumours and wild theories. That is completely counterproductive. So please provide a bit more information! By the way, have you already reported your problems/issues/errors with Panda Dome on Windows XP to Panda’s support team?

A review Of VirIT kind of old but I would say rather indicative of what to expect 12 years later. https://www.insightsintechnology.com/2014/01/virit-explorer-lite.html @AstroSkipper Conidering this plus the post right above this one, I think I am going to get myself an AV..

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

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!

What I now expect from an anti-malware programme is that it simply warns me of any threats. No automatic removal, as I’ll take care of that myself should one ever arise. I have my own specialist tools for that. And most alerts are false positives anyways. It’s very important that it uses very little RAM and CPU. That’s why I think VirIT eXplorer Lite is great for my system. And I prefer real offline definition updates. Cutting down unnecessary features is therefore no problem for me.

@modnar Or do you use an extended kernel or an additional layer in your Windows XP installation where you have installed IOBit Malware Fighter 12.5?

I also mentioned that very often, people who use Windows XP also use the latest versions of Windows, such as 10, 11 and so on. If you’re completely disappointed by one operating system in terms of Panda Dome, it doesn’t reflect well on the others. Here is aditionally a screenshot with nearly all Panda hotline numbers at no costs: All Windows XP users here on MSFN and all guests reading this thread! Call them and report your issues with Panda Dome under Windows XP!

That's great, but as you say, it has to be more than just you and me! Especially good that they now have reports from two different countries. 👍

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.

Check all available log or dump files! Maybe, there you get a hint.