Microsoft today pushed Windows 10 Mobile Build 15025 to insiders in Fast Ring. As expected this build again doesn’t bring anything new in terms of new features and changes. It has many fixes and improvements however.
It fixes the issue where some Alcatel Idol 4s devices were not able to receive Build 15204 last week. It also fixes some Continuum issues being faced with devices like Lumia 950 and HP elite X3.
The Build also has its share of known issues that you may like to read before installing this build. As a Fast Ring build it may have even more hidden bugs and issues.
Windows 10 Mobile Build 15025 Changelog:
- We fixed the targeting issue that caused some variants of the Alcatel IDOL 4S to not receive Build 15204 last week. All variants of the Alcatel IDOL 4S should receive Build 15205.
- FYI: We fixed the issue where supported Windows 10 Mobile devices were showing the update to the Windows 10 Anniversary Update as “not yet available” in the Upgrade Advisor app.
- We fixed an issue where Continuum would stop working when HP Elite X3 case is closed.
- We fixed an issue where Continuum would hang or render incorrectly after disconnecting on devices like the Lumia 950.
- We fixed an issue with Microsoft Edge where you might get into a bad state after opening a new Microsoft Edge windows and screen off with the JIT process suspended.
- We fixed an issue with where the device screen might stay black when disconnecting from a Continuum dock after screen has timed out normally.
- We fixed an issue with backup and restore which impacts users with slower network connection.
- We fixed an issue around Microsoft Edge reliability.
Windows 10 Mobile Build 15025 Known issues:
- A small percentage of devices may experience text message backup loss related to backup and recovery of the messaging database.
- For Insiders who have upgraded from a prior 150xx build to this build, the “Add Bluetooth or other devices” Settings page and the Connect UX page may fail to open.
- The copyright date is incorrect under Settings > System > About. It shows as 2016 when it should be 2017. Thanks to the Windows Insiders that reported this!
- Insiders may experience random shutdowns on some devices.