{"componentChunkName":"component---src-templates-post-template-js","path":"/windows-winget-setup-en","result":{"data":{"markdownRemark":{"id":"3dbeb67c-3a70-582a-bf4f-eb1d59a63645","html":"
\n

This page has been machine-translated from the original page.

\n
\n

This time, I will use Windows Package Manager, whose major version was just recently released, to install the applications I normally use.

\n

This article covers the following:

\n
    \n
  1. How to use Windows Package Manager
    2. \n
  2. A list of Windows Package Manager commands
    3. \n
  3. Installing frequently used applications with Windows Package Manager
    4. \n
  4. Errors that occur when using Windows Package Manager
    5. \n
\n

Basically, I will refer to the following official documentation and official blog post.

\n\n\n

Table of Contents

\n\n

Enable Windows Package Manager

\n

Download [Microsoft.DesktopAppInstaller_8wekyb3d8bbwe.appxbundle] from the GitHub releases page.

\n\n

I will use the latest version available right now, v1.0.11692. (The version in the screenshot is old, though…)

\n

\n \n \n \n \n \n \n \n \n

\n

If you can confirm in PowerShell that commands such as [winget.exe install —id search APPNAME] work, you are good to go.

\n

\n \n \n \n \n \n \n \n \n

\n

winget Commands

\n

The commands currently available in winget seem to be as follows.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
CommandOverview
exportExports a list of installed packages.
featuresDisplays the status of experimental features.
hashGenerates the installer’s SHA256 hash.
importInstalls all packages from a file.
installInstalls the specified application.
listDisplays installed packages.
searchSearches for applications.
settingsSearches for applications.
showDisplays details of the specified application.
sourceAdds, removes, and updates the Windows Package Manager repositories accessed by the winget tool.
validateValidates manifest files submitted to the Windows Package Manager repository.
uninstallUninstalls the specified package.
upgradeUpgrades the specified package.
\n

Install Applications

\n

So, I installed the tools I usually use with winget.

\n

The list of applications I install with winget is as follows.

\n

Web Browsers

\n\n

Development Tools

\n\n

Communication Tools

\n\n

Others

\n\n

Installation Script

\n

The tools above can be installed with the following script.

\n
winget.exe install --id Google.Chrome\nwinget.exe install --id Mozilla.Firefox\nwinget.exe install --id SlackTechnologies.Slack\nwinget.exe install --id Discord.Discord\nwinget.exe install --id Zoom.Zoom\nwinget.exe install --id LINE.LINE\nwinget.exe install --id Canonical.Ubuntu\nwinget.exe install --id Debian.Debian\nwinget.exe install --id Typora.Typora\nwinget.exe install --id Microsoft.VisualStudioCode\nwinget.exe install --id Microsoft.VisualStudio.2019.Community\nwinget.exe install --id Microsoft.WindowsTerminal\nwinget.exe install --id Git.Git\nwinget.exe install --id Amazon.Kindle\nwinget.exe install --id Microsoft.PowerToys\nwinget.exe install --id WiresharkFoundation.Wireshark\nwinget.exe install --id Adobe.AdobeAcrobatReaderDC\nwinget.exe install --id SoftwareFreedomConservancy.QEMU\nwinget.exe install --id Spotify.Spotify\nwinget.exe install --id OBSProject.OBSStudio
\n

At present, unlike Linux’s apt command, you cannot install multiple packages together on a single line. To install them in bulk, you need to load an import file defined in JSON format using the [--import-file] option.

\n

Troubles When Installing Applications with winget

\n

Hash Mismatch

\n

When installing with winget, if you do not specify a version it is treated as the latest, and during installation winget performs hash verification against the manifest file it has.

\n

It seems fairly common for inconsistencies to occur between the manifest file winget has and the actual installer.

\n
PS C:`Users`kash1064> winget.exe install --id Google.Chrome\n見つかりました Google Chrome [Google.Chrome]\nこのアプリケーションは所有者からライセンス供与されます。\nMicrosoft はサードパーティのパッケージに対して責任を負わず、ライセンスも付与しません。\nDownloading https://dl.google.com/edgedl/chrome/install/GoogleChromeStandaloneEnterprise64.msi\n  ██████████████████████████████  75.2 MB / 75.2 MB\nインストーラーのハッシュが一致しません; このチェックを無効にするには、--force を使用します
\n

After looking at the issue, it seems that, under the current specification, it is unavoidable that this error occurs in some cases.

\n

That makes it seem less stable for automation by script.

\n\n

Version Mismatch with the Microsoft Store Version

\n

If the same application is installed from the Microsoft Store, the following mismatch error may occur.

\n

Uninstalling the application installed from the Microsoft Store resolves it.

\n

\n \n \n \n \n \n \n \n \n \\

\n

Summary

\n

I tried installing applications with Windows Package Manager, whose major version has been released.

\n

There still seem to be many issues to work through, but being able to install the applications you want with a single copy-and-paste, without the usual “Google search → download the installer → install” steps, is extremely convenient.

","fields":{"slug":"/windows-winget-setup-en","tagSlugs":["/tag/windows/","/tag/winget/","/tag/notes/","/tag/備忘録/","/tag/english/"]},"frontmatter":{"date":"2021-06-27","description":"This time, I will use Windows Package Manager, whose major version was just recently released, to install the applications I normally use.","tags":["Windows","winget","Notes","備忘録","English"],"title":"Install Frequently Used Applications with Windows Package Manager (winget)","socialImage":{"publicURL":"/static/dc4d8b7f8795f3c3d3489d9957d155f2/no-image.png"}}}},"pageContext":{"slug":"/windows-winget-setup-en"}},"staticQueryHashes":["251939775","401334301","825871152"]}