dencorso

Well, I've tested it until today, and finding it works OK for me, too, have just bought the license to have it permanently in premium mode. I've kept MSE, however, because MBAM doesn't require the removal and it remains capable of detecting all that was known to the last definitions file. Moreover, as you all have posted, removing it seems to be a PITA, and I'm not in the mood for such a experience these days. Thanks for the suggestion, @Dave-H! You do rock! And thanks for all who posted here till now, besides Dave. All your posts helped me a lot in deciding what to do. It's wonderful to belong to such a helpful and knowledgeable coummunity!

Yes, it hasn't. However, just for the record, if anyone ever decides to try and do such thing in the right way, this thread at reboot is a must read: http://reboot.pro/topic/18570-extents/ There one'll find injective code that ought to be useful for a properly done kernelex. As I said in the past, the way to do that is to inject code at the run time images of kernel32.dll advapi.dll and some other processes, and use that code to redirect requests for missing functions to modules providing them. Myself, I have not interest whatsoever in even trying to do that. It's too much work, and moving XP to a virtual machine (esp. VirtualBox) just works: I've a experimental one on 7 Ultimate SP1 x64, working great, but which I intend to move to debian stretch x64, probably next month. So that when both XP and 7 x32 eventually become actually unusable I'll just move on to debian for banking and browsing the web, while keeping my loved XP applications runing in seamless mode to do my work, as always. No 10 ever on my end, and may MS rot in hell! Just my 2¢...

Welcome to MSFN, @Mov AX, 0xDEAD! Hope you have here a long and productive stay!

Game Over just for MSE, of course! XP shall live forever, but an Antivirus without current virus definitions has gone the ENIAC way, already.

Sure. Contumacy against the facts leads nowhere. Game Over.

True. That's because they show just a handful of the lates ones... At the time I posted, one still could see:

Done!

Not here.

Is it still possible to acquire Malwarebytes 3.5.1? Or is it only for those who already have aquired it?

It has a "Subsystem Version" = 6.0, which prevents its running on XP, but should allow it to run on Vista, unless there were some missing dependency. It's good to know for a fact it does work. Vista users, then, are all set till Windows Embedded Industry 7 SP1 EoS, on October 12, 2021, at least!

According to MS, v.1.293.2807.0 (released on 6/3/2019 3:24:58 PM) actually is the last one of the 293 series. The next one was already v.1.295.12.0 (released on 6/3/2019 9:08:21 PM), the 1st of the 295 series. See: https://www.microsoft.com/en-us/wdsi/definitions/antimalware-definition-release-notes N.B.: One needs to select the desired version in the "Security Intelligence Update Version" box.

Hi, Usher! Long time no see! Good to have you around! Look, while I don't have either mpa*-fe.exe files, I do have the 2807 definitions (which should be enough for you). I don't know whether those are the very last, but they're certainly quite near it. Here you go: mpxxx_vdm.1_293_2807.0.7z

Yes. I did it, of course. One single dependency missing in ADVAPI32.DLL: EventActivityIdControl Dream on...

I confirm it. On XP SP3, even MSE Updater v1.9 does not succeed in updating the definitions, anymore. It, however, works normally on 7 SP1 (see attached image), so it seems the format of the updates files has changed and the older engine v 1.1.15800.1 does not understand the new v. 1.295.*.* series, while the new engine does. Please do notice I'm still using MSE v. 4.4.304.0 on 7 SP1, specifically to be able to do tests like these. Unless @heinoganda can come with a solution for this, I fear this time it's Game Over for us!

I think (but haven't tested yet) that if one creates a scheduled task that runs MSEU v1.9 every 8h (or maybe even every 12h) should prevent MSE from trying to auto-update, even when keeping the POSReady trick key. And observe that the issue only happens once every 24h, so one that doesn't keep XP running constantly and has MSEU v1.9 in the Startup folder won't ever even notice it.

I think @VistaLover has a point, here. Changing both app.support.* strings to default straight here to this thread on MSFN is easy to do and might be a good 1st step. This @roytam1 might implement already in his next installment of the compiled versions of all browsers he's providing modded versions for XP. It's much simpler than rebranding, uncontroversial and breaks nothing, while being an incontrovertible proof something is actually being done to proactively prevent people from going to PM forums for support.

No, while it sort of worked, it's useless: it just caused two 10005 DCOM errors, instead of and instalation WUA error 20 and the 2003 MSE error. And the 2001 MSE error continued to happen all the same. This is just an interim report, to kee y'all up to date. I'll now try to disable BITS, instead... But I doubt it'll work as intended, either. Yet, the only way to find out is by trying, so I'm going for it. See attached images for more info.

Sure!

Hey! Good to see you around, @submix8c! You have been missed!

http://reboot.pro/files/file/313-offlinereg/...

Then again, there was plenty of drizzle!

That's because there're brooks and creeks galore, and few levees...

Since yesterday, even I am getting those "403 Forbidden"... I guess xper is tweaking the forums...

And it's good to see you this side of the door: hope you brought slurpee, too!

OK. I've just sanitized this thread. Please do post all rampant paranoia posts on the proper thread, instead: The posts that should already have been posted in the above thread were moved into it. Thanks for your cooperation.