Downloads of v 1.0.2:


Last Update:

07 Dec 2016

Package Maintainer(s):

Software Author(s):

  • chocolatey


chocolatey core extension admin

Chocolatey Core Extensions

This is not the latest version of Chocolatey Core Extensions available.

1.0.2 | Updated: 07 Dec 2016



Downloads of v 1.0.2:



Software Author(s):

  • chocolatey

Chocolatey Core Extensions 1.0.2

This is not the latest version of Chocolatey Core Extensions available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed


To install Chocolatey Core Extensions, run the following command from the command line or from PowerShell:


To upgrade Chocolatey Core Extensions, run the following command from the command line or from PowerShell:


To uninstall Chocolatey Core Extensions, 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 chocolatey-core.extension -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 chocolatey-core.extension -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 chocolatey-core.extension installed
    name: chocolatey-core.extension
    state: present
    version: 1.0.2
    source: STEP 3 URL

See docs at

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

chocolatey_package 'chocolatey-core.extension' do
  action    :install
  version  '1.0.2'
  source   'STEP 3 URL'

See docs at

    Name: chocolatey-core.extension,
    Version: 1.0.2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller chocolatey-core.extension
   Name     = 'chocolatey-core.extension'
   Ensure   = 'Present'
   Version  = '1.0.2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'chocolatey-core.extension':
  provider => 'chocolatey',
  ensure   => '1.0.2',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install chocolatey-core.extension version="1.0.2" source="STEP 3 URL"

See docs at

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 07 Dec 2016.


This package provides helper functions installed as a Chocolatey extension.
These functions may be used in Chocolatey install/uninstall scripts by declaring this package a dependency in your package's nuspec.

# Export functions that start with capital letter, others are private
# Include file names that start with capital letters, ignore others
$ScriptRoot = Split-Path $MyInvocation.MyCommand.Definition

$pre = ls Function:\*
ls "$ScriptRoot\*.ps1" | ? { $_.Name -cmatch '^[A-Z]+' } | % { . $_  }
$post = ls Function:\*
$funcs = compare $pre $post | select -Expand InputObject | select -Expand Name
$funcs | ? { $_ -cmatch '^[A-Z]+'} | % { Export-ModuleMember -Function $_ }

#Export-ModuleMember -Alias *
    Get application install location

    Function tries to find install location in multiple places. It returns $null if all fail. The following
    locations are tried:
      - local and machine (x32 & x64) various Uninstall keys
      - x32 & x64 Program Files up to the 2nd level of depth
      - native commands available via PATH
      - locale and machine registry key SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths

    Use Verbose parameter to see which of the above locations was used for the result, if any.

    PS> Get-AppInstallLocation choco

    Returns the install location of the application 'choco'.

    [String] or $null
function Get-AppInstallLocation {
        # Regular expression pattern
        [string] $AppNamePattern

    function strip($path) { if ($path.EndsWith('\')) { return $path -replace '.$' } else { $path } }

    $ErrorActionPreference = "SilentlyContinue"

    Write-Verbose "Trying local and machine (x32 & x64) Uninstall keys"
    [array] $key = Get-UninstallRegistryKey $AppNamePattern
    if ($key.Count -eq 1) {
        Write-Verbose "Trying Uninstall key property 'InstallLocation'"
        $location = $key.InstallLocation
        if ($location -and (Test-Path $location))  { return strip $location }

        Write-Verbose "Trying Uninstall key property 'UninstallString'"
        $location = $key.UninstallString.Replace('"', '')
        if ($location) { $location = Split-Path $location }
        if ($location -and (Test-Path $location))  { return strip $location }

        Write-Verbose "Trying Uninstall key property 'DisplayIcon'"
        $location = $key.DisplayIcon
        if ($location) { $location = Split-Path $location }
        if ($location -and (Test-Path $location))  { return strip $location }
    } else { Write-Verbose "Found $($key.Count) keys, aborting this method" }

    $dirs = $Env:ProgramFiles, "$Env:ProgramFiles\*\*"
    if (Get-ProcessorBits 64) { $dirs += ${ENV:ProgramFiles(x86)}, "${ENV:ProgramFiles(x86)}\*\*" }
    Write-Verbose "Trying Program Files with 2 levels depth: $dirs"
    $location = (ls $dirs | ? {$_.PsIsContainer}) -match $AppNamePattern | select -First 1 | % {$_.FullName}
    if ($location -and (Test-Path $location))  { return strip $location }

    Write-Verbose "Trying native commands on PATH"
    $location = (Get-Command -CommandType Application) -match $AppNamePattern | select -First 1 | % { Split-Path $_.Source }
    if ($location -and (Test-Path $location))  { return strip $location }

    $appPaths =  "\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths"
    Write-Verbose "Trying Registry: $appPaths"
    $location = (ls "HKCU:\$appPaths", "HKLM:\$appPaths") -match $AppNamePattern | select -First 1
    if ($location) { $location = Split-Path $location }
    if ($location -and (Test-Path $location))  { return strip $location }

    Write-Verbose "No location found"
    Get temporary location for the package based on its name and version.

    The function returns package cache directory within $Env:TEMP. It will not create the directory
    if it doesn't exist.

    This function is useful when you have to obtain the file using `Get-ChocolateyWebFile` in order
    to perform certain installation steps that other helpers can't do.



function Get-PackageCacheLocation {
    param (
        # Name of the package, by default $Env:ChocolateyPackageName
        [string] $Name    = $Env:ChocolateyPackageName,
        # Version of the package, by default $Env:ChocolateyPackageVersion
        [string] $Version = $Env:ChocolateyPackageVersion

    if (!$Name) { Write-Warning 'Environment variable $Env:ChocolateyPackageName is not set' }
    $res = Join-Path $Env:TEMP $Name

    if (!$Version) { Write-Warning 'Environment variable $Env:ChocolateyPackageVersion is not set' }
    $res = Join-Path $res $Version

    Parses parameters of the package

    Get-PackageParameters "/Shortcut /InstallDir:'c:\program files\xyz' /NoStartup" | set r
    if ($r.Shortcut) {... }
    Write-Host $r.InstallDir

function Get-PackageParameters([string] $Parameters = $Env:ChocolateyPackageParameters) {
    $res = @{}
    $re = "\/([a-zA-Z]+)(:([`"'])?([a-zA-Z0-9- _\\:\.]+)([`"'])?)?"
    $results = $Parameters | Select-String $re -AllMatches | select -Expand Matches
    foreach ($m in $results) {
        $a = $m.Value -split ':'
        $opt = $a[0].Substring(1); $val = $a[1..100]
        if ($val -match '^(".+")|(''.+'')$') {$val = $val -replace '^.|.$'}
        $res[ $opt ] = if ($val) { $val } else { $true }
    Retrieve registry key(s) for system-installed applications from an exact or wildcard search.

    This function will attempt to retrieve a matching registry key for an already installed application,
    usually to be used with a chocolateyUninstall.ps1 automation script.

    The function also prevents `Get-ItemProperty` from failing when handling wrongly encoded registry keys.

.PARAMETER SoftwareName
    Part or all of the Display Name as you see it in Programs and Features.
    It should be enough to be unique.

    If the display name contains a version number, such as "Launchy (2.5)", it is recommended you use a
    fuzzy search `"Launchy (*)"` (the wildcard `*`) so if Launchy auto-updates or is updated outside
    of chocolatey, the uninstall script will not fail.

    Take care not to abuse fuzzy/glob pattern searches. Be conscious of programs that may have shared
    or common root words to prevent overmatching. For example, "SketchUp*" would match two keys with software
    names "SketchUp 2016" and "SketchUp Viewer" that are different programs released by the same company.



    [array]$key = Get-UninstallRegistryKey -SoftwareName "VLC media player"

    Exact match: software name in Programs and Features is "VLC media player"

    [array]$key = Get-UninstallRegistryKey -SoftwareName "Gpg4win (*)"

    Version match: software name is "Gpg4Win (2.3.0)"

    [array]$key = Get-UninstallRegistryKey -SoftwareName "SketchUp [0-9]*"

    Version match: software name is "SketchUp 2016"
    Note that the similar software name "SketchUp Viewer" would not be matched.

function Get-UninstallRegistryKey {
        [Parameter(Mandatory=$true, ValueFromPipeline=$true)]
        [string] $SoftwareName
    Write-Debug "Running 'Get-UninstallRegistryKey' for `'$env:ChocolateyPackageName`' with SoftwareName:`'$SoftwareName`'";

    $ErrorActionPreference = 'Stop'
    $local_key       = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
    $machine_key     = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
    $machine_key6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'

    Write-Verbose "Retrieving all uninstall registry keys"
    [array]$keys = Get-ChildItem -Path @($machine_key6432, $machine_key, $local_key) -ea 0
    Write-Debug "Registry uninstall keys on system: $($keys.Count)"

    Write-Debug "Error handling check: `'Get-ItemProperty`' fails if a registry key is encoded incorrectly."
    [int]$maxAttempts = $keys.Count
    for ([int]$attempt = 1; $attempt -le $maxAttempts; $attempt++)
        $success = $false

        try {
            [array]$foundKey = Get-ItemProperty -Path $keys.PsPath -ea 0 | ? { $_.DisplayName -like $SoftwareName }
            $success = $true
        } catch {
            Write-Debug "Found bad key."
            foreach ($key in $keys){ try{ Get-ItemProperty $key.PsPath > $null } catch { $badKey = $key.PsPath }}
            Write-Verbose "Skipping bad key: $badKey"
            [array]$keys = $keys | ? { $badKey -NotContains $_.PsPath }

        if ($success) { break; }
        if ($attempt -eq 10) {
            Write-Warning "Found more than 10 bad registry keys. Run command again with `'--verbose --debug`' for more info."
            Write-Debug "Each key searched should correspond to an installed program. It is very unlikely to have more than a few programs with incorrectly encoded keys, if any at all. This may be indicative of one or more corrupted registry branches."

    Write-Debug "Found $($foundKey.Count) uninstall registry key(s) with SoftwareName:`'$SoftwareName`'";
    return $foundKey
  Download file with choco internals

  This function will download a file from specified url and return it as a string.
  This command should be a replacement for ubiquitous WebClient in install scripts.

  The benefit of using this command instead of WebClient is that it correctly handles
  system or explicit proxy.

  PS C:\> $s = Get-WebContent ""
  PS C:\> $s -match 'Example Domain'

  First command downloads html content from and stores it in $s.
  Now you can parse and match it as a string.

  PS C:\> $opts = @{ Headers = @{ Referer = '' } }
  PS C:\> $s = Get-WebContent -url "" -options $opts

  You can set headers for http request this way.



  This function can only return string content.
  If you want to download a binary content, please use Get-WebFile.

function Get-WebContent {
        # Url to download

        # Additional options for http request.For now only Headers property supported.

    $filePath =  get_temp_filepath
    Get-WebFile -Url $Url -FileName $filePath -Options $Options 3>$null

    $fileContent = Get-Content $filePath -ReadCount 0 | Out-String
    Remove-Item $filePath


function get_temp_filepath() {
    $tempDir = Get-PackageCacheLocation
    $fileName = [System.IO.Path]::GetRandomFileName()
    Join-Path $tempDir $fileName

    Register application in the system

    The function will register application in the system using App Paths registry key so that you
    can start it by typing its registred name in the Windows Start menu on using run dialog (Win + R).

    To make applications available in the shell, add to your profile Set-AppKeyAliases function.

    Register-Application 'c:\windows\notepad.exe'

    Register application using name derived from its file name.

    Register-Application 'c:\windows\notepad.exe' -Name ntp

    Register application using explicit name.

   Set-AppKeyAliases        -
   Application Registration -

function Register-Application{
        # Full path of the executable to register.

        # Optional name to register with. By default exe name will be used.

        # Register application only for the current user. By default registration is for the machine.

    if (!(Test-Path $ExePath)) { throw "Path doesn't exist: $ExePath" }
    if (!$Name) { $Name = Split-Path $ExePath -Leaf } else { $Name = $Name + '.exe' }

    $appPathKey = "HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\$Name"
    if ($User) { $appPathKey = "HKCU:\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\$Name" }

    If (!(Test-Path $AppPathKey)) { New-Item "$AppPathKey" | Out-Null }
    Set-ItemProperty -Path $AppPathKey -Name "(Default)" -Value $ExePath

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
Chocolatey Core Extensions 1.3.5 256792 Thursday, November 14, 2019 Approved
Chocolatey Core Extensions 1.3.4 461428 Wednesday, October 30, 2019 Approved
Chocolatey Core Extensions 1.3.3 9335327 Wednesday, October 11, 2017 Approved
Chocolatey Core Extensions 1.3.2 18722 Tuesday, October 10, 2017 Approved
Chocolatey Core Extensions 1.3.1 1513002 Tuesday, May 23, 2017 Approved
Chocolatey Core Extensions 1.3.0 325892 Friday, April 21, 2017 Approved
Chocolatey Core Extensions 1.2.0 380191 Monday, March 20, 2017 Approved
Chocolatey Core Extensions 1.1.0 225019 Thursday, February 23, 2017 Approved
Chocolatey Core Extensions 1.0.7 199837 Monday, February 13, 2017 Approved

This package has no dependencies.

Discussion for the Chocolatey Core Extensions Package

Ground Rules:

  • This discussion is only about Chocolatey Core Extensions and the Chocolatey Core Extensions 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 Chocolatey Core Extensions, 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