Update Windows Apps with WinGet: Preview First, Upgrade Second

Windows Package Manager, better known as WinGet, can check installed applications against package sources and upgrade many of them from a terminal. It is fast, scriptable, and far less tedious than opening a dozen vendor updaters. It is not a reason to run an unreviewed bulk command on an important machine.

Start with an inventory

Open Windows Terminal and run:

winget upgrade

This is the inspection step. WinGet lists packages for which it can identify a newer available version. Read the package name, installed version, available version, and source. If a package name is ambiguous, do not guess; inspect it before approving the change.

Upgrade one package first

For a targeted update, use the package identifier shown by the inventory:

winget upgrade --id Vendor.PackageName

The identifier is safer than a broad text match. Review any installer prompt and reopen the application after the update to confirm that settings, plugins, and file associations still work.

Use “all” only after reviewing the list

Once the inventory is understood, this command requests every normally eligible update:

winget upgrade --all

Pinned packages are excluded by default. That is useful when a driver utility, development tool, or production application must stay on a tested release. The --include-pinned option overrides that protection, so it should be a conscious choice rather than a copied addition.

Unknown versions need extra caution

WinGet sometimes recognizes an installed application but cannot determine its current version. Those entries are not automatically included in a normal bulk upgrade. The --include-unknown option can include them, but the uncertainty means you should verify the app and installer source first.

Important limits

• WinGet does not replace Windows Update for the operating system and many drivers.
• An application may still display its own license, migration, or restart prompt.
• Closing active work before a bulk run prevents installers from forcing a disruptive restart.
• The --uninstall-previous behavior depends on package support and should not be assumed to provide a rollback copy.

A dependable maintenance routine

Run the preview, update a small number of critical applications, then use the bulk command for the remainder. Save the terminal output when maintaining several machines. If an upgrade fails, the package identifier and exit code give you a precise starting point for diagnosis.

WinGet is most valuable when it makes updates visible and repeatable. The five seconds spent reading the preview are what keep convenience from becoming guesswork.