Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

58,480

Downloads of v 1.9.25180:

10

Last Update:

28 Oct 2024

Package Maintainer(s):

Software Author(s):

  • Microsoft

Tags:

winget-cli winget powershell

WinGet PowerShell Module (Microsoft.WinGet.Client) (Install)

  • 1
  • 2
  • 3

1.9.25180 | Updated: 28 Oct 2024

Downloads:

58,480

Downloads of v 1.9.25180:

10

Maintainer(s):

Software Author(s):

  • Microsoft

WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.9.25180

Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by Microsoft. The inclusion of Microsoft trademark(s), if any, upon this webpage is solely to identify Microsoft goods or services and not for commercial purposes.

  • 1
  • 2
  • 3

All Checks are Passing

3 Passing Tests


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install WinGet PowerShell Module (Microsoft.WinGet.Client) (Install), run the following command from the command line or from PowerShell:

>

To upgrade WinGet PowerShell Module (Microsoft.WinGet.Client) (Install), run the following command from the command line or from PowerShell:

>

To uninstall WinGet PowerShell Module (Microsoft.WinGet.Client) (Install), run the following command from the command line or from PowerShell:

>

Deployment Method:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)


2. Setup Your Environment

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://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. Copy Your Script

choco upgrade winget.powershell -y --source="'INTERNAL REPO 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 winget.powershell -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

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

Exit $exitCode

- name: Install winget.powershell
  win_chocolatey:
    name: winget.powershell
    version: '1.9.25180'
    source: INTERNAL REPO URL
    state: present

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


chocolatey_package 'winget.powershell' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '1.9.25180'
end

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


cChocoPackageInstaller winget.powershell
{
    Name     = "winget.powershell"
    Version  = "1.9.25180"
    Source   = "INTERNAL REPO URL"
}

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


package { 'winget.powershell':
  ensure   => '1.9.25180',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

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


4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Package Approved

This package was approved as a trusted package on 30 Oct 2024.

Description

This is the PowerShell module for the WinGet command line tool, 'Microsoft.WinGet.Client'.

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.

Notes

  • This module requires at least PowerShell v5.1.0.
  • This module requires WinGet CLI to be installed. We don't add this as a dependency as you may have this already installed outside of the Chocolatey ecosystem. However, to install it using Chocolatey CLI, run choco install winget.
  • 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.

tools\.skipAutoUninstaller
 
tools\chocolateyBeforeModify.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition

. $(Join-Path -Path $toolsDir -ChildPath "$($env:ChocolateyPackageName)-helpers.ps1")

Remove-Module -Name $moduleName -Force -ErrorAction SilentlyContinue
tools\chocolateyInstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition

. $(Join-Path -Path $toolsDir -ChildPath "$($env:ChocolateyPackageName)-helpers.ps1")

if ($PSVersionTable.PSVersion -lt [version]$minPSVersion) {
    throw "$moduleName module requires a minimum of PowerShell v$minPSVersion."
}

# 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"
    $destinationPath += $desktopPath
}

if ($params.Core) {
    $destinationPath += Join-Path -Path $env:ProgramFiles -ChildPath "PowerShell\Modules\$moduleName"
}

ForEach ($destPath in $destinationPath) {
    Write-Verbose "Installing '$modulename' to '$destPath'."

    # PS > 5 needs the module version at the end
    $fullDestPath = (Join-Path -Path $destPath -ChildPath $moduleVersion)

    # check destination path exists and create if not
    if (-not (Test-Path -Path $fullDestPath)) {
        $null = New-Item -Path $fullDestPath -ItemType Directory -Force
    }

    Get-ChocolateyUnzip -FileFullPath $sourcePath -Destination $fullDestPath -PackageName $moduleName

    # save the locations where the module was installed so we can uninstall it
    Add-Content -Path $savedParamsPath -Value $destPath
}

# cleanup the module from the Chocolatey $toolsDir folder
Remove-Item -Path $sourcePath -Force -Recurse
tools\chocolateyUninstall.ps1
$ErrorActionPreference = 'Stop'

$toolsDir = Split-Path -parent $MyInvocation.MyCommand.Definition
. $(Join-Path -Path $toolsDir -ChildPath "$($env:ChocolateyPackageName)-helpers.ps1")

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
}
tools\LICENSE.txt
    MIT License

    Copyright (c) Microsoft Corporation. All rights reserved.

    Permission is hereby granted, free of charge, to any person obtaining a copy
    of this software and associated documentation files (the "Software"), to deal
    in the Software without restriction, including without limitation the rights
    to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
    copies of the Software, and to permit persons to whom the Software is
    furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in all
    copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    SOFTWARE
tools\Microsoft.WinGet.Client.zip
md5: C2263B537BD60632CDCA43F72DCC498C | sha1: 1C1CDEB39F1ADC719D123C7AAB746C14F888325C | sha256: C0A7616D9E7881B81F5ADCC42BD8A47A483F5DB3AC56152429A42C3CBF0E80EB | sha512: 5F2D1B8908EBD49C21C40A79B209EE57D7ECB623DF3D2E8B0FFFA1CAC159DE0F6D85B2AB4DCC76D2929A722D86EACC93794A7531E508089386A80DFC07B13EEE
tools\VERIFICATION.txt

VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

NOTE: There is no releases on the GitHub project source page.

1. Download the module from the PowerShell Gallery either using the PowerShell below or directly from the gallery:

    Save-Module -Name Microsoft.WinGet.Client -Path <PATH TO DOWNLOAD TO>

2. 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.

File 'LICENSE.txt' is obtained from https://github.com/microsoft/winget-cli/blob/master/LICENSE
tools\winget.powershell-helpers.ps1
$ErrorActionPreference = 'Stop'

$moduleName = 'Microsoft.WinGet.Client' # this could be different from package name
$moduleVersion = '1.9.25180'
$savedParamsPath = Join-Path $toolsDir -ChildPath 'parameters.saved'
$minPSVersion = '5.1.0'

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.

Add to Builder Version Downloads Last Updated Status
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.9.2505 10392 Tuesday, September 24, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.9.2411 17167 Thursday, August 29, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.8.1911 6143 Thursday, July 11, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.8.1791 1200 Saturday, June 29, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.8.1133 2988 Thursday, April 25, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.7.10861 1662 Thursday, March 28, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.7.10661 2446 Thursday, March 7, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.7.10651 24 Wednesday, March 6, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.7.10613 780 Saturday, March 2, 2024 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 1.6.3133 13312 Sunday, November 19, 2023 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 0.2.2 925 Wednesday, October 11, 2023 Approved
WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 0.2.1 1431 Thursday, June 8, 2023 Approved

This package has no dependencies.

Discussion for the WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) Package

Ground Rules:

  • This discussion is only about WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) and the WinGet PowerShell Module (Microsoft.WinGet.Client) (Install) 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 WinGet PowerShell Module (Microsoft.WinGet.Client) (Install), 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