Merge pull request #5596 from MicrosoftDocs/main

Auto Publish – main to live - 2025-07-17 05:00 UTC

Author: learn-build-service-prod[bot]

hub/package-manager/winget/features.md

@@ -1,14 +1,13 @@
 ---
 title: features Command
 description: Displays the list of experimental features available and the state.
-ms.date: 07/11/2024
+ms.date: 07/16/2025
 ms.topic: overview
-ms.localizationpriority: medium
 ---
 
 # features command (winget)
 
-The **features** command of the [winget](index.md) tool displays a list of the experimental features available with your version of the Windows Package Manager. Experimental features are only available in preview builds. Instructions for obtaining a preview build can be found in the [GitHub repository](https://github.com/microsoft/winget-cli).
+The **features** command of the [winget](index.md) tool displays a list of the experimental features available with your version of the Windows Package Manager.
 
 Each feature can be turned on individually by enabling the features through [**settings**](./settings.md).
 
@@ -18,13 +17,13 @@ You can find the latest up to date information features on the [experimental fea
 
 `winget features [<options>]`
 
-![features command](./images/features.png)
+:::image type="content" source="./images/features.png" alt-text="Screenshot listing winget features." lightbox="./images/features.png":::
 
 Notice above that the status of each feature is listed. If the feature is **disabled** you will not be able to use it. If the feature is **enabled** you will notice that the command will be available to you through **winget**.
 
-![features command help options](./images/features-help.png)
+:::image type="content" source="./images/features-help.png" alt-text="Screenshot listing winget features command help options." lightbox="./images/features-help.png":::
 
-To enabled any disabled features, go to **settings** and enable the feature.
+To enable any disabled features, go to **settings** and enable the feature.
 
 > [!NOTE]
 > Features may be managed by group policy. You can use the **winget --info** command to view any policies in effect on your system.

hub/package-manager/winget/images/features.png

@@ -1,14 +1,13 @@
 ---
 title: list Command
 description: Displays the list of listed apps and if an update is available.
-ms.date: 07/11/2024
+ms.date: 07/15/2025
 ms.topic: overview
-ms.localizationpriority: medium
 ---
 
 # list command (winget)
 
-The **list** command of the [winget](./index.md) tool displays a list of the applications currently installed on your computer. The list command will show apps that were installed through the Windows Package Manager as well as apps that were installed by other means.
+The **list** command of [WinGet](./index.md) displays a list of the applications currently installed on your computer. The list command will show apps that were installed through the Windows Package Manager as well as apps that were installed by other means.
 
 The **list** command will also display if an update is available for an app, and you can use the [**upgrade**](./upgrade.md) command to update the app.
 
@@ -24,10 +23,9 @@ The following aliases are available for this command:
 
 `winget list [[-q] <query>] [<options>]`
 
-![Image of list command usage](./images/list.png)
+:::image type="content" source="./images/list.png" alt-text="Screenshot listing winget list command options." lightbox="./images/list.png":::
 
-> [!NOTE]
-> If you want to list all apps with available updates use `winget upgrade` (without any arguments).
+To list all apps with available updates, use the command: `winget list --upgrade-available` (without any arguments).
 
 ## Arguments
 
@@ -60,6 +58,8 @@ The options allow you to customize the list experience to meet your needs.
 | **--authentication-account** | Specify the account to be used for authentication. |
 | **--accept-source-agreements** | Used to accept the source license agreement, and avoid the prompt. |
 | **--upgrade-available** | Lists only packages which have an upgrade available. |
+| **-u, --unknown, --include-unknown** | Lists packages even if their current version cannot be determined. |
+| **--pinned, --include-pinned** | Lists packages even if they have a pin that prevents upgrades by WinGet. |
 | **-?, --help** |  Get additional help on this command. |
 | **--wait** | Prompts the user to press any key before exiting. |
 | **--logs,--open-logs** | Open the default logs location. |
@@ -71,25 +71,25 @@ The options allow you to customize the list experience to meet your needs.
 
 ### Example queries
 
-The following example lists a specific version of an application.
+The following example lists installed applications with a given substring in their name.
 
-![list name command](./images/list-name.png)
+:::image type="content" source="./images/list-name.png" alt-text="Screenshot of using the winget --list git command to all installed applications with the name git." lightbox="./images/list-name.png":::
 
 The following example lists all application by ID from a specific source.
 
-![list id with source command](./images/list-id-source.png)
+:::image type="content" source="./images/list-id-source.png" alt-text="Screenshot listing winget list --id Git.Git to show all installed applications coming from that source." lightbox="./images/list-id-source.png":::
 
 The following example limits the output of **list** to 9 apps.
 
-![list count command](./images/list-count.png)
+:::image type="content" source="./images/list-count.png" alt-text="Screenshot listing winget list --count 9 to limit the number of installed apps listed to only 9." lightbox="./images/list-count.png":::
 
 ## List with update
 
-As stated above, the **list** command allows you to see what apps you have installed that have updates available.
+As stated above, the **list** command allows you to see what apps you have installed that have upgrades available.
 
-In the image below, you will notice the preview version of Terminal has an update available.
+In the image below, you will notice applications with an upgrade available.
 
-![Image of list with update command](./images/list-update.png)
+:::image type="content" source="./images/list-update.png" alt-text="Screenshot listing winget list --upgrade-available to show installed apps with an available upgrade." lightbox="./images/list-update.png":::
 
 The **list** command will show not only the update version available, but the source that the update is available from.
 

hub/package-manager/winget/images/list-count.png

@@ -1,7 +1,7 @@
 ---
 title: Debugging and troubleshooting issues with WinGet
 description: Provides information on logging and WinGet diagnostics.
-ms.date: 11/15/2024
+ms.date: 07/15/2025
 ms.topic: troubleshooting-general
 ---
 
@@ -44,6 +44,20 @@ If you need more comprehensive log files, that provide the complete communicatio
 > winget source add -n mysource -t Microsoft.REST -a https://www.contoso.org --verbose
 ```
 
+### settings
+
+You can specify the default logging level for WinGet to use in your WinGet Settings file. The **settings** command will open the settings.json file in your default JSON editor.
+
+Example with verbose logging:
+```JSON
+{
+    "$schema": "https://aka.ms/winget-settings.schema.json",
+    "logging": {
+        "level": "verbose"
+    }
+}
+```
+
 ## Known issues
 
 A list of known issues with sources and behaviors is kept up to date in the [Windows Package Manager Client repository](https://www.github.com/microsoft/winget-cli).  If you encounter issues when using the WinGet tool, go [here](https://github.com/microsoft/winget-cli/tree/master/doc/troubleshooting) for troubleshooting.
@@ -52,6 +66,12 @@ A list of known issues with sources and behaviors is kept up to date in the [Win
 
 The WinGet tool returns exit codes to indicate success or failure of the command.  Find a table of exit codes and their meanings in the ["Return codes" file of the Windows Package Manager Client repository](https://github.com/microsoft/winget-cli/blob/master/doc/windows/package-manager/winget/returnCodes.md).
 
+The WinGet **error** command accepts errors from "Exit codes" and displays a description for known error codes for WinGet, MSIX, and MSI installers. Many .exe-based installers have non-standard error codes and may not be displayed.
+
+```CMD
+> winget error 1603
+```
+
 ### Scope for specific user vs machine-wide
 
 Not all installers support installing in “user” scope vs. “machine” scope consistently.
@@ -75,3 +95,7 @@ The user agent string for WinGet has the following format:
 Example: 
 
 `winget-cli WindowsPackageManager/1.9.25200 DesktopAppInstaller/Microsoft.DesktopAppInstaller v1.24.25200.0`
+
+### System Context
+
+WinGet is delivered via the App Installer as a packaged application. MSIX (packaged) applications depend on an App Execution Alias to be resolved on the PATH environment variable. The WinGet CLI is not supported in the system context. The Microsoft.WinGet.Client PowerShell module can be used in the system context with applications that are installed machine wide.