WinGet on Work You Can Explain

Build a Reproducible Windows Setup

Fri, 24 Jul 2026 00:00:00 -0500

A reproducible Windows setup is not a screenshot of installed applications. It is a tested set of source artifacts that explains what the student needs, how to establish it, and how to verify the result.

Create a versioned repository containing package IDs, an inspected WinGet export or configuration, small setup steps, secret-free examples, and a verification script. Begin with current course requirements, not every application installed over the computer’s lifetime.

Install Your First Developer Tools with WinGet

Fri, 24 Jul 2026 00:00:00 -0500

Use WinGet as an inspectable installer, not a shortcut around course or device policy. Search for a tool, inspect the exact package ID, publisher, source, and version, install one approved package, then verify both WinGet’s record and the tool itself.

Check availability and constraints

In a standard PowerShell session:

winget --version
winget --help

WinGet availability depends on Windows, App Installer, organization policy, and device management. A school may block sources, installations, Store access, or administrator elevation. Do not bypass those controls. Ask institutional IT or the instructor when a required tool is unavailable.

Upgrade Software Safely with WinGet

Fri, 24 Jul 2026 00:00:00 -0500

Upgrade one package intentionally. First inventory available updates, identify the installed and available versions, read relevant release information, protect current work, upgrade the exact package, and verify behavior.

Inventory without changing

Run from a standard PowerShell session:

winget list --upgrade-available

Microsoft documents this filter in winget list. The result can include software originally installed by other means, and version detection may be incomplete.

Do not begin with a bulk upgrade. Choose one course-required, noncritical tool whose interruption you can tolerate.