Downloads of v 2.3:


Last Update:

14 Feb 2017

Package Maintainer(s):

Software Author(s):

  • Henry++


chrlauncher chromium chrome updater portable

chrlauncher (portable)

This is not the latest version of chrlauncher (portable) available.

2.3 | Updated: 14 Feb 2017



Downloads of v 2.3:



Software Author(s):

  • Henry++

chrlauncher (portable) 2.3

This is not the latest version of chrlauncher (portable) available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


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


To upgrade chrlauncher (portable), run the following command from the command line or from PowerShell:


To uninstall chrlauncher (portable), 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 chrlauncher.portable -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 chrlauncher.portable -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 chrlauncher.portable installed
    name: chrlauncher.portable
    state: present
    version: 2.3
    source: STEP 3 URL

See docs at

Coming early 2020! Central Managment Reporting available now! More information...

chocolatey_package 'chrlauncher.portable' do
  action    :install
  version  '2.3'
  source   'STEP 3 URL'

See docs at

    Name: chrlauncher.portable,
    Version: 2.3,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller chrlauncher.portable
   Name     = 'chrlauncher.portable'
   Ensure   = 'Present'
   Version  = '2.3'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'chrlauncher.portable':
  provider => 'chocolatey',
  ensure   => '2.3',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install chrlauncher.portable version="2.3" 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 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 was approved by moderator AdmiringWorm on 18 Feb 2017.


A small and very fast portable launcher and updater for Chromium.

This package:

  • installs chrlauncher, not Chromium.
  • will set chrlauncher to download/install/update Chromium without the need for admin rights.
  • by default, sets the install location for Chromium to be the per-user, %APPDATA% directory. Use the /Shared package parameter (below) to make the Chromium install location be in the chrlauncher directory and have Chromium (and all its settings) shared among all users.


Other (system-wide) chrlauncher settings can be modified in the chrlauncher.ini file located in the same directory as the target of the Chromium Launcher desktop shortcut. Some options include:

  • Auto download updates
  • Show a chrlauncher window when updating (default is a tray icon only)
  • Type of Chromium build
  • Update check period

Package Parameters

The following package parameters can be set:

  • /Default - Make chrlauncher the default "browser". This option requires installing with admin rights.
  • /Shared - Share the Chromium install among all users.

These parameters can be passed to the installer with the use of -params.
For example:
choco install chrlauncher.portable -params '"/Default"'.

$ErrorActionPreference = 'Stop'  # stop on all errors

$PackageName = 'chrlauncher.portable'
$version     = '2.3'
$url         = ''
$checkSum    = '4b5acc8133e90cab735559e652dea5f6996f0c4781d4ccf65bd517e2561734d0'

$PackageDir = Split-path (Split-path $MyInvocation.MyCommand.Definition)

$InstallArgs = @{
   PackageName   = $PackageName
   Url           = $Url 
   UnzipLocation = (Join-path $PackageDir ($PackageName.split('.')[0] + $version))
   checkSum      = $checkSum
   checkSumType  = 'sha256'
Install-ChocolateyZipPackage @InstallArgs

$BitLevel = Get-ProcessorBits
$target   = Join-Path $InstallArgs.UnzipLocation "$BitLevel\chrlauncher.exe"
$shortcut = Join-Path ([System.Environment]::GetFolderPath('Desktop')) 'Chromium Launcher.lnk'

Install-ChocolateyShortcut -ShortcutFilePath $shortcut -TargetPath $target

# Capturing Package Parameters.
$UserArguments = @{}
if ($env:chocolateyPackageParameters) {
   $match_pattern = "\/(?<option>([a-zA-Z]+)):(?<value>([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)|\/(?<option>([a-zA-Z]+))"
   $option_name = 'option'
   $value_name = 'value'

   if ($env:chocolateyPackageParameters -match $match_pattern ){
      $results = $env:chocolateyPackageParameters | Select-String $match_pattern -AllMatches
      $results.matches | ForEach-Object {$UserArguments.Add(
   } else { Throw 'Package Parameters were found but were invalid (REGEX Failure)' }
} else { Write-Debug 'No Package Parameters Passed in' }

if ($UserArguments.ContainsKey('Default')) {
   $msgtext = 'You want chrlauncher as the system default browser.'
   Write-Host $msgtext -ForegroundColor Cyan
   $Bat = Join-Path $InstallArgs.unzipLocation "$BitLevel\SetDefaultBrowser.bat"
   $NoPauseBat = Join-Path (Split-Path $Bat) 'NoPauseSetDefaultBrowser.bat'
   (Get-Content $Bat) -ne 'pause' | Out-File $NoPauseBat -Encoding ascii -Force
   & $NoPauseBat

if ($UserArguments.ContainsKey('Shared')) {
   $msgtext = 'You want chrlauncher to install/update/launch a single instance of Chromium to be shared (including settings, bookmarks, etc.) among all users.'
   Write-Host $msgtext -ForegroundColor Cyan
   $Acl = get-acl $InstallArgs.UnzipLocation
   $InheritanceFlag = [System.Security.AccessControl.InheritanceFlags]::ContainerInherit -bor [System.Security.AccessControl.InheritanceFlags]::ObjectInherit
   $PropagationFlag = [System.Security.AccessControl.PropagationFlags]::InheritOnly
   $rule = New-Object'BUILTIN\Users','Modify',$InheritanceFlag,$PropagationFlag,'Allow')
   set-acl $InstallArgs.UnzipLocation $Acl
} else {
   $msgtext = 'chrlauncher will install/update/launch Chromium independently for each user.'
   Write-Host $msgtext -ForegroundColor Cyan
   $INIfile = Join-Path (Split-Path $target) 'chrlauncher.ini'
   (gc $INIfile) -replace "^(ChromiumDirectory=).*$",'$1%appdata%\Chromium\bin' | Set-Content $INIfile

$PackageName = 'chrlauncher.portable'
$version = '2.3'
$PackageDir = Split-path (Split-path $MyInvocation.MyCommand.Definition)
$InstallDir = (Join-path $PackageDir ($PackageName.split('.')[0] + $version))
$BitLevel = Get-ProcessorBits

if (Test-Path 'HKLM:\Software\Clients\StartMenuInternet\chrlauncher') {
   Write-Debug 'Removing registry keys that set chrlauncher as the default browser.'
   $Regfile = Join-Path $InstallDir "$BitLevel\RegistryCleaner.reg"
   regedit /s $Regfile

Remove-Item $InstallDir -Recurse -Force

$shortcut = Join-Path ([System.Environment]::GetFolderPath('Desktop')) 'Chromium Launcher.lnk'
if ([System.IO.File]::Exists($shortcut)) {
    Write-Debug 'Found the desktop shortcut. Deleting it...'

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
chrlauncher (portable) 2.5.6 411 Saturday, March 16, 2019 Approved
chrlauncher (portable) 2.5.5 85 Thursday, February 28, 2019 Approved
chrlauncher (portable) 2.5.4 165 Friday, December 21, 2018 Approved
chrlauncher (portable) 2.5 126 Friday, November 16, 2018 Approved
chrlauncher (portable) 2.4.3 439 Tuesday, March 13, 2018 Approved
chrlauncher (portable) 2.4.1 467 Saturday, August 5, 2017 Approved
chrlauncher (portable) 2.3 440 Tuesday, February 14, 2017 Approved
chrlauncher (portable) 273 Wednesday, February 8, 2017 Approved
chrlauncher (portable) 2.2 288 Monday, February 6, 2017 Approved

This package has no dependencies.

Discussion for the chrlauncher (portable) Package

Ground Rules:

  • This discussion is only about chrlauncher (portable) and the chrlauncher (portable) 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 chrlauncher (portable), 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