Discussion in 'NOD32 version 2 Forum' started by jg88swe, Dec 20, 2004.
what is new in NOD32 2.12.4?
The retail version is still 2.12.3...
A new beta ?
Versions 2.12.x are almost same - only minor fixes are encorporated.
where do we get it - update or complete download
But the tryout version is already 2.12.4....
Next automatic update of the program components 2.13.0 will be available by the beginning of next year.
May I ask you what's new in that version, Marcos ?
probably changed as a result of crackers/hackers releasing dodgy copies...
If retail is going straight to 2.13.0, do you care what they do with the trial version?
Here are some of the new features: automatic, fully controlled submission of suspicious files, detection of suspicious files run on system startup, the support for potentially dangerous applications in all modules, new EMON, an option to unregister DMON from the system, improved cleaning algorithm and some other minor improvements.
Oh, I almost forgot to mention the best feature I like a lot - a bubble in the right-hand corner that replaces the pop-up window after an update
thanks for this description.
I can't wait anymore !
Sounds great Marcos, thanks for sharing.
Will this come in the form of a Beta first or straight through as an update?
With all due respect:
What I do miss in this description is that the problem with Winmgmt for users on Windows 98SE/ME has been fixed
See for example:
NOD32 and Winmgmt.exe
Winmgmt and nod32 in windows me
Quotes from that last link:
"the process Winmgmt is triggered by the security center on WinXP SP2. There was a bug in evaluating a condition on Win9x version of NOD32 which has been fixed. The ammendment will take effect in version 2.13.0 (of Nod) available by the beginning of next year."
Has it been fixed ?
And if so, in which version ?
And if not, why not ?
Doesn't the first paragraph I quoted provide all the answers to the questions you asked
Has it been fixed? - "which has been fixed"
And if so, in which version ? - "the amendment will take effect in version 2.13.0 (of Nod) available by the beginning of next year" - which may have changed a little - or so it appears....
And if not, why not ? - "not not - fixed that is... - apparently in 2.13.0 - according to the source you quoted"
Can´t wait to test it...
Well, I know it´s off topic, but in case I don´t get back in the forum this year, I´d like to wish a Merry Christmas and a Happy New Year for every FRIEND I have here.
I guess this will require a reboot after this component upgrade? I wish we didn't have to reboot.
Merry Christmas and Happy New Year to you and everyone else.
I'd like to echo BOTH of bsilva's wishes, from a "how the heck do we upgrade and reboot a couple thousand PCs" standpoint.
You don't necessarily need to update program components if you cannot afford to reboot. Almost every program that is tightly binded to the operating system requires a reboot after the installation. An alternative option is to select the Never restart computer option in the update type setup so that an update will take effect after next reboot.
So what is new in 2.12.4 ?
See post nine.
I believe Marcos was referring to 2.13.0.
Sorry but why exit first trial this version and not for retail customers?
is it possible to test for retail?
There's no difference in functionality between versions 2.12.2, 2.12.3 and 2.12.4. Unless you experience a certain problem, we suggest to stay with the version you currently have. The reason why there is only a trial version 2.12.4 is that a minor fix was made only to the trial version because the commercial version was not affected by this.
Macros is there any chanse that NOD32 integrate ability to submit all start-up objects to Eset, on user request, for analyse because spywares comming out more and more.....
I think its good way to get more samples for you guys
I would assume that FanJ was just asking for confirmation that indeed this Winmgmt.exe problem has been fixed in the upcoming version, since Marcos did not mention it in his description of new features etc.
That would be a nice courtesy for a simple yes or no, since responses from Eset personel have been made in the meanwhile.
In one of the threats on this forum, I mentioned this little bug had been fixed and it would take effect in the program update 2.13.0.
Separate names with a comma.