Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


dencorso

After MSE Game Over: Which Antiviruses are Known for a Fact to be Working on XP SP3 as of May 2019?

Recommended Posts

Posted (edited)
9 minutes ago, mo832 said:

I think I found the problem!!  :thumbup

The first thing I did when the problem started was to go to about:config and look for anything related to "smoothing". Whatever was there did not fix anything, so I moved on to other areas. Today, I had the impulse to go back and scour about:config line by line to see if anything would look to be related.

I searched on "font" and see a bunch of lines related to gfx.* , I played with a bunch of them, toggled, changed values, etc., and when I found the one called gfx.font_rendering.cleartype.always_use_for_content;  it was set to default(false). I set it to true and Boom!!

Now... I think I would have remembered if I had done this myself, even accidentally. There is almost zero chance it was changed by me. How weird would it be to assume that Panda changed this?

 

Well I'm glad you found a fix!
I would actually be very surprised if Panda would have changed that setting, but I can't imagine what else could have done it either.
:)

Edited by Dave-H
Quote added as post has appeared on a new page

Share this post


Link to post
Share on other sites

Most likely, gfx.font_rendering.cleartype.always_use_for_content was always set to false. That is the default value when FF is installed.

Whatever Panda did to Firefox's font rendering, evidently setting that pref to true bypassed or overrode it somehow.

So thankfully, you're back to normal now, but we may never know just exactly what happened.

  • Like 1

Share this post


Link to post
Share on other sites
13 hours ago, dencorso said:

Why don't you just redeploy your backup from just before installing Panda and try again from scratch? :dubbio:

Read this (esp. the 1st Q of the included FAQ):
https://blog.malwarebytes.com/malwarebytes-news/2016/12/announcing-malwarebytes-3-0-a-next-generation-antivirus-replacement/

So, i think it does replace MSE.

One part says "Which Operating Systems does Malwarebytes 3.0 work under?
We continue to support all versions from Windows XP to Windows 10. Our Anti-Ransomware technology is only enabled on Windows 7 and higher."

Is it valid to the latest version of Malwarebytes?

Because i have installed Malwarebytes 3.5.1 as i saw somewere, that this is the latest version compatible with windows XP.

Share this post


Link to post
Share on other sites

Yes it is.
It should continue to receive definition updates for the foreseeable future though.
:yes:

Share this post


Link to post
Share on other sites

I have an "elementary" question but would like some thoughts from you folks because I haven't ever gotten the concept...

What is the difference between malware/ransomware/virus/worm?

What is are the requirements to be considered anti-malware or anti-virus?

Why do we make a distinction, why do we care what it's called, shouldn't we just protect against any "unwanted bad stuff"?

Share this post


Link to post
Share on other sites

In short:

  • malware is any "unwanted bad stuff";
  • virus is a type of "unwanted bad stuff" that reproduces itself, without outside help;
  • ransomware is a type of "unwanted bad stuff" which encrypts one's files (usually just .doc(x)/,xls(x)/.pdf/.jp(e)g) and asks for money to restore (?) them;


There're much more, trojans/worms/internet bombs/etc.

Share this post


Link to post
Share on other sites

Ok, so why do people correct each other when you say "I got a virus", and they say "actually, it's a worm". Who cares? Get rid of it! ;)

What is a "true antivirus" software?

Share this post


Link to post
Share on other sites

One that only catches viruses... I doubt any exist anymore.
However, traditional AVs are, nowadays, signature-based antimalwares, with some heuristics (not always very good) on top of it.
Malwarebytes, OTOH, says it uses their own methods (not clearly disclosed) which appear to be very good heuristics and just a little pinch of signature-based as a seasoning. It just works, though.

  • Like 2

Share this post


Link to post
Share on other sites

On one of my xp machines, I still have malwarebytes v1.65 installed from years ago. The last time I ran it was 2016. A few days ago, I opened it and it prompted me to update the signatures, which I did, and then I ran a full scan overnight. Is this old version, with new signatures, acceptable to run in 2019?  Would it still be relatively effective?

Share this post


Link to post
Share on other sites
On 6/4/2019 at 8:18 PM, Jody Thornton said:

[...] I've removed MSE, and just opted for Malwarebytes v1.75 (with current definitions)

Sure. But maybe you can update to v. 1.75 and it'll still recognize your license as valid.
However, do a full system backup befor messing with AVs. Just to keep on the safe side.

Share this post


Link to post
Share on other sites

I have Malware-bytes Anti-malware free v1.75. It's a good on-demand scanner. Its big weakness is that it doesn't do real-time scanning; i.e., it doesn't automatically scan anything you download or copy/load from a USB drive. You have to remember to do those things yourself, or else upgrade to the paid version.

BTW, Avast hit its first false positive today, with SwiftSearch. I had downloaded the "combined" 32-/64-bit version but it looked like malware to Avast. So I downloaded the "pure" 32-bit version (which is smaller anyway). It works fine without Avast panicking.

Share this post


Link to post
Share on other sites

never thought KAV Free Antivirus was going to work in XP, saw in other forum recomendation to install on XP Sp3, downloaded and installed version 19.0 it's working fantastic so far.. :-)

untitled.JPG

  • Like 2

Share this post


Link to post
Share on other sites

For anyone still struggling to bite the bullet by installing a replacement to MSE (so far I'm finding them all downright scary if not outright destructive and it is just reminding me why I switched to MSE in the first place) these MSE registry changes seem to do two things.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware\Signature Updates]
"ASSignatureDue"=dword:0000016d
"AVSignatureDue"=dword:0000016d

...where 16d = 365 days

They stop the 2001 Event ID errors for Microsoft Antimalware, plus - and this did surprise me - my MSE has turned from orange back to green. This is deceptively comforting as it is obviously purely cosmetic. Even so MSE is not entirely useless as it is still doing its job even as the signature files become increasingly out of date.

I'm guessing this gives 365 days before MSE thinks the 1.293.2807.0 definitions are too old. I'm also guessing the value could be increased even further.

Ben.

Edited by Ben Markson
Typos!
  • Like 2

Share this post


Link to post
Share on other sites
4 hours ago, Ben Markson said:

For anyone still still snuggling to bite the bullet by installing a replacement to MSE (so far I'm finding them all downright scary if not outright destructive and it is just reminding me why I switched to MSE in the first place) these MSE registry changes seem to do two things.


[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware\Signature Updates]
"ASSignatureDue"=dword:0000016d
"AVSignatureDue"=dword:0000016d

...where 16d = 365 days

They stop the 2001 Event ID errors for Microsoft Antimalware, plus - and this did surprise me - my MSE has turned from orange back to green. This is deceptively comforting as it is obviously purely cosmetic. Even so MSE is not entirely useless as it is still doing its job even as the signature files become increasingly out of date.

I'm guessing this gives 365 days before MSE thinks the 1.293.2807.0 definitions are too old. I'm also guessing the value could be increased even further.

Ben.

forget about MSE since you can't update it so it's useless, what's the point for keeping it??

Share this post


Link to post
Share on other sites
7 hours ago, CRK said:

never thought KAV Free Antivirus was going to work in XP, saw in other forum recomendation to install on XP Sp3, downloaded and installed version 19.0 it's working fantastic so far.. :-)

untitled.JPG

.Net Framework 4 or later is listed among the requirements. Do you have .Net Framework 4 installed or is Kaspersky Free working without it?

I never installed any version of .Net Framework on XP. Don't want to start now.

 

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...