14 DAY TRIAL // UPDATE: Microsoft has fixed the issue in the Mail and Calendar app with a new version. You need to update to 16006.11001.20083.0 to resolve the bug. Original story below.
It’s not a secret that it’s all just a matter of time until Windows phones go dark once and for all, but for the time being, the platform is still in maintenance mode and Microsoft has no other option than to make sure everything’s running smoothly.
But as it turns out, the software giant has disappointed its mobile users one more time, as an update to the Mail and Calendar apps on Windows 10 Mobile introduced a bug causing them to crash at launch.
And while you may be tempted to believe that only a few people still use Windows phones these days, it looks like there are a lot of them, so the bug is impacting more than just a handful of devices.
The Reg spotted a Microsoft Community discussion with more than 22 pages of complaints posted since November 7 when the issue was introduced by the update to Mail and Calendar version 16006.11001.20083.0.
“Mail and Calendar no longer starts. After a short flash screen the app crashed back to the main screen. Tried restart and soft reset. App got updated today 07-11-2018. This morning before the update it worked fine,” topic starter A. User explains in their post.
All models affected, no workaround available
Right now, it looks like the glitch hits pretty much any device, regardless of model, and I’ve seen reports of both old and new Lumia phones being affected, including the former flagship Lumia 950.
It goes without saying that Microsoft hasn’t provided any statement, though there’s a chance the company is already investigating these reports.
However, given Microsoft is already struggling to leave Windows 10 Mobile behind and the team probably counts just a few engineers still working on the platform, it could take a while until a fix is released.
In the meantime, those still running Windows 10 Mobile should consider a switch to Android or iOS because right now, this is pretty much the only way to go. No workaround has been found to correct the issue until a fix lands.