How to Sideload Apps on Windows Phone After Store Shutdown

With the Windows Phone Store effectively shut down, the only reliable way to get apps onto a Lumia in 2026 is sideloading — installing app packages directly instead of through the Store. I’ve been sideloading onto Windows Phone since the 8.1 days, and the good news is that the platform was built with this in mind. The better news: once you set it up, it takes about two minutes per app. This guide walks through every method, from the simplest to the most powerful.

[IMAGE: Windows Phone “Settings > Update & security > For developers” screen]

First, understand the file types

Windows Phone apps come in a few package formats. Knowing which you have determines the install method:

• .xap — the classic Windows Phone 8/8.1 package format.
• .appx / .appxbundle — the Windows 10 Mobile package format (also used by UWP apps).
• .appxbundle + dependencies — some apps need framework dependency packages (e.g., the VC++ runtime) installed alongside them.

Your device’s OS version matters: an 8.1 device installs XAPs; a Windows 10 Mobile device installs APPX/APPXBUNDLE. Check under Settings > System > About.

Method 1: Enable developer mode and use the built-in installer (easiest)

Windows 10 Mobile includes an app deployment path that doesn’t need a PC for already-downloaded packages.

1. Go to Settings > Update & security > For developers.
2. Select Developer mode (or “Sideload apps” if developer mode is unavailable on your build). Accept the warning.
3. Transfer your .appx/.appxbundle file to the phone via USB (copy it to the Downloads or Documents folder) or download it directly in the browser.
4. Open the File Explorer app (built into Windows 10 Mobile), navigate to the file, and tap it. The OS installer launches and installs the package.

If the app reports a missing dependency, install the dependency package first using the same tap-to-install method, then install the main app.

[IMAGE: Tapping an .appxbundle file in File Explorer showing the install prompt]

Method 2: Deploy from a PC with the Windows Phone tools

For XAP files on 8.1 devices, or for bulk deployment, a PC is the most dependable route. You’ll need the Windows Phone SDK / Windows 10 Mobile tools that include the Application Deployment utility (sometimes called WPV App Deployment).

1. On the phone, enable developer/sideload mode as in Method 1.
2. On the PC, install the matching SDK for your device’s OS version. The deployment tool ships with it.
3. Connect the phone via USB and unlock the screen.
4. Open the deployment tool, choose Device as the target, browse to your .xap or .appx, and click Deploy.
5. The app appears in your app list when deployment completes.

This method gives the clearest error messages, which is invaluable when a package has dependency or signing issues.

Method 3: WConnect / Device Portal over USB or Wi-Fi (power users)

Windows 10 Mobile includes a Device Portal — a web-based management interface — once developer mode is on. Pair it with the wconnect helper on your PC and you can install packages through a browser.

1. In For developers, turn on Device Portal and Device discovery. Note the pairing PIN.
2. On the PC, run wconnect.exe usb (for USB) and enter the PIN when prompted. For Wi-Fi, both devices must be on the same network and you use the phone’s shown IP address.
3. Open the Device Portal URL in your PC browser, go to Apps, choose your .appx and any dependency files, and click Install.

Device Portal is also handy for grabbing logs, screenshots, and managing installed apps remotely.

Where to get legitimate app packages

Now that the Store is down, sourcing packages is the real challenge. Stick to legitimate sources:

• Open-source projects: Many community developers publish their UWP/WP apps as downloadable APPX on their official project pages or code repositories. These are free and legal to install.
• Developer-provided downloads: Some developers, knowing the Store is gone, host their own apps’ packages directly. Use only the developer’s official site.
• Your own backups: If you previously backed up your purchased apps’ packages, you can redeploy them to your own device.

Common errors and fixes

“This app won’t install” / generic failure

Usually a missing dependency. Install the required framework package (often a Microsoft VCLibs or .NET Native runtime APPX) first, then retry.

Deployment fails with a signing/certificate error

The package may be unsigned or its trial certificate expired. Legitimate developer packages are signed; if yours isn’t, you’ll need developer mode fully enabled (not just sideload mode) to install unsigned packages, and even then some builds refuse. Prefer signed releases.

“Not enough storage”

Move apps to SD card under Settings > System > Storage, or clear temporary files. Low-RAM devices like the 520 are especially tight.

Device not detected by the PC

Unlock the phone screen, use a data-capable USB cable (not a charge-only cable), and confirm the phone shows under “Portable Devices” in Windows Device Manager.

What to sideload first

Once your pipeline works, these categories deliver the most value:

• A modern-ish browser shell — see our browser alternatives guide.
• Messaging alternatives — covered in our WhatsApp alternatives article.
• An email client that still authenticates — see best email clients for Windows Phone.
• Offline tools and media players — most of which are already pre-installed.

Understanding dependencies (the thing that trips everyone up)

The number-one reason a sideload fails is a missing dependency, so it’s worth understanding properly. Many UWP apps are built on shared framework packages — runtime libraries that Microsoft used to install silently through the Store. Common ones include the Microsoft Visual C++ Runtime (VCLibs) and the .NET Native Runtime packages. When you sideload an app that needs one of these and it isn’t already present, the install fails, often with an unhelpful generic error.

The fix is straightforward once you know it: install the dependency package first, then the app. Legitimate app distributions usually bundle the required dependency APPX files alongside the main package for exactly this reason. When you save an app for your library, save its dependencies too, in the same folder. A good habit is to keep a “dependencies” subfolder containing the common runtimes so any future sideload has them ready.

Architecture matters: ARM vs x86

Lumia phones use ARM processors, so you need the ARM build of any package and its dependencies — not the x86 or x64 versions that are meant for Intel-based tablets and PCs. If you download a dependency runtime, grab the ARM variant. Installing the wrong architecture is another silent cause of failures. When a package name includes “arm,” that’s the one your Lumia wants.

Keeping sideloaded apps organized

Once you’re sideloading regularly, a little organization saves hours later:

• Maintain a master folder on your PC: one subfolder per app, each containing the app package plus its dependencies and a short note on the source and version.
• Mirror it to a microSD card so you can install directly on the phone via File Explorer without a PC.
• Record where each package came from so you can fetch updates from the same legitimate source later.
• Test after every OS reset — a clean reset wipes sideloaded apps, and your organized library makes re-arming the phone a ten-minute job.

Frequently asked questions

Is sideloading legal?

Sideloading itself — installing app packages directly — is a built-in, supported feature of Windows Phone, and installing software you have the right to use is legal. What’s not legal or condoned is installing pirated or cracked applications. Stick to open-source apps, developer-provided packages, and your own backups.

Do I need to unlock my phone or root it to sideload?

No. Basic sideloading only requires enabling developer/sideload mode in Settings. You don’t need to unlock the bootloader or root the device for normal app installation. Those deeper modifications are only for custom firmware and full file-system access.

Why does my app install but then crash on launch?

Usually a missing or wrong-architecture dependency, or an app that relied on a Microsoft service that’s now offline. Reinstall the correct ARM dependency first; if it still crashes, the app may simply depend on a dead backend and can’t be fixed by sideloading.

Can I sideload apps without a PC?

Yes — on Windows 10 Mobile, once developer mode is on, you can tap an .appx/.appxbundle file in the built-in File Explorer to install it. Keep your packages on the device or an SD card and you never need a computer for routine installs.

Final thoughts

Sideloading is the single most important skill for keeping a Lumia useful in 2026. The Store may be gone, but the platform’s developer tooling never required it — and that’s the loophole that keeps these devices alive. Set up developer mode once, build a backed-up library of your legitimate packages, and you’ll never be at the Store’s mercy again. Start by enabling For developers mode right now, then come back and try Method 1 with a single open-source app to confirm your pipeline works.