..:: PCSX2 Forums ::..

hi

i just downloaded 1.2.1 standalone installer from the official pcsx2 homepage.

after i installed it avast av found a
Win32ropper-gen virus in the file
"uninst-pcsx2-r5875.exe"

may be a fals alarm may be not.....



(search in forum found nothing if this is a known prob)

get a suitable anti-virus or add an exception to your current one.
It's of course a false positive

am getting the same problem, fine at 1.3.1-1415. then the problem happens at 1.3.1-1416

https://www.virustotal.com/en/file/f24fe.../analysis/
even if it a false positive i am not downloading it, may i woud if it was one,but thire are 7 error it is getting postive from other 6 scanners

(11-24-2015, 04:15 PM)haloharry97 Wrote: [ -> ]am getting the same problem, fine at 1.3.1-1415. then the problem happens at 1.3.1-1416

get a real anti-virus or add an exception, as said above

This is the time when we moved the buildbot from vcredist2013 to vcredist2015.
I would consider avast trustworthy but all others are at least unknown to me.

Unsure why that happens. (I actually have avast as well at home. I can check that when I am back. I compiled the last versions by myself an didn't get warnings. Don't know about the buildbot though.)

The installer for sure should not have a virus and shouldn't alert avast.
Where did you download it? (Please link to it)
Is avast updated?

Kaspersky reports it too and they are one of the best in the industry. There has been some discussion in bored post here about it. It's related to a pattern match in padnull.



I reported it as false which is why is may not be showing as flagged by Kaspersky in virustotal.

Download the binary archive (http://pcsx2.net/download/releases/windows.html), that package does not contain that file since it is not generated from the installer that reports the false positive if you do not want to add the exception on your AV software

Is this a new result after we moved to vs2015?

(11-24-2015, 06:34 PM)willkuer Wrote: [ -> ]Is this a new result after we moved to vs2015?

Unknown for sure.

It's likely a combination of that and some new malware coming out which happens to have a bit that matches a bit in padnull.dll

Actually I made a test and Kaspersky is still detecting it, I reported it as false positive again.