Welcome to the Chocolatey Community Package Repository! The packages found in this section of the site are provided, maintained, and moderated by the community.
Moderation
Every version of each package undergoes a rigorous moderation process before it goes live that typically includes:
- Security, consistency, and quality checking
- Installation testing
- Virus checking through VirusTotal
- Human moderators who give final review and sign off
More detail at Security and Moderation.
Organizational Use
If you are an organization using Chocolatey, we want your experience to be fully reliable. Due to the nature of this publicly offered repository, reliability cannot be guaranteed. Packages offered here are subject to distribution rights, which means they may need to reach out further to the internet to the official locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition of Chocolatey (including the free open source edition), you can host your own packages and cache or internalize existing community packages.
Disclaimer
Your use of the packages on this site means you understand they are not supported or guaranteed in any way. Learn more...
- Passing
- Failing
- Pending
- Unknown / Exempted

Downloads:
608
Downloads of v 1.0.2.20190614:
351
Last Update:
08 Jul 2019
Package Maintainer(s):
Software Author(s):
- Michael Chavinda
Tags:
admin powershell module bash with- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download

posh-with (PowerShell Module)
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
608
Downloads of v 1.0.2.20190614:
351
Maintainer(s):
Software Author(s):
- Michael Chavinda
Edit Package
To edit the metadata for a package, please upload an updated version of the package.
Chocolatey's Community Package Repository currently does not allow updating package metadata on the website. This helps ensure that the package itself (and the source used to build the package) remains the one true source of package metadata.
This does require that you increment the package version.
All Checks are Passing
2 Passing Test
To install posh-with (PowerShell Module), run the following command from the command line or from PowerShell:
To upgrade posh-with (PowerShell Module), run the following command from the command line or from PowerShell:
To uninstall posh-with (PowerShell Module), 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
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 https://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
-
Open Source
- Download the Package Download
- Follow manual internalization instructions
-
Package Internalizer (C4B)
- Run
choco download poshwith --internalize --source=https://chocolatey.org/api/v2
(additional options) - Run
choco push --source="'http://internal/odata/repo'"
for package and dependencies - Automate package internalization
- Run
3. Enter your internal repository url
(this should look similar to https://chocolatey.org/api/v2)
4. Choose your deployment method:
choco upgrade poshwith -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 poshwith -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 poshwith installed
win_chocolatey:
name: poshwith
state: present
version: 1.0.2.20190614
source: STEP 3 URL
See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
Coming early 2020! Central Managment Reporting available now! More information...
chocolatey_package 'poshwith' do
action :install
version '1.0.2.20190614'
source 'STEP 3 URL'
end
See docs at https://docs.chef.io/resource_chocolatey_package.html.
Chocolatey::Ensure-Package
(
Name: poshwith,
Version: 1.0.2.20190614,
Source: STEP 3 URL
);
Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.
cChocoPackageInstaller poshwith
{
Name = 'poshwith'
Ensure = 'Present'
Version = '1.0.2.20190614'
Source = 'STEP 3 URL'
}
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
package { 'poshwith':
provider => 'chocolatey',
ensure => '1.0.2.20190614',
source => 'STEP 3 URL',
}
Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.
salt '*' chocolatey.install poshwith version="1.0.2.20190614" 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 by moderator mkevenaar on 19 Jul 2019.
Program prefixing for continuous workflow using a single tool.
You can pass the following parameters:
/core
- Installs the module in the AllUsers scope for PowerShell Core;/desktop
- Installs the module in the AllUsers scope for Windows PowerShell (ie. Desktop Edition);
You can pass both /core
and /desktop
parameters to install on both. If you pass no parameters then /desktop
is assumed.
NOTE: This module requires a minimum of PowerShell v3.
NOTE: This is an automatically updated package. If you find it is out of date by more than a week, please contact the maintainer(s) and let them know the package is no longer updating correctly.
$ErrorActionPreference = 'Stop'
$moduleName = 'posh-with' # this could be different from package name
Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue
$ErrorActionPreference = 'Stop'
$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$moduleName = 'posh-with' # this may be different from the package name and different case
$moduleVersion = '1.0.2' # this may change so keep this here
$savedParamsPath = Join-Path $toolsDir -ChildPath 'parameters.saved'
if ($PSVersionTable.PSVersion.Major -lt 3) {
throw "$moduleName module requires a minimum of PowerShell v3."
}
# module may already be installed outside of Chocolatey
Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue
# remove the saved parameters file if it exists
if (Test-Path -Path $savedParamsPath) {
Remove-Item -Path $savedParamsPath -Force
}
$params = Get-PackageParameters
$sourcePath = Join-Path -Path $toolsDir -ChildPath "$modulename.zip"
$destinationPath = @()
if ($params.Desktop -or (-not $params.Core)) {
$desktopPath = Join-Path -Path $env:ProgramFiles -ChildPath "WindowsPowerShell\Modules\$moduleName"
# PS > 5 needs to extract to a folder with the module version
if ($PSVersionTable.PSVersion.Major -ge 5) {
$desktopPath = Join-Path -Path $desktopPath -ChildPath $moduleVersion
}
$destinationPath += $desktopPath
}
if ($params.Core) {
$destinationPath += Join-Path -Path $env:ProgramFiles -ChildPath "PowerShell\Modules\$moduleName\$moduleVersion"
}
ForEach ($destPath in $destinationPath) {
Write-Verbose "Installing '$modulename' to '$destPath'."
# check destination path exists and create if not
if (Test-Path -Path $destPath) {
$null = New-Item -Path $destPath -ItemType Directory -Force
}
Get-ChocolateyUnzip -FileFullPath $sourcePath -Destination $destPath -PackageName $moduleName
# save the locations where the module was installed so we can uninstall it
Add-Content -Path $savedParamsPath -Value $destPath
}
# For PowerShell 4 the module destination needs to be added to the PSModulePath
if ($PSVersionTable.PSVersion.Major -lt 4) {
$modulePaths = [Environment]::GetEnvironmentVariable('PSModulePath', 'Machine') -split ';'
if ($modulePaths -notcontains $destPath) {
Write-Verbose "Adding '$destPath' to PSModulePath."
$newModulePath = @($destPath, $modulePaths) -join ';'
[Environment]::SetEnvironmentVariable('PSModulePath', $newModulePath, 'Machine')
$env:PSModulePath = $newModulePath
}
}
# cleanup the module from the Chocolatey $toolsDir folder
Remove-Item -Path $sourcePath -Force -Recurse
$ErrorActionPreference = 'Stop'
$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
$moduleName = $env:ChocolateyPackageName # this may be different from the package name and different case
$savedParamsPath = Join-Path $toolsDir -ChildPath 'parameters.saved'
if (Test-Path -Path $savedParamsPath) {
$removePath = Get-Content -Path $savedParamsPath
}
else {
$removePath = Join-Path -Path $env:ProgramFiles -ChildPath "WindowsPowerShell\Modules\$moduleName"
}
ForEach ($path in $removePath) {
Write-Verbose "Removing all version of '$moduleName' from '$path'."
Remove-Item -Path $path -Recurse -Force -ErrorAction SilentlyContinue
}
# remove path of module from $env:PSModulePath
if ($PSVersionTable.PSVersion.Major -lt 4) {
$modulePaths = [Environment]::GetEnvironmentVariable('PSModulePath', 'Machine') -split ';'
Write-Verbose "Removing '$sourcePath' from PSModulePath."
$newModulePath = $modulePaths | Where-Object { $_ -ne $sourcePath }
[Environment]::SetEnvironmentVariable('PSModulePath', $newModulePath, 'Machine')
$env:PSModulePath = $newModulePath
}
From: https://github.com/JanDeDobbeleer/posh-with/blob/master/LICENSE.txt
LICENSE
Copyright 2016 Michael Chavinda
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
md5: BBFD3AB26150DD81183B9AF1C1F91609 | sha1: E49C221EBFFCF8C527819D0E0C39513440920060 | sha256: E625A87234AE2BD13CC651EB88001EB461ACC757EB935E9189DD08973C919F0F | sha512: 64E2043237B3C50EC6C43D9EF364B03F93590AC6EB9AC526E074C263860D6E5B13951600C4A03E988296B70F77FA78AB6BADA3524BBF86581BB9DE308780CD46
VERIFICATION
To verify the files using the project source:
1. Please go to the project source location (https://github.com/JanDeDobbeleer/posh-with) and download the source files;
2. Build the source to create the binary files to verify;
3. Use Get-FileHash -Path <FILE TO VERIFY> to get the file hash value from both the built file (from step 1 above) and the file from the package and compare them;
Alternatively you can download the module from the PowerShell Gallery ...
Save-Module -Name posh-with -Path <PATH TO DOWNLOAD TO>
... and compare the files from the package against those in the installed module. Again use Get-FileHash -Path <FILE TO VERIFY> to retrieve those hash values.
Log in or click on link to see number of positives.
- poshwith.1.0.2.20190614.nupkg (e242aa288224) - ## / 61
- posh-with.zip (e625a87234ae) - ## / 60
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 |
---|---|---|---|
posh-with (PowerShell Module) 1.0.2.20190614 | 351 | Monday, July 8, 2019 | Approved |
posh-with (PowerShell Module) 1.0.2 | 257 | Monday, May 14, 2018 | Approved |
2016 Michael Chavinda
-
- chocolatey (≥ 0.10.8)
Ground Rules:
- This discussion is only about posh-with (PowerShell Module) and the posh-with (PowerShell Module) 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 posh-with (PowerShell Module), 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.