novice 20 Posted November 2, 2014 Share Posted November 2, 2014 If I press " Check for update" I get " Installed version 7.0.317.4 is up to date" however on ESET website "7.0.325.0" is available. Link to comment Share on other sites More sharing options...
rugk 397 Posted November 2, 2014 Share Posted November 2, 2014 Of course I would just recommend to install v8. It was already strange that they release a new v7-version and you're right it's strange too that they don't release this v7 update as a PCU. However it can be that they can only register one version (number) as the newest version and ESET wants to do this with v8 later (as I highly assume), so it wouldn't be useful to do this with the "new" v7 before. This are only my assumptions. Maybe ESET has different reasons for this. Link to comment Share on other sites More sharing options...
novice 20 Posted November 2, 2014 Author Share Posted November 2, 2014 To be honest, I did not understand anything! (other than "install version 8") :( Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted November 2, 2014 Administrators Share Posted November 2, 2014 It was already strange that they release a new v7-version and you're right it's strange too that they don't release this v7 update as a PCU. It's not strange. The new build is basically the previous version with current engine and modules included which is something that existing v7 users already have. And yes, upgrading to v8 is recommended as it provides better protection compared to v7. Link to comment Share on other sites More sharing options...
Solution rugk 397 Posted November 2, 2014 Solution Share Posted November 2, 2014 (edited) OK, more simple: I recommend: Install the new version of NOD32 - version 8. After ESET released v8 they still released a new v7 - 7.0.325.x and here. This release was surprising (for me), because there was already v8 out and users can upgrade to v8. It's also surprising for me that the new v7 wasn't released as a PCU (via the GUI-internal "updater"). - That is what you experienced. A reason for this could be that they can only set one version number as the newest version number (e.g. 8.0.304). I thought they want to do this later and because of this they don't want to set the newest version to "7.0.325", because then users have to upgrade to 7.0.325 and (maybe only a few days later) to v 8.0.304. This are only my assumptions. Maybe ESET has a different explanation for this. Related: Changelog for v 7.0.325 @Marcos Okay, so you wanted to release the latest version 7 with fully-up-to-date modules, so if there are users who install the v7 instead of v8, they don't have to update so much (VSDs) and they are already quite up-to-date. Is this right? And there are even some bug fixes in this version. (Changelog linked above) So you wanted to care about v7 although you released v8 already. Is this correct? Edited November 7, 2014 by rugk Link to comment Share on other sites More sharing options...
Administrators Marcos 4,935 Posted November 2, 2014 Administrators Share Posted November 2, 2014 I've been notified there were also some bug fixes included in 7.0.325 as well besides current modules. Since v8 is a new major version, it may suffer from not yet known bugs. For that reason, it made sense to make one more build of v7 which addresses most prevalent issues known from previous builds of v7. We'll see if and when it could be made available as a PCU for existing v7 users. Link to comment Share on other sites More sharing options...
rugk 397 Posted November 2, 2014 Share Posted November 2, 2014 (edited) Okay thanks for your answer! That's a good explanation for the two questions. Edited November 2, 2014 by rugk Link to comment Share on other sites More sharing options...
novice 20 Posted November 2, 2014 Author Share Posted November 2, 2014 Well, that is totally different :) Thanks! Link to comment Share on other sites More sharing options...
Recommended Posts