This forum thread needs a solution.
Kudos1 Stats

Please STOP forced update to 22.xx

Posted: 06-Mar-2020 | 4:36PM · 8 Replies ·

Sorry for my bad English ...

I have a computer with few resources and I like to use my old version of Norton Internet Security. I never had any problems and the low memory consumption added to the total compatibility with my system means that I do NOT want to carry out an update.

Unfortunately, even with the "Automatic Download of New Version" option UNCHECKED, Live Update performs the download and forced installation of version 22.xx.

I am very unhappy with Norton, as the company is not respecting my decision (and that of many other users) to continue with an earlier and more pleasant version for systems with few resources.

I would like a solution.

Replies

Kudos0

Re: Please STOP forced update to 22.xx

Posted: 07-Mar-2020 | 11:29AM · Edited: 09-Mar-2020 | 3:30AM · Permalink

I have a solution, 

[Admin Edit: Removed personal email address from public forums as per forum guidelines]

Kudos0

Re: Please STOP forced update to 22.xx

Posted: 07-Mar-2020 | 10:52PM · Permalink

I am interested in this "solution"... what might that be?
And why not just post it here in the forum?
 

Kudos0

Re: Please STOP forced update to 22.xx

Posted: 07-Mar-2020 | 11:02PM · Permalink

I'd like to know the solution... why not just post it here? 

Kudos1 Stats

Re: Please STOP forced update to 22.xx

Posted: 08-Mar-2020 | 12:00AM · Edited: 08-Mar-2020 | 12:31AM · Permalink

Problems reported in these threads as well and especially affected XP users

https://community.norton.com/en/forums/forced-norton-product-n360-upgrad...
https://community.norton.com/en/forums/norton-securityautomatically-unin...
https://community.norton.com/en/forums/recent-forced-nis-update-xp-sp3-v...

May I know which Winblows system you're using?  XP I presume?
AFAIK there seem to be little to no system issues on Vista (or later) systems upon such forced upgrade.

For now there is nothing we can do but to wait for Symantec/NLL to issue a fix.  And they should address that in TWO ways:

a. Immediately amend their Live Update mechanism such that NO more software version upgrades (NOT updates) are injected into older software versions, and force-deployed without consent -- such that users (regardless of system version) who would like remain in v21.x usability can do so without issue;

b. Work out a TRUE fix on v22.x when dealing with especially XP system, such that XP users who have been hijacked from v21.7.x to v22.x (and didn't have their systems appropriately backed up and imaged) will continue to stick to v22.x with no further issue.

Kudos0

Re: Please STOP forced update to 22.xx

Posted: 09-Mar-2020 | 5:03PM · Permalink

Hi Velho do Saco:

I don't have a solution for you, but Norton employee Gayathri_R posted Active Customers in the Legacy Versions Are Being Upgraded in the Product Updates Announcements blog yesterday (08-Mar-2020) about these forced upgrades.
----------
32-bit Vista Home Premium SP2 * Firefox ESR v52.9.0 * Norton Security Deluxe v22.15.2.22 * MB Free v3.5.1

Kudos1 Stats

Re: Please STOP forced update to 22.xx

Posted: 10-Mar-2020 | 11:30PM · Edited: 10-Mar-2020 | 11:38PM · Permalink

@Velho do Saco
If you're simply dissatisfied with v22.x then that would NOT warrant Symantec to investigate.   You'll need to provide proof of actual system error instances, plus full descriptions and any datalogging, for their reference.

Whether Symantec will be able to finally fix those XP system issues remains to be seen.  But for affected XP users, they'll heed to actively stand up and tell Symantec that their v22.xx has been (and still is) breaking their systems ALL THESE YEARS.

@macri

You're out of the XP camp/workflow so any XP system issues we've reported are of minimal concern to you.  But do please show some more sympathy/concern to these affected users, many of whom are not as tech-savvy as you.

Anyway here's what I understand from this forced new version hijack scenario:

1. The notice Gayathri_R has put out regarding such forced hijack is just informational.  When the situation escalates then Symantec/NLL will have to face up to the problem, review such new version forced upgrade policy, and revoke it whenever necessary;

However, whether this is a result of the Broadcom assets transfer and any possible restructuring, nobody knows -- except that this Broadcom thing has already caused various license chaos;

2. The notice states that previous client software versions' engines are at least 5+ years old and that updates are necessary for better protection.  That's probably just some kind of liability claim.  Trouble is, v22.x is also 5+ years old, and that no real new software version (eg. 23.x) has been announced.  And needless to say, v22.x is still buggy to this day;

3. v22.x was first deployed at around 2014 when XP(SP3) was reaching EOL (except for PoS builds, which was until around 2019). Did Symantec lose heart to this outdated OS and thus simply put all the resources to Vista, 7, 8.x etc. etc., while forgetting that many are, to this day, still have to run on XP for everyday workflow?  If they indicate that support is still provided down to XP then it's their obligation to work out all the bugs, and fix them accordingly;

4. The Reference Memory error issues were first reported in 2015.  Per admin request, datalogging has been carried out on those system error instances back then.  But since then there's been no solid follow-up, and to this day, the XP-specific bugs remain;

5. What's the reason for (4)?  Is it because XP users were not aware of such problem, or simply think such problem is not 22.x-related, thus they didn't report them to the Symantec admin, and as a result, letting the problem slip through?  Is it because Symantec did NOT collect enough data on such issues (Reference Memory error etc.) from affected XP users, leading to the company's dismissal of such problem and moving on to other issues?

6. Customers are not stupid when it comes to software upgrade.  And many would take the IT tech's approach: do NOT upgrade/update anything until all issues have been accounted for.  Which is why, when v22.x didn't work on XP as expected, affected customers simply remained in the trusted v21.x.  Has Symantec even been aware of that?

7. As for why Symantec carried out this forced hijack, it could be the usual streamlining practice to migrate all customers into the same customer support.  So without careful consideration, they simply forced all customers (current and legacy) into one solution, WITHOUT even asking.  Such mean and selfish behavior from a company like this!!  If they think they can live with past fame and glory, then sorry -- this 22.x software simply breaks that.

May I now use the opportunity to call out all current XP users who are suffering from the issues from forced v22.x software upgrade hijack to voice their concerns, complete with proof?  Your feedback is needed to push Symantec/NLL into facing up to their mess......

Kudos0

Re: Please STOP forced update to 22.xx

Posted: 11-Mar-2020 | 3:22AM · Permalink

@macri

You're out of the XP camp/workflow so any XP system issues we've reported are of minimal concern to you.  But do please show some more sympathy/concern to these affected users, many of whom are not as tech-savvy as you.

MY sentiments EXACTLY!!
That indifference and judgmental disregard is the kind of attitude I face EVERYWHERE when it comes to computer issues - that I should just abandon my 15+ years of work that was created and solely operational on an XP system (specialty file types that can only open on designated programs that are 32-bit based) and start from scratch with a new modern OS, because Microsoft and Bill Gates need want more money.  It took me almost 10 years to learn all the ins & outs of XP, I am too damn old to start over trying to understand the dumbed-down lightweight idiot machines of Vista/7/8/8.1/10. Not too mention, too damn poor. 

May I now use the opportunity to call out all current XP users who are suffering from the issues from forced v22.x software upgrade hijack to voice their concerns, complete with proof?  Your feedback is needed to push Symantec/NLL into facing up to their mess......

Amen and Hallelujah.

Kudos0

Re: Please STOP forced update to 22.xx

Posted: 12-Mar-2020 | 1:08AM · Edited: 12-Mar-2020 | 1:14AM · Permalink

@WTWASP

I guess this the quote "The future belongs to those who prepare for it" can be interpreted in this ever-changing computer arena in multiple ways/disciplines.

Some people simply think progress is everything and anything that gets old becomes obsolete trash, and thus won't bother stockpiling for supplies and resources at a typical time, until it's too late when they realize it.  That includes computer hardware, software etc. at that timeframe.  The reason of course is that they think the piece of hardware/software may become outdated/obsolete etc. when new ones come out.  True, but for an experienced (or even power) user, this fact has to be evaluated BOTH ways......

Unfortunately, as we look back the past few years, many may realize that the better times of computing would be back then, during the mid-late 2000s up to the early-mid 2010s, until w10 kicked in and messed up the entire OS workflow completely.  Even w8.x would be considered better, although w7 was always recommended due to its robustness.

The only difference here is that, while prepared customers could revert to their previous OS environments in the case of w10 forced (almost) upgrade, here the option to revert to NIS/NS v21.7.xx has been closed -- due to Symantec's being inconsiderate to the plethora of legacy (XP in particular) users where such machines are still their lifeline -- especially those who need to retain the win32 environments for various usages (eg. legacy software running, resting etc. etc.).  I for one will strive to retain my current XP desktop, even if I transition into a new one w/w7p64 installed (absolutely NO w10).

As for Win OS, it's indeed bitter to learn a new system.  Back then when Vista/7 was out many would still stick to (or revert to) XP, until later when w7 became more mature and thus accepted by many -- until the w8 disaster in around 2012 which eventually escalated to the present time w10 fiasco.  For a system that breaks more upon every forced system update, what can you expect??  As for me, I also learned w7 the hard way (and through a small, slow netbook); but one you get through, you'll appreciate the virtues of w7 (even though, w7 is still considered to be not as straight forward and simple as XP).

I'd say, at least update your knowledge base of Win OS up to the point of w7 or 8.x -- or even w10, even though you don't need to deploy it (unless you're stuck with the new/current generation of hardware).  Many IT pros still stick to w7 as we speak, due to many advance management software still not working properly under w10/ws2016 etc.  But at least they know w10 (at a decently fluent level) and how to deal with it whenever necessary.