ShiftTools ShiftTools
Zero-Upload Browser Utility

Store Package Extractor

Use this Microsoft Store app downloader to resolve official direct links (.appx, .msixbundle) from any Store URL or ProductId for offline installs.

Interactive Tool Workspace

Loading local in-browser WebAssembly engine & hardware cryptographic sandbox...

Installing a UWP utility, Windows Terminal, WhatsApp, or Xbox runtime on a Windows LTSC workstation, an air-gapped lab PC, or a machine where the Microsoft Store app is blocked or corrupted shouldn't require risky third-party repack websites. This Microsoft Store app downloader resolves official, cryptographically signed .appx, .msixbundle, and dependency installer links (VCLibs, UI.Xaml, NET.Native) directly from Microsoft's Delivery Optimization (tlu.dl.delivery.mp.microsoft.com) servers using a Store URL, ProductId, or quick-pick app catalog.

When you need official .msixbundle and .appx installers outside the Store app

The built-in Microsoft Store client hides its raw installer packages in a locked WindowsApps folder and refuses to run at all on many enterprise and stripped-down Windows builds:

  • Windows 10/11 Enterprise LTSC and Windows Server workstations: LTSC builds ship without the Microsoft Store app installed, yet engineers still need official packages like Windows Terminal, PowerToys, WinGet (Microsoft.DesktopAppInstaller), HEVC Video Extensions, or Python.
  • Air-gapped labs, classrooms, and offline PC provisioning: Downloading the main .msixbundle plus its required Microsoft.VCLibs.140.00 and Microsoft.UI.Xaml dependency frameworks once onto a USB drive and deploying them across 30 offline machines via PowerShell.
  • Fixing a broken or looping Microsoft Store client: Downloading the fresh official Microsoft.WindowsStore .msixbundle and DesktopAppInstaller packages directly from Microsoft's CDN to repair the Store itself with Add-AppxPackage.
  • Archiving a specific working version of an app: Saving a known-good .appx or .msixbundle installer locally before an automatic Store update changes the interface.

How to use the Microsoft Store app downloader (3 tailored workflows)

Depending on whether you need a single .msixbundle installer, a multi-app offline USB provisioning kit, or an automated PowerShell deployment script for Windows LTSC, choose the workflow that fits your setup:

Method 1: Resolve by Microsoft Store Web URL or 12-Character ProductId

  1. Paste your Store link or identifier: Paste any https://apps.microsoft.com/detail/9N... link, a 12-character alphanumeric ProductId (such as 9N0DX20HK701 for Windows Terminal), or a PackageFamilyName into the command bar.
  2. Set your Release Ring and target CPU: Select Retail (Stable) (or RP, WIS, or WIF Insider rings) and pick your processor architecture (x64, arm64, x86, or neutral).
  3. Click Resolve Packages: The workbench queries Microsoft's FE3 Delivery Optimization catalog and separates the returned links into Main App Bundles, Required Framework Dependencies (VCLibs, UI.Xaml, NET.Native), and optional .BlockMap files.
  4. Download the Recommended Offline Kit: Keep the auto-selected Recommended badges checked (which pairs the latest main .msixbundle with the newest matching x64 dependencies) and click Download on each file.

Method 2: Build a Multi-App Offline Provisioning Kit (PC Setup Cart & Checkout Flow)

  1. Open the Built-In 48-App Directory Drawer: Browse by category (System & Dev, Media & Codecs, Productivity, Social) when you don't want to hunt for Store URLs manually.
  2. Add multiple apps to your PC Setup Cart: Click + Setup Cart on every utility your fresh workstation needs (for example, Windows Terminal, App Installer / WinGet, HEVC / AV1 Video Extensions, and Python 3.12).
  3. Open the PC Setup Cart Drawer and click Resolve Entire Cart: The batch resolver queries Microsoft's FE3 catalog for every queued item in sequence and locks in the newest primary installer URL and file size for each app.
  4. Export your batch checkout manifest: Click Export Cart PowerShell (.ps1) or Export Cart URL List (aria2c / curl) to download and install the entire software stack across offline PCs in one pass.

Method 3: Sideload via PowerShell, WinGet, or DISM (Script Studio)

  1. Scroll to the Automated Offline Installer & Script Studio directly below the package table after resolving an app.
  2. Pick your deployment target tab:
  • PowerShell Sideload: Generates an Add-AppxPackage -Path ".\..." -DependencyPath $Deps command for files already in your Downloads folder.
  • Auto-Download & Install (.ps1): Generates a self-contained script that downloads the dependencies and main bundle via Invoke-WebRequest into $env:TEMP and installs them in exact dependency order.
  • WinGet & DISM LTSC: Outputs the winget install --id ... command alongside DISM.exe /Online /Add-ProvisionedAppxPackage /SkipLicense for provisioning golden Windows Enterprise LTSC images for all users.
  • aria2c / cURL Batch: Outputs 16-connection aria2c -x 16 -s 16 and curl.exe -L commands for high-speed downloading.
  1. Click Copy Code or Download .PS1 Script and run it in an elevated PowerShell prompt.

Power-user workspace features built for system administrators

Built-in Quick App Catalog (no need to open Microsoft Store)

If you don't have the Microsoft Store URL handy, you can pick essential Windows packages - such as Windows Terminal (9N0DX20HK701), App Installer / WinGet (9NBLGGH4NNS1), Microsoft Store (9WZDNCRFJBMP), PowerToys (XP89DCGQ3K6VLD), VP9 / AV1 / WebP Media Extensions, Calculator, Photos, and Notepad - directly from the built-in quick selector.

Smart Recommended Kit (Main App + Dependency Matcher)

Raw FE3 catalog dumps often return 40 to 90 files across four CPU architectures (x86, x64, arm, arm64) and multiple older versions of Microsoft.UI.Xaml. Instead of making you guess which 4 files out of 80 you actually need, Smart Recommended Kit filters for your selected CPU architecture (e.g., x64 + neutral), picks the newest version of each dependency family (VCLibs, UI.Xaml, NET.Native.Framework, NET.Native.Runtime), and selects the primary .msixbundle / .appx automatically.

One-click PowerShell (.ps1) and Bulk Downloader (aria2c, curl, IDM) exports

Installing an .msixbundle on a clean PC fails with HRESULT: 0x80073CF3 if you don't install its VCLibs and UI.Xaml dependencies first. The built-in PowerShell Script Generator outputs a ready-to-run .ps1 script that installs every dependency in the exact order before registering the main package via Add-AppxPackage -Path ... -DependencyPath ....

Multi-App PC Setup Cart

Setting up a new workstation rarely stops at one app. You can resolve Windows Terminal, add its kit to the PC Setup Cart, resolve HEVC/AV1 codecs, add them to the cart, and export one unified offline installer script and download manifest for the entire machine.

A real example: installing Windows Terminal (9N0DX20HK701) offline on Windows 11 LTSC (x64)

Suppose you have a freshly installed Windows 11 IoT Enterprise LTSC (x64) workstation with no Microsoft Store app and want to install Windows Terminal:

  1. Click Windows Terminal (9N0DX20HK701) in the Quick Catalog (or paste https://apps.microsoft.com/detail/9n0dx20hk701) with Ring set to Retail and Architecture set to x64.
  2. Click Resolve Packages. Microsoft's FE3 catalog returns the package manifest containing Microsoft.WindowsTerminal_..._8wekyb3d8bbwe.msixbundle (~44.8 MB) along with Microsoft.VCLibs.140.00.UWPDesktop_14.0.33728.0_x64__8wekyb3d8bbwe.appx and Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe.appx.
  3. Click Select Recommended Kit (x64) - the tool automatically selects those exact 3 files and ignores the x86 and arm64 variants.
  4. Download the 3 packages and click Copy PowerShell Install Command:
   Add-AppxPackage -Path ".\Microsoft.VCLibs.140.00.UWPDesktop_14.0.33728.0_x64__8wekyb3d8bbwe.appx"
   Add-AppxPackage -Path ".\Microsoft.UI.Xaml.2.8_8.2310.30001.0_x64__8wekyb3d8bbwe.appx"
   Add-AppxPackage -Path ".\Microsoft.WindowsTerminal_1.21.2911.0_8wekyb3d8bbwe.msixbundle"
  1. Run the script in an elevated PowerShell prompt - Windows Terminal installs cleanly in four seconds with full Microsoft digital signature verification.

Practical tips, mistakes, and limitations

  • Why tlu.dl.delivery.mp.microsoft.com links expire: Microsoft generates temporary time-limited signed CDN tokens on its Delivery Optimization URLs (typically valid for 10 to 30 minutes). Download your files shortly after resolving them, or re-click Resolve if a link expires.
  • XP... Win32 Store IDs vs 9N... UWP/MSIX Store IDs: Traditional UWP and MSIX apps (whose ProductIds start with 9, like 9N0DX20HK701) are distributed via Microsoft's FE3 XML SOAP catalog as .appx and .msixbundle packages. Newer Win32 "Spark" wrappers whose IDs start with XP (like VS Code or Discord in the Store) are distributed as standard .exe / .msi installers via WinGet (winget install --id ...); for those, the tool provides the direct winget command.
  • Avoid double-clicking dependencies out of order: Always install Microsoft.VCLibs, Microsoft.NET.Native, and Microsoft.UI.Xaml .appx files before installing the main .msixbundle, or use the generated PowerShell .ps1 script which handles the sequence automatically.

Privacy and data handling transparency

To resolve official Microsoft CDN download URLs without CORS blocks, your browser sends only the public Microsoft Store ProductId / URL and selected Release Ring (Retail, RP, WIS, WIF) to our lightweight stateless resolver endpoint (https://api.shifttools.in/api/msstore), which queries Microsoft's public fe3.delivery.mp.microsoft.com SOAP catalog and returns the official *.microsoft.com download URLs. All actual installer downloads happen directly between your browser and Microsoft's official servers - we never host, modify, or proxy executable binary files.

Companion system and developer utilities

Need to transfer your downloaded .msixbundle offline installer kit to another PC on your network without a USB stick? Beam the files directly peer-to-peer with ShiftDrop P2P File Transfer. You can also inspect manifest JSON structures in JSON Formatter or create short shareable links with Custom URL Shortener. Read our complete tutorial on how to download Microsoft Store apps offline.

Frequently Asked Questions

Are the .appx and .msixbundle files downloaded from Microsoft's official servers?

Yes, 100%. Every download link resolved by this tool points directly to Microsoft's official Delivery Optimization CDN (tlu.dl.delivery.mp.microsoft.com). Every package carries Microsoft's original cryptographic Authenticode signature, which Windows verifies automatically during installation. When you paste a Microsoft Store URL or 12-character ProductId (such as 9MZ95KL8MR0L), the resolver queries Microsoft's official FE3 Delivery catalog for signed package links.

What is the difference between .appx, .msix, .appxbundle, and .msixbundle?

An .appx or .msix file is a single-architecture Windows package (for example, only x64 or only arm64). A bundle (.appxbundle or .msixbundle) packages multiple CPU architectures and language resource packs together into a single file so Windows can install the right slice automatically. The results table lists the main .msixbundle, .appx, or .eappx installer alongside required UWP framework dependencies like Microsoft.VCLibs and Microsoft.UI.Xaml.

Why did Add-AppxPackage fail with error 0x80073CF3 ( missing framework )?

Error 0x80073CF3 means the main app requires a shared runtime framework - almost always Microsoft.VCLibs.140.00, Microsoft.UI.Xaml, or Microsoft.NET.Native - that is not yet installed on your PC. Click Select Recommended Kit in the tool to download those small .appx dependency files from the same list and install them right before the main .msixbundle.

Which CPU architecture should I choose: x64, x86, arm64, or neutral?

For almost all modern Intel and AMD 64-bit Windows 10 and Windows 11 PCs, choose x64 (plus any neutral bundle). Choose arm64 for Snapdragon / Surface Pro ARM laptops or Windows 11 on Apple Silicon Parallels VMs, and x86 only for legacy 32-bit Windows installations.

What is the "Inspect Manifest" button used for?

Inspect Manifest displays the exact package family names, version numbers, file sizes, SHA-1/SHA-256 package hashes, and dependency tree returned by Microsoft's FE3 catalog so system administrators can audit package metadata before downloading a single byte. Filter pills (x64, x86, ARM64, neutral) and the hide-dependencies toggle let you isolate the exact binary architecture matching your target Windows PC.

How does the Multi-App PC Setup Cart work?

When you are preparing an offline USB stick for a fresh Windows installation, you can resolve multiple apps one after another and click Add to Setup Cart on each. Opening the Cart lets you export a single combined PowerShell provisioning script (.ps1) or bulk download list (aria2c / IDM) for all your selected apps and dependencies at once.