WPHub is a forum for Windows-powered phones and PDAs. We talk about Windows Mobile, Windows Phone and Windows 10 Mobile: apps, firmware, recovery, development, and ways to keep these devices useful today.

• Windows Mobile 5 / 6 / 6.1 / 6.5;
• Windows Phone 7 / 7.5 / 7.8;
• Windows Phone 8 / 8.1;
• Windows 10 Mobile.

Yes. For music, the camera, old games, offline apps, or just collecting old hardware, they can still be perfectly usable.

Online stuff is the difficult part. Old browsers struggle with modern websites, many APIs and servers are gone, and the official stores are either shut down or unreliable. Calls and mobile data also depend on the bands and network generations still supported by your carrier.

Windows Mobile is Microsoft's older Windows CE-based mobile platform. The best-known versions are 5, 6, 6.1 and 6.5.

This is the stylus, CAB-file, Windows CE/Win32 and .NET Compact Framework era.

They are two different platforms. Windows Phone was not a normal upgrade from Windows Mobile: Microsoft replaced the UI, app model and a large part of the platform itself.

So a Windows Mobile application cannot simply be installed on Windows Phone.

Yes. If you have a compatible CAB file or PC installer, you usually do not need an official store at all.

Windows Phone 7 was the first generation of Microsoft's redesigned phone platform, with Metro and Live Tiles. Under the hood it still used Windows CE; the move to Windows NT came with WP8.

• Windows Phone 7;
• Windows Phone 7.5 (Mango);
• Windows Phone 7.8.

Yes, mostly as an offline device. The Marketplace has been gone for years, and old Microsoft or third-party services often fail at sign-in or simply cannot reach their servers anymore.

Installing apps outside the Marketplace is only practical on devices with a working unlock, developer-unlock or custom-ROM method.

The biggest change was the kernel. WP7 used Windows CE, while WP8 moved to Windows NT and shared much more of its foundation with desktop Windows 8.

Microsoft did not cut old apps off overnight, though. Many WP7/7.5 apps still ran on WP8. The reverse was different: an app written only for WP8 would not run on WP7.

Quite a lot. The obvious additions were Action Center, quick toggles, Start-screen backgrounds through transparent tiles, Internet Explorer 11, and Cortana in supported regions.

No. Microsoft shut down the Windows Phone 8.1 Store on December 16, 2019.

You can no longer use it normally to download new apps or reinstall old purchases. Apps already on the phone may keep working as long as they do not depend on a retired server or service.

Yes, but not through a normal consumer workflow anymore. Microsoft once provided Application Deployment through the SDK; today people usually rely on device-unlock methods and third-party tools for XAP/APPX deployment.

Windows 10 Mobile was the phone edition of Windows 10. It brought UWP apps, a shared Windows 10 foundation and, on selected devices, Continuum.

The final release was Windows 10 Mobile 1709. Microsoft ended support on December 10, 2019.

Officially, only phones approved by Microsoft had an upgrade path. Plenty of WP8.1 devices never received an official route to W10M.

Unofficial methods exist for some unsupported Lumia models, but they are very device-specific and depend on partitions, firmware and drivers.

Do not rely on the built-in Store for everyday use anymore. It kept working in some form for years after W10M support ended, but around February 2025 users started reporting widespread page-loading and installation errors.

In 2026 the situation is inconsistent. Some of it depends on the Store client version, the account and even the page you are trying to open. Older clients such as the 11805 branch still work partially for some users.

No. The modern Edge WebView2 Runtime was never released for Windows 10 Mobile.

That does not mean WebView2 is the single reason the Store stopped working. The Store went through several clients and relied on a mix of web and server components over the years.

Because the app on your phone and the service behind it are two separate things. The server may have been shut down, the API changed, authentication replaced, or certificates updated.

The app can be exactly the same as before and still have nothing useful left to connect to.

Yes. W10M has Developer Mode and app deployment, but a particular APPX/XAP may still need dependencies, a certificate or extra permissions.

Older XAP packages, system apps and some mods may need Interop Unlock. And a WP8.1 package is not guaranteed to work on W10M just because it installs.

Yes. The community still maintains app archives and third-party catalogs for WP8.1 and W10M.

Just do not install random packages blindly. Check where the file came from, who built it and what dependencies it needs. If a checksum is available, even better.

Because IE Mobile and the old Edge engine have not received modern web-platform updates in years. Current websites expect newer JavaScript APIs, authentication methods, encryption, codecs and CSS features that those browsers simply do not have.

That is why a simple site may still work while a modern web app shows a blank page, breaks during sign-in or renders badly.

Most of the time, something changed on the server rather than on the phone. The service may have changed its API, certificates or sign-in flow, or dropped Windows Phone support completely.

In simple terms, firmware is the phone's system images: the OS itself, boot partitions, drivers and other components tied to a particular model.

Usually, no. Two Lumia phones that look almost identical may still use different modems, displays, SoCs, partition layouts and drivers.

The more details you provide, the easier it is for someone to help:

• exact model and RM number, if known;
• Windows version and build number;
• what you were doing right before it failed;
• what appears on screen and whether the phone vibrates;
• whether it reacts to charging;
• how it shows up on a PC;
• what recovery tools or images you have already tried.

Use a clear title and put the important details in the first post. For example:

Model: Lumia 950

OS: Windows 10 Mobile 1709

Problem: app does not launch

Error: exact message or code

Already tried: list what you have done

Because the same Windows version can run on phones with very different bootloaders, modems, displays and firmware. Something safe on one Lumia can brick another.

Please post it in the thread. Include the app/tool versions, required files and a short list of the steps that fixed it.

This matters a lot for old Windows phones: links and guides disappear over time, and your post may save someone else an evening later.

Absolutely. Good guides are one of the most useful things a legacy-device forum can keep.

Include the phone model, OS version, requirements, where the files came from, any risks, and the steps in order. File checksums are useful too when you have them.