Yeah, it seems symantec updated it's virus definitions again and all uninstallation files recognize like Trojan.Zlob. And now i even can't download and run nsis installation package.
Checked using:
Norton Antivirus 2006.
Symantec Antivirus 10.0 Corporate Edition.
Developers, please do something with that idiots in symantec 😉
Nsis is a Great job, btw 🙂
NSIS 2.17 vs Symantec = Trojan.Zlob (here we go again)
23 posts
Well, so you know is a false positive...don't need to be alarm.
Have a nice day 🙂
Have a nice day 🙂
/ot
>> Developers, please do something with that idiots in symantec
rough words - forum, ban these (...) Symantec consumers.
Symatec products always suck - and they suck ev'time a bit more.
I never had a postive false with NOD, but i see lots with Symantec, McAfee, KAV, and some more.
and one more - symantec has a deal with microsoft that some nice tweaking and modifier tools where treaten as virus/trojans/aso.
>> Developers, please do something with that idiots in symantec
rough words - forum, ban these (...) Symantec consumers.
Symatec products always suck - and they suck ev'time a bit more.
I never had a postive false with NOD, but i see lots with Symantec, McAfee, KAV, and some more.
and one more - symantec has a deal with microsoft that some nice tweaking and modifier tools where treaten as virus/trojans/aso.
well I am sure it is a false positive... but people using my installer are reporting Trojan.Zlob found with Norton Antivirus. I can't have that, can anyone do anything about this? or tell me what needs to be done to avoid it?
- Make sure they're using the latest definitions, because this has, as far as I know, already been fixed.
- If it hasn't been fixed, report this to Symantec and give them my e-mail for more details (kichik@users.sf.net).
- Rebuild your installer with another version, such as the newly released 2.18.
Thank you, I'll follow steps 1 and 3 for now.
>> such as the newly released 2.18
And again i miss the News for that...
And again i miss the News for that...
Kichik,
I can second intelworker's issue. SAV 10 corporate with 7/1/06 v8 defs, which are latest as of right now (10:00 AM EST). I'll email Symantec, and give them your info, as I've got over multiple packages deployed to 70,000 users that can't be updated on the fly. ;-)
Thanks for the help.
Mike
I can second intelworker's issue. SAV 10 corporate with 7/1/06 v8 defs, which are latest as of right now (10:00 AM EST). I'll email Symantec, and give them your info, as I've got over multiple packages deployed to 70,000 users that can't be updated on the fly. ;-)
Thanks for the help.
Mike
I think there should be a sticky about false positives
Good idea. I'll see what I can do.
Edit: I'll let Kichik create an announcement post as he knows best 🙂
-Stu
Edit: I'll let Kichik create an announcement post as he knows best 🙂
-Stu
Does 2.18 cause the same problem ?
I had quite a few of my installs wiped out by this latest problem with Symantec.
So far, however, rebuilding them in NSIS version 2.18 seems to have worked. (Using a different compression algorithm may also work, although I've found nothing concrete to support this claim.)
So far, however, rebuilding them in NSIS version 2.18 seems to have worked. (Using a different compression algorithm may also work, although I've found nothing concrete to support this claim.)
Does 2.18 cause the same problem ?I just installed 2.18 to get around this problem. Didn't work. 🙁
I have installed 2.18 and no problems at all.
I had 2.17 installed. Got the error. Found this message thread. Read that 2.18 doesn't have the problem, then downloaded and installed 2.18 (and selected the option to remove the old version). Right after installation, my Symantec deleted lmza_solid as shown in my attached screen shot.
I uninstalled 2.18 and reinstalled it. It didn't happen the second time. Weird.
I uninstalled 2.18 and reinstalled it. It didn't happen the second time. Weird.
Well...instead unistalling NSIS, you can uninstall symantec and try another AV product? 😁
That's what I would suggest as well 😛
Originally posted by JoelAnd what about people using my installer? What kind of trust would I be showing if I tell them to uninstall Norton/Symantec?
Well...instead unistalling NSIS, you can uninstall symantec and try another AV product? 😁
FYI:
After installing updates to Symantec (Corporate edition), the problems went away not only in my installations, but also 3rd party installations (such as the one for FileZilla and InkScape).
Just in case it's useful for anyone, here are the details on the version I was using:
Program version: 10.0.2.2000
Scan Engine: 61.1.0.11
Virus Definition File: 7/3/2006 rev.22
After installing updates to Symantec (Corporate edition), the problems went away not only in my installations, but also 3rd party installations (such as the one for FileZilla and InkScape).
Just in case it's useful for anyone, here are the details on the version I was using:
Program version: 10.0.2.2000
Scan Engine: 61.1.0.11
Virus Definition File: 7/3/2006 rev.22
brummelchen: if you miss new releases, you should monitor them!
Originally posted by JoelI don't use Symantec at home, but it's the standard at my company. But even if it were up to me, I can't make my ~1,000,000 users switch and wouldn't want to.
Well...instead unistalling NSIS, you can uninstall symantec and try another AV product? 😁
AntiVir, also known as Free-AV found the same virus in the installer of Ubisofts "The Settlers II - Heritage of Kings" Demo installer.
Yes, they seem to use NSIS! 🙂
False Positive was corrected in recent definition updates, but i added it to the Wiki 🙂
Yes, they seem to use NSIS! 🙂
False Positive was corrected in recent definition updates, but i added it to the Wiki 🙂