Downloads of v 63.0.3207.0:


Last Update:

05 Sep 2017

Package Maintainer(s):

Software Author(s):

  • The Chromium Authors


chromium admin google cross-platform foss chrome browser

Chromium snapshots build

This is not the latest version of Chromium snapshots build available.

  • 1
  • 2
  • 3

63.0.3207.0 | Updated: 05 Sep 2017



Downloads of v 63.0.3207.0:



Software Author(s):

  • The Chromium Authors

  • 1
  • 2
  • 3
Chromium snapshots build 63.0.3207.0

This is not the latest version of Chromium snapshots build available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed

Validation Testing Passed

Verification Testing Passed


Scan Testing Resulted in Flagged:

This package was submitted (and approved) prior to automated virus scanning integration into the package moderation processs.

We recommend clicking the "Details" link to make your own decision on installing this package.


To install Chromium snapshots build, run the following command from the command line or from PowerShell:


To upgrade Chromium snapshots build, run the following command from the command line or from PowerShell:


To uninstall Chromium snapshots build, run the following command from the command line or from PowerShell:


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

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • 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. Enter your internal repository url

(this should look similar to

4. Choose your deployment method:

choco upgrade chromium -y --source="'STEP 3 URL'" [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 chromium -y --source="'STEP 3 URL'"

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

Exit $exitCode

- name: Ensure chromium installed
    name: chromium
    state: present
    version: 63.0.3207.0
    source: STEP 3 URL

See docs at

chocolatey_package 'chromium' do
  action    :install
  version  '63.0.3207.0'
  source   'STEP 3 URL'

See docs at

    Name: chromium,
    Version: 63.0.3207.0,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller chromium
   Name     = 'chromium'
   Ensure   = 'Present'
   Version  = '63.0.3207.0'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'chromium':
  provider => 'chocolatey',
  ensure   => '63.0.3207.0',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install chromium version="63.0.3207.0" source="STEP 3 URL"

See docs at

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved as a trusted package on 05 Sep 2017.


This package installs the Chromium snapshots builds by default to the '%programfiles(x86)%' instead of %localappdata%\Chromium.
If you have installed this package in the past to the %localappdata%\Chromium location it will continue to be installed in this location.
These builds can be unstable. MD5 checking is done on the file before install.

$ErrorActionPreference = 'Stop'

$version = '63.0.3207.0'

$chromium_string = "\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Chromium"
$hive = "hkcu"
$Chromium = $hive + ":" + $chromium_string

if (Test-Path $Chromium) {
  $silentArgs = '--do-not-launch-chrome'
} else {
  $silentArgs = '--system-level --do-not-launch-chrome'

$packageArgs = @{
  packageName   = 'chromium'
  fileType      = 'exe'
  url           = ''
  url64bit      = ''
  silentArgs    = $silentArgs
  validExitCodes= @(0)
  softwareName  = 'Chromium'
  checksum      = 'bbab5244cda477de89e90f742af0b661'
  checksumType  = 'md5'
  checksum64    = '38d62926f29815b195a504e82c8b32d2'
  checksumType64= 'md5'

Install-ChocolateyPackage @packageArgs
	$registry = Get-UninstallRegistryKey -SoftwareName $packageName
	$file = $registry.UninstallString
  $Arg_chk = ($file -match "--system-level")
	$chromiumArgs = @{$true = "--uninstall --system-level"; $false = "--uninstall"}[ $Arg_chk ]
	$silentArgs = @{$true = '--uninstall --system-level --force-uninstall'; $false = '--uninstall --force-uninstall'}[ $Arg_chk ]
	$myfile = $file -replace( $chromiumArgs )
	# All arguments for the Uninstallation of this package
	$packageArgs = @{
	PackageName = 'Chromium'
	FileType = 'exe'
	SilentArgs = $silentArgs
	validExitCodes =  @(0,19,21)
	File = $myfile
	# Now to Uninstall the Package
	Uninstall-ChocolateyPackage @packageArgs
	# This at the moment does not remove the libs\Chromium folder

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.

Version Downloads Last Updated Status
Chromium Snapshots 97.0.4679.0-snapshots 22 Friday, October 22, 2021 Approved
Chromium Snapshots 97.0.4678.0-snapshots 31 Thursday, October 21, 2021 Approved
Chromium Snapshots 97.0.4677.0-snapshots 22 Wednesday, October 20, 2021 Approved
Chromium Snapshots 97.0.4675.0-snapshots 31 Tuesday, October 19, 2021 Approved
Chromium Snapshots 97.0.4674.0-snapshots 25 Monday, October 18, 2021 Approved
Chromium Snapshots 97.0.4673.0-snapshots 23 Sunday, October 17, 2021 Approved
Chromium Snapshots 97.0.4672.0-snapshots 13 Saturday, October 16, 2021 Approved
Chromium Snapshots 97.0.4671.0-snapshots 38 Friday, October 15, 2021 Approved
Chromium Snapshots 97.0.4670.0-snapshots 31 Thursday, October 14, 2021 Approved
Chromium Snapshots 97.0.4669.0-snapshots 33 Wednesday, October 13, 2021 Approved

This package has no dependencies.

Discussion for the Chromium snapshots build Package

Ground Rules:

  • This discussion is only about Chromium snapshots build and the Chromium snapshots build 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 Chromium snapshots build, 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