Vivaldi Will not Open After Update

pablowains

Same issue here. I had never had this type of issue before with Vivaldi running on Windows 10 Pro. I will try to restore to a previous version.

ShlomiYahbes

@Gwen-Dragon
Thank you !!
That was helpful now I can run Vivaldi at my work laptop !
But I have another problem.. with the Call from
do you have a solution ?

rsjeffrey

Is a solution to this problem on the horizon?

I use Norton 360, and the latest Vivaldi update works only when I use the workaround - which I assume makes browsing less secure. Other browsers (e.g. Firefox) do not seem to suffer similar problems when they update. I prefer using Vivaldi, but if it is to grow its user base, it has to resolve these update issues - this is not the first.

Hopkins

Just before Christmas I started having problems with Vivaldi failing to open - or, at least, a few executables pop up for a second before dying. Today, I got it running using the Windows 8 compatibility work around mentioned here - thanks. However, my problem seems to relate to permissions on a DCOM service. The event viewer records an event each time opening of Vivaldi fails, which says:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
{2593F8B9-4EAF-457C-B68A-50F6B8EA6B54}
 and APPID 
{15C20B67-12E7-4BB6-92BB-7AFF07997402}
 to the user [DOMAIN\user.name] SID (S-1-5-21-1454471165-879983540-725345543-201510) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

The AppID 15C20B67-12E7-4BB6-92BB-7AFF07997402 refers to the RuntimeBroker.

Looking up this message on Google gives some suggestions, but I cannot implement them because I only have user permissions (and Vivaldi has been installed just as a normal user).

I hope that this helps.

ShlomiYahbes

@Gwen-Dragon
I did
https://forum.vivaldi.net/topic/43014/call-from-phone-name-new-feature

Thank you!

PzSniper

Same issue with latest Norton Antivirus Plus 22.19.9.63, but workaround fixed the issue, for now

also reported to NortonLifeLock https://community.norton.com/en/forums/symantec-endpoint-protection-nortonlifelock-antivirus-crash-cause-vivaldi-issue-–-workaround

R8MARC

@Gwen-Dragon This registry entry worked for me.

cristane

Vivaldi 10 still won't open on my laptop, and being a work laptop, I don't want to change any registries or mess with the antivir. Temporarily went back to Chrome, but I'll be checking once in a while to see if you fixed it.

cristane

@Gwen-Dragon I installed an old copy of Vivaldi 9, and it works like a charm. So why does Symantec complain only about the new version?

iAN CooG

@cristane said in Vivaldi Will not Open After Update:

Vivaldi 9

there is NO Vivaldi 9, maybe 2.9?

cristane

@iAN-CooG Yep, sorry, when I said Vivaldi 9 and 10 I actually meant 2.9 and 2.10. I had 2.9 installed and worked great, then updated it to 2.10 which stopped working, so downgraded back to 2.9.
No idea why Symantec has issues with one but not with the other. Hopefully this will be solved eventually.

TG2

@Gwen-Dragon said in Vivaldi Will not Open After Update:

@cristane said in Vivaldi Will not Open After Update:

No idea why Symantec has issues with one

Please report this False Positive to Symantec support.
Gwen, this doesn't just seem to be a Symantec problem. I'm not getting any alerts logged in Symantec (app/option offered as part of free Comcast Service offering) My errors show up in DCOM messages.

Like previous users I install the last version of 2.9 and I'm back in Vivaldi!! .. which I have not been into, in nearly a freakin' week since accepting the 2.10 update/upgrade.

It looks like a duck, it quacks like a duck .. its a GD DUCK! Its your company's application, if something has gone wrong, in how Norton identifies it, or how the system (win 10, 1909) works with it, we the user can't push this off on them, without specifics that PROVE the problem is symantec. ... or Windows .. Maybe its an escalation of privileges (I've right clicked and tried run-as admin .. and been equally treated to the standard UAC) .. so what is it?

There are a great many users, that have chosen to run Vivaldi .. but its not appropriate to see the single update from 2.9 to 2.10 cause Vivaldi not to start, and then blame it on everyone else.

Something is at the core of the changes from 2.9 to 2.10 that is causing strife .. not for 100% of the users, but for enough of us, that there are 4 pages of complaints / posts, about this problem, on the Vivaldi forum alone.

As the great Craig Ferguson use to say .. I look forward to your angry letters...

Pesala

@TG2 Save yourself a lot of grief. Uninstall your AV and make do with Windows Defender. I have had no issues in more than three years of using Windows 10 with Windows Defender and Windows Firewall as my only Antivirus.

TG2

@Pesala said in Vivaldi Will not Open After Update:

@TG2 Save yourself a lot of grief. Uninstall your AV and make do with Windows Defender. I have had no issues in more than three years of using Windows 10 with Windows Defender and Windows Firewall as my only Antivirus.
I'm sorry .. but I've been using Norton since 2004 ... across difficult years, where Xfinity didn't offer it .. and in 15 years..... the handful of issues experienced, across XP, 7, 8~8.1 and 10 .... have been less than countable on fingers .. much less fingers and toes!

I put my first Email server live in 1998, and web sites, pages, numerous issues crossing McAfee (wow the uninstaller failures they've had) which is why I've stuck with Norton.

I should be totally honest .. there was a time I paid for ZoneAlarm firewall and used Avast ... 4 years to be real about it .. but that was around the time Comcast went away from Norton ... and because I'd had multiple issues with McAfee .. that is why I avoided any of those as if they were with plague ..

But lets just take the past 3 years .. in 2017 I built this new PC on bleeding edge AMD Ryzen ... and in 3 years.. the number of problems using this machine nearly 24 7 .. and lets classify that .. running Vmware Workstation pro versions 11 through 15, across 2 different companies, with 4 different VPN products (the reason I go serious about using VM's for customer one-offs) zero problems that I could point at Norton and say.. "norton you F'd me" ... NOT ONE!

you're telling me that in all of that experience .. that its just the move from 2.9 to 2.10 of vivaldi and now the problem is 100% nortons' fault?

Sorry .. but no .. Roll back to 2.9 ... vivaldi works .. roll into 2.10 .. program doesn't even start .. and I get logged issues with it for Microsoft DCOM failures..

no sir / no mam ... this is somethign Vivaldi needs to work through .. they should reach out to established users (not me while I've got the history I've no more time for BS) and ask those users to help trouble shoot what it is .. and how-if at all possible- they vivaldi can help move this problem forward..

I'm sorry .. but this so far .. is on Vivaldi. Regardless if they are only just following chrome ...or not . for all we know .. its the failure of Vivaldi to nudge users ever closer into an "allow" dialog .. which is not the same as "vivaldi.exe" failed to execute ... etc.)

Please don't get me wrong.. I came to Vivaldi specifically for anti-chrome and anti-movement to this borderless BS and "to the edge"borderless programing that browser programs have taken us, and hope and pray that companies like Vivaldi survive and thrive, so that we (the user) can benefit from a browser that CAN and will and DOES provide out of bandwidth alternatives to the "status quote" application set... that it survives, and hopefully thrives showing those other browsers the door...

Pesala

@TG2 said in Vivaldi Will not Open After Update:

you're telling me that in all of that experience .. that its just the move from 2.9 to 2.10 of vivaldi and now the problem is 100% nortons' fault?

Actually due to a Chromium Update, and yes, false-positives are 100% the fault of AV programs. It is down to them to fix it, but a workaround has already been offered in this thread if you cared to read Gwen-Dragon's posts.

Ayespy

@TG2 Symantec already admitted it was their fault, so no point in arguing that.

They claimed to have applied a fix for Chromium 79, (and therefore Vivaldi removed their registry hack to evade the error, in the new version of Vivaldi) but the fix doesn't actually work, so it is still pending whether Symantec will ACTUALLY fix their broken detection routine, or whether Vivaldi will have to re-institute the registry hack which insulates it from Symantec's interference.

Here's the thing: Vivaldi works perfectly well on over a million Windows systems. Add Symantec, and Symantec silently prevents Vivaldi from running, with no notice to the user. If you have 3rd party software on your system which prevents other known and trusted software from running, it is NOT the fault of that other known and trusted software. It is the fault of the 3rd party software that is doing the blocking. Vivaldi is not enacting unwanted crippling of software. Symantec is.

Here is Vivaldi's diplomatic boilerplate response to the issue:

"Hi,
Thanks for reporting this issue, and sorry for the trouble!
This sounds like an issue caused by Symantec Endpoint Protection/Norton antivirus.
Unfortunately Symantec has not yet fully fixed the problem. Previous versions of Vivaldi worked because we had disabled a feature ("RendererCodeIntegrity") by default, due to this issue. The feature was re-enabled in Vivaldi version 2.10, after Symantec claimed it was fixed on their end, but unfortunately this fix was not comprehensive enough.
For now, you can use this workaround to let you run the latest version of Vivaldi, until a proper fix is in place:

https://help.vivaldi.com/article/symantec-endpoint-protection-crash-workaround/

Please keep an eye out for Symantec/Norton updates as well, in case they release a fix.
I hope this helps, we will continue looking into this on our end. Thanks for your time and for using Vivaldi!
Best wishes,"

That's the truth of the matter. But the fact is, there is NO "security" software that never interferes with your system or your apps. They all do at some point. Just because you got off lucky for a long time with a brand of "security" software doesn't mean it's pure and perfect. They all interfere with your system to a greater or lesser degree.

TG2

@Pesala said in Vivaldi Will not Open After Update:

@TG2 said in Vivaldi Will not Open After Update:

you're telling me that in all of that experience .. that its just the move from 2.9 to 2.10 of vivaldi and now the problem is 100% nortons' fault?

Actually due to a Chromium Update, and yes, false-positives are 100% the fault of AV programs. It is down to them to fix it, but a workaround have already been offered in this thread if you cared to read Gwen-Dragon's posts.

And if YOU would bother to read that .. Norton has already released updates that correct their end of the problem.

"Upgrade to Symantec Endpoint Protection 14.2.x to address the incompatibility with Chrome on Windows 10 Creators Update, version 1703 or later and Windows Server 2019. "

SO ... we come back to .. Installing 2.10 ... Vivaldi fails to start .. everything else is up to date .. and as I've mentioned in the Event Viewer are DCOM failures, these only happen with vivaldi 2.10 and not with 2.9! Problem is NOT just "norton"!

Ayespy

@TG2 said in Vivaldi Will not Open After Update:

Norton has already released updates that correct their end of the problem.

Yeah, not really. They claimed so, but that was not accurate.

Pesala

@TG2 said in Vivaldi Will not Open After Update:

And if YOU would bother to read that .. Norton has already released updates that correct their end of the problem.

I should have appended my previous post with:

I look forward to your angry letters...

TG2, you are the one getting angry and suffering needlessly due to your wrong understanding of the problem.

Gaëlle

Good news
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.