Vivaldi Will not Open After Update
-
Hey all, we have a test build with a possible fix for the Symantec issue that we want to do a minor update with, but first we want to test it, we don't have any internal users with the issue, so I thought I would ask here
If it works for you, just reply here, and we'll have it shipped asap, thanks!https://downloads.vivaldi.com/stable/Vivaldi.2.9.1705.34.x64.exe
https://downloads.vivaldi.com/stable/Vivaldi.2.9.1705.34.exe
-
@Aronand I am the original poster and yes it works for me. I am on Windows 10 Home 64bit and so far so good
-
@rigsby999 Great, thanks!
-
Symantec with a big team, solving an issue - 1 month
Vivaldi, with a small team, solving an issue - few days
You are the best, congrats
-
@rigsby999 Reversion to an earlier build is, for security and compatibility reasons, never, never, never a good idea,
-
@Ayespy Maybe so, but when the new version doesn't work and cannot be even be opened??
-
@rigsby999
Hi, there is an updated version to solve the issue.https://vivaldi.com/blog/minor-update-for-vivaldi-2-9-windows-only/
Cheers, mib
-
@mib2berlin Thanks - yes - I was one of the first to install it earlier and I fed back that it works for me.
-
@rigsby999 Then you can adjust your 3rd party blocking software. In this case, Vivaldi went out of their way to make changes in the browser to adjust for the bad updates in blocking software (which themselves will be fixed by next week, reportedly).
This is one reason I don't run 3rd party "security" software. Inevitably, it interferes, sooner or later, with the normal operation of your system.
-
@Ayespy I was the original reporter of this problem and as I mentioned in an earlier post, I am just a non-technical, but security conscious, home user. I wouldn't know how to adjust my third party, though widely used, blocking software. Yes, I am very impressed with how quickly the Vivaldi team came up with a solution, but surely in the meantime it would be better for users such as myself to stay with or revert back to the last functional version rather than being left without a default browser and all the valuable personal data stored within it.
-
I had the same problem but the test build did the trick for me too. I have Windows 10 Home 64-bit version 1809. Thanks for fixing it so quickly.
Andy
-
Has there been a regression in 2.10??
I had issues with crash on startup (and random crashes) relating to Symantec before - submitted logs etc. But first time I have this issue after upgrading:
I ran the 2.10 upgrade this morning, and afterwards Vivaldi just wouldn't start. Process closing as soon as it started. (I got a small blank window if launching from CLI with profile selection switch but nothing else). I also tried to install an earlier RC in Standalone mode, that wouldn't launch either.Setting it (User install exe) to Win8 compatibility mode did the trick.
Win 10 Pro, and yes, both SEP and MalwareBytes running on this, with most settings managed by my organisation. -
@flo78 Ok nevermind, I see everyone is posting about this now. I've added --disable-features=RendererCodeIntegrity to the shortcut now rather than use Compatibility mode.
-
I too have the problem of after updating Vivaldi this morning to version 2.10 the browser will not open. I am running NAV and MBAM.
-
@bobkzzz The solutions are listed in the answers to the comments above yours. Symantec and NAV both improperly prevent Vivaldi from running. Until they fix their broken security software, the solutions/workarounds are listed above.
-
-
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.
-
@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 ? -
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.
-
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.
