Vivaldi will not open after updating to 2.10 (Symantec/Norton)
-
And here we go again. Nervously took the step to update to version 2.10.1745 which was announced as "The stable release of Vivaldi 2.10 has arrived!".
Just as happened in October when I updated from 2.8 to version 2.9, Vivaldi will not open after the installation to 2.10. I have now gone back to the last known stable version 2.9.1705.34.
I am assuming the problem could be Symantec/Norton not being ready again, but why release a new version and announce it as stable when previous issues still exist?
Anyone else getting same issue and if so is there a solution?
-
Same here followed link ^^ and all good for now. thanks.
-
@Gwen-Dragon I also cannot start 2.10. My anti-virus is Norton, not Symantec. I have uninstalled and re-installed 2.10 but it didn't help.
I've tried this:
@Gwen-Dragon said in Vivaldi Will not Open After Update:
Did you check in windows Taskmanager if there are any Vivialdi zombie processes running? If yes terminate them.
May be the last session is broken after you updated or shutdown your OS
- Open your profile folder by copy&paste
%LOCALAPPDATA%\Vivaldi\User Data\Default
into explorer address field - Delete these files:
- Last Session
- Last Tabs
- Current Tabs
- Current Session
but that did not help either.
I would appreciate any further suggestions.
- Open your profile folder by copy&paste
-
@Gwen-Dragon I have the same problem. Every other browser works with Norton so the problem rests with you for not making it compatible. Norton software is not crappy. I will not use your browser until you fix the problem. That's too bad because I like your browser and used it more than any of my other browsers.
-
Same problems for me, This disable features above fixed it.
I'm using Symantec Endpoint protection 14.2.1023.0100 but this does not seem to be the issue since it is not logged as stopping it.
I am always installing interesting things that do get stopped by symantec but I get a message from Symantec and an entry in the log.
-
Can't you guys add an exception in the AV settings for Vivaldi?
At least until the issue is fixed at the AV vendor side. -
I think the last time around this happened, a fix from Vivaldi and not Norton was given.
-
@vincenoga1 said in Vivaldi will not open after updating to 2.10:
@Gwen-Dragon I have the same problem. Every other browser works with Norton so the problem rests with you for not making it compatible. ...
By that same logic, because Vivaldi works with every other AV, the problem lies with Norton/Symantec for not making their AVs compatible. Reality: it's never quite as simple as that kind of reasoning implies. Moreover, @Ruario stated in https://forum.vivaldi.net/post/338116, "Symantec need to get their act together. They have acknowledged this is entirely their issue and had ages to fix this but do nothing."
-
I beg to differ. As stated, last time around it wasn't Norton that did the fix but Vivaldi. When I was notified regarding the Vivaldi update, all worked well. No updates as to Norton at that point.
-
I'm not defending Norton here, but why issue another major release of Vivaldi when it was known from launch of the previous version (2.9) that the issue caused this problem for so many users? At the very least, there should have been a prominent warning in the release notes to warn Norton users of the likely consequences of installing the update.
-
@Blackbird So why release the update knowing full well that it won't work for potentially thousands or even millions of users? Surely pre-release testing on Norton enabled systems would have made the problem obvious?
-
@rigsby999 Probably you have not understood one basic thing: Vivaldi is NOT obliged to fix someone else's caused bug.
Please read the article @Gwen-Dragon posted from Symantec: THEY are causing the problem to MILLIONS of Chrome/Chromium users.
From my POV, you should switch to some less bugged AV. Problem solved.
Also Vivaldi posted this on the help pages: https://help.vivaldi.com/article/symantec-endpoint-protection-workaround/
What else should you expect from the Vivaldi team, calling everyone privately to ask them which AV they use and to warn about Symantec AV being bad? -
@iAN-CooG Yes I have read the Symantec article and yes they should have sorted the issue out by now. Their article refers to errors when trying to open webpages. The problem I and other users have is that after the update, Vivaldi will not open to allow us to even try to get to a webpage! As I said earlier I am not defending Symantec or their Norton products. But this was a known issue to Vivaldi. So instead of saying boldly in the release notes "The stable release of Vivaldi 2.10 has arrived!" why not add the caveat that some Norton users may experience problems? At least then we would have prior warning and a choice of whether or not to proceed with the upgrade.
-
Same here. I started using Vivaldi a few days ago and I loved it. Today I'm not able to open it. Does my love end today? Looks like.
-
@Gwen-Dragon So I updated again to version 2.10 and modified my main Vivaldi shortcut to include the line of code in the workaround. Vivaldi would now open but:
-
I have multiple home start pages which all disappeared.
-
As Vivaldi is my default browser, my many other desktop shortcuts and other links will not open. I am not going through each of them to add the workaround code, so I have again uninstalled versioned 2.10 and gone back to 2.9.1705.34
-
-
Actually Chrome did not and has not a problem with Norton. I tried Chrome when Vavaldi updated and failed but when trying Chrome, there was no snags.
-
I do see where you're coming from. My question is, why does Norton accept vivaldi.exe two days ago and not now? What's changed or has anything changed in the vivaldi.exe?
-
Norton will always be part of Fight Club. Accept the challenges.
-
@Gwen-Dragon Yes. This works. Thanks.
For others, remember your right clicking on desk top not the short cut. Then follow the instructions from Gwen's article.Setting up a new computer. It took 2.10 easily but now realizes I haven't added my Norton/Symantic yet so I will likely be back again for these instructions.
Also another work around, longer, is to right click on the program and choose "trouble shoot compatibility". Run that. It won't find the problem but it will open Vivaldi, but as soon as you close the program you will have to do it again so obviously avoid closing the program for as long as possible.
-
@rigsby999 There are multiple makers of software (including OS's, browser extensions, AVs, and so on) that have already demonstrated they are capable of crashing families of browsers at some point in time or another. Their software design is their responsibility, not Vivaldi's... keeping track of their bugs (and ensuing fixes, whenever or if-ever released) is their responsibility, not Vivaldi's... and Norton/Symantec is but one AV player (at 10%-14% marketshare; Win Defender has 50%) in the universe of potentially conflicting AV software. To my knowledge, the makers of no other affected chromium browsers are including warnings about Norton/Symantec's 'conflict' problems with their browsers either.