14 DAY TRIAL // Just like the PC sibling, Windows 10 Mobile Redstone build 14295 comes with several bug fixes and known issues, so those who are running the preview on their smartphones should have a look at this change log in order to know exactly what to expect when updating.
Without a doubt, since it’s a preview build of the Redstone update coming later this year, it’s kind of obvious that bugs continue to exist, but what’s also important to know is that you could come across issues that aren’t necessary part of this change log. This is why being an insider is so important, as the feedback you send to Microsoft can help the company diagnose problems and fix them in the following releases.
One of the bug fixes included in this new build concerns languages and keyboards that previously failed to download. Microsoft says everything should now work correctly, but there’s still an issue where the reboot option doesn’t show up after installing a new language or keyboard. As a result, make sure you manually restart the device when the process completes.
Restoring should now complete successfully
A second important bug fix is related to the restore system that previously failed to work correctly in build 14291, and Microsoft says that no matter if you reset the phone or not, restoring should run smoothly.
“We fixed the issue where if you reset your phone on Build 14291 and restore your phone from a backup, restore will fail to install apps from your backup’s apps list leaving blank grey titles on Start. You should be able to reset your phone on this build, do a restore from a backup, and have your apps installed and restored appropriately,” Gabe Aul, head of the Windows Insider program, explained.
As far as the known issues are concerned, the Band synchronization issue continues, so you might not be able to use the smartwatch with this build unless you reset the phone or re-pair the Band.
Furthermore, if you upgrade from an older build, you might not be able to connect to a Miracast receiver, and currently, the team is still working on a fix. No workaround is available at the moment.
The full change log can be found below, and make sure that you submit any other bug that you come across to the company to get a fix as soon as possible.