Does NTLite allow AppX updates or inserts?
- Thread starter ppw0
- Start date
NTLite allows you to add downloaded Appx or MSIX packages, including any free Store apps, to the image. They're added as Updates, or you can use DISM /Add-ProvisionedAppxPackage on the mounted image.
Paid apps must always be installed from the Store.
The restriction is sideloaded apps won't activate until after Windows is online for 10-15 min., when the app licensing service contacts MS and provisions a per-machine license. If your app distribution includes a License.xml, then the package can be enabled immediately.
Use this script to download current versions of the default Apps, or any free Store app if you know its ProductID.
PowerShell GUI for Downloading Microsoft Store Apps - W10_11StoreApps.ps1
If you select the Fast ring, it's possible to find Insider versions of Apps not available on production releases. The script will download any required Appx dependencies, so simply import the entire folder in the Updates page.
Paid apps must always be installed from the Store.
The restriction is sideloaded apps won't activate until after Windows is online for 10-15 min., when the app licensing service contacts MS and provisions a per-machine license. If your app distribution includes a License.xml, then the package can be enabled immediately.
Use this script to download current versions of the default Apps, or any free Store app if you know its ProductID.
PowerShell GUI for Downloading Microsoft Store Apps - W10_11StoreApps.ps1
If you select the Fast ring, it's possible to find Insider versions of Apps not available on production releases. The script will download any required Appx dependencies, so simply import the entire folder in the Updates page.
WebView2 Runtime is available in three versions: web installer, standalone installer, and fixed version CAB.
The first two options have permanent download links, the last one is listed by build version. Unfortunately the CAB isn't an update package, it's just the folder distribution zipped as a CAB file. Therefore it's best to run the standalone installer in Post-Setup, using "/silent /install" flags.
The first two options have permanent download links, the last one is listed by build version. Unfortunately the CAB isn't an update package, it's just the folder distribution zipped as a CAB file. Therefore it's best to run the standalone installer in Post-Setup, using "/silent /install" flags.