Jump to content

How to stop automatic build or version upgrade please


Rick_27
 Share

Recommended Posts

NOD32 v16.0.22.0 forces upgrade to v16.0.24.0, and even though I have the box unchecked for No Product Application Feature Updates - but the 'hover over' on that checkmark says it has no effect on security and stability updates, and so I suppose it deemed itself power over my wish and went right ahead and auto updated to v16.0.24, even though I don't want it to right now, please and thank you.

Not that it matters to my question, but I don't want v16.0.24 because it's has a bug in it and conflicts with my screenshot programs both Printkey & FastStone when clicking the sys tray icon of NOD, and it does this on either Win7 & Win10. But no matter with what that issue is I don't care really and I'm sure it'll get fixed, but I want and choose to stay on v16.0.22.0 which works fine.  Please I don't want to talk about the bug anymore and don't want to be a beta tester for a paid license, as well I don't care to upload any bug logs for the same reason, thank you, please.  

My only question is - How can I  ..and can I as a paid user stop it from automatically updating to v16.0.24.0 ?
Yes or no

(yes I know I can turn off all updates to stop it, but no point since naturally I definitely want continuous virus definition module updates to work right along)

notes
(I've uninstalled v16 and installed v15.2.17.0 to test that at the moment, and 'for now' it lets me stay with that version while still updating definitions - for now anyway)

My only question is, Can I, and is there a way to stop my paid licensed version of NOD32, from updating itself to the next product build, or version, whether v16 (or v15) (or even if I have to revert to v14 to do it is fine because I don't like forced updates irregardless; I want to choose where and when myself, simple as that)

Yes or no please, and if yes what is the way to do it.

Thank you!

My License is valid for Essential Security NOD32 only
    License Key: xxxxxxxx
    Public ID: xxxxxxx
    Product: ESET NOD32 Antivirus     
    Quantity: 2     
    Expiry: 11/24/2025

   

Link to comment
Share on other sites

  • Administrators

You can disable only feature updates but not stability and security updates. We strongly recommend keeping the program up to date so that it stays fully compatible with newer Windows 10/11 versions and that you are fully protected when the particular program version reaches limited support or EOL that doesn't guarantee basic module updates.

Link to comment
Share on other sites

Thank you for the reply

Quote

You can disable only feature updates but not stability and security updates.

Perhaps I had too many questions in one post.

So let me ask you the question this way. If I choose to stay with the latest version of v15 (which is v15.2.17.0 at the moment) does my checkbox disabling "Feature Updates" ..does that permanently stop it from updating to v16?  Doesn't that fall under "Feature Updates"?

Link to comment
Share on other sites

  • Administrators
1 hour ago, Rick_27 said:

Doesn't that fall under "Feature Updates"?

Yes, v16 is a feature update so disabling the option will prevent updates to v16 and newer unless ESET enforces it. However, I wonder why you want to keep the program at v15.2. As I wrote, newer versions bring also support for newer operating system updates besides fixing bugs and possibly adding or improving security features as well.

Link to comment
Share on other sites

Thanks again for the reply.

Quote

Yes, v16 is a feature update so disabling the option will prevent updates to v16 and newer unless ESET enforces it.

Okay that's good, I feel better now about my overall purchase then. 

Thinking about it though, when I tested the v15 Trial I could of sworn (iirc) that it did force to v16. Unless maybe Trial versions have lesser rights?

When you say "unless ESET enforces it" ..what versions have they ever done that with so far?

 

Quote

I wonder why you want to keep the program at v15.2.

No need to wonder, I've already said in my OP I had v16.0.22.0 installed and it forced upgraded me to v16.0.24.0, and that version is not stable for me. I click the NOD32 System Tray icon and my Printkey or FastStone takes a screenshot from the click alone, LoL. And as I said it does it on both Win7 & Win10 and so I know it's an ESET bug and not OS related.  I just don't want to deal with it at all, it's my right.  Also tbh I have a personal disagreement with any company (MS does the same thing) that force upgrades a software for any reason.  There should be an option button leaving it up to the purchaser of the software to make that decision for themselves, irregarless of the marketing reasons given; especially if they're qualified in the decision.

When it comes to Win7 there is certainly nothing in AV NOD32 v16 that works better in the engine than your latest v15.2.17.0 with it, or v14 for that matter. I also use Win10 Enterprise LTSC 2021 (posting with Win7 now though) and pretty much I could say the same for that OS too, that NOD v15.2.17.0  is more than fine. Staying with a particular version you don't have to always worry about updates breaking things, LoL, because let's face it they pretty much always do.  Newer versions (sometimes just marketing gimicks for sales) are not always better; well again imho (no offense meant please) 

I never use all that banking stuff, etc, anyway. I turn it all off and only want the AV engine, that's it.  Speaking of which your Essential Security NOD32 versions give us every conceivable adjustment to turn things on/off, that's why I like it (except now to find out it needs 2 update buttons - one on/off  for Feature Updates, and another on/off for Stability updates, but absolutely always gives the choice for just virus definitions updates alone. This week is a good example why, your v16.0.24.0 breaks me while v16.0.22.0 is fine. If ESET Force Updates me to v16.0.24.0 (which they did) ..I'll install back to v15 which I did. 

 

Link to comment
Share on other sites

  • Administrators

When v15 reaches EOL in October 2023 (https://support-eol.eset.com/en/policy_home/product_tables.html), it will be upgraded automatically to a fully supported version.

As for ESET NOD32 Antivirus, it provides only very basic protection. It doesn't contain Network protection, ie. ESET would not stop network attacks against unpatched security holes in network protocols or RDP/SMB brute-force attacks which are a common infection vector nowadays. Also it does not support ESET LiveGuard, a cloud sandbox in which downloaded files detonate first and only if no malicious behavior is detected they are allowed to run locally as well.

Link to comment
Share on other sites

  • Most Valued Members
19 hours ago, Rick_27 said:

NOD32 v16.0.22.0 forces upgrade to v16.0.24.0, and even though I have the box unchecked for No Product Application Feature Updates - but the 'hover over' on that checkmark says it has no effect on security and stability updates, and so I suppose it deemed itself power over my wish and went right ahead and auto updated to v16.0.24, even though I don't want it to right now, please and thank you.

Not that it matters to my question, but I don't want v16.0.24 because it's has a bug in it and conflicts with my screenshot programs both Printkey & FastStone when clicking the sys tray icon of NOD, and it does this on either Win7 & Win10. But no matter with what that issue is I don't care really and I'm sure it'll get fixed, but I want and choose to stay on v16.0.22.0 which works fine.  Please I don't want to talk about the bug anymore and don't want to be a beta tester for a paid license, as well I don't care to upload any bug logs for the same reason, thank you, please.  

My only question is - How can I  ..and can I as a paid user stop it from automatically updating to v16.0.24.0 ?
Yes or no

(yes I know I can turn off all updates to stop it, but no point since naturally I definitely want continuous virus definition module updates to work right along)

notes
(I've uninstalled v16 and installed v15.2.17.0 to test that at the moment, and 'for now' it lets me stay with that version while still updating definitions - for now anyway)

My only question is, Can I, and is there a way to stop my paid licensed version of NOD32, from updating itself to the next product build, or version, whether v16 (or v15) (or even if I have to revert to v14 to do it is fine because I don't like forced updates irregardless; I want to choose where and when myself, simple as that)

Yes or no please, and if yes what is the way to do it.

Thank you!

My License is valid for Essential Security NOD32 only
    License Key: xxxxxxxx
    Public ID: xxxxxxx
    Product: ESET NOD32 Antivirus     
    Quantity: 2     
    Expiry: 11/24/2025

   

I will also add that while I understand that some people don't won't to or might not have the time to report bugs, it's never a good idea to presume they will just be fixed.

 

The issue is that there are so many different software and hardware combinations. It might be that no other member has the same setup that causes the bug that you have or uses the program that conflicts with Eset

Link to comment
Share on other sites

Quote

When v15 reaches EOL in October 2023 (https://support-eol.eset.com/en/policy_home/product_tables.html), it will be upgraded automatically to a fully supported version.

Okay I see, at the EOL of a version there is no choice anymore, even though a person has it check-marked not to have Feature Upgrades, nonetheless the program ignores that and you'll be automatically version upgraded at what ESET calls EOL. IMO this should not be the case and should be a prompt, yes, but not Forced! Definitely it should be stated in the hover-over on that button, and somewhere more obvious in the literature.

Okay I have all my answers, and Marcos you're giving the perfect answers as a good Administrator for the company you work for should give, it's the corporate way, and so well done for ESET

 

___________

@peteyt, as a paid user I don't want to be a beta tester, and I've proven that to be the case already while having it forced on me with no way out. No thanks! ..I'll stay with a more well tested/proven v15 for now.  I do not need all these new marketing frills and unnecessary GUI changes in my own personal use. I've always just wanted a very good AV engine without the frills, and/or at least a way to turn options off and thank goodness ESET gives me most 95% (but not all) of those options. 

Of course ymmv ..and that's fine

 

Link to comment
Share on other sites

  • Most Valued Members
On 12/13/2022 at 3:17 PM, Rick_27 said:

Okay I see, at the EOL of a version there is no choice anymore, even though a person has it check-marked not to have Feature Upgrades, nonetheless the program ignores that and you'll be automatically version upgraded at what ESET calls EOL. IMO this should not be the case and should be a prompt, yes, but not Forced! Definitely it should be stated in the hover-over on that button, and somewhere more obvious in the literature.

Okay I have all my answers, and Marcos you're giving the perfect answers as a good Administrator for the company you work for should give, it's the corporate way, and so well done for ESET

 

___________

@peteyt, as a paid user I don't want to be a beta tester, and I've proven that to be the case already while having it forced on me with no way out. No thanks! ..I'll stay with a more well tested/proven v15 for now.  I do not need all these new marketing frills and unnecessary GUI changes in my own personal use. I've always just wanted a very good AV engine without the frills, and/or at least a way to turn options off and thank goodness ESET gives me most 95% (but not all) of those options. 

Of course ymmv ..and that's fine

 

Oh I understand. As newer versions come out there's often going to be issues so I can see why people often stay behind, especially in regards to business.

My point however was that there is no guarantee that the conflict that happens with your screenshot program will be fixed because someone has to report it for Eset to know there's an issue.

I work as a service desk assistant and we often get calls about people who've had issues for ages but one day decide to finally report it and they aren't happy that it's been ongoing for ages. The issue is that half the time it's user specific and so until they made the call we had no idea the issue was effecting them

Link to comment
Share on other sites

Yes I understand your point, and since you're a service desk assistant then you can pass a mention of the bug along, or not.  I'm not going to do that except for what I've already done here already; sure if they give me another year extension on my license I can be a beta tester, but my time of doing those things have long passed.  

I know you guys have to look at things from a Corporate way of thinking; been there done that.  I'm looking at things from an end user point of view now, and I've seen things that this program does which I think there needs to be the changes made I've already expressed, and a few more. I know it may not get done because the ESET team supports itself and the Corporate way to best keep itself funded.  I understand the business process.

Hopefully you all have understood my points already made with my suggestions :)

Anyway, I think NOD32 is my favorite AV program so far, and so that is nice :)

Luckily I get to choose which version I use, but I only have to do that because of the Forced Update Process that I do not agree with at all.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...