Vivaldi will not open after updating to 2.10 (Symantec/Norton)
prascal last edited by Gwen-Dragon
@eddybryon Norton was always - since the early days - a very heavy, resource intense and system occupying software. If somewhere on the machine a problem occurred for sure Norton was in any way involved ... which gave me never that secure and confident feeling ... however maybe it's not so bad anymore.. Anyway, for me, the alarm bells are going off if I see a Norton somewhere on a computer...
modedit moved posts from https://forum.vivaldi.net/topic/43113/top-web-browser-to-use-in-2020/6
Pesala last edited by Pesala
Pathduck last edited by Pathduck
This post is deleted!
@rigsby999 Indeed I had the VERY same issue. Yes, they claimed it was Symantec/Norton. Advised to turn off security to update. Not happening. I reverted back to the prior version I had installed that actually worked and was more stable than 2.10 not opening. Oh yeah, I lost all my custom settings, bookmarks and so on. SO I am not ready to try to upgrade again. I did mine about a month ago, seeing by your recent post, nothing has changed!
Blackbird last edited by
... I reverted back to the prior version I had installed that actually worked and was more stable than 2.10 not opening. Oh yeah, I lost all my custom settings, bookmarks and so on. ...
Vivaldi 2.10 not opening when using Norton/Symantec is not a 'stability' issue... it's caused by the antivirus falsely detecting the updated program as malicious and interfering with its opening after installation/updating. Why the AV does what it does is an issue the AV maker has acknowledged to Vivaldi as the AV maker's responsibility, not Vivaldi's. Even if Vivaldi creates some magical "workaround", there's no guarantee the problem won't recur in the future since it depends on what whatever the AV is doing wrongly. Part of this probably revolves around Vivaldi having a too-small marketshare for the AV maker to make fixing their AV (and keeping it fixed) a priority.
Also, when one reverts a program to a prior version, a user always runs a risk that something will break unless reversion support is specifically designed into and advertised for the software. Hence before "running things backward" for any software version, one should always take care to copy that software's personal data to a safe place beforehand.
Thanks for reaching out and sorry for the trouble.
Symantec and Norton have just told us that they have pushed new updates via Symantec LiveUpdate, that is supposed to fix the issue for us. You will have to perform the update to benefit from this fix.
Please let us know how it goes.
Running on version 2.10.1745.23
Funcionando en version 2.10.1745.23
I can also verify that the installed stable version now starts properly (standalone snapshot has been working normally all along).
As the originator of this topic, I can now also confirm that version 2.10.1745.26 is working and with the registry workaround removed.