microsoft / microsoft/winget-cli

"No applicable installer found" message is too vague.

Open
#5,545 4 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Issue-Feature
Dominant language
C++
Stars
26.4k
Forks
1.8k
Avg merge
1d 11h
Merged PRs (30d)
15

Description

Brief description of your issue

Tried to install talosctl with the following command:
winget install -e --id Sidero.talosctl

The output:
No applicable installer found; see logs for more details.

After several hours of searching online, trying user vs. machine installs, I finally found the --verbose-logs switch. In the logs:

2025-06-18 15:49:06.858 [CLI ] Starting installer selection.
2025-06-18 15:49:06.858 [CLI ] Installer [X64,portable,Unknown,en-US] not applicable: Current OS is lower than supported MinOSVersion (10.0.18362) for Portable install
2025-06-18 15:49:06.858 [CLI ] Installer [Arm64,portable,Unknown,en-US] not applicable: Current OS is lower than supported MinOSVersion (10.0.18362) for Portable install

So, I'm running on Server 2019, and the OS can't do portable installs with Winget. I can accept this outcome, but Winget SHOULD HAVE TOLD ME IN THE ERROR MESSAGE.

Sorry, just a bit frustrated. Please have the error message tell the user exactly why no applicable installer was found. At a minimum, put the reason in the non-verbose logs.

Note that there are other open issues that may have the same root cause, such as #2176

Steps to reproduce

winget install -e --id Sidero.talosctl

Expected behavior

Installation of app, or an error message explaining what went wrong.

Actual behavior

A vague error message that normally occurs when there's no machine-wide installer available.

Environment
C:\temp>winget --info
Windows Package Manager v1.11.400
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Server v10.0.17763.7434
System Architecture: X64
Package: Microsoft.DesktopAppInstaller v1.26.400.0

Winget Directories
-------------------------------------------------------------------------------------------------------------------------------
Logs                               %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir
User Settings                      %LOCALAPPDATA%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\settings.json
Portable Links Directory (User)    %LOCALAPPDATA%\Microsoft\WinGet\Links
Portable Links Directory (Machine) C:\Program Files\WinGet\Links
Portable Package Root (User)       %LOCALAPPDATA%\Microsoft\WinGet\Packages
Portable Package Root              C:\Program Files\WinGet\Packages
Portable Package Root (x86)        C:\Program Files (x86)\WinGet\Packages
Installer Downloads                %USERPROFILE%\Downloads
Configuration Modules              %LOCALAPPDATA%\Microsoft\WinGet\Configuration\Modules

Links
---------------------------------------------------------------------------
Privacy Statement   https://aka.ms/winget-privacy
License Agreement   https://aka.ms/winget-license
Third Party Notices https://aka.ms/winget-3rdPartyNotice
Homepage            https://aka.ms/winget
Windows Store Terms https://www.microsoft.com/en-us/storedocs/terms-of-sale

Admin Setting                             State
--------------------------------------------------
LocalManifestFiles                        Disabled
BypassCertificatePinningForMicrosoftStore Disabled
InstallerHashOverride                     Disabled
LocalArchiveMalwareScanOverride           Disabled
ProxyCommandLineOptions                   Disabled
DefaultProxy                              Disabled

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with winget install -e --id Sidero.talosctl on the Windows Server environment described, then inspect the installer-selection output and diagnostic logs. The change is complete when a failed selection reports the relevant applicability reason in the normal error output rather than only in verbose logs.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.