If you've ever tried to download a Windows app manually — perhaps using a tool like store.rg-adguard.net or the NexaTools Microsoft Store Generator — you've probably encountered file extensions like .msix, .appx, .msixbundle, and .appxbundle. But what exactly are these file types, and how do they differ from traditional .exe or .msi installers?
This guide explains everything you need to know about Windows' modern packaging formats.
Use the NexaTools Microsoft Store Generator to get direct download links for any app package — no Store client required.
Generate Download Links →The Windows Package Format Timeline§
To understand these formats, it helps to see how Windows app packaging has evolved:
| Era | Format | Introduced | Used By |
|---|---|---|---|
| Windows 8 | .appx |
2012 | Windows Store apps |
| Windows 8.1 | .appxbundle |
2013 | Multi-architecture Store bundles |
| Windows 10 | .msix |
2018 | Modern Store + Win32 apps |
| Windows 10 1809+ | .msixbundle |
2018 | Multi-architecture modern bundles |
What Is `.appx`?§
.appx is the legacy Windows application package format, introduced with Windows 8 in 2012. It is essentially a ZIP archive (you can open it with 7-Zip) containing:
- The compiled application binaries
AppxManifest.xml— the app's identity, capabilities, and registration dataAppxSignature.p7x— the cryptographic digital signatureAppxBlockMap.xml— a manifest of all files and their hashes for integrity verification- Application resources (images, data files, etc.)
.appx packages are architecture-specific — a package built for x64 will not install on an arm64 device.
File structure example:
MyApp_1.0.0.0_x64.appx (ZIP archive)
├── AppxManifest.xml
├── AppxSignature.p7x
├── AppxBlockMap.xml
├── Assets/
│ ├── SplashScreen.png
│ └── StoreLogo.png
└── MyApp.exe
What Is `.msix`?§
.msix is the modern Windows application package format, introduced in Windows 10 version 1809 (2018). It supersedes .appx and adds several important improvements:
Key Improvements Over `.appx`§
- Containerization: Apps installed via
.msixrun in a lightweight virtualized environment, preventing them from writing to registry paths or file locations outside their sandbox — making uninstallation clean and complete. - Modification Packages: MSIX supports delta updates — only changed components are downloaded, reducing bandwidth usage.
- Win32 Compatibility: Unlike
.appx, MSIX can package traditional Win32 desktop applications (.exe-based) in a containerized format. - Better Group Policy Support: IT administrators can manage MSIX-packaged apps via Group Policy and Microsoft Endpoint Manager.
Internal Structure§
The internal structure is nearly identical to .appx but with enhanced signing and manifest schemas:
MyApp_1.0.0.0_x64.msix (ZIP archive)
├── AppxManifest.xml ← Enhanced schema vs. .appx
├── AppxSignature.p7x ← PKI signature chain
├── AppxBlockMap.xml
├── [Content_Types].xml
└── VFS/ ← Virtual File System (Win32 compat layer)
└── ProgramFilesX64/
└── MyApp/
What Is `.appxbundle` and `.msixbundle`?§
A bundle is a container that holds multiple architecture-specific packages in a single file.
For example, a single .msixbundle might contain:
MyApp_x64.msix— for 64-bit Intel/AMD processorsMyApp_x86.msix— for 32-bit systemsMyApp_arm64.msix— for ARM-based devices (Surface Pro X, Windows on ARM PCs)
When you install a bundle, Windows automatically selects and installs only the architecture-appropriate inner package. This is why bundles are the most common format distributed through the Microsoft Store — a single file works for all device types.
Bundle vs. Individual Package: Which Should I Download?§
| Scenario | Recommendation |
|---|---|
You know your architecture (most users are x64) |
Download the individual .msix / .appx for your arch |
| You're unsure of your architecture | Download the .msixbundle — Windows picks the right one |
| Deploying to multiple device types | Use the .msixbundle |
| Minimizing download size | Download the specific architecture package |
How to Install `.msix` and `.appx` Files§
Method 1: App Installer (Easiest)§
Simply double-click the .msix or .appxbundle file. The native App Installer will launch and guide you through installation.
Method 2: PowerShell§
For scripted or offline installations:
# Install a single package
Add-AppxPackage -Path "C:\Downloads\MyApp.msix"
# Install a bundle
Add-AppxPackage -Path "C:\Downloads\MyApp.msixbundle"
# Install for all users (requires admin)
Add-AppxPackage -Path "C:\Downloads\MyApp.msix" -Volume (Get-AppxVolume)
Method 3: DISM (Enterprise / Offline Image)§
For deploying to Windows images or offline machines:
DISM /Online /Add-ProvisionedAppxPackage /PackagePath:"MyApp.msixbundle" /SkipLicense
How to Get `.msix` and `.appx` Files for Any Store App§
You don't need to use the Microsoft Store client to get these files. The NexaTools Microsoft Store Generator queries Microsoft's official Store API and returns direct CDN download links for any app's .msix, .msixbundle, .appx, or .appxbundle files.
This is the same technology powering tools like store.rg-adguard.net — but without the ads, tracking scripts, and outdated interface.
How to use it:
- Find the app on
apps.microsoft.comand copy the Product ID from the URL (e.g.,9NKSQGP7F2NH) - Paste it into the NexaTools Store Generator
- Click Generate Links
- Download the package for your architecture
Inspect `.msix` and `.appx` Files§
Want to examine what's inside a package before installing? Use the NexaTools Appx/MSIX Inspector — a free, browser-based tool that:
- Parses
AppxManifest.xmlto display the app's identity, capabilities, and target device families - Lists all files in the package
- Highlights declared capabilities (especially sensitive ones like
runFullTrust) - Shows the digital signature block
- All locally in your browser — no file is uploaded to any server
Frequently Asked Questions§
Can I open a `.msix` file with 7-Zip or WinRAR?§
Yes. .msix and .appx files are ZIP archives. Rename them to .zip and open with 7-Zip, WinRAR, or Windows Explorer to browse their contents.
Why are some packages `.appx` and others `.msix` in the Store generator results?§
The format depends on how the developer packaged their app. Legacy apps use .appx; modern apps use .msix. Both install via the same methods.
What is a `.blockmap` file?§
A .blockmap file is a download accelerator manifest that allows the Store to perform chunk-based differential downloads. You do not need to download .blockmap files — they are used internally by the Store client and serve no purpose for manual installation.
What is the difference between a signed and unsigned package?§
All packages distributed through the Microsoft Store are digitally signed by Microsoft. If you try to install an unsigned package, Windows will block it (unless Developer Mode is enabled). The NexaTools generator only retrieves officially signed packages from Microsoft's CDN — they are always safe to install.
My `.msix` says "Untrusted Publisher" during install — is it safe?§
This warning appears when the app's certificate chain is not in Windows' Trusted Root Certification Authorities store. For packages downloaded from Microsoft's CDN via the NexaTools generator, this should not appear — all Microsoft Store apps are signed with Microsoft's root certificate.