The quickest way to check the WinGet version in Windows 11 is to open Windows Terminal, PowerShell, or Command Prompt and run winget --version. WinGet prints one focused value, such as v1.29.250. For the Windows version, architecture, and App Installer package version that go with that client, run winget --info.
I reproduced three read-only checks on Windows 11 Home Single Language version 25H2, build 26220.7872. winget --version returned v1.29.250; winget --info identified Windows Package Manager v1.29.250 and the Microsoft.DesktopAppInstaller package v1.29.250.0; and a targeted PowerShell package query confirmed App Installer version 1.29.250.0 for X64. No package was installed, updated, removed, downloaded, repaired, or queried from a remote source.
Which WinGet version number should you record?
Record the value from winget --version when an app, script, bug report, or feature requires a particular WinGet client version. The leading v is presentation, so v1.29.250 means client version 1.29.250. Do not compare that value with the Windows 11 build number, a Store app's version, or the version of a package you plan to install.
WinGet is the command-line client for Windows Package Manager. Microsoft delivers it as part of the App Installer system component on Windows desktop. That packaging relationship is why winget --info can show both a Windows Package Manager client version and a Microsoft.DesktopAppInstaller MSIX package version.
The package version can have a fourth numeric component. On the tested PC, the client was 1.29.250 while the package was 1.29.250.0. That does not indicate a mismatch or broken install; the two fields use related but not necessarily identical display formats.
Table of contents
How can you check the WinGet client version?
- Right-click Start and select Terminal, or open PowerShell or Command Prompt.
- Type
winget --versionand press Enter. - Read the single version printed on the next line.
- Close the terminal when you have recorded it.
Microsoft documents -v and --version as equivalent global options. The longer form is easier to recognize in screenshots and scripts. Type two ordinary hyphen characters before version; a typographic dash copied from formatted text will not be parsed as the same option.
If the command prints the normal WinGet help instead of a version, check the spelling and dashes. If Windows says winget is not recognized, skip to the missing-command section below rather than downloading an executable from an unrelated website.
What extra details does winget --info show?
Run winget --info when you need context for troubleshooting or a bug report. Microsoft says the output can include the client version, Windows build, system architecture, App Installer MSIX package version, WinGet directories, legal links, policy state, and administrator settings.
- In the same kind of standard terminal, type
winget --info. - Read Windows Package Manager for the client version.
- Read Windows and System Architecture for the operating-system context.
- Read Package for the Microsoft.DesktopAppInstaller package version.
Microsoft's WinGet info reference explains why this command is useful for issue reports. It also shows why a full screenshot deserves a privacy review: lower sections can list local directory patterns and configured policy or administrator settings. Share only the lines the support case needs.
The command reports what is installed locally; it does not promise that the displayed build is the newest stable or preview release. Release channels, Microsoft Store rollout timing, Windows Insider enrollment, and organization policy can make two healthy PCs show different versions.
How can you check the App Installer package version in PowerShell?
A targeted Appx query verifies the package that delivers WinGet without enumerating every installed app. Open PowerShell and run:
Get-AppxPackage Microsoft.DesktopAppInstaller |
Select-Object Name, Version, Architecture
This third result is the App Installer package version, not a replacement for winget --version. It is helpful when WinGet will not start, when the client and its host package need to be compared, or when a support request specifically asks for the MSIX package identity.
Keep the query targeted. A broad Get-AppxPackage inventory can reveal many installed packages and account-scoped details that do not help a WinGet version question. Do not add -AllUsers or elevate simply to produce a larger list.
How can you tell whether the installed version is current?
First decide which channel you intend to use. Most Windows 11 PCs receive App Installer through Microsoft Store updates. Windows Insider or WinGet preview users can receive builds on a different cadence. A preview number should not be treated as the normal target for a stable PC, and a larger number alone is not a reason to install an untrusted package.
Check App Installer in Microsoft Store Library and use its normal update flow. For release notes and channel labels, compare with the official microsoft/winget-cli release list. Read whether a release is stable, preview, or a release candidate before comparing numbers.
Do not use winget upgrade as proof of the WinGet client's own update status. That command is primarily for packages WinGet manages. Because the client is delivered through App Installer, the Store/system-component channel is the clearer update path for ordinary Windows 11 desktops.
What should you do if winget is not recognized?
Microsoft says WinGet is included with App Installer and may not be available until the first user sign-in has allowed Store registration to complete. On a newly created account, wait for that registration and check for Store updates before assuming the executable is missing.
Use the targeted PowerShell query above to see whether Microsoft.DesktopAppInstaller is registered for the current account. If the package is absent, install or repair App Installer only through Microsoft's documented channel. If it is present but WinGet still fails, restart the terminal after updates and collect winget --info or the exact error for troubleshooting.
Avoid third-party WinGet download sites, copied binaries, registry edits, or broad Appx re-registration commands without a diagnosed cause. Organization policy can also limit Windows Package Manager; on a work or school PC, ask the administrator before attempting to bypass it.
Why can two Windows 11 PCs show different WinGet versions?
App Installer updates can reach devices at different times. One PC may be on a stable Store release while another is enrolled in an Insider or preview channel. A managed device can also hold a version through policy or staged deployment. The Windows 11 feature version does not uniquely determine the WinGet client number.
When comparing machines, capture all four useful facts: WinGet client version, App Installer package version, Windows build, and architecture. winget --info collects those together. Keep the comparison tied to the requirement you are troubleshooting instead of assuming every machine must immediately display the largest number on the release page.
Once you know the installed client version, the WinSides complete WinGet commands list covers search, show, list, install, upgrade, export, and other operations. A practical example is the separate guide to installing Visual Studio Code with WinGet.
What should you hide before sharing WinGet version evidence?
The single --version result is normally safe to share. A complete --info output can expose directory conventions, configured policies, and administrator settings. A terminal prompt can expose a user name or current folder if it uses the default path-rich prompt.
Crop the image to the command and required result. Do not include unrelated command history, package inventories, local paths, account identifiers, tokens, or private repository settings. The three published images here are article-specific derivatives from maximized ShareX frames; they exclude the taskbar, clock, desktop, prompt path, unrelated apps, and unused terminal space.
Frequently Asked Questions
What command shows the WinGet version?
Run winget --version or winget -v. The result is the installed WinGet client version.
Why does App Installer have an extra .0 in its version?
The WinGet client and its App Installer MSIX package use related version fields with different display formats. A client such as 1.29.250 can be delivered in package 1.29.250.0.
Does winget --info update anything?
No. It reports local WinGet, Windows, architecture, package, directory, link, policy, and administrator-setting information; it does not install or update a package.
Is the WinGet version the same as the Windows 11 build?
No. Windows and App Installer have their own update channels and version numbers. Use winget --info to record both without confusing them.
Use --version for the client and --info for context
Run winget --version for the focused client number. Use winget --info when you also need the Windows build, architecture, and App Installer package version, and use the targeted Appx query when the package identity itself is the troubleshooting target. Compare versions within the intended release channel and update App Installer only through Microsoft's normal path.
For more interesting articles, stay tuned to WinSides.com!
Community
Comments (0)