Installing Software on Windows Mobile: Full Guide

Installing software on the Windows Mobile platform depends entirely on which version you are using: the classic Windows Mobile 6.x (Pocket PC) line, the later Windows Phone 7/8/10, or the modern Windows 10/11 on ARM devices. This guide covers all three, explaining the official stores, sideloading options, and the security considerations for each, so you can get the apps you need without bricking your device.

Background: The Three Eras of Windows Mobile

Microsoft’s mobile operating systems have gone through several distinct phases, each with a completely different way of installing software. Understanding which one you have is the first step.

Windows Mobile 6.x (2007-2010): The classic Pocket PC and Smartphone platform. It ran on devices from HTC, Samsung, and others. Software came as .cab files or via desktop sync with ActiveSync or Windows Mobile Device Center.
Windows Phone 7/8/10 (2010-2017): A complete reboot. It was a closed platform with a single official app store (the Windows Phone Store). Sideloading was heavily restricted, especially on Windows Phone 7.
Windows 10/11 on ARM (2017-present): Not a phone OS in the traditional sense, but full Windows running on ARM processors (like the Surface Pro X or some tablets). It can install software like a desktop PC, using .exe, .msi, or the Microsoft Store.

Installing on Windows Mobile 6.x (Classic)

If you have an older device, you have the most freedom but also the most risk. Software is usually distributed as a .cab file, which is an installer archive. You can install it directly on the device or via a desktop connection.

Direct installation: Copy the .cab file to your device’s storage (via USB, SD card, or email). Use the file explorer on the device to navigate to the file and tap it. Follow the on-screen prompts.
Via ActiveSync (Windows XP) or Windows Mobile Device Center (Windows Vista/7): Connect the device to your PC. In the sync software, go to “Programs and Services” or “File Management” and add the .cab file to the device. Then run it from the device.
Desktop installers: Some software came as a .exe that ran on your PC and then pushed the app to the device via the sync connection. These often installed to a default location and created a shortcut in the Start menu.

Common problem: Many old .cab files are signed for specific processors (ARM, MIPS, SH3). Installing the wrong one will fail. Always check the device’s processor type (Settings > System > About) and download the correct version.

Installing on Windows Phone 7, 8, and 10

Windows Phone was a departure. The only official way to install apps was through the Store app on your phone. The Store was the sole source, and it was curated by Microsoft. There was no “sideloading” in the traditional sense for consumers.

Windows Phone 7: No sideloading at all for the public. Developers could unlock a limited number of devices for testing, but that required a developer account and a special tool.
Windows Phone 8: Introduced “sideloading” for business and developer scenarios. You could deploy apps from a PC using the Windows Phone Developer Tool, but only if the phone was developer-unlocked (which required a developer account) or if it was a company-managed device.
Windows Phone 10: Allowed sideloading of apps from the web, but only if you enabled the “Sideload apps” option in Settings > Update & security > For developers. You could then download an .appx or .xap file and install it. However, the files had to be signed by a trusted certificate, which limited practical use.

Reality check: The Windows Phone Store was shut down in 2019. If you have a Windows Phone 8 or 10 device, you can no longer install apps from the official store. Sideloading is the only option, and it’s now extremely limited because the servers that signed the certificates are gone. In practice, most Windows Phones are now only useful for calls, texts, and basic web browsing.

Installing on Windows 10/11 on ARM

Modern Windows on ARM devices (like the Surface Pro X or the new ThinkPad X13s) run the full Windows operating system. You can install software just like on a regular PC.

Microsoft Store: The simplest method. Open the Store app, search for an app, and click “Get” or “Install.” The Store will handle the installation and updates.
Desktop apps (.exe, .msi): You can download and run installers from the web. The installer will run like on any Windows PC. However, you need to be aware of the architecture:

ARM64 native apps: These run at full speed. They are increasingly common, especially for major apps like Chrome, Firefox, and Office.
x86 (32-bit) apps: These run in emulation. They work, but may be slower and use more battery.
x64 (64-bit) apps: These also run in emulation on ARM64, but only on newer versions of Windows 11. On Windows 10 ARM, x64 emulation was not available, so you could only run 32-bit x86 apps.

Portable apps: Some software is distributed as a .zip file that you extract and run without an installer. This works fine on ARM as long as the executable architecture is supported.

How to check architecture: In Settings > System > About, you’ll see “System type” which tells you if you’re running a 64-bit or 32-bit OS. For ARM devices, it will say “ARM-based processor.” If you’re unsure about an app’s compatibility, check the developer’s website or the Store listing.

Choosing the Right Installation Method

The best method depends on your device and what you’re trying to install. Here’s a quick decision guide:

For classic Windows Mobile 6.x: Use direct .cab installation for small apps. Use desktop sync for larger apps or if you need to manage multiple devices. Always verify the processor architecture.
For Windows Phone 8/10: If you have a developer-unlocked device, you can sideload .appx files. For everyone else, the Store is (was) the only option. Since the Store is dead, you’re limited to sideloading with a custom certificate, which is a complex process.
For Windows 10/11 ARM: Use the Microsoft Store for convenience and safety. Use direct .exe installers for software not in the Store, but check the architecture first. For portable apps, just extract and run.

Common Problems and Troubleshooting

You’ll likely run into issues, especially with older devices. Here are the most common ones and how to fix them.

“The file is not a valid Windows Mobile application” (6.x): The .cab is for the wrong processor. Download the ARM version (most common).
Installation fails on Windows Phone 8/10: The certificate is not trusted. You need to install the developer certificate on the phone first. This is a multi-step process that requires a PC and the Windows Phone Developer Tool.
App won’t run on Windows on ARM: The app is x64 and you’re on Windows 10 ARM (which doesn’t support x64 emulation). Upgrade to Windows 11 ARM or find an ARM64 or x86 version.
ActiveSync won’t connect (6.x): On Windows 10/11, ActiveSync and Windows Mobile Device Center are not supported. You’ll need to use a virtual machine with Windows XP or Vista, or use a third-party tool like Windows Mobile Device Center for Windows 8 (which sometimes works).
Storage space is low: On old devices, internal storage was tiny (often 256MB or less). Install to an SD card if possible. In the .cab installer, it will ask for a location. Choose “Storage Card.”

Security and Safety Considerations

Installing software from any source other than the official store carries risks. Here’s what you need to know.

Malware: Old Windows Mobile devices have no modern security updates. Installing a .cab from an untrusted site could compromise your data. Only install from well-known sources like XDA Developers or the developer’s official site.
Certificate trust: On Windows Phone and Windows 10 ARM, sideloaded apps must be signed. If you install a certificate from an unknown source, you’re trusting that source with full access to your device. Only do this if you understand the risk.
Data loss: Some installers may overwrite system files. Always back up your data before installing anything, especially on Windows Mobile 6.x.
Bricking: In rare cases, a bad install can make the device unusable. This is more common with custom ROMs or system tweaks. Stick to normal apps to avoid this.

Alternatives to Native Installation

If you’re having trouble installing software, or if the software you need isn’t available, consider these alternatives.

Web apps: Many services (email, calendar, notes) work perfectly in the browser. On Windows Phone, the browser is your best friend.
Remote desktop: Use a remote desktop client (like Microsoft Remote Desktop) to access a full PC from your mobile device. This works on all Windows Mobile versions, though the experience varies.
Virtual machines: For Windows Mobile 6.x, you can run the entire OS in an emulator on your PC. This is a good way to test software without risking your device.
Custom ROMs: For some devices, you can replace the OS with a newer version (e.g., Android or a custom Windows Mobile build). This is advanced and risky, but can breathe new life into old hardware.

Frequently Asked Questions

Can I install Android apps on Windows Phone?

No. Windows Phone 8.1 and 10 had a feature called “Project Astoria” that allowed some Android apps to run, but it was never released to the public. There is no practical way to run Android apps on a Windows Phone.

How do I install .cab files on Windows Phone?

Windows Phone does not use .cab files. It uses .xap (Windows Phone 8) or .appx (Windows Phone 10) files. You can sideload these if your phone is developer-unlocked, but it’s a complex process that requires a PC and specific tools.

Is it safe to sideload apps on Windows 10 ARM?

It’s as safe as installing software on any PC. You should only download from reputable sources. The risk is higher than the Microsoft Store because the Store checks apps for malware. But if you’re careful, it’s generally fine.

Why can’t I install apps on my Windows Phone 8.1?

The Windows Phone Store is no longer available. Microsoft shut it down in 2019. You can only sideload apps if you have the necessary developer tools and the phone is unlocked. For most users, this means the phone is limited to its built-in apps.

Can I use a Windows Mobile 6.x device in 2024?

Yes, but with limitations. You can still make calls, send texts, and use basic apps. However, most modern websites won’t render properly, and email services like Gmail may require OAuth2, which old devices don’t support. You can use it as a music player or a simple organizer.

What is the difference between Windows Mobile and Windows Phone?

Windows Mobile (6.x and earlier) was a mobile version of the classic Windows desktop. It had a start menu and could run many desktop-like apps. Windows Phone (7-10) was a completely new OS designed for touchscreens, with a tile-based interface and a strict app store policy. They are not compatible.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →