winget_windows_package_manager

winget Windows Package Manager

Return to PowerShell Module Installation - Install-Module WinGet, winget Windows Package Manager vs Chocolatey

winget - the Windows Package Manager

Snippet from Wikipedia: Windows Package Manager

The Windows Package Manager (also known as winget) is a free and open-source package manager designed by Microsoft for Windows 10 and Windows 11. It consists of a command-line utility and a set of services for installing applications. Independent software vendors can use it as a distribution channel for their software packages.


WinGet is a command-line tool for managing Windows software packages. It allows users to discover, install, upgrade, remove, and configure applications on Windows 10 and Windows 11 systems.

Here are some usage examples to help you get started with WinGet:

  1. Basic Commands
  1. Search for a Package

To search for a package, use the `search` command: ```powershell winget search <package_name> ``` Example: ```powershell winget search vscode ```

  1. Install a Package

To install a package, use the `install` command: ```powershell winget install <package_name> ``` Example: ```powershell winget install Microsoft.VisualStudioCode ```

  1. Upgrade a Package

To upgrade a package, use the `upgrade` command: ```powershell winget upgrade <package_name> ``` Example: ```powershell winget upgrade Microsoft.VisualStudioCode ```

  1. List Upgradable Packages

To list all packages that have updates available, use the `upgrade` command without specifying a package name: ```powershell winget upgrade ```

  1. Uninstall a Package

To uninstall a package, use the `uninstall` command: ```powershell winget uninstall <package_name> ``` Example: ```powershell winget uninstall Microsoft.VisualStudioCode ```

  1. Show Package Details

To show details about a specific package, use the `show` command: ```powershell winget show <package_name> ``` Example: ```powershell winget show Microsoft.VisualStudioCode ```

  1. Advanced Commands
  1. Install a Package by ID

Each package in WinGet has a unique identifier. You can install a package using its ID: ```powershell winget install –id <package_id> ``` Example: ```powershell winget install –id Microsoft.VisualStudioCode ```

  1. Install a Specific Version

To install a specific version of a package, use the `–version` option: ```powershell winget install <package_name> –version <version_number> ``` Example: ```powershell winget install Microsoft.VisualStudioCode –version 1.56.2 ```

  1. Export and Import Package Lists

You can export a list of installed packages and then import it on another system.

**Export:** ```powershell winget export -o packages.json ```

**Import:** ```powershell winget import -i packages.json ```

  1. Install Multiple Packages

You can install multiple packages by chaining the install commands: ```powershell winget install Microsoft.VisualStudioCode && winget install Google.Chrome ```

  1. Examples of Commonly Used Packages
  1. Install Google Chrome

```powershell winget install Google.Chrome ```

  1. Install 7-Zip

```powershell winget install 7zip.7zip ```

  1. Install Git

```powershell winget install Git.Git ```

  1. Install Node.js

```powershell winget install OpenJS.NodeJS ```

  1. Scripting with WinGet

You can use WinGet in PowerShell scripts to automate software management tasks. Here’s an example script to install a list of applications:

```powershell $packages = @(

   "Google.Chrome",
   "Microsoft.VisualStudioCode",
   "7zip.7zip",
   "Git.Git",
   "OpenJS.NodeJS"
)

foreach ($package in $packages) {

   winget install $package --silent --accept-package-agreements --accept-source-agreements
} ```

This script iterates through a list of package names and installs each one silently, accepting all package and source agreements.

WinGet is a powerful tool for managing software installations on Windows, simplifying the process of keeping applications up to date and ensuring consistency across multiple systems.


]] | latest release version = v1.0.11692 | latest release date = {{Start date and age | 2021 | 06 | 14}}<ref name="github">{{cite web | //github.com/microsoft/winget-cli/tags | title=Tags · microsoft/winget-cli · GitHub | website=GitHub | language=en | access-date=2021-07-10}}</ref> | latest preview version = v-0.4.11391-preview | latest preview date = {{Start date and age | 2021 | 05 | 20}}{{r | github}} | repo = {{URL | https://github.com/microsoft/winget-cli}} | programming language = [[C++ ]] | operating system = [[Windows 10, Windows 11 ]] | platform = | size = | language = English | language count = <!-- DO NOT include this parameter unless you know what it does --> | language footnote = | genre = [[Package manager ]] | license = [[MIT License ]] | website = {{URL | https://docs.microsoft.com/en-us/windows/package-manager/}} }} The '''Windows Package Manager''' (also known as '''winget''') is a [[free and open-source package manager designed by Microsoft for Windows 10 and Windows 11. It consists of a command-line utility and a set of services for installing applications.<ref>

</ref><ref name=“devblogs”>Windows Package Manager Preview ] | Windows Command Line]</ref> [[Independent software vendor | ISVs can use it as a distribution channel for their software packages.

History

Windows Package Manager was first announced at the Microsoft Build (developer conference) | Build developer conference in May 2020.<ref>Microsoft debuts Windows Package Manager for your dev environment ] | VentureBeat]</ref><ref name="devblogs" /> Before deciding to develop Windows Package Manager, the team behind it explored [[Chocolatey, Scoop, Ninite, AppGet, Npackd and the PowerShell-based OneGet.<ref name=“devblogs” /> After the announcement of winget, Keivan Beigi, the developer of AppGet claimed<ref>

</ref>

that Microsoft interviewed him in December 2019 under the pretense of acquiring AppGet and hiring Beigi. After talking with Beigi, Microsoft allegedly ceased communication with him until confirming one day before the launch of winget that they would not be hiring him. Beigi was dismayed at Microsoft's lack of attribution of AppGet. The release of winget led Beigi to announce that AppGet would be discontinued in August 2020.<ref>

</ref><ref>

</ref><ref>

</ref> Microsoft responded with a blog post crediting a number of winget's features to AppGet.<ref>

</ref><ref>Microsoft gives AppGet creator credit for Windows Package Manager - Neowin</ref>

Microsoft released version 1.0 of Windows Package Manager on May 27, 2021. The Microsoft Community Repository included over 1,400 packages at that date.<ref>

</ref>

Overview

The winget tool supports installers based on .exe | EXE, .msix | MSIX, and .msi | MSI.<ref>Use the winget tool to install and manage applications ] | Microsoft Docs]</ref> The public ''Windows Package Manager Community repository'' hosts [[manifest files for supported applications in YAML format.<ref name=“winget-pkgs”>GitHub - microsoft/winget-pkgs: The Microsoft community Windows Package Manager manifest repository</ref> In September 2020, Microsoft added the ability to install applications from the Microsoft Store (digital) | Microsoft Store and a command auto-completion feature.<ref>

</ref>

To reduce the likelihood of malicious software making its way into the repository and onto the target machine, Windows Package Manager uses Microsoft SmartScreen, static analysis, SHA256 cryptographic hash function | hash validation and other processes.<ref name=“zdnet”>

</ref><ref>How to Use Windows Package Manager - Petri</ref>

The winget client source code and the community manifest repository are licensed under MIT License and hosted on GitHub.<ref>

</ref><ref name=“winget-pkgs” />

Commands

See also

References

winget_windows_package_manager.txt · Last modified: 2025/02/01 06:21 by 127.0.0.1

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki