Vivaldi Will not Open After Update
-
Same problem here. I see Vivaldi.exe processes being created in Task Manager, but after 1 second, they all vanish and only the update_notifier.exe remains. Nothing is happening on the screen.
I've renamed my whole User Data folder but it's the same.
We're using Symantec Endpoint Protection here, but this didn't log any probem/threat.
Windows 10 Enterprise x64 1903.
-
@Gwen-Dragon said in Vivaldi Will not Open After Update:
I do not know which Windows Defender/Ati-Malware Settings these users have – may be the cause.
Windows Defender, although very valid as AV, is known for more false positives than usual.
-
@Catweazle said in Vivaldi Will not Open After Update:
In another thread a problem of Vivaldi with Symantec is reported.
Turn it off and try againI just played around with SEP and it seems to be the "Memory Exploit Mitigation" that's being triggered. Although there doesn't appear anything in the logs and there's no notification, when I disable only this, Vivaldi is coming up again.
Of course, this is no workaround as disabling this is against company policy.
EDIT: Chrome 78 works fine, by the way. But we had to update SEP to 14.2 for that.
-
I have the same problem after 2.9 is updated. Vivaldi browser not starting.
Symantec endpoint protection 14.0 is running (windows 10 OS).
I will check the above mentioned link for solution -
Same here: Not starting after update. Symantec Endppoint present.
I can start vivaldi with "vivaldi --no-sandbox". -
@Gwen-Dragon said in Vivaldi Will not Open After Update:
See this:
@Aronand said in Vivaldi 2.9: Adding more to the Vivaldi Menu:@tree1891: Its a known issue caused by Symantec then, here is some info on it from them, they also provide a workaround afaik. https://support.symantec.com/us/en/article.tech256047.html
So a workaround for me seems to be adding
--disable-features=RendererCodeIntegrityto the Vivaldi shortcut. Then, Vivaldi starts even with SEP working normally. -
@petrsmelysw See my comment above.
-
@Gwen-Dragon Thanks a lot
--disable-features=RendererCodeIntegrity
Adding the above in vivaldi shortcut worked for me -
@rigsby999 I have scanned through the replies but my apologies if somone has already given this answer. I also had this problem and tried disabling Norton and Malwarebytes, also I reinstalled Vivaldi, but none of that helped. I then set the vivaldi.exe file to run in compatibily mode for Windows 8 (for me located in C:\Users(your User name)\AppData\Local\Vivaldi\Application. That worked for me. Hope this might help someone.
As an aside, I am not sure if I have noticed any speed improvement in the new version, but I have only just got it working and will need to use it more.
Regards
Limburg
Windows 10 Pro 1903. 64 bit. -
@Gwen-Dragon did work for me!
Also have Symantec Endpoint Protection v14, "Memory Exploit Mitigation" deactivation (mentioned by @mbirth) did also work, but I reactivated this SEP preference now. Adding --disable-features=RendererCodeIntegrity just works. -
@Gwen-Dragon said in Vivaldi Will not Open After Update:
If you use Symantec this Help page https://help.vivaldi.com/article/symantec-endpoint-protection-crash-workaround/ will solve some problem.
The help page says to use the workaround for a standalone version, as well as a normally installed version, but it is not necessary (for me, at least). I have Norton and the standalone snapshot RC2 in the C: directory without the "disable etc" runs fine.
-
@mbirth said in Vivaldi Will not Open After Update:
So a workaround for me seems to be adding --disable-features=RendererCodeIntegrity to the Vivaldi shortcut. Then, Vivaldi starts even with SEP working normally.
Thank you very much for this find. I'm saddened that I didn't check the forum before completely obliterating my existing installation. Have a lot of stuff to tweak once again.
I let the good people on Chocolatey Disqus know about the issue and this thread as well. Hopefully Symantec fixes this soon. Thanks also to @Gwen-Dragon who I always see in the thread every time there is a problem, helping to direct the conversation to the source of the problem - you do a lot to keep this software working and I really appreciate you.
Anyone know if there's a way for me to restore my previous tab session if I couldn't back it up from within the app? I kept a copy of everything in
C:\Users\<user>\AppData\Local\Vivaldi, but it looks like session management is handled from within the browser and as it goes in this thread, I didn't have the ability to launch the application. -
@penguinairlines If you kept a copy, all of your data and settings are in the User Data/Default folder. Specifically, within Default are files for Current Session, Current Tabs, Last Session, Last Tabs, and History.
-
I had the same issue with a portable install, and the solutions with compatibility mode or adding --disable-features=RendererCodeIntegrity worked (I also have Norton Security), however there is one more thing that worked for me: simply renaming the installation folder
-
@Gwen-Dragon Hi - I've tried that and it's made no difference. I deleted those files after installing the problem version 2.9. Is that correct?
-
@Gwen-Dragon This Symantec workaround has worked for me, but there are other issues. Every time Vivaldi opens it says that Sync is disabled and I have to go and log into my account. Checking the save password box has no effect and so I have to do this every time I open Vivaldi. The other issue is that the workaround is only effective on a shortcut direct to the Vivaldi program itself, it does not work on desktop shortcuts etc. I am going back to version 2.8 until these problems hav been resolved.
-
Running 2.9 in compatibility mode for Windows 8 or 7 works but seems a little clunky. For instance, when closing the browser, it seems to close each tab individually before finally closinf the application itself.
-
@mbirth This works for me, but Vivaldi won't work without this even without my antivirus running. So I'm pretty sure it's the version that's broken..
-
@Awpii The version of what? When third-party software blocks an app, it is not the fault of the app.
-
Users with Symantec do not need to modify their command line for Vivaldi. Per the linked Symantec page:
On November 12th, 2019 Application Control definitions will be released to address the issue for Windows Server 2016 and Windows 10 RS1 devices already on SEP 14.2 or later. This will prevent the issue from occurring once CodeIntegrityRenderer is enabled again. Operating Systems other than Windows Server 2016 or Windows 10 RS1, SEP can be upgraded to 14.2 or later to address the incompatibility as well.
If upgrading SEP is not an option, or the OS is one of those listed above, the incompatibility can be worked around by adding an Application Control exception for Chrome (Chrome.exe) and/or Microsoft Edge Chromium (MSEdge.exe).
Replace the program name with Vivaldi's exe, that way you can keep the Renderer Code Integrity in place, simply by making an exception in Symantec. The exception can be removed once Symantec releases their fix. I assume creating a similar exception in other programs that have false positives for Vivaldi is also possible, I just don't use any of these so you'll have to look into the program for what the feature name is.
