Leaderboard

And if anyone thinks that there is hardly anything worse to report about SUPERAntiSpyware, I have to disappoint them. We now come to the "official support" for SUPERAntiSpyware, which has since been taken over by the American company USTechSupport. If you want to fill out the online form on the SUPERAntiSpyware homepage, you are required to provide a telephone number. Rejected! An email to support is answered immediately, but of course by a bot. You can write whatever you want, but you won't get any help. Just a recommendation that it's best to use the telephone support. And for this information, the support ticket is then marked as resolved. I've never seen such rubbish. The hotline is probably chargeable. It all smells like a rip-off. That wasn't the case when I contacted SUPERAntiSpyware support the last time years ago before it was acquired by RealDefense LLC in 2023 which is also an American company. But when it comes to America, nothing surprises me anymore.

FFmpeg update. XP: shared static libfdk-aac VISTAx86: shared static libfdk-aac

It used to be (intentionally) broken to burden (very high CPU usage) the csrss.exe service (as seen in Task Mgr). I've installed Avast (from v18 online installer) in my testing XP_VM and will tell you tomorrow. Today everything was calm. Avast and AVG in their new, broken, state begin to burden the system through csrss.exe the next day... EDIT: The results are in and nothing changed: AvastSvc.exe constantly eats up ~25% of (dual-core configured) CPU in VM and csrss.exe eats up the other 20% of (dual-core configured) CPU. So both take up almost 1 whole core! That is outrageous, but Avast got our data, they don't care.

I also tested again the real-time protection module of SUPERAntiSpyware. The CPU usage on my old computer is high and completely unacceptable. Therefore, a Professional licence is not worthwhile at all on low-performance computers.

SUPERAntiSpyware stopped Windows XP support with the version 10.0.0.1254 which was the last working installer version. Until the end of last year, it was still possible to update to version 10.0.0.1266 via automatic updates. Since the beginning of the year, this is no longer possible. Users are constantly being nagged to perform a programme update under Windows XP SP3 32-bit that renders the entire installation unusable after application. This is because it updates to the 64-bit version 10.0.0.1282. The old files are of course overwritten, and anyone who has not created a backup beforehand is lost. Luckily, after hours of searching, I found a Norton Ghost image of my other XP partition with the last changed files when SUPERAntiSpyware was updated to the version 10.0.0.1266. That's why I was able to manually restore the destroyed installaton. Furthermore, the size of the virus definition file that is downloaded has increased significantly. As before, it takes forever to load. The only good thing is that the definitions are still being updated at all. So, nothing is fine. You don't need one. I've had a lifetime licence for the Professional version since 2013. It used to be worth something when Windows XP was still supported. Those days are finally over.

Today, I have uninstalled Panda Free Antivirus 21.01.00 and installed Panda once again but via their online installer. The version installed by their online installer is 22.03.05. The online installer downloads the legacy installer FREEAV_LGC.exe (117MB) and not the common FREEAV.exe (161MB) under Windows XP. Unfortunately, the version 22.03.05 needs much longer for starting when booting Windows XP. It is round about 5 to 6 minutes on my old machine. The culprit is the process PSANHost.exe which places very high demands on the CPU, up to 99%. The previously installed version 21.01.00 only needed 2 minutes. I'll keep the currently installed version a while just for testing purpose but I think I'll go then back to version 21.01.00. The next days, I'll use to see how this version behaves in my system doing all the things I usually do.

The site duck.ai are known to not work if the config "security.csp.enable" are set to true.

Here are some facts about the sizes of SUPERAntiSpyware's virus definition files from 2024 to 2026: SASDEFINITIONS.EXE 210,345,304 bytes 07.07.2024 SASDEFINITIONS.EXE 214,737,232 bytes 27.05.2025 SASDEFINITIONS.EXE 353,800,400 bytes 23.01.2026 The virus definition file SASDEFINITIONS.EXE has increased by 4,391,928 bytes from July 2024 to May 2025, which is a normal increase of approx. 2% within 10 months. From May 2025 to January 2026, however, it increased by 139,063,168 bytes. This is an unbelievable increase of approx. 65% within only 8 months and definitely a no-go. The file has become totally bloated for whatever reason. Now, I finally know why the download takes much longer time than before, apart from the catastrophic download speed on their update server, which is used by the programme.

I don't know about American phone numbers but you should know that. The number is (801) 523-6766.

And after all these facts, here is my theory about what could be behind this destruction of 32-bit installations. Users are offered a programme update for SUPERAntiSpyware, and then, after the damage has been done, they are ripped off with great telephone support (because all is great there ) and whatever else. This is what my cat has to say about it:

Athough I have disabled the checking for programme updates in SUPERAntiSpyware's settings, every time I start it up or update the definitions, I am annoyed by the usual pop-up promising a programme update. Therefore, I would like to warn you against updating the programme via Automatic Updates at this point. Stay at the version 10.0.0.1254 or uninstall it!

So I was hoping to get a pic of my 95 *upgrade* cd (would be very FIRST version sold at college campus bookstore, there were "A", "B", and "C" releases of 95). I have three prime-suspect locations to search in my "small hoard", but I could not find it Online reading seems to label releases as RTM, Plus, SP1, OSR1, OSR2, OSR2.1, OSR2.5, but I simply *do not remember* them being called that when being sold at the college bookstore, I remember them being called 95a, 95b, and 95c and I know mine would have been the VERY FIRST and that it was an "upgrade" and does *NOT* have the "for sale only with new pc" on its label. Online reading also seem to suggest that the difference between "retail" and "oem" is whether it *includes* Internet Explorer and/or which *version* it includes. From memory, I guess I do not remember it rolling out that way. Here in the USA, the largest (be it "good" or "bad" is a discussion for another day) consumer market, we-in-the-US think of the word "retail" as a distinction of WHO can BUY the item. *Supply Chains* are broken down into classifications like "Tier 1", "Tier 2", and "Tier 3". In the vane of an *OEM* (Microsoft) building/creating Win95 and SELLING it, if Acer, IBM, NEC, HP, Dell, Packard Bell, Texas Instrument, and the like could BUY them to INCLUDE in their manufactured-then-sold computers, that is not (at least here in the US) considered as *RETAIL*. If Amazon, Best Buy, Radio Shack, Tiger Direct, Costco, Walmart *retail stores* were allowed to BUY them and turn around and sell to people like you and me, THAT is considered a *RETAIL* item. I guess I see things that way. But maybe the rest of the world doesn't?

Speaking of latest antiviruses, has anybody tested the latest Avast database definitions for v18? I know they have discontinued the XP compatibility check recently, but i'm curious if Avast can be still used as a real time protection AV? I'm not a fan of cloud only protection like Panda, even though currently it's the best solution for antimalware protection other than SUPERAntiSpyware (the definition updates are still being released, just checked on my XP x32 VM), which is fine for me. If only i had a key for Pro edition...

When I set up my Win 7 notebook two years ago I had wanted to use TinyWall as a firewall ... it was listed as a simple firewall that worked. However, it was listed for only Windows 11 / 10 so I went with an older version of ZoneAlarm that worked with Win 7. It works good as just a firewall, no complaints. Just two days ago I discovered that there was an older TinyWall version that did work with Win 7. https://tinywall.pados.hu/ TinyWall is a lightweight, user-friendly, and secure firewall for Windows. It is also completely free. Under FAQ: The latest version of TinyWall runs on Intel- or AMD-based Windows 11 / 10. An older version, TinyWall 3.2.5, also supports Windows 8.1 / 8 / 7. Just asking if anyone is using TinyWall 3.2.5 on their Win 7 setup and if you have any comments, good or bad? Thanks ...

Many thanks, indeed ; but the naysayers/doubters are again back at it, one of them even went as far as to downvote your comment; I posted one last "analysis" there, but, frankly, I'm totally disheartened by all those "experts of today", who leave no room for old-school volunteers like myself ... Well then, I, you, Reino (and possibly others) know that the IOS HLS formats do still work, let the masses on GH's issue tracker stick to their reservations ...

Bound means prelinked, a rarity these days. An address will appear there that should match the function address in the lower box. If so, the load will be faster, if not, a bit slower. Early versions of my ImportPatcher could validate bound import links.

Done.

It works now. But let me say one thing. While it is legit to complain as I did, and also helps to know what is the issue and see if I can fix, or can be fixed, if it is necessary to use the latest curl_cffi, just do it. Don't downgrade because a person complains. If I can use the x86, awesome, I'll use. In cases as with this tool, how many times are we dealing with over 2³² of data/memory needs to use the x64. It is more a matter of slightly better performance. off-topic from here Now, about the "modern DNS extensions". Actually they aren't modern... I mean, the original proposed standard RFC is from 1999, and then ratified as internet standard on 2013. It is fair to use it, but, why now? If I could I would update the hardware, OS, software, but... I don't live in a world of magic.

I don't think there will be many users of the 64-bit version that also have an old local DNS resolver, but nevertheless I will downgrade curl_cffi to version 0.13.0 for the next release. Forcing these modern DNS extensions on a legacy-OS target is counter-productive anyway. Meanwhile, here is a 64-bit test version, so we can see if curl_cffi 0.13.0 doesn't give issues for you with 2026.01.19.143412.

Sweet! I'm so huge into *everything* PORTABLE that I have never installed *any* C++ runtime. None. Naughta. Zilch. I prefer to manually place the SMALL HANDFUL of .dll's that some programs require to be SELF-CONTAINED within that program's OWN ROOT DIR. It's almost always the same two or three or four .dll's and even though my setup has those existing as "duplicates" across my hard drive, it's still MUCH LESS space than the full runtimes. Kind of like how several .dll's land in the root dirs of things like Supermium, Mypal, Serpent, etc.

@johk What happens if you switch to the 32-bit yt-dlp variant for Win7 ? https://github.com/nicolaasjan/yt-dlp/releases/download/2026.01.19.143412/yt-dlp_x86_win7.exe That one doesn't come with the curl_cffi Python module bundled (it's currently only 64-bit); some sites require this module to work, but NOT youtube.com (yet) ... curl_cffi is a Python binding (wrapper) for curl-impersonate, not for "ordinary" curl ; curl-impersonate uses Google's BoringSSL crypto lib (not Libre/OpenSSL), making it incompatible with < Win7 (I have Vista) ... curl 8.15.0-IMPERSONATE (Windows) libcurl/8.15.0-IMPERSONATE BoringSSL zlib/1.3 brotli/1.1.0 zstd/1.5.6 c-ares/1.30.0 WinIDN nghttp2/1.63.0 ngtcp2/1.11.0 nghttp3/1.9.0 Release-Date: [unreleased] Protocols: dict file ftp ftps gopher gophers http https imap imaps ipfs ipns ldap ldaps mqtt pop3 pop3s rtsp smb smbs smtp smtps telnet tftp ws wss Features: alt-svc AsynchDNS brotli ECH HSTS HTTP2 HTTP3 HTTPS-proxy HTTPSRR IDN IPv6 Largefile libz NTLM SSL SSLS-EXPORT threadsafe Unicode UnixSockets zstd

Or generally on old machines with a single-core processor. After restarting my computer, it additionally installs or updates some modules like, for example, NNSNAHS (Network Activity Hook Server Service) which makes starting much worse. Now, I get a popup that no firewall is installed for a short time, and Panda gets deactivated. A further one minute later, it finally activates itself. So the start was extended by at least another minute. Not good.

There is no noticeable increase in startup time with 22.03.05 on my machine, it seems perfectly normal as it was before Panda was installed, so I can only assume that it just doesn't run well on your particular hardware.

I am very interested in both since I have none of them. Can you upload them in any way?

My .NET Framework 4 is version 4.0.30319. Where does yours come from? Do you have a link or the installation file?

Forgot say, the laptop is from 2013, based on Haswell Pentium mobile 3550M. https://ark.intel.com/products/77404

So I got some time today, I tried the driver, I had to add my device inf., it installed fine, but gives error 43 code.

It's meaningless, since many people simply don't report crimes, don't want to get involved with the police, etc, and the issue is rather serous (remember the scandal you mentioned), Supermium browser, which this one is based on, is paid.

It doesn't work that way, here we respect intellectual property, even though we understand most of it belongs to another man (win32), despite all of the above, there needs to be a clear statement with Open Source code published by the author, none of that happened, so far.

Why not release a better optimised product together, then? One million releases with constant fixes only confuses people. And what does he mean by "legacy" Thorium repo? It's also confusing since Windows 7,8,8.1 are all legacy, too.

I assume it depends on the version of wsusscn2.cab file you have used for offline scanning. My version is of 11/12/2019 and works like a charme.

Of course you'll lose your update history. My suggestion was to make an image of your OS partition to revert back at any time you want. I can restore my whole system in less than a half hour (very old computer, very slow). Your Windows Update history is located in "DataStore.edb". So you can backup this file at first. In your Windows Update Log you can see clearly: 2022-01-27 12:28:48:824 1860 1560 Agent *********** Agent: Initializing Windows Update Agent *********** 2022-01-27 12:28:48:824 1860 1504 Report WARNING: Reporter failed to upload events with hr = 80240004. I guess there is a problem with your Windows Update Agent. I have added a link of "winUpdRestore!v28" right down at the bottom, a more recent version of "winUpdRestore!v23". I used it first. Then you have to reinstall Windows Update Agent. Resetting of SoftwareDistribution folder is not the same. I suggested you: After this procedure you have to reinstall "Restore_WU_XP_2003". Here you have to check if "install.cmd" did its job properly i.e. all commands in "install.cmd" have to be performed properly. Check the correct version of "wuaueng.dll" in both folder system32 and system32\dllcache. Check if all registry entries have been added. If not do it manually by creating a reg file for importing necessary entries from "install.cmd" and copying wuaueng.dll first in folder system32\dllcache and then in folder system32. And what about some posts before where So a lot to do! https://www.mediafire.com/file/xn2a1rlriapkhym/winUpdRestore%21v28.zip/file

Alright, here is the Windows Update Log from my flawlessly MU accessing system: https://www.mediafire.com/file/iflfdi6ncoceop8/Windows_Update_2022_-_AstroSkipper.7z/file @Dave-H Comparing my log file to yours you can see what entries you have to have access MU successfully: 2022-01-27 11:49:29:484 1128 b48 Misc =========== Logging initialized (build: 7.6.7600.256, tz: +0100) =========== 2022-01-27 11:49:29:625 1128 b48 Misc = Process: C:\WINDOWS\System32\svchost.exe 2022-01-27 11:49:29:625 1128 b48 Misc = Module: C:\WINDOWS\system32\wuaueng.dll 2022-01-27 11:49:29:484 1128 b48 Service ************* 2022-01-27 11:49:29:625 1128 b48 Service ** START ** Service: Service startup 2022-01-27 11:49:29:625 1128 b48 Service ********* 2022-01-27 11:49:30:812 1128 b48 Agent * WU client version 7.6.7600.256 2022-01-27 11:49:30:812 1128 b48 Agent * Base directory: C:\WINDOWS\SoftwareDistribution 2022-01-27 11:49:30:843 1128 b48 Agent * Access type: No proxy 2022-01-27 11:49:30:875 1128 b48 Agent * Network state: Connected 2022-01-27 11:50:21:546 1128 b48 Agent *********** Agent: Initializing Windows Update Agent *********** 2022-01-27 11:50:21:546 1128 b48 Agent *********** Agent: Initializing global settings cache *********** 2022-01-27 11:50:21:546 1128 b48 Agent * WSUS server: <NULL> 2022-01-27 11:50:21:546 1128 b48 Agent * WSUS status server: <NULL> 2022-01-27 11:50:21:562 1128 b48 Agent * Target group: (Unassigned Computers) 2022-01-27 11:50:21:562 1128 b48 Agent * Windows Update access disabled: No 2022-01-27 11:50:21:562 1128 b48 DnldMgr Download manager restoring 0 downloads 2022-01-27 11:50:21:593 1128 b48 AU ########### AU: Initializing Automatic Updates ########### 2022-01-27 11:50:21:593 1128 b48 AU AU setting next sqm report timeout to 2022-01-27 10:50:21 2022-01-27 11:50:21:609 1128 b48 AU # AU disabled through User preference 2022-01-27 11:50:21:609 1128 b48 AU Initializing featured updates 2022-01-27 11:50:21:625 1128 b48 AU Found 0 cached featured updates 2022-01-27 11:50:21:625 1128 b48 AU AU finished delayed initialization 2022-01-27 11:50:22:890 1128 b48 Report *********** Report: Initializing static reporting data *********** 2022-01-27 11:50:22:890 1128 b48 Report * OS Version = 5.1.2600.3.0.65792 2022-01-27 11:50:23:078 1128 b48 Report * Computer Brand = MICRO-STAR INTERNATIONAL CO., LTD 2022-01-27 11:50:23:093 1128 b48 Report * Computer Model = AWRDACPI 2022-01-27 11:50:23:109 1128 b48 Report * Bios Revision = 6.00 PG 2022-01-27 11:50:23:109 1128 b48 Report * Bios Name = Award Modular BIOS v6.00PG 2022-01-27 11:50:23:109 1128 b48 Report * Bios Release Date = 2002-10-24T00:00:00 2022-01-27 11:50:23:109 1128 b48 Report * Locale ID = 1031 2022-01-27 12:50:23:968 1128 b48 AU AU received policy change subscription event 2022-01-27 12:50:33:703 1128 b48 AU AU received policy change subscription event There are no "warnings" related to wuident.cab as show in your log file: 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:214 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:558 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:25:902 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: Send failed with hr = 80072efe. 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: SendRequest failed with hr = 80072efe. Proxy List used: <(null)> Bypass List used : <(null)> Auth Schemes used : <> 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestUsingProxy failed for <https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab>. error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation MakeRequest failed. error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: SendRequestToServerForFileInformation failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: WinHttp: ShouldFileBeDownloaded failed with 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Misc WARNING: DownloadFileInternal failed for https://www.update.microsoft.com/v11/3/legacy/windowsupdate/selfupdate/wuident.cab: error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup FATAL: IsUpdateRequired failed with error 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed: 0x80072efe 2022-01-27 12:29:26:261 1860 1504 Setup WARNING: SelfUpdate: Default Service: IsUpdateRequired failed, error = 0x80072EFE 2022-01-27 12:29:26:261 1860 1504 Agent * WARNING: Skipping scan, self-update check returned 0x80072EFE 2022-01-27 12:29:26:339 1860 1504 Agent * WARNING: Exit code = 0x80072EFE 2022-01-27 12:29:26:339 1860 1504 Agent ********* 2022-01-27 12:29:26:339 1860 1504 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates] 2022-01-27 12:29:26:339 1860 1504 Agent ************* 2022-01-27 12:29:26:339 1860 1504 Agent WARNING: WU client failed Searching for update with error 0x80072efe So my first quick conclusion is you have to reset your Windows Update client and install two versions one after another (the order is important). At first WindowsUpdateAgent30-x86.exe and then WindowsUpdateAgent-7.6-x86.exe using the option /WUforce e.g. WindowsUpdateAgent30-x86 /WUforce and WindowsUpdateAgent-7.6-x86 /WUforce. For resetting Windows Update there is a nice tool I used when I had problems with MU. It's called winUpdRestore!v23. If you don't have it or you can't find it I can upload for you. These steps would have been my next suggestions for you in any case. I did these steps definitely when I fixed my system. You should backup your partition by making an image using Norton Ghost for older computers and Aomei, Macrium or Acronis for newer ones if something is going wrong or you have to revert back. Hope we'll get ahead.

@Dave-H You was too quick in replying! But I agree. Delete it!

You're absolutely right. My screenshot belongs to current user. When you compare yours to mine there is one thing strange and this is your Microsoft Root Cerificate Authority 2011. You have twice and I don't know why. If it were my system I would delete the one with "Friendly Name" <none>.

Same here. Aero not working .

This is realy fantastic !

Yes, all of them . Opera's own launcher and installer not needed (you only need your portable launcher) , also may throw away opera_autoupdate and opera_crashreporter . (!) How needs that ?

I'm not seeing it imported either. Not sure if this is even possible, but do you have an extension or plugin generating imports that Firefox itself is not importing? Again, not even sure if this is possible (but I know it can be done in Edge [corporate environment]).

First of all, thanks for uploading the files! I was surprised to learn that there is supposed to be a .NET Framework version 4.0.30320 for Windows XP. I couldn't find anything about it in any official source. In any case, your installer "Microsoft .NET 4.0.30320 Full" is the same one I have, and it has the number 4.0.30319.1. Presumably, at least for Windows XP, there is no version 4.0.30320. You can find out your current version installed with the following command: reg query "HKLM\SOFTWARE\Microsoft\NET Framework Setup\NDP\v4\Full" /v Version Although it is actually Microsoft .NET Framework 4.0.30319, I have nevertheless found a reference to version 4.0.30320 in Windows XP. Apparently, the Client Profile and the Extended are assigned exactly this version number:

Do you really mean KB2890375 and not KB2890573? The latter is already in my archive and can still be downloaded. It is of version 10.0.40219.457.

Today, Panda Dome 18.07.04 has been automatically updated to version 20.02.01 on my Windows XP partition. At the moment, no significant delay when starting the computer. So, you have installed Panda Dome, too. How does your main interface look like? Can you post a screenshot? On my POSReady partition, no interface background images are shown, quite unlike my partition without POSReady updates. I think that there is some kind of problem in my POSReady partition.

I didn't notice any problems while installing or uninstalling. About running for a longer time with real-time protection I can't say anything but the portable installation can't produce any compatibility issues. BTW, my Malwarebytes Premium 3.5.1 installation still exists on my Windows XP partition.

@Dave-H The more recent portabel versions create a sub-directory called RogueKiller with some files, i.e. settings, logs, reports and signatures inside. But they do not load any drivers which, however, are necessary for real-time protection. Apart from that, I already posted a screenshot of the main interface of the portable version where I marked red: Schutz in Portable-Modus nicht verfügbar which means translated: Protection not available in portable mode. BTW, I found this in their changelog: Although the most recent installer version 16.5.4.0 wasn't able to load its driver when I tested it, it is possible that some previous installer of version 16 still work under Windows XP, even if the Adlice homepage now requires Windows 7 as a minimum requirement. Have a look here: Maybe. it is again an issue of the free version. What you can do is to try out the most recent installer version or a previous one as a 30-day trial version. Then you will definitely know and can report back here.

But only in the hope that the older installer versions will continue to be supported and supplied with signatures. You buy a license, but the current installer can no longer be used under Windows XP. The portable version is unfortunately restricted compared to the installer one.

That would be too easy, reminds a second grader school project. And most importantly, why would someone do that for a member who is not here for a year? Probably already forgot and chills somewhere on Bahamas. Last but not least, ask the admins to look at the logs! They will show real IPs.

My version of 11/12/2019 is probably the same that you have used from November 2019. Then it works offline with this version but using WSUS server + WUMT doesn't work in your system. Is that correct?

I haven't tested Option 3 in my system (no need to do) but Option 1 works perfectly too such as Option 2. What's the problem with WSUS server + WUMT in your system?

Hi , I'd like to add . All versions starting from Opera 69 do NOT remember extensions' settings . They revert all settings to default if the browser is re-launched. Chromium is even worse . It simply turns them off (tested on chrome 86). I mean the extensions without locale settings , which I managed to install.

You see , you've just confirmed what win32 have been saying , you don't need to go any further than April 2017 for system replacement (yet you don't listen again !) , and the instructions were not deleted , they are here , repeated many times in the comments . I'm not gonna respond you anymore , please write to someone else and refrain from asking me and win32 the same questions over again , if you don't respect me , at least show some decency towards his marvellous work. Don't want this to end blocking you up completely . Edit : Better to use internal messaging and not pollute this topic with personal instructions , thanks. Goodbye.