The Microsoft Store is the default way most Windows 10 and Windows 11 users install apps, but the Store client isn’t always the most convenient option. It can be slow, it sometimes fails to install an app due to a glitch, or you may simply want an offline copy of an installer to deploy across several machines, archive for later, or use on a PC that doesn’t have Store access. In these situations, a “direct download link” — a URL that points straight to the actual package file on Microsoft’s content delivery network (CDN) — becomes useful.
These packages come in a handful of formats. APPX was the original format introduced with Windows 8, while MSIX is its modern successor, offering features like differential updates and cleaner uninstalls. AppxBundle and MSIXBundle are container files that hold several architecture-specific packages (x86, x64, ARM) in one file, letting the Windows installer pick the right one automatically for your device.
Because Microsoft doesn’t expose a simple “download” button on the Store website for these packages, a small ecosystem of tools has grown up around extracting them: browser-based link generators, PowerShell one-liners, and network-inspection techniques for more advanced cases. This guide walks through the main methods, in order of how commonly they’re used, along with the setup you’ll need afterward to actually install what you download.
A quick note before diving in: only use these methods for apps you’re entitled to install — most generators intentionally block paid apps and games for this reason — and be aware that grabbing a package this way bypasses the Store’s usual update mechanism, so you’ll need to manage updates yourself.
Methods
Method 1: Use a Web-Based Link Generator (the standard approach)
This is the most common and easiest method, and it doesn’t require installing anything.
- Find the app’s Store page. Open the Microsoft Store (or apps.microsoft.com in a browser), locate the app you want, and copy its listing URL, or note its Product ID / Store App ID shown in the page’s address or details.
- Paste the link into a generator site. Sites built for this purpose — the best-known being RG-Adguard’s package tool — accept a Store URL or product ID and query Microsoft’s servers on your behalf.
- Review the results. The tool returns a list of files: the app’s package (labeled AppxBundle or MSIXBundle) and its dependency/updater packages (sometimes labeled EAppxBundle), along with metadata like version number, SHA-1 hash, file size, and link expiry time.
- Download the right files. You typically need both the main bundle and the update-related package for a clean install. Note that the file description also includes the expiry date, so download soon after generating the link since these direct CDN URLs don’t stay valid indefinitely.
Keep in mind that these tools are commonly configured to block listings for paid apps and games, returning an empty list instead of download links — so this method is really intended for free apps.
Method 2: Use a PowerShell One-Liner Generator
A newer style of tool skips the web interface entirely and instead gives you a single PowerShell command tied to a specific app ID. These services generate direct official download links for Appx, MSIX, and MSIXBundle packages, paired with a one-click PowerShell command you can run in a terminal.
The general workflow:
- Get the app’s Store ID from its listing page.
- Visit a PowerShell-based generator, enter the ID, and copy the generated command (usually something like
irm <generator-url>/ms/APP_ID | iex). - Open PowerShell (as Administrator, if the tool recommends it) and run the command.
- The script fetches the correct package directly from Microsoft’s CDN and, depending on the tool, either downloads it to a folder or offers to install it immediately.
This method is popular with people managing several machines because it can be scripted and repeated without manually clicking through a web page each time. As with any command copied from a third-party site, read it before running it, and only use generators from sources you trust — a script that pipes straight into iex (Invoke-Expression) executes immediately, so verify what a shortened or unfamiliar link actually does first.
Method 3: Capture the CDN URL with a Network Debugger (advanced)
Sometimes an app doesn’t show up correctly in a link generator, or you need the exact package version currently being served to your specific PC, region, and architecture — for example, while troubleshooting a failed Store install. In that case, you can watch the Store app request the file itself.
This method is more technical, but it can reveal the direct CDN URL that the Store uses, via an HTTPS-capable network debugging tool such as Fiddler Classic, Fiddler Everywhere, or HTTP Toolkit — Fiddler Classic remains a common choice for this kind of Windows desktop troubleshooting. The rough process:
- Install and open your chosen network debugger, and enable HTTPS decryption if the tool requires it for that traffic.
- Start the Microsoft Store app and begin installing or updating the target app.
- Watch the captured traffic for requests going out to Microsoft’s package delivery domains.
- Copy the resulting package URL once you spot it.
This approach is most useful when the listing simply won’t resolve in a link generator, when you need the exact package version currently offered to your PC, when you want to see which dependencies the Store pulls in automatically, or when you’re diagnosing a Store installation failure more generally. It’s overkill for everyday downloading, but it’s the most reliable fallback when the simpler tools come up empty.
Method 4: Automated/Bulk Extraction Tools
If you regularly need packages for many apps — say, for enterprise deployment, testing, or archiving — dedicated automation tools exist that wrap the same underlying process into a repeatable job. Tools of this kind extract MSIX/APPX packages for offline installation on Windows 10/11, letting you choose the target architecture and returning details such as the URL, version, size, and SHA1 hash for each package. These are generally built on cloud automation platforms and are aimed at developers or IT administrators who want to script the extraction of many apps at once rather than doing it one at a time through a browser.
After Downloading: Installing the Package
Once you have the files, Windows needs Developer Mode (or sideloading permissions) turned on before it will install an app package outside the Store. On Windows 11, this is found by opening Settings, going to Privacy & security, switching to the Security section, expanding the “For Developers” menu, and toggling Developer Mode on. If Windows shows a warning about installing apps from outside the Store, that’s expected — it’s simply confirming you understand the source isn’t the Store itself.
Once Developer Mode is active and any related packages finish installing, double-clicking the AppxBundle or MSIXBundle file will launch the standard installer. The updater-labeled file (often the EAppxBundle) isn’t a separate app — it’s used for updating rather than the initial install, and any dependency packages listed alongside the main bundle should be installed first if you hit an error.
Conclusion
Generating a direct download link for a Microsoft Store app is mostly a matter of picking the right tool for the situation. For a one-off free app, a browser-based link generator is the fastest route. If you’re setting up several machines or want something scriptable, a PowerShell-based generator saves time. When a listing won’t resolve or you need to match an exact version being served to your PC, a network debugger like Fiddler gives you the ground-truth CDN URL. And for large-scale or repeated extraction, an automation tool built specifically for the job is worth the setup.
Whichever method you use, remember that you’re bypassing the Store’s normal install and update flow — Developer Mode needs to be enabled first, download links tend to expire, and paid apps are usually excluded from these tools by design. Used within those limits, direct download links are a genuinely useful shortcut for offline installs, deployment, and troubleshooting.
FAQ
1. Is it legal or safe to download Microsoft Store apps this way?
For free apps, yes — you’re retrieving the same package Microsoft would otherwise deliver through the Store, just via a different route. Most link generators deliberately exclude paid apps and games to avoid facilitating piracy, since sideloading a paid app this way would bypass the purchase requirement. Safety-wise, stick to well-known, reputable generator sites, since you’re trusting them to proxy a request to Microsoft’s servers rather than serve you a modified file — verifying the SHA-1 hash shown alongside a download is a good habit if one is provided.
2. Why do I need to enable Developer Mode to install these files?
Windows normally only installs apps through the Store, which handles licensing and update checks automatically. Installing a package file directly is technically “sideloading,” and Windows requires Developer Mode (or a sideloading policy) enabled as a safeguard, since it’s stepping outside that managed pipeline. Once it’s on, .appx and .msix files can be installed by double-clicking them like any other installer.
3. Will an app installed this way still update automatically?
No — apps installed via direct package files aren’t tracked by the Store’s update system unless you later reinstall or relink the app through the Store itself. That’s why generators typically supply an “updater” package alongside the main app bundle: you’re expected to periodically re-download and reinstall newer versions manually if you want to stay current.
4. Why does my download link stop working after a while?
The URLs returned by these tools point to Microsoft’s CDN with time-limited access tokens attached, similar to how a signed download link works on many other platforms. They’re generated fresh for each request and are only meant to be valid briefly, which is why generator sites typically display an expiry time next to each file — if the link stops working, simply regenerate it rather than trying to reuse an old one.
