Final version of NOD32 2.12 released

[flyrfan111]

I think 2.12.0 was a beta version given out to certain people that had issues with the 11b beta version. 2.12.1 is the current release version.

[tosbsas]

Yeah thinks so too - download on fryday gave me:

NOD32 Antivirus System information
Virus signature database version: 1.852 (2004082
Dated: Samstag, 28. August 2004
Virus signature database build: 4786

Information on other scanner support parts
Advanced heuristics module version: 1.009 (20040817)
Advanced heuristics module build: 1058
Internet filter version: 1.002 (2004070
Internet filter build: 1013
Archive support module version: 1.019 (20040823)
Archive support module build version: 1099

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Administrative tools
Version: 2.12.1
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.1
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.1
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.1

Operating system information
Platform: Windows 2000
Version: 5.0.2195 Service Pack 4
Version of common control components: 5.81.4916
RAM: 160 MB
Processor: x86 Family 6 Model 5 Stepping 0 (233 MHz)


By the win win2k - I can download without any problem the ewido suite - must be ZA problem

[Blackspear]

2.12.1 is the final release.

Cheers

[WilliamP]

Thank you . I'm glad .That is the one I have.

[SaphireX]

Well after reading that my version was the 2.12.0 and not the 2.12.1 version I uninstalled the "old" one and installed the new one........and updated it!

Since my last post with version 2.12.0--- I did discover some "issues" as this was based on a fresh install of XP SP1 followed by a clean install of SP2

1. Some files still cannot be moved or deleted within folders --a 2nd try usually works however

2. DivX AVI files would play slow ..like something was acting on the file I am guessing AMON ?--MPEG/RM/MOV not affected!

Now after installing the NOD32 2.12.1 version the slow playing of DivX AVI's seems to have gone away ...after playing a few clips---time will tell I guess...

---But! moving or deleting files sometimes requires doing it again as the 1rst time >>it pops up warning that "another program is accessing the file" --I presume AMON maybe?

In any event maybe I need a registry hack to reduce the timing that AMON is looking/scanning files since this might be an AMD64 thing ??

Saphire

NOD32 Antivirus System information
Virus signature database version: 1.852 (2004082
Dated: Saturday, August 28, 2004
Virus signature database build: 4786

Information on other scanner support parts
Advanced heuristics module version: 1.009 (20040817)
Advanced heuristics module build: 1058
Internet filter version: 1.002 (2004070
Internet filter build: 1013
Archive support module version: 1.019 (20040823)
Archive support module build version: 1099

Information on installed components
NOD32 For Windows NT/2000/XP/2003 - Base
Version: 2.12.1
NOD32 For Windows NT/2000/XP/2003 - Internet support
Version: 2.12.1
NOD32 for Windows NT/2000/XP/2003 - Standard component
Version: 2.12.1

Operating system information
Platform: Windows XP
Version: 5.1.2600 Service Pack 2
Version of common control components: 5.82.2900
RAM: 1023 MB
Processor: AMD Athlon(tm) 64 Processor 3200+ (2002 MHz)

[Nirvy]

Hmm yes i have the 2.12.0 beta that was given to me to fix the SP2 problems.

Do i have to download another version *again*!? Doesnt it autoupdate??

[Blackspear]

Originally Posted by Nirvy

Hmm yes i have the 2.12.0 beta that was given to me to fix the SP2 problems.

Do i have to download another version *again*!? Doesnt it autoupdate??

At present you will have to download the new version from www.nod32.com and I say thank God for that. I for one do NOT want it to auto-update, due to the many problems associated with it, as can be seen here on this forum and the Beta forum. If it auto-updates now, we are going to be inundated with phone calls from clients wanting to know how to fix the mess…

I have advised my techs not to touch it with a barge poll, not to install it on any PC's or with any new licenses being sold, to continue using v2.0 This will remain my advice until the problems have been resolved. I believe they have released this version way to quickly, the amount of problems we are seeing here at Wilders was not seen with the previous major update from v1.0 to v2.0...

Cheers

Hi !

Does anyone know, when the international versions will be available ?

Regards,
ww

[SaphireX]

So Blackspear...if I understand correctly you have advised your "techs" not to install the latest version 2.12.1 until the "bugs" are fixed ?

Well hopefully, everyone that does install this new release on an XP SP2 machine will take detailed notes on any problems they find and email them off to Eset Support or post here in a problem thread for that explicit purpose ...so that fixes are just around the corner!

Saphire

[Blackspear]

Originally Posted by SaphireX

So Blackspear...if I understand correctly you have advised your "techs" not to install the latest version 2.12.1 until the "bugs" are fixed?...

Correct.

Originally Posted by SaphireX

…Well hopefully, everyone that does install this new release on an XP SP2 machine will take detailed notes on any problems they find and email them off to Eset Support or post here in a problem thread for that explicit purpose ...so that fixes are just around the corner!

I don’t mind Beta testing Nod32, I just don’t want my clients to, they expect a complete and fairly perfect running program, this is what they have paid for, not to be Beta testers…

Cheers

[PLeX™]

My company is fairly new to NOD32 but we've been experiencing the same IMON issues it seems everyone is having with 2.000.11b and 2.12.1. The fix seemed to be disabling IMON.

Many of these systems had 2.000.9 before upgrading and had no problems surfing until 11b or 2.12.1. The one thing all these systems had in common was that they had either Norton AntiVirus 2003/2004 or Symantec AntiVirus Corp 8/9 uninstalled. We were able to fix the problem.

Since we concluded IMON seemed to be the problem, we tried the network repair option within NOD32. This did not fix the issue.

Next we tried the Winsock repair from a previous thread: Winsock Repair method (post #5 Blackspear).

All systems we tried this on fixed the IMON issue. We suspect other programs/spyware that mess with the Winsock may have this problem as well.

We did try Winsock Fix 1.2 on a few systems and this seemed to work on all but one system.

Hopefully this points someone in a direction to investigate.

[bolleke3]

Nobody who can answer my question?

"NOD32 2.12 will be available as a standard program component update soon. Until the update is released, please do not "downgrade" program components to version 2.000.8/9, if offered.
When will this update been made available?
Bolleke3

[Blackspear]

Originally Posted by bolleke3

"NOD32 2.12 will be available as a standard program component update soon. Until the update is released, please do not "downgrade" program components to version 2.000.8/9, if offered...

Where did you get this information from?

Cheers

[RickFriedman]

Originally Posted by Blackspear

Where did you get this information from?

Cheers

Actually, it's in the very first post of this thread.

Rick

[Blackspear]

Originally Posted by RickFriedman

Actually, it's in the very first post of this thread...

LOL, no worries, it has been a while since I looked at the 1st page

Cheers

[Mele20]

Rereading the first post by Marcos in this thread I find this interesting tidbit:


"If NOD32 detects a probable NewHeur_PE virus, we will highly appreciate if you quarantine the file (this option will be enabled by default) and send it from quarantine as an attachment to sample@nod32.com (it's intentionally sample and not samples, though both addresses work)."

I've had a number of what I believe to be false positives found by Amon since installing this version. I have not been able to send them from quarantine! What does that quote mean? It should mean a one click option in quarantine like most all other av have and off it goes to Eset. Instead I have had a heck of time sending these. I almost didn't send them as it is too much trouble. I had no idea how to send those AMON found in System Restore. (It keeps finding them there. Very irritating). I sure couldn't send them from quarantine. A world class av should not make such an absolute mess of quarantine.

I expect more false positives because that is the price we will all pay for the emphasis now on advanced heuristics. Whether or not that emphasis is worth it remains to be seen...in my mind at least.