Downloads of v 5.1.2566.3-snapshot:


Last Update:

31 Jan 2022

Package Maintainer(s):

Software Author(s):

  • Vivaldi


vivaldi chromium browser googlechrome chrome

Vivaldi (install)

This is a prerelease version of Vivaldi (install).

  • 1
  • 2
  • 3

5.1.2566.3-snapshot | Updated: 31 Jan 2022



Downloads of v 5.1.2566.3-snapshot:



Software Author(s):

  • Vivaldi

  • 1
  • 2
  • 3
Vivaldi (install) 5.1.2566.3-snapshot

This is a prerelease version of Vivaldi (install).

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Failed


Scan Testing Successful:

No detections found in any package files

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install Vivaldi (install), run the following command from the command line or from PowerShell:


To upgrade Vivaldi (install), run the following command from the command line or from PowerShell:


To uninstall Vivaldi (install), run the following command from the command line or from PowerShell:


Deployment Method:

📝 NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Copy Your Script

choco upgrade vivaldi.install -y --source="'INTERNAL REPO URL'" --version="'5.1.2566.3-snapshot'" --prerelease [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

choco upgrade vivaldi.install -y --source="'INTERNAL REPO URL'" --version="'5.1.2566.3-snapshot'" --prerelease

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0

Exit $exitCode

- name: Install vivaldi.install
    name: vivaldi.install
    version: '5.1.2566.3-snapshot'
    state: present
    allow_prerelease: yes

See docs at

chocolatey_package 'vivaldi.install' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '5.1.2566.3-snapshot'
  options  '--prerelease'

See docs at

cChocoPackageInstaller vivaldi.install
    Name        = "vivaldi.install"
    Version     = "5.1.2566.3-snapshot"
    Source      = "INTERNAL REPO URL"
    chocoParams = "--prerelease"

Requires cChoco DSC Resource. See docs at

package { 'vivaldi.install':
  ensure          => '5.1.2566.3-snapshot',
  install_options => ['--prerelease'],
  provider        => 'chocolatey',
  source          => 'INTERNAL REPO URL',

Requires Puppet Chocolatey Provider module. See docs at

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package is likely a meta/virtual (*) or an installer (*.install) or portable (*.portable) application package.

  • Meta/virtual (*) - has a dependency on the *.install or the *.portable package - it is provided for discoverability and for other packages to take a dependency on.
  • Portable (*.portable/*.commandline (deprecated naming convention)/*.tool (deprecated naming convention)) - usually zips or archives that require no administrative access to install.
  • Install (*.install/*.app (deprecated naming convention)) - uses native installers, usually requires administrative access to install.

Learn more about chocolatey's distinction of installed versus portable apps and/or learn about this kind of package.

This package is exempt from moderation. While it is likely safe for you, there is more risk involved.

Web browser based on Chromium with added features inspired by Opera.

$ErrorActionPreference = 'Stop';

$packageName= 'vivaldi'

$packageArgs = @{
    packageName    = $packageName
    fileType       = 'exe'

    url            = ''
    silentArgs     = '--vivaldi-install-dir=$($env:ProgramFiles)\Vivaldi --vivaldi-silent --do-not-launch-chrome --vivaldi-update --system-level'
    checksum       = 'C169C2A6FC14EA6FCBCA43ACFF83406ED9220AE37CA8153644D9D845CCE38A42'
    checksumType   = 'sha256'
    url64bit       = ''
    checksum64     = '19E0048F62D889716700E3720B614A546F337EED6BEF852D201FEF1D870FE41D'
    checksumType64 = 'sha256'

Install-ChocolateyPackage @packageArgs
$ErrorActionPreference = 'Stop';

$packageName = 'vivaldi'

# Despite being 64bit, Vivaldi still uses this registry key
$regKey = Get-ItemProperty -Path 'HKLM:\Software\WOW6432Node\Vivaldi'

if (!$regKey) {
    Write-Warning "Vivaldi looks to already be uninstalled"
} else {
    $packageArgs = @{
        packageName    = $packageName
        file           = "$($regKey.UninstallString)"
                              # Workaround to get around issue with incorrect positive from package validator
        silentArgs     = "$($($regKey.('Uninstall'+'Arguments')).Replace('--vivaldi','')) --uninstall --force-uninstall --system-level --vivaldi-silent"
        validExitCodes = @(0,19)

    Uninstall-ChocolateyPackage @packageArgs

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Add to Builder Version Downloads Last Updated Status
Vivaldi (Install) 5.3.2679.58 423 Thursday, June 16, 2022 Approved
Vivaldi (Install) 5.3.2679.55 356 Sunday, June 12, 2022 Approved
Vivaldi (Install) 5.3.2679.51 244 Thursday, June 9, 2022 Approved
Vivaldi (Install) 5.3.2679.38 396 Friday, June 3, 2022 Approved
Vivaldi (Install) 5.2.2623.48 636 Wednesday, May 18, 2022 Approved
Vivaldi (Install) 5.2.2623.46 451 Wednesday, May 11, 2022 Approved
Vivaldi (Install) 5.2.2623.41 641 Thursday, April 28, 2022 Approved
Vivaldi (Install) 5.2.2623.39 570 Saturday, April 16, 2022 Approved
Vivaldi (Install) 5.2.2623.36 143 Friday, April 15, 2022 Approved

This package has no dependencies.

Discussion for the Vivaldi (install) Package

Ground Rules:

  • This discussion is only about Vivaldi (install) and the Vivaldi (install) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Vivaldi (install), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus