Skip to content

Commit b9283ce

Browse files
authored
Update windows.management.deployment/packagemanager_provisionpackageforallusersasync_653384863.md
1 parent c046048 commit b9283ce

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

windows.management.deployment/packagemanager_provisionpackageforallusersasync_653384863.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,8 @@ The progress and the result of the app package deployment.
2323
## -remarks
2424
To provision a package you must be an administrator. The app package to be provisioned must be staged, and it must be on the system volume.
2525

26-
If the package is already provisioned, this performs a "clean" reprovision. A "clean" reprovision will remove all previous installs of this package so the package, so that the package will be re-offered to all users that may have previously removed it, as if it were its first provision. This will not affect any users that currently have the package installed.
26+
If the package is already provisioned, this performs a "clean" reprovision. A "clean" reprovision removes all previous installs of this package, so the package is re-offered to all users that might have previously removed it as if it were its first provision. This doesn't affect any users that currently have the package installed.
27+
2728

2829
> [!NOTE]
2930
> If you are provisioning optional packages, you must specify each optional package individually with its own method call. Starting with Windows Build 22000, you can use the overload of [ProvisionPackageForAllUsersAsync](packagemanager_provisionpackageforallusersasync_1152150951.md), to specify additional optional packages to install with a single call.

0 commit comments

Comments
 (0)