Vivaldi Will not Open After Update
-
@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.
-
As a humble everyday non professional techie home user, I'm not understanding much about the solutions and workarounds being suggested. I would suggest that anyone experiencing this problem reverts back to version 2.8.1664.44 until such time as either Vivaldi or Symantec fixes the issue. You will need to uninstall the problem version 2.9 before reinstalling 2.8. A download link for the Windows 64bit version 2.8.1664.44 can be found here:
https://www.techworld.com/download/internet-tools/vivaldi-28166444-64-bit-3330772/
-
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.
-
