Version 7.0.302.26 Released ... What is it?

[howardagoldberg 14]

On the ESET download page for offline downloads, the version has been bumped to 7.0.302.26 (from 7.0.302.0).

 

The MSI is about 3MB larger than 302.0. Anyone know what the difference is and if we should perform an update?

 

Inside the NOD32 interface, clicking on check for update indicates that 7.0.302.0 is "up to date."

Edited October 24, 2013 by howardagoldberg

[FicmanS 0]

I was wondering the same, that was a quick update..  Change log anybody?

[dwomack 160]

Anything after the first three sets of numbers (7.0.302 in this case) is simply a regional localization suffix. In this case, it refers to diferent versions of the EULA for various regions.

 

So your version 7.0.302 is up to date, regardless of which numbers come after that. Thanks for the great question!

[howardagoldberg 14]

Anything after the first three sets of numbers (7.0.302 in this case) is simply a regional localization suffix. In this case, it refers to diferent versions of the EULA for various regions.

 

So your version 7.0.302 is up to date, regardless of which numbers come after that. Thanks for the great question!

 

... Except that:

 

1) If you download *any* of the localizations, the file version is all the same at the moment 7.0.302.26 (yes, I went through all of them -- same file version!). There seems to be no differentiation between localizations for version number or file size, and

 

2) This file is actually 3MB larger than what was posted for U.S. English on the release date which was 7.0.302.0.

 

Normally, the last numbers for localization are .0, .2, .3, etc. So, something else is at play here potentially -- thus my question. I am thinking there may actually be a glitch with the website.

 

Let us know if you find out anything. Thanks!

[eset lover 2]

Anything after the first three sets of numbers (7.0.302 in this case) is simply a regional localization suffix. In this case, it refers to diferent versions of the EULA for various regions.

 

So your version 7.0.302 is up to date, regardless of which numbers come after that. Thanks for the great question!

 

... Except that:

 

1) If you download *any* of the localizations, the file version is all the same at the moment 7.0.302.26 (yes, I went through all of them -- same file version!). There seems to be no differentiation between localizations for version number or file size, and

 

2) This file is actually 3MB larger than what was posted for U.S. English on the release date which was 7.0.302.0.

 

Normally, the last numbers for localization are .0, .2, .3, etc. So, something else is at play here potentially -- thus my question. I am thinking there may actually be a glitch with the website.

 

Let us know if you find out anything. Thanks!

i am in same confusion

[Marcos 5,074]

The only change in 7.0.302.26 compared to 7.0.302.0 is an updated EULA. The fact that the msi installer is larger can be caused by current modules and engine that are always embedded when a newer installer is built.

[siljaline 57]

If sites like NeoWin and others would make a note of these things - we would see less threads like this, I think.


 

[Aryeh Goretsky 378]

Hello,

Thanks. I left a comment there.

Regards,

Aryeh Goretsky

If sites like NeoWin and others would make a note of these things - we would see less threads like this, I think.

[tonyr6 0]

Updated it anyway.

[siljaline 57]

ESET Support NEWS via the Web should be your one-stop-shop for all Product Release news and announcements.
 

Those who connect with ESET socially may do so hxxp://www.eset.com/us/ using the social share widgets.

 

 

Edited November 6, 2013 by siljaline

[DrTeeth 5]

Clicking on the 'more information' link in the notification box does nothing at all. Getting that to work would help .

[howardagoldberg 14]

The only change in 7.0.302.26 compared to 7.0.302.0 is an updated EULA. The fact that the msi installer is larger can be caused by current modules and engine that are always embedded when a newer installer is built.

 

7.0.302.26 is now being pushed out via the internal update mechanism in NOD32. The update size (vs. the full installer) is about 20MB. That's more than an EULA update ... and if it were only EULA, it would not be pushed out en masse, correct? Any chance of a change log being released?

[Arakasi 549]

 

The only change in 7.0.302.26 compared to 7.0.302.0 is an updated EULA. The fact that the msi installer is larger can be caused by current modules and engine that are always embedded when a newer installer is built.

 

7.0.302.26 is now being pushed out via the internal update mechanism in NOD32. The update size (vs. the full installer) is about 20MB. That's more than an EULA update ... and if it were only EULA, it would not be pushed out en masse, correct? Any chance of a change log being released?

 

 

I just received and installed this update via, Application update.

[DrTeeth 5]

 

7.0.302.26 is now being pushed out via the internal update mechanism in NOD32. The update size (vs. the full installer) is about 20MB. That's more than an EULA update ... and if it were only EULA, it would not be pushed out en masse, correct? Any chance of a change log being released?

 

That is exactly what I thought. All that bandwidth for an EULA? No way.

[SweX 871]

DrTeeth FYI.

 

https://forum.eset.com/topic/1303-whats-new-in-7030226/?p=7198

 

Hello,

 

 

it was a bug, it was supposed to be available only for those, who would click on Check for new version and those who were doing fresh installation.

It wasn't intended to be pushed to all customers via regular update.

 

We are sorry for the inconvenience.

[howardagoldberg 14]

 

DrTeeth FYI.

 

https://forum.eset.com/topic/1303-whats-new-in-7030226/?p=7198

 

Hello,

 

 

it was a bug, it was supposed to be available only for those, who would click on Check for new version and those who were doing fresh installation.

It wasn't intended to be pushed to all customers via regular update.

 

We are sorry for the inconvenience.

 

 

... so, is it a problem if we did install .26? Still, 20MB for EULA smells funny. The full file is around 70MB. The update is 20MB. That cannot simply be EULA ... especially since there were no new modules installed via the update.

[Peter Randziak 1,130]

Hello,

 

the PCU is always built for multiple versions of our products so it has to contain all parts of the product, which are not updated via regular update chanel i.e. the modules.

[Marcos 5,074]

If you consider the size of all binaries and help files except modules and the engine, they can easily reach ~20MB.