Windows 8.1 Appx Install

[Marti Buday]

TheAdd-AppxPackage cmdlet adds a signed app package to a user account. An app package has an.msix or .appx filename extension. Use the DependencyPath parameter to add all otherpackages required for the installation of the app package.

This command gets the full path of the package manifest file of an installed Windows Store app, andthen registers that package. You can use DisableDevelopmentMode to register an applicationthat's staged by the StagePackageAsync API, has been disabled, or has become corrupted duringtesting.

This command adds an app package along with its optional packages. It's an atomic operation, whichmeans that if the app or its optional packages fail to install, the deployment operation will beaborted

This command adds an app package but only installs the required section of a streaming app. Callingthis command again without the RequiredContentGroupOnly parameter proceeds to install the restof the application in the order defined by the AppxContentGroupMap.xml

Specifies an array of file paths of dependency packages that are required for the installation ofthe app package. The app package has an .msix, .appx, .msixbundle, or .appxbundle filenameextension. You can specify the paths to more than one dependency package. If a package is alreadyinstalled for a user, you can skip adding it to the DependencyPath.

Indicates that this cmdlet registers an existing app package installation that has been disabled,didn't register, or has become corrupted. Use the current parameter to specify that the manifest isfrom an existing installation, and not from a collection of files in development mode. You can alsouse this parameter to register an application that thePackage Manager API has staged. Use theRegister parameter to specify the location of the app package manifest .xml file from theinstallation location.

Specifies an array of optional packages that must be installed along with the app package. It's anatomic operation, which means that if the app or its optional packages fail to install, thedeployment operation will be aborted.

Indicates that this cmdlet forces all active processes associated with the package or itsdependencies to shut down. If you specify this parameter, don't specify theForceTargetApplicationShutdown parameter.

Indicates that this cmdlet forces the deployment of all resource packages specified from a bundleargument. This overrides the resource applicability check of the deployment engine and forcesstaging of all resource packages, registration of all resource packages, or staging and registrationof all resource packages. This parameter can only be used when specifying a resource bundle orresource bundle manifest.

Specifies the PackageFamilyName of the optional packages that are in a related set that need to beinstalled along with the app. Unlike the external packages flag, you don't need to pass in a pathto the optional packages. It's an atomic operation, which means that if the app or its optionalpackages fail to install, the deployment operation will be aborted.

Indicates that this cmdlet registers an application in development mode. You can use developmentmode to install applications from a folder of unpackaged files. You can use the current parameterto test your Windows Store apps before you deploy them as app packages. To register an existing apppackage installation, you must specify the DisableDevelopmentMode parameter and theRegister parameter. To specify dependency packages, use the DependencyPath parameter andthe DisableDevelopmentMode parameter.

Specifies that only the required content group that's specified in the AppxContentGroupMap.xmlmust be installed. At this point the app can be launched. Calling Add-AppxPackage and specifyingthe path to the app triggers the rest of the app to be installed in the order defined in theAppxContentGroupMap.xml.

Specifies that the package being added is a dependency package update. A dependency package isremoved from the user account when the parent app is removed. If you don't use this parameter, thepackage being added is a primary package and isn't removed from the user account if the parent appis removed. To update an already installed package, the new package must have the same packagefamily name.

I don't want to have to go to the Microsoft Store page, start fiddler, start the download, capture the .appx file URL and then manually download it so that I can use Add-AppxPackage.(See how Windows OS Hub did that here)

You can now use winget to install msstore apps on windows 10 and 11.Use winget search --source=msstore to make a search, and use the id of the app to install and upgrade the app.For example, to install Netflix:

store.rg-adguard.net is a GUI for generating direct download links to store apps. Peeking at the source of that page, we can piggyback off them to download the content directly, but using PackageFamilyName, rather than Name (in your example it would be Microsoft.HEVCVideoExtension_8wekyb3d8bbwe).

This correctly downloads neutral and x64 packages but untested for arm and 32bit systems. the path must point to a folder. It will download the package and its dependencies and save them all as their original file names while avoiding name collisions like chrome.

Microsoft's Universal Windows Platform applications used the .Appx or .AppxBundle file format in older versions of Windows 10. They're were normally installed from the Windows Store, but Windows 10 allows you to sideload Appx packages from anywhere.

You'll still find ".appx" files floating around on the Internet, however, they have generally been replaced with MSIX files. If you need to use an APPX file to install something you still can, and the information here holds.

Windows 10 "Universal apps" or "Universal Windows Platform" apps used to be distributed in .Appx or .AppxBundle files. These are application packages that include the name, description, and permissions of an app along with the application's binaries. Windows can install and uninstall these packages in a standard fashion, so developers don't have to write their own installers. Windows can handle everything in a consistent way, allowing it to cleanly uninstall applications with no leftover registry entries.

If a developer makes a .Appx program, you normally don't download and install it directly. Instead, you visit the Windows Store, search for the program you want to install, and download it from the Store. All software in the Windows Store was in .Appx or .AppxBundle format behind the scenes, but has been largely replaced with the .msix format.

In some cases, you may need to install a .Appx or .AppxBundle package from outside the Store. For example, your workplace may provide an application you need in .Appx format, or you may be a developer who needs to test your own software before uploading it to the Store.

You can only install .Appx or .AppxBundle software if sideloading is enabled on your Windows 10 device. Sideloading is enabled by default starting with the November Update, but sideloading may be disabled by company policy on some devices.

To check if sideloading is enabled, head to Settings > Update & Security > For Developers. Ensure the setting here is set to either "Sideload apps" or "Developer mode". If it's set to "Windows Store apps", you won't be able to install .Appx or .AppxBundle software from outside the Windows Store.

If this option is set to "Windows Store apps" and you enable sideloading, Windows will warn that apps you install could expose your device and data, or harm your PC. It's like installing normal Windows software: You should only install software from sources you trust.

On Windows 10's Anniversary Update, Microsoft added a new "App Installer" tool that allows you to install .Appx or .AppxBundle applications graphically. To install them, just double-click a .Appx or .AppxBundle package.

Windows 10 also includes PowerShell cmdlets you can use to install an .Appx package. The cmdlet offers more features than the App Installer tool, such as the ability to point Windows at a dependency path that contains other packages the .Appx package needs.

To install an Appx package with PowerShell, first open a PowerShell window. You can search the Start menu for "PowerShell" and launch the PowerShell shortcut to open one. You don't need to launch it as Administrator, as .Appx software is just installed for the current user account.

If you're developing your own software, the above cmdlet won't be ideal for you. It will only install properly signed applications, but you don't necessarily want to sign your application while developing it.

That's why there's an alternate way to install Appx software. This only works with apps left in "unpackaged" form. The Desktop App Converter also creates both an unpackaged app, which you can install using the below command, and the final .Appx application package.

Yeah, that is what I am going to try next. I finally figured out how to mount the image, change a file (the StartMenuLayout.xml), and dismount the/saved the image. I then used ImgBurn to create a modified .iso that I am testing. If this works I will try using the remove-appxpackages powershell cmdlets and recreate the .iso again.

Ok. I finally got this working. Turns out my issue was with the version of PowerShell/DISM I was using. To get this to work I had to move to a Windows 10 system and I did the following. When I tried this same process on Windows 8.1 I constantly got the error that I had the wrong version of DISM.

I came across this post and found it very helpful as I was able to get the wim as per my needs but is there a script which we can run while capturing the wim where we can remove the App tiles for the removed apps as they are still getting displayed displayed in the start menu?

I followed these instructions and verified that that apps have been removed from the wim. However, after recreating the iso and running through install, I find that all of the apps are still installed. Tried installing both online and offline, with the same results. Windows 10 1803 VL iso.

3a8082e126