Downloads:

49,922,585

Downloads of v 37.0.2062.102:

2,143

Last Update:

29 Aug 2014

Package Maintainer(s):

Software Author(s):

  • Google Inc.

Google Chrome (32-bit)

This is not the latest version of Google Chrome (32-bit) available.

  • 1
  • 2
  • 3

37.0.2062.102 | Updated: 29 Aug 2014

Downloads:

49,922,585

Downloads of v 37.0.2062.102:

2,143

Software Author(s):

  • Google Inc.

  • 1
  • 2
  • 3
Google Chrome (32-bit) 37.0.2062.102

This is not the latest version of Google Chrome (32-bit) available.

  • 1
  • 2
  • 3

Some Checks Have Failed or Are Not Yet Complete

Not All Tests Have Passed


Validation Testing Unknown


Verification Testing Unknown


Scan Testing Successful:

No detections found in any package files

Details

To install Google Chrome (32-bit), run the following command from the command line or from PowerShell:

>

To upgrade Google Chrome (32-bit), run the following command from the command line or from PowerShell:

>

To uninstall Google Chrome (32-bit), 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 https://community.chocolatey.org/api/v2. 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 https://community.chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade googlechrome -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 googlechrome -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Ensure googlechrome installed
  win_chocolatey:
    name: googlechrome
    state: present
    version: 37.0.2062.102
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'googlechrome' do
  action    :install
  version  '37.0.2062.102'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: googlechrome,
    Version: 37.0.2062.102,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller googlechrome
{
   Name     = 'googlechrome'
   Ensure   = 'Present'
   Version  = '37.0.2062.102'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'googlechrome':
  provider => 'chocolatey',
  ensure   => '37.0.2062.102',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install googlechrome version="37.0.2062.102" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 27 Nov 2014.

Description

Chrome is a fast, simple, and secure web browser, built for the modern web.

Note

This package uses Chrome’s administrative MSI installer and installs only the 32-bit version, even on a 64-bit OS. If you want the 64-bit version, install the google-chrome-x64 package instead and remove all versions of the GoogleChrome package.


tools\chocolateyInstall.ps1
$packageName = 'GoogleChrome'
$fileType = 'msi'
$silentArgs = '/quiet'
$url = $('' +
  'https://dl.google.com/tag/s/appguid%3D%7B8A69D345-D564-463C-AFF1-A69D9E530F96' +
  '%7D%26iid%3D%7B00000000-0000-0000-0000-000000000000%7D%26lang%3Den%26browser%3D3%26' +
  'usagestats%3D0%26appname%3DGoogle%2520Chrome%26needsadmin%3Dprefers/edgedl/chrome/' +
  'install/GoogleChromeStandaloneEnterprise.msi')
$version = '37.0.2062.102'

function Find-CID {
  param([String]$croot, [string]$cdname, [string]$ver)

  if (Test-Path $croot) {
  Get-ChildItem -Force -Path $croot | foreach {
    $CurrentKey = (Get-ItemProperty -Path $_.PsPath)
    if ($CurrentKey -match $cdname -and $CurrentKey -match $ver) {
    return $CurrentKey.PsChildName
    }
  }
  }
  return $null
}

$uroot = 'HKLM:\SOFTWARE\Google\Update\Clients'
$uroot64 = 'HKLM:\SOFTWARE\Wow6432Node\Google\Update\Clients'

try {

  $msid = Find-CID $uroot "Google Chrome binaries" "$version"
  if ($msid -eq $null) {
  # try 64bit registry
    $msid = Find-CID $uroot64 "Google Chrome binaries" "$version"
  }
  if ($msid -ne $null) {
     Write-Host "Google Chrome $version is already installed."
  } else {
    Install-ChocolateyPackage $packageName $fileType $silentArgs $url
  }

} catch {
  Write-ChocolateyFailure $packageName $($_.Exception.Message)
  throw
}
tools\chocolateyUninstall.ps1
$packageName = 'GoogleChrome'

try {

  $app = Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -eq 'Google Chrome'}
  if ($app) {
    $msiArgs = $('/x' + $app.IdentifyingNumber + ' /q REBOOT=ReallySuppress')
    Start-ChocolateyProcessAsAdmin $msiArgs 'msiexec'
  }

  Write-ChocolateySuccess $packageName


} catch {
  Write-ChocolateyFailure $packageName $($_.Exception.Message)
  throw
}

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
Google Chrome 91.0.4472.164 467669 Friday, July 16, 2021 Approved
Google Chrome 91.0.4472.124 838493 Friday, June 25, 2021 Approved
Google Chrome 91.0.4472.114 529276 Friday, June 18, 2021 Approved
Google Chrome 91.0.4472.106 481548 Tuesday, June 15, 2021 Approved
Google Chrome 91.0.4472.101 431957 Thursday, June 10, 2021 Approved
Google Chrome 91.0.4472.77 740546 Wednesday, May 26, 2021 Approved
Google Chrome 90.0.4430.212 699506 Monday, May 10, 2021 Approved
Google Chrome 90.0.4430.93 608720 Tuesday, April 27, 2021 Approved

This package has no dependencies.

Discussion for the Google Chrome (32-bit) Package

Ground Rules:

  • This discussion is only about Google Chrome (32-bit) and the Google Chrome (32-bit) 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 Google Chrome (32-bit), 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