How to Open MSIX File on Windows 11, 10 & 7 (Plus APPX and Bundles)

What is an MSIX file?

An MSIX file is a Windows app package: a signed, ZIP-based installer that Windows 10 (version 1709 and later) and Windows 11 install with its built-in installer app. Microsoft introduced MSIX in 2018 to replace the mix of MSI installers, ClickOnce, App-V and the older APPX format with one consistent package type. Every MSIX app is digitally signed, installs and uninstalls cleanly, and declares the capabilities (permissions) it needs — similar in spirit to how mobile app stores work.

Structurally, an .msix file is a ZIP archive containing a required AppxManifest.xml (the app's identity, dependencies and declared capabilities), an AppxBlockMap.xml (hashes used to verify every file during installation), a [Content_Types].xml, the app's own files and an AppxSignature.p7x digital signature. That is exactly what the tool above reads.

How to install an MSIX file on Windows 10 and 11

To open an MSIX file on Windows 10 or 11 you only need App Installer, which ships with Windows and updates itself through the Microsoft Store.

1. Double-click the .msix file. Windows opens the installer window with the app's name, publisher, version and permissions.
2. Check the publisher name. A well-known app should show its real company name, not a person or a random string.
3. Click Install. Most packages install per user and don't need administrator rights.
4. Find the new app in the Start menu. The downloaded .msix file is no longer needed afterwards.

Windows can't open the MSIX file? Fix App Installer

When Windows can't open an MSIX file, App Installer is usually missing, outdated or blocked. Each message points to a different fix.

"How do you want to open this file?" or "You'll need a new app to open this .msix file"

App Installer is missing or was removed — common on Windows LTSC/IoT editions, Windows Server, "debloated" installs and some company PCs. Fix it in one of these ways:

1. Install App Installer (publisher: Microsoft, free) from the Microsoft Store page, then double-click the file again.
2. If it's installed but old, update it: Microsoft Store > Library > Get updates, or run winget upgrade Microsoft.AppInstaller in an administrator terminal.
3. No Store access? Microsoft offers the App Installer download at aka.ms/getwinget. Check the installed version with (Get-AppxPackage Microsoft.DesktopAppInstaller).Version.
4. Or skip App Installer entirely and install from PowerShell — that uses Windows' deployment engine directly.

A website's "Install" button does nothing (ms-appinstaller disabled)

Many download pages used an ms-appinstaller: link that opened App Installer straight from the browser. Because attackers abused it to push malware disguised as well-known apps, Microsoft disabled the ms-appinstaller protocol by default on December 28, 2023, starting with App Installer version 1.21.3421.0. Those links now fail on most PCs. The fix is simple and safer: use the site's direct download link for the .msix, .msixbundle or .appinstaller file, save it, and open it from your Downloads folder. On managed PCs an administrator can turn the protocol back on with the EnableMSAppInstallerProtocol Group Policy; in October 2024 Microsoft added SmartScreen reputation checks for download URLs in App Installer 1.24.2411.0 and later.

"This app package is not supported for installation by App Installer because it uses certain restricted capabilities"

The package declares a restricted capability that App Installer refuses to handle (for example unvirtualizedResources, which lets an app write outside its container), or your copy is out of date. It's not a sign that the file is damaged. Try these fixes in order:

1. Update App Installer (winget upgrade Microsoft.AppInstaller) and try again — for several users this alone fixed it.
2. Install it from PowerShell: Add-AppxPackage -Path "C:\path\to\file.msix". PowerShell isn't subject to App Installer's restriction.
3. If the app is also in the Microsoft Store (Python, Teams and many others are), install that version instead.

The inspector above lists every restricted capability a package declares (marked Restricted on the Capabilities tab). Note that runFullTrust is restricted too, but it appears in almost every desktop app and App Installer normally accepts it.

Windows in S mode: "only apps from the Microsoft Store"

Windows 10/11 in S mode runs only Microsoft Store apps, so a downloaded MSIX won't install. Look for the same app in the Store, or switch out of S mode from the Activation page in Settings (Windows 11: Settings > System > Activation) using the Microsoft Store link there. Switching is free but permanent: you can't turn S mode back on.

Sideloading and Developer Mode on Windows 10 and 11

You don't need Developer Mode to install a normal, properly signed MSIX. Installing a package from outside the Store is called sideloading. Microsoft notes that before Windows 10 version 2004, sideloading had to be switched on in Enterprise, Education and LTSC editions, while Home and Pro allowed it by default. On current Windows 10 and 11, a signed package with a trusted certificate installs without changing any setting, unless an administrator policy blocks it.

Developer Mode is only needed for development: registering an unpacked app folder, deploying from Visual Studio, or installing unsigned test packages. It does not make an untrusted certificate trusted. Where to find it:

Install an MSIX with PowerShell (bundles, dependencies, all users)

PowerShell is the most reliable way to open MSIX files when the double-click route fails. Its Appx commands install .msix, .msixbundle, .appx and .appxbundle files, show the exact error code when something fails, and work even where App Installer isn't available.

• Install for your account: Add-AppxPackage -Path .\ContosoNotes.msix (run it in the folder that holds the file, or give the full path in quotes)
• Install with framework dependencies (for example a VCLibs or Windows App SDK package shipped alongside): Add-AppxPackage -Path .\ContosoNotes.msix -DependencyPath .\Microsoft.VCLibs.x64.14.00.Desktop.appx
• Install from a web address: Add-AppxPackage -Uri https://example.com/app.msixbundle — unaffected by the ms-appinstaller change, but only use it with URLs you trust.
• Install from an .appinstaller file: Add-AppxPackage -AppInstallerFile .\app.appinstaller
• Provision for every user on the PC (elevated PowerShell): Add-AppxProvisionedPackage -Online -PackagePath .\ContosoNotes.msix -SkipLicense
• Unsigned test package (Windows 11 only): Add-AppxPackage -Path .\test.msix -AllowUnsigned. It works only if the package's publisher contains Microsoft's special unsigned-package OID; it's meant for quick developer testing.
• Check what's installed: Get-AppxPackage *contoso* lists the full package name, version and install location.

How to open an MSIXBUNDLE or APPXBUNDLE file

You open MSIX files in bundle form (.msixbundle) and APPX bundles (.appxbundle) exactly like a single package: double-click it and click Install, or run Add-AppxPackage -Path .\App.msixbundle. A bundle is a ZIP that holds several complete packages — usually one per CPU architecture plus resource packages for languages and screen scales — and Windows installs only the ones that match your PC.

• Manifest location: a bundle has no AppxManifest.xml at its root. Its list of packages lives in AppxMetadata/AppxBundleManifest.xml, and each inner .msix/.appx has its own manifest.
• What the bundle manifest records for each package: file name, type (application or resource), architecture, version, size, and the language, scale or DirectX level it serves.
• See what's inside: drop the bundle into the inspector; the Packages tab lists every package and its Inspect button opens one for a full look at its capabilities.
• Extract it: MakeAppx unbundle /p MyBundle.msixbundle /d "C:\Out", or open it in 7-Zip (more).
• Wrong architecture error (0x80073CF3)? The bundle has no package for your CPU — for example only x64 on an ARM64 PC that can't use it. Download the build made for your device.

Can you open an MSIX file on Windows 7?

You can open an MSIX file on Windows 7 only through MSIX Core, and only if the developer built the package for it. Windows 7 has no App Installer and no native MSIX support (that starts with Windows 10 version 1709). MSIX Core is Microsoft's open-source installer that brings MSIX installation to Windows 7 SP1, Windows 8.1, Windows Server with Desktop Experience, and Windows 10 versions older than 1709.

1. Check the package: it must declare the target MSIXCore.Desktop with MinVersion="6.1.7601.0" (Windows 7 SP1). The inspector above shows this in the Windows 7 / 8.1 (MSIX Core) row. If it's missing, the package won't install on Windows 7 at all — ask the developer for a Windows 7 installer.
2. Install MSIX Core: download msixmgrSetup-x64.msi or msixmgrSetup-86.msi from Microsoft's msix-packaging releases page on GitHub and run it on a fully updated Windows 7 SP1.
3. Trust the certificate: MSIX Core requires the publisher's certificate in Trusted Root Certification Authorities (certutil -addstore root publisher.cer), and only if you trust the publisher.
4. Install the package: double-click it, or run msixmgr.exe -AddPackage C:\Apps\app.msix in an elevated Command Prompt. Remove it later with msixmgr.exe -RemovePackage <package full name>.

Common MSIX file problems and how to fix them

Most failures when you open MSIX files come down to three things: the signature, a damaged download, or a policy on the PC.

"This app package is not signed with a trusted certificate"

MSIX requires every package to be signed, and Windows must trust that certificate. Store apps and most big vendors are signed with certificates Windows already trusts. In-house or self-signed apps need their certificate added to Local Machine > Trusted People first (steps).

"App installation failed" / "The package could not be opened"

The file is often incomplete or corrupted, or it's not really a package. Re-download it and check its size against what the source lists. Drop it into the tool above: if it can't find a valid End Of Central Directory record, the ZIP container itself is damaged.

Install blocked on a work or school PC

Policies such as "Allow all trusted apps" or AppLocker can block sideloaded packages (error 0x80073CFF). Ask your IT department to deploy the app; don't try to bypass company policy.

Where to find the real reason for a failure

Open Event Viewer > Applications and Services Logs > Microsoft > Windows > AppxDeployment-Server, or run Get-AppPackageLog -ActivityID <id> with the ID from the error text. The installer app also writes logs to %LocalAppData%\Packages\Microsoft.DesktopAppInstaller_8wekyb3d8bbwe\LocalState\DiagOutputDir.

MSIX installation error codes explained

When you can't open an MSIX file, the installer shows "App installation failed with error message:" followed by a description and a hex code; PowerShell shows the same code as an HRESULT. These are the ones people hit most:

How to trust a publisher's certificate from the package itself

1. Right-click the .msix file → Properties → Digital Signatures tab, select the signer and click Details.
2. Click View Certificate → Install Certificate, choose Local Machine and approve the admin prompt.
3. Pick Place all certificates in the following store, browse to Trusted People, and finish the wizard. (Microsoft advises against the user store, and Trusted Root is not recommended for App Installer.)
4. Double-click the .msix again. Remove the certificate later from certlm.msc if you stop using the app.

How to extract or inspect an MSIX file without installing it

Because MSIX and APPX packages are ZIP archives, you can open MSIX files like any archive to read the manifest, icons or bundled files — no installation needed.

1. In the browser: the tool above shows the manifest details, capabilities and full file list, and opens packages inside bundles.
2. Rename to .zip: make a copy, change .msix to .zip, and use File Explorer's Extract All (or any ZIP tool).
3. 7-Zip: right-click the file > 7-Zip > Open archive; no renaming needed.
4. Microsoft's MakeAppx (part of the Windows SDK, in C:\Program Files (x86)\Windows Kits\10\bin\<version>\x64\): MakeAppx unpack /v /p MyPackage.msix /d "C:\Out" for a package, or MakeAppx unbundle /v /p MyBundle.msixbundle /d "C:\Out" for a bundle.
5. MSIX Hero: a free, open-source (GPLv3) MSIX toolkit for Windows 10/11 that opens packages, shows their manifest and signature, and manages installed apps.

Extracting a package doesn't install it, and encrypted Store packages (.emsix, .eappx) can't be opened this way.

How to open an MSIX file on Mac or Linux

1. You can't open an MSIX file on a Mac to run it: MSIX apps only work on Windows, with no way to install or launch one on macOS, Linux, ChromeOS or Android.
2. To use the app, run it inside a Windows 10/11 virtual machine, or look for the developer's native Mac/Linux version.
3. To look inside, rename the file to .zip (or open it with any archive tool such as The Unarchiver or unzip) and extract it.
4. Or drop it into the tool on this page, which works in any modern browser on any OS and shows the parsed AppxManifest.xml without extracting anything.

How to uninstall an MSIX app (and where it's installed)

1. Open Settings > Apps > Installed apps (Windows 10: Apps & features), find the app, click the … menu and choose Uninstall. Right-clicking the app in the Start menu and choosing Uninstall does the same.
2. From PowerShell: Get-AppxPackage *contoso* | Remove-AppxPackage.

MSIX apps install into C:\Program Files\WindowsApps, a protected folder you can't normally browse or edit, and keep their settings in %LOCALAPPDATA%\Packages\<package family name>. Uninstalling removes both cleanly — one of the main advantages over classic installers. Once the app is installed, the downloaded .msix file is no longer needed and can be deleted.

.msix vs .msixbundle vs .appx vs .appinstaller

• .msix — A single app package for one CPU architecture. Open it: Double-click (App Installer) or Add-AppxPackage.
• .msixbundle — Several .msix packages (e.g. x64 + ARM64, plus resource packs) in one file; Windows installs only the parts your PC needs. Open it: Same as .msix (details).
• .appx / .appxbundle — The older Windows 8/10 app package formats MSIX grew out of; same ZIP-based layout. Open it: Same as .msix; the tool above inspects both.
• .appinstaller — A small XML file that points to a package URL and tells Windows how to check for updates. Open it: Double-click; Windows downloads the package it references.
• .msixupload / .appxupload — Developer upload packages for Microsoft Store submission, not meant to be installed. Open it: Extract as ZIP to get the .msix/.msixbundle inside.
• .emsix / .eappx / .emsixbundle — Encrypted Store packages. Open it: Can't be opened or installed manually.

MSIX vs MSI vs EXE installers

• Signing: MSIX — Required; MSI — Optional; EXE setup — Optional.
• Install location: MSIX — Protected WindowsApps folder, per user; MSI — Usually Program Files, per machine; EXE setup — Anywhere the installer chooses.
• Uninstall: MSIX — Clean — files and registry changes are virtualized; MSI — Usually clean, can leave leftovers; EXE setup — Depends entirely on the vendor.
• Admin rights: MSIX — Not needed for a per-user install; MSI — Usually needed; EXE setup — Usually needed.
• Drivers, services, shell add-ons: MSIX — Limited support; MSI — Full support; EXE setup — Full support.
• Windows 7: MSIX — Only via MSIX Core; MSI — Yes; EXE setup — Depends on the app.

If a vendor offers both, MSIX is the tidier choice for a normal app; pick the MSI or EXE when you need features MSIX restricts, such as drivers, some system-wide plugins, or apps that must write into their own install folder. Like an APK on Android, an MSIX is a signed, self-describing package rather than a program that runs its own setup logic.

Related file extensions

Sources and technical references

MSIX is a Microsoft-defined packaging format; every fact on this page was checked against Microsoft's documentation in October 2026.

• What is MSIX? — Microsoft Learn — overview of the format.
• MSIX features and supported platforms — Microsoft Learn — Windows 10 1709+ support and the sideloading change in Windows 10 2004.
• Microsoft addresses App Installer abuse — Microsoft Security Response Center — ms-appinstaller disabled on December 28, 2023 (App Installer 1.21.3421.0) and the October 2024 update.
• Install or update App Installer — Microsoft Learn — winget upgrade and offline download.
• App Installer — Microsoft Store — the official App Installer listing.
• Troubleshoot App Installer issues — Microsoft Learn — certificate stores, event logs and log folder.
• Troubleshooting packaging, deployment, and query of Windows apps — Microsoft Learn — meaning of each error code.
• Enable your device for development — Microsoft Learn — Developer Mode settings paths.
• Sideload line of business apps — Microsoft Learn — sideloading settings on Windows 10 and 11.
• Add-AppxPackage — Microsoft Learn and Create an unsigned MSIX package — parameters and -AllowUnsigned rules.
• MSIX Core — Microsoft Learn, Deploy with MSIX Core and Support MSIX Core in your package — Windows 7 SP1 support, msixmgr commands and the MSIXCore.Desktop target.
• Bundling MSIX packages — Microsoft Learn and Bundle manifest Package element — how bundles and AppxBundleManifest.xml work.
• Create an app package with MakeAppx.exe — Microsoft Learn — unpack and unbundle commands.
• Windows 10 and Windows 11 in S mode FAQ — Microsoft Support — Store-only apps and switching out of S mode.
• MSIX Hero — free open-source MSIX toolkit.

Frequently asked questions