How to Install an MSIX File on Windows 10 and 11

On Windows 10 and Windows 11, the default route is a double-click: open the downloaded .msix or .msixbundle file and Windows starts App Installer, which shows details about the app, such as its publisher, and guides you through the install. If that doesn’t work, PowerShell’s Add-AppxPackage command installs the same file, and either way the package must be signed with a certificate your PC trusts.

Windows 10 reached end of support on October 14, 2025, but these steps still work there.

What an MSIX file is

MSIX is Microsoft’s app package format for Windows 10 and Windows 11. A .msix file holds one app package. A .msixbundle groups several packages, usually builds of the same app for different processor types, so Windows can pick the right one. Older packages may use the related .appx and .appxbundle extensions, and they install the same way. An MSI file is different: it’s the older Windows Installer format and runs its own setup wizard rather than App Installer.

MSIX packages are meant to be digitally signed, and the signature names the publisher. Windows checks it before it installs anything, which is why the publisher shown during install matters and why most errors below come back to signing.

Install by double-clicking (App Installer)

  1. Download the .msix or .msixbundle file from the developer’s own website or another source you trust.
  2. Open your Downloads folder and double-click the file.
  3. App Installer opens. Read the publisher name and the other details it shows. If the publisher isn’t the company you expected, close the window.
  4. Select the install button and follow the prompts. When it finishes, the app appears in the Start menu like any other app.
Windows App Installer window for an MSIX package showing the publisher and the Install button highlighted
(1) Check the publisher and version, then (2) click Install. (Illustration)

Microsoft’s MSIX pages differ on whether current Windows 10 accepts signed packages from outside the Store by default, so a Windows 10 PC may need sideloading or Developer Mode turned on first (see below). On Windows 11, sideloading of standard signed packages is enabled by default.

If double-clicking does nothing

App Installer ships as part of Windows and, according to Microsoft’s App Installer page, updates itself from the Microsoft Store when updates are turned on. If it seems missing or broken:

  • Check its version in PowerShell with (Get-AppxPackage Microsoft.DesktopAppInstaller).Version. No output means it isn’t installed for your account.
  • Update it with winget upgrade Microsoft.AppInstaller, or from the Microsoft Store.
  • On a PC without the Store, Microsoft points to aka.ms/getwinget for the App Installer package. Installing winget on Windows 10 covers that route and what winget can do afterward.

Install with PowerShell (Add-AppxPackage)

Microsoft describes Add-AppxPackage as the command that adds a signed app package to a user account. It accepts .msix, .msixbundle, .appx and .appxbundle files, and it’s the better choice when App Installer won’t open or when you need to add dependency packages.

  1. Find the file in File Explorer, hold Shift, right-click it, and choose Copy as path.
  2. Open Windows PowerShell (on Windows 11 it also runs inside Terminal). Search for PowerShell from Start if it isn’t on the right-click Start menu.
  3. Type Add-AppxPackage -Path, a space, then paste the path, for example Add-AppxPackage -Path "C:\Users\<name>\Downloads\NoteTaker.msix".
  4. Press Enter. PowerShell shows progress while it works and returns to the prompt when it’s done; an error appears in red with a code you can look up below.

A normal install for your own account doesn’t need an administrator window. If you see an access-denied error (0x80070005), Microsoft’s troubleshooting guide suggests running PowerShell as administrator.

Packages that need dependencies

Some apps rely on separate framework packages that the developer ships alongside the main file, often in a Dependencies folder for your processor type. Add them in the same command with -DependencyPath, as in Microsoft’s own example:

Add-AppxPackage -Path ".\MyApp.msix" -DependencyPath ".\winjs.msix"

Packages that are already installed on the PC don’t need to be listed again.

Signed packages and certificates

Windows installs only packages signed with a certificate it trusts. A package from a commercial developer is usually signed with a certificate that chains to a trusted authority, so it installs without extra steps. A package signed with the developer’s own test certificate (a self-signed certificate) fails with error 0x800B0109, which Microsoft’s MSIX troubleshooting guide describes as a certificate that isn’t in the device’s trusted stores.

The safe fix is a properly signed package from the publisher. Microsoft’s guidance for organizations is that an administrator imports a known publisher’s certificate into the Local Computer’s Trusted People store, never the user store and never the trusted root store for a self-signed certificate. If a download came with a certificate file and instructions to trust it, and you don’t know the developer, don’t. Installing that certificate tells Windows to trust anything signed with it.

When Windows blocks the install

  • Only Store apps are allowed. A PC in S mode, or with the app source setting limited to the Microsoft Store, refuses packages from elsewhere. Installing apps outside the Microsoft Store on Windows 11 explains both settings. A warning that an app isn’t Microsoft-verified is a separate prompt, covered in installing unverified apps on Windows 11.
  • Sideloading is off on Windows 10. Older Windows 10 versions need sideloading or Developer Mode turned on before they accept packages from outside the Store. These switches are on the For developers page in Windows 10 Settings, and the exact labels differ between versions.
  • Windows 11 developer settings. Microsoft’s Developer Mode page says the switch is on the For developers page before Windows 11 25H2, and in the For developers section of System > Advanced from 25H2 on. It needs administrator access, and Microsoft says ordinary users have no need to turn it on.
  • Work or school PC. Organizations can block apps from outside the Store through policy. Ask IT.
  • A web page’s install link does nothing. Microsoft disabled the ms-appinstaller web protocol by default in December 2023 for security reasons. Download the file, then open it from your Downloads folder.

MSIX error codes and fixes

Code What Microsoft says it means What to try
0x800B0109 The signing certificate’s root isn’t trusted on this device. Get a properly signed package from the publisher; see the certificate section above.
0x80073CF3 The package failed update, dependency or conflict validation, for example a missing dependency, a conflicting package or the wrong processor architecture. Add the dependency packages with -DependencyPath and make sure the file matches your PC’s architecture.
0x80073CF0 The package couldn’t be opened, for example because it’s unsigned or the publisher name doesn’t match the certificate. Download the file again from the developer; ask them for a correctly signed build.
0x80073CFF Installing it needs a developer license or sideloading turned on. Turn on sideloading or Developer Mode as described above, if you trust the package.
0x80073D02 The app (or one it depends on) is in use. Close the app and try again.
0x80070005 Access denied. Run PowerShell as administrator; Microsoft also mentions security software as a possible cause.

For anything else, Microsoft points to the event log: open Event Viewer and go to Applications and Services Logs > Microsoft > Windows > AppxDeployment-Server > Operational. The code meanings for 0x80073CF3, 0x80073CF0 and 0x80073CFF come from Microsoft’s app package troubleshooting page.

Check or remove an installed MSIX app

MSIX apps show up in Settings > Apps with everything else (the list may be named Apps & features on Windows 10); checking installed apps in Windows 10 covers the list and the PowerShell commands that export it. To remove one:

  • Right-click the app in the Start menu and choose Uninstall.
  • Or open Settings > Apps > Installed apps, select the More icon next to the app, and choose Uninstall.
  • In PowerShell, find the full package name with Get-AppxPackage *NoteTaker*, then run Remove-AppxPackage -Package followed by that name.

More removal routes, including fixes for apps that won’t uninstall, are in uninstalling a program on Windows 11.

MSIX install answers

Do I need administrator rights to install an MSIX file?

Not for a normal install to your own account. Turning on Developer Mode, importing a certificate for all users and removing a package for every account all need an administrator.

Can I install an unsigned MSIX package?

Not by double-clicking. Microsoft says unsigned packages need additional trust configuration, so treat an unsigned package from someone else as a reason to stop.

How do I update an MSIX app?

Install the newer version of the same package by double-click or Add-AppxPackage; some apps also update themselves through an .appinstaller file the developer publishes.

Start with the double-click; switch to PowerShell only when App Installer can’t open the file or the package needs dependencies.