Fix: Can’t Install Appx, AppxBundle, and Msixbundle Files in Windows

Trying to install an Appx, AppxBundle, or Msixbundle file in Windows only to hit errors or see nothing happen? You're not alone. These modern app packages, used by many Windows Store and third-party apps, can run into permission problems, missing dependencies, or system restrictions that block installation. Here’s how to diagnose what’s wrong and actually get your app installed.

Check Windows Version and Edition

Not all versions of Windows support installing Appx, AppxBundle, or Msixbundle files directly. These formats are designed for Windows 10 and 11, but features vary by edition. On Windows 10/11 Home and Pro, sideloading must be enabled. On Windows 10 S mode, manual installation of these packages is blocked entirely. Windows 8.1 supports only the Appx format, not AppxBundle or Msixbundle.

To check your version, press Windows + R, type winver, and press Enter. If you’re using Windows 7 or 8, these packages won’t install; you’ll need to upgrade. If you’re using S mode, switch out of it in Settings under Update & Security > Activation. On Enterprise or Education editions, group policy restrictions may apply, so consult your IT administrator if necessary.

Enable Sideloading of Apps

By default, Windows only allows app installation from the Microsoft Store. To install Appx, AppxBundle, or Msixbundle files downloaded elsewhere ("sideloading"), you need to enable this ability. Go to Settings > Update & Security > For Developers. Select Sideload apps. If it’s grayed out, you may lack administrator rights. Log in as an admin user or contact your administrator to change this setting.

Changing this won’t lower your security if you only install trusted packages. After sideloading is enabled, try installing your app again. If you see the change isn’t saving, group policies may be blocking it, in which case you’ll need to discuss with your organization’s IT department.

Install App Installer from Microsoft Store

Windows 10/11 relies on a built-in tool called "App Installer" to handle Appx, AppxBundle, and Msixbundle files. If it’s missing, outdated, or corrupted, your packages won’t open or install. Try double-clicking the file; if you get a message about missing an app or nothing happens, that’s likely the cause.

Open the Microsoft Store and search for "App Installer." Download or update it. If you had it previously, but it’s not working, uninstall and reinstall the app. Once installed, double-click your package file again. You should see a straightforward installer window. If not, restart your PC and try again.

Use PowerShell to Install the Package

If the graphical installer fails or you need more detailed error messages, PowerShell is your friend. Right-click the Start button and select Windows PowerShell (Admin) or Terminal (Admin). Use the following command:

• For Appx/AppxBundle: Add-AppxPackage -Path "C:\Path\To\YourFile.appx"
• For Msixbundle: Add-AppxPackage -Path "C:\Path\To\YourFile.msixbundle"

If you encounter a dependency error, you’ll see an error message listing the missing package. Download and install the required dependency, then rerun the command. PowerShell’s output can help pinpoint permission or signing issues that the GUI hides.

Check Package Signing and Trusted Certificates

All Appx, AppxBundle, and Msixbundle files must be digitally signed. If you try to install an unsigned or incorrectly signed package, Windows will refuse with messages like "App installation failed with error 0x800B0100" or "The certificate used to sign this package could not be verified."

If you received the file from a developer or organization, ask them to provide a properly signed package or a copy of the signing certificate. To manually install a certificate, double-click the .cer file (if provided) and select Install Certificate, then choose Local Machine > Trusted People. If you don’t trust the source or the package is unsigned, don’t install it - unsigned apps can be malicious or tampered with.

Resolve Common Error Codes and Dependency Issues

Installation often fails due to missing dependencies, especially with larger AppxBundles or Msixbundle files. Errors like 0x80073CF3 (dependency not found) mean your PC needs another package first. Read the error message for the missing dependency’s name and version. Download it from the same source or a trusted repository, install it, then retry your app.

Other common codes:

• 0x80070005: Access denied - Run as administrator or check group policies.
• 0x80073D02: App already installed or in use - Uninstall previous version, reboot, and try again.
• 0x80073CF6: Package installation failed - Often caused by corrupted downloads, disk space issues, or registry problems. Redownload the package and check your disk health.

Temporarily Disable Antivirus and Group Policy Restrictions

Some third-party antivirus or endpoint protection software blocks the installation of sideloaded apps or unknown packages. If you keep getting blocked without a clear reason, try temporarily disabling your antivirus. Be sure to re-enable it after installation. Also, enterprise environments may enforce restrictions via Group Policy. Run gpedit.msc, navigate to Computer Configuration > Administrative Templates > Windows Components > App Package Deployment, and check policies that block sideloading or unsigned packages. If grayed out, you’ll need admin access to change them.

Remember that disabling security software, even briefly, carries some risk. Only do this when you are certain your package is from a trusted source. If you’re unable to change group policies yourself, contact IT support for assistance.

Try a Clean User Profile or System Reset

If you’ve tried every fix but nothing works, the issue may be with your user profile or Windows installation. Corrupt user profiles can block app installations and cause permission errors. Create a new local user account from Settings > Accounts > Family & other users, log in, and try installing the package there.

If that fails, run DISM and SFC to repair Windows system files. Open an administrator command prompt and run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth. If problems persist, a Windows "Reset this PC" (under Settings > Update & Security > Recovery) can solve deep OS corruption, though it should be a last resort.

Frequently asked questions