A practical guide to sideloading Microsoft Store app packages with App Installer, PowerShell, winget, and offline dependencies.
APPX and APPXBundle files are application packages used by Microsoft Store-style apps in Windows 10 and Windows 11. They contain the app itself, its manifest, digital signature, resources, and installation metadata.
Newer packages often use the MSIX or MSIXBundle format. For most users, the installation process is almost the same: you either open the package with App Installer or install it through PowerShell.
APPX packages are executable application packages, so treat them like regular installers. Only install files from trusted sources, especially if they are not downloaded from Microsoft Store or the software developer’s official website.
x64, ARM64, or x86.64-bit operating system, x64-based processor.On current versions of Windows 10 and Windows 11, sideloading trusted app packages is usually enabled by default. However, if installation is blocked, check the developer settings.
The easiest method is to open the package directly in App Installer. This graphical installer is available on most Windows 10 and Windows 11 systems and provides a familiar install window similar to Microsoft Store.
.appx, .appxbundle, .msix, or .msixbundle file in File Explorer.If double-clicking the file does not open an installer window, App Installer may be missing, disabled, or damaged. In that case, use the PowerShell method below or reinstall App Installer from Microsoft Store when possible.
PowerShell is the most reliable way to install APPX packages manually, especially when App Installer does not work or when you need to install dependencies first.
Add-AppxPackage command with the full path to the package.PowerShell — install APPXAdd-AppxPackage -Path "C:\Users\User\Downloads\AppName.appx"
PowerShell — install bundleAdd-AppxPackage -Path "C:\Users\User\Downloads\AppName.appxbundle"
The same command also works for .msix and .msixbundle files:
PowerShell — install MSIXBundleAdd-AppxPackage -Path "C:\Users\User\Downloads\AppName.msixbundle"
If you downloaded an app with several dependency packages, put all files in one folder and install dependencies first. You can also install all packages in the folder with a loop:
PowerShell — install all packages in folderGet-ChildItem "C:\AppPackages" -Include *.appx,*.appxbundle,*.msix,*.msixbundle -Recurse |
ForEach-Object { Add-AppxPackage -Path $_.FullName }
Add-AppxPackage -Path in PowerShell, then drag the package file into the PowerShell window. Windows will paste the full file path automatically.
winget is the Windows Package Manager. It is not mainly designed for arbitrary local APPX files, but it can install many Microsoft Store and repository apps by package ID. Use this method when the app is available in the winget repository.
Command Prompt or PowerShellwinget search appname
winget install examplewinget install --id Publisher.AppName
If you already have a local .appx or .appxbundle file, Add-AppxPackage is usually the better tool.
Some APPX packages require additional framework packages, such as Microsoft UI XAML, VCLibs, .NET Native Runtime, or other runtime components. If a dependency is missing, Windows may show an error instead of installing the app.
Microsoft.VCLibs.x64.appxMicrosoft.VCLibs.x86.appxMicrosoft.UI.Xaml.x64.appxMicrosoft.NET.Native.Runtime.appxMicrosoft.NET.Native.Framework.appxIf the app archive contains a Dependencies folder, install the packages that match your system architecture before installing the main app package.
PowerShell — install dependencyAdd-AppxPackage -Path "C:\AppPackages\Dependencies\Microsoft.VCLibs.x64.appx"
Then install the main package:
PowerShell — install main packageAdd-AppxPackage -Path "C:\AppPackages\AppName.appxbundle"
By default, Add-AppxPackage installs the app for the current user. Administrators can provision an app so it is installed for new user accounts created on the computer. This is useful on shared PCs, school computers, and enterprise images.
PowerShell — provision package for new usersAdd-AppxProvisionedPackage -Online -PackagePath "C:\AppPackages\AppName.appxbundle" -SkipLicense
If the package requires a separate license file, use -LicensePath instead of -SkipLicense.
PowerShell — with license fileAdd-AppxProvisionedPackage -Online -PackagePath "C:\AppPackages\AppName.appxbundle" -LicensePath "C:\AppPackages\license.xml"
You can remove most APPX apps from Settings, the Start menu, or PowerShell.
First, find the package name:
PowerShell — find packageGet-AppxPackage *appname*
Then remove it for the current user:
PowerShell — remove packageGet-AppxPackage *appname* | Remove-AppxPackage
| Error or Symptom | Likely Cause | What to Try |
|---|---|---|
Deployment failed |
The package is blocked, corrupted, incompatible, or missing dependencies. | Check the full PowerShell error text, install dependencies, and verify architecture. |
0x80073CF3 |
Package failed validation, usually due to missing framework dependencies. | Install the required VCLibs, UI XAML, .NET Native, or other framework packages first. |
0x80073D02 |
The app or one of its components is currently running. | Close the app, restart Windows, then try again. |
This app package is not supported for installation |
The package type, signature, architecture, or Windows version is not compatible. | Download the correct package for your Windows version and CPU architecture. |
The package could not be opened |
The file is incomplete, damaged, or blocked by security software. | Download the package again from the original source and scan it before installation. |
| Double-click does nothing | App Installer is missing or file association is broken. | Use PowerShell with Add-AppxPackage or repair App Installer. |
Some packages do not require administrator rights, but elevation can help when installing dependencies, provisioning packages, or repairing app deployment problems.
If Windows marks the file as downloaded from the internet, right-click the package, select Properties, enable Unblock if available, and click OK. Then try the installation again.
If Store-style app deployment is generally broken, try resetting the Microsoft Store cache:
Run dialog or Command Promptwsreset.exe
Yes. You can install many APPX, APPXBundle, MSIX, and MSIXBundle files directly with App Installer or PowerShell. However, some apps still rely on Store services, licensing, or online dependencies.
Not always. Many signed packages install without Developer Mode. If Windows blocks the package, check Settings → For developers and enable sideloading or Developer Mode only when required.
No. An .exe file is a traditional executable installer or program. An .appx file is a packaged app format with a manifest, signature, permissions, and controlled deployment through the Windows app platform.
Yes, if App Installer is available and the package is valid. Otherwise, install it with PowerShell using Add-AppxPackage -Path.
The same app or a newer version may already be installed. Open Settings → Apps, uninstall the existing version if appropriate, or use the developer’s recommended update package.
For most users, the best way to install an APPX, APPXBundle, MSIX, or MSIXBundle file is to double-click it and use App Installer. If that fails, PowerShell is the most dependable alternative:
Recommended commandAdd-AppxPackage -Path "C:\Path\To\Package.appxbundle"
When installation errors appear, check three things first: the package source, CPU architecture, and missing dependencies. These are the most common reasons why APPX packages fail to install on Windows 10 and Windows 11.