Downloads of v 4.2:


Last Update:

24 Nov 2019

Package Maintainer(s):

Software Author(s):

  • Gerson Kurz



pathed - edit PATH variable from command prompt

  • 1
  • 2
  • 3

4.2 | Updated: 24 Nov 2019



Downloads of v 4.2:



Software Author(s):

  • Gerson Kurz



  • 1
  • 2
  • 3
pathed - edit PATH variable from command prompt 4.2

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests

Validation Testing Passed

Verification Testing Passed


Scan Testing Successful:

No detections found in any package files


To install pathed - edit PATH variable from command prompt, run the following command from the command line or from PowerShell:


To upgrade pathed - edit PATH variable from command prompt, run the following command from the command line or from PowerShell:


To uninstall pathed - edit PATH variable from command prompt, 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 pathed -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 pathed -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 pathed installed
    name: pathed
    state: present
    version: 4.2
    source: STEP 3 URL

See docs at

chocolatey_package 'pathed' do
  action    :install
  version  '4.2'
  source   'STEP 3 URL'

See docs at

    Name: pathed,
    Version: 4.2,
    Source: STEP 3 URL

Requires Otter Chocolatey Extension. See docs at

cChocoPackageInstaller pathed
   Name     = 'pathed'
   Ensure   = 'Present'
   Version  = '4.2'
   Source   = 'STEP 3 URL'

Requires cChoco DSC Resource. See docs at

package { 'pathed':
  provider => 'chocolatey',
  ensure   => '4.2',
  source   => 'STEP 3 URL',

Requires Puppet Chocolatey Provider module. See docs at

salt '*' chocolatey.install pathed version="4.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 by moderator Pauby on 04 Dec 2019.


This tool helps you to edit the PATH environment variable from a command line - within limits.

$ErrorActionPreference = 'Stop'; # stop on all errors
$toolsDir              = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"

$packageArgs = @{
    packageName     = 'pathed'
    # 32-bit
    FileFullPath    = "$toolsDir\"
    # 64-bit
    FileFullPath64  = $FileFullPath
    # misc
    Destination     = $toolsDir

Get-ChocolateyUnzip @packageArgs

pathed is freeware, BSD-licensed.
md5: 50E96AD15DE5372C65BF257100E4B87C | sha1: 509CC3C950BDB0D879258478FE7B955D6E0985F3 | sha256: A60EC022CAECA9FF1599AA3F748EBCB8ED92A7C7255D30A3C4A7F6EF3F0E626B | sha512: 0D0566EEDA61551527E53D931564A434165B1EBD3F516A740C60924DB49B76A9EBFC7951EE1957C040085870A6ED5C0E5C803C648F5CD64DA819A2A3544DBB7A
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

The extension has been downloaded from their official download link listed on <>
and can be verified like this:

1. Download the following gtools installer:

2. Extract the gtools-current.exe into some folder and copy following files that are required to run pathed 

3. You can use one of the following methods to obtain the checksum 
  - Use powershell function 'Get-Filehash'
  - Use chocolatey utility 'checksum.exe'

  filename: pathed.exe
  checksum type: sha256
  checksum: 1128cec0d856e066df878d02d21ac7800503aee72b91d3c0629b745cb6255329

  filename: GSharpTools.dll
  checksum type: sha256
  checksum: f438cbd4b4a900540a61da8b6018b6db030b03e0a75173b335f7a0f5733a943a

  filename: log4net.dll
  checksum type: sha256
  checksum: 3691c63ee84b2628e0c021418d0dee979b50ce550178db3efc5e19fe5bad5b4c

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

This package has no dependencies.

Discussion for the pathed - edit PATH variable from command prompt Package

Ground Rules:

  • This discussion is only about pathed - edit PATH variable from command prompt and the pathed - edit PATH variable from command prompt 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 pathed - edit PATH variable from command prompt, 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