WinGet, Microsoft’s Windows Package Manager, can install applications from a command line. It is useful when setting up a Windows PC, but package names and sources should be checked before installation. Do not paste a command from an unknown website or assume every search result is the application you intended.
Check that WinGet is available
Open Windows Terminal or PowerShell and run winget --version. If the command is unavailable, check whether App Installer is installed and updated through Microsoft’s supported channels. Work or school PCs may be managed by an administrator who controls package sources or installation rights.
Find and inspect each package
Search for an application with winget search, then inspect the exact result with winget show --id PACKAGE.ID. Check the publisher, package ID, version and installer details before you proceed. A familiar app name can have similarly named entries from different sources.
Install a reviewed set
Microsoft documents installing several package IDs in one command. For example, after checking the IDs and current install details, a command can list packages such as Microsoft.VisualStudioCode Microsoft.PowerShell Git.Git. WinGet processes packages in sequence. You can also run a separate winget install --id PACKAGE.ID command for each app so you can review prompts and results individually.
Leave installers interactive unless you understand what a silent option suppresses. Read any source or package agreement prompts; do not automatically accept them just to make a script run unattended. If an installer requests administrator access, confirm that the application and publisher are expected.
Review and recover
Check the final output for failed packages, restart requests or unclear source selection. Install only software you actually need, keep Windows and applications updated, and use the publisher’s own download instructions if WinGet does not offer a trustworthy match. For repeatable setups, Microsoft documents export and import commands, but review the resulting list before importing it on another computer.
WinGet can save time, but verifying package identity is still part of safe software installation.
