NIS/NAV/N360 22.5.0.124 - WHEN WILL THIS BE FIXED?????

click > HOT ISSUES - NIS/NAV/N360 22.5.0.124

Post back your issue... Thanks

hi Mike

In my opinion most of the problems with the new version of NAV/NIS/N360 have been when the update was delivered by the Live Update automatically. I updated by using the New Version Check in the dropdown menu on the main Norton UI, and have had little problem with it other than the ID Safe not working properly which has for me been fixed.

The new version once installed correctly seems to work much more smoothly than the old indeed my laptop seems to have an overall improvement.

Perhaps a full uninstall of the program by uninstalling through Windows "Uninstall a Program" running the Norton Removal Tool then reinstalling your Norton product would help.

If you prefer to revert to the previous version there are several threads in the forum which help in this, depending on which product you have installed.

Michael

Hi bjm_, how do we reply to the HOT ISSUES one because it looks like you can't and its a moderated one? In which case can the moderators update it with all the other stuff like endless reboots and borked machines on downloading and installing?

Hi michaelsalis   have to disagree with you there, I downloaded my update manually and it really borked my machine, and on another it had downloaded itself and semi-borked it so not convinced either route is any better. NEITHER route should be doing this though.

Still hoping to see some awakening from Symantec though but looks like no-one from Symantec's bothered so clearly on a hiding to nothing on that one.

Cheers,

David

Sorry, floplot, how can he mark the thread as solved?

No-one's actually answered the question yet!!!!

Michael merely appears to be back to where he was before the 22.5.0.124 update torched his machine. I kinda doubt he's happy about his (corporate speak) "experience".

Norton is supposed to protect our computers, not trash them in a poorly developed and poorly tested update.  No real response or accountability from Norton here.

Unless I'm mistaken, this update covers issues with Windows 10- no mention of older operating systems.

Last night I received a large Live Update which included an update for the NSBU Engine on 2 Windows 8.1, 2 Windows 7 and 1 Windows Vista devices.

I have not had chance to check them all as I only discovered it was to update to 22.5.2.15.

When checking my Surface Pro 8.1 the version is as above and Outlook appears to at least be sending what it thinks is Spam to the Junk folder although on this occasion the emails were not Spam but it is early days so shall see what happens over the next few days.

On at least the Vista and 1 Windows 7 device the version is shown as 22.0.0.110. I have run Live Update on both these devices no further Engine updates have been received and the version remains 22.0.0.110. I don't know if Outlook is diverting Spam as I've not received any.

It was strange that the Surface asked for a restart after the download/installation whereas none of the other devices did.

I decided to uninstall NSwB on the Vista device as a test when I reinstalled the 22.5.2.15 version was installed. I have not been able to check Outlook as no Spam has been received.

Michael 

Perhaps I'm wrong, but there seems to be a prevalent misconception regarding Spam/Junk email detection and who/what/if detected and filtered it...

1) Many email client programs already have built-in filtering (which may, or may not be user controllable).
2) Many ISPs offer filtering (which can electively be turned on/off, and maybe otherwise configurable/controllable).
3) Norton security products have filtering (which BTW, defaults to being turned on, but can electively be turned off).

All three of these different "detection systems" can be simultaneously operational...

So how does one know which filter did a given message's spam/junk detection/filtering?

The only one of the above three that specifically identifies itself as the acting agent is Norton - It identifies itself as the acting agent by adding a "Tag" at the beginning of the offending message's subject field. More specifically, it inserts the text, "[Norton AntiSpam]" into the field.

So, for example - If some nefarious type sends you a spam/junk email containing lots of bad news web-links in its message body, and labels it with a subject line of "Check out these great prospects!" - If/when the Norton AntiSpam filter does the job of detecting this message for what it really is, the message that ends up in your email client's junk/spam bin (hopefully) is a message re-titled (by Norton) "[Norton AntiSpam] Check out these great prospects!"

Update from Norton Team:

As described in the HOT ISSUES link above the team discovered some issues with the 22.5.0 release of the software.  These impacted a very small number of users and we apologize for any inconvenience caused.  Every Norton software update is carefully monitored for any problems across our global customer base.  If problems are reported by users we endeavor to resolve them as quickly as possible.

You will note that the more recent (as of 7/22/15) update 22.5.2 corrects many of these issues and should resolve outstanding concerns you may have.  Note that what was released as version 22.5.0 was not Beta code as has been characterized by some posters.  The only way in which you will ever receive Beta software is if you explicitly sign up and request to be a part of a Beta program. 

As always we welcome your feedback on all of our software releases.  We also encourage you to contact the Norton support team if you are having problems with Norton software so we can diagnose the problem with your specific machine configuration.

It is important to keep your Norton software up to date – malware is changing continuously and new vulnerabilities and exploits are being detected on a daily basis.  The Norton security team continuously monitors for threats globally and pushes down software and solutions to your system to protect you and your data.       

sonfly1-

Comments made due to the instability of this initial release being like a Beta were made to reflect the evident lack of proper and through testing by Norton before the release.  Many think it was so bad it should have still been in the Alpha stage.

I'm glad Norton has corrected many of the issues with this release after the fact- this just points out the poor pre-testing by Norton of this release.  And the initial release caused problems for users on ALL machine configurations to varying degrees.

For over 5 years I've never had problems with Norton updates and new versions until now.  Defend your mistake all you want, but this has shaken my confidence in Norton.

I wish I had been aware of this forum last week.  Symantec just bricked my netbook.  I upgraded it to windows 10 and everything was working fine (which, frankly had me quite surprised).  But then I got a message from NAV that I need to upgrade to a new version.  I went ahead -- huge mistake!  After several hours of telling me that it was downloading, it eventually gave up.  The computer tried to reboot but it was not to be.  Windows 10 had been destroyed.  The OS tries to do a repair but failed.  I tried booting using the windows.old but that also failed.  On Friday I wasted an hour chatting with a useless support person ("are you writing from the affected PC?"  "Of course not! it is dead!").  He promised that a more senior person would call me but of course that never happened.  Eventually, I gave up and used the PC's recovery procedure to reinstall Windows 7.  Needless to say I lost all my applications and data in the process.  Thanks for nothing!

If you upgrade to windows 10 DO NOT upgrade NAV.  remove the old version and find a replacement.