Microsoft says this build release was a mistake
Dona Sarkar already published a lengthy post on Microsoft’s official Windows Insider blog explaining that build 16212 is actually an internal branch build that was accidentally released due to a system error. The good news is that the Insider Team was quick to revert the deployment and blocked this build from going out to more people. One phone has just rebooted, but is stuck in an endless reboot loop: it displays the colored flag Microsoft logo for a short time, then reboots, … The second phone is asking for the required reboot to start the update process but I I’m hesitant to push the “Restart now” button after the experience with the first phone. Anyone else seeing this strange build and behavior?
How to fix the bugs caused by Windows 10 build 16212
If you already installed build 16212 on your PC, you now have two options:
How to fix endless reboot loops on Windows 10 Mobile
Build 16212 will send your phone into endless reboot loops. The only way to recover is to use the Windows Device Recovery Tool and re-flash. You can then join the Windows Insider Program again. If your device has downloaded this build but has not yet installed it, simply reset your phone via Settings > System > About. Don’t forget to do a backup first via Settings > Update & security > Backup. RELATED STORIES YOU NEED TO CHECK OUT:
Project NEON for Microsoft Photos comes to Windows 10 Insiders Windows 10 phones officially supported by the Insider Program
Name *
Email *
Commenting as . Not you?
Save information for future comments
Comment
Δ
