You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: hub/package-manager/winget/install.md
+17-12Lines changed: 17 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,22 +1,21 @@
1
1
---
2
2
title: install Command
3
3
description: Installs the specified application.
4
-
ms.date: 07/11/2024
4
+
ms.date: 07/15/2025
5
5
ms.topic: overview
6
-
ms.localizationpriority: medium
7
6
---
8
7
9
8
# install command (winget)
10
9
11
-
The **install** command of the [winget](index.md)tool installs the specified application. Use the [**search**](search.md) command to identify the application you want to install.
10
+
The **install** command of [WinGet](index.md) installs the specified application. Use the [**search**](search.md) command to identify the application you want to install. Use the [**show**](show.md) command to view details about the application and the installer selected by WinGet for your system.
12
11
13
12
The **install** command requires that you specify the exact string to install. If there is any ambiguity, you will be prompted to further filter the **install** command to an exact application.
If the query provided to **winget** does not result in a single application, then **winget** will display the results of the search. This will provide you with the additional data necessary to refine the search for a correct install.
105
+
If the query provided to **WinGet** does not result in a single application, then **WinGet** will display the results of the search. This will provide you with the additional data necessary to refine the search for a correct install.
107
106
108
107
The best way to limit the selection to one file is to use the **id** of the application combined with the **exact** query option. For example:
109
108
@@ -117,12 +116,18 @@ If multiple sources are configured, it is possible to have duplicate entries. Sp
117
116
winget install --id Git.Git -e --source winget
118
117
```
119
118
120
-
The **msstore** source uses unique identifiers as the "Id" for packages. These do not require the **exact** query toption. For example:
119
+
The **msstore** source uses unique identifiers as the "Id" for packages. These do not require the **exact** query option. For example:
121
120
122
121
```CMD
123
122
winget install XP9KHM4BK9FZ7Q -s msstore
124
123
```
125
124
125
+
You may also use the install command to install multiple packages. For example:
126
+
127
+
```CMD
128
+
winget install Microsoft.Edit Microsoft.NuGet
129
+
```
130
+
126
131
## Local install
127
132
128
133
The **manifest** option enables you to install an application by passing in a YAML file directly to the client. If the manifest is a multi-file manifest, the directory containing the files must be used. The **manifest** option has the following usage.
|**-m, --manifest**| The path to the manifests of the application to install. |
135
140
136
-
> [!NOTE]
137
-
> Installing packages from local manifest files may have risks. As an extra measure of precaution this feature needs to be enabled by an administrator. To enable this feature run `winget settings --enable LocalManifestFiles`. To disable this feature run `winget settings --disable LocalManifestFiles`.
141
+
Installing packages from local manifest files may have risks. As an extra measure of precaution this feature needs to be enabled by an administrator. To enable this feature run `winget settings --enable LocalManifestFiles`. To disable this feature run `winget settings --disable LocalManifestFiles`.
138
142
139
143
### Log files
140
144
141
-
The log files for winget unless redirected, will be located in the following folder: **\%temp%\\AICLI\\*.log**
145
+
The log files for WinGet unless redirected, will be located in the following folder:
Some applications when installed will require the user to agree to the license or other agreements before installing. When this occurs, the Windows Package Manager will prompt the user to agree to the agreements. If the user does not agree, the application will not install.
146
151
147
-

152
+
:::image type="content" source="./images/agreements.png" alt-text="Screenshot of user agreement prompt in winget." lightbox="./images/agreements.png":::
148
153
149
154
From the command line, you can auto accept the agreements by passing the following option **--accept-package-agreements** on the command line. This can be beneficial when scripting the Windows Package Manager.
0 commit comments