Microsoft explains yesterday’s broken Windows 10 build issue and how to fix it

Yesterday Microsoft pushed out a number of builds from their internal branches to both PC and mobile which, in the case of mobile, bricked a number of devices and was even offered (but not installed) to devices which were not on Insider rings.

Dona Sakar has now posted on the Windows Blog explaining the incident and also apologised to users.

She blamed “an inadvertent deployment to the engineering system that controls which builds/which rings to push out to insiders” and says only a small portion of the 2 million insiders received the builds.

For those affected on PC, who received RS_EDGE_CASE, she notes that users can either wait for the next build, which should come in more than a week, or roll back via Settings > Update & security > Recovery. Users have 10 days to roll back, as long as they did not use Disk Cleanup to remove old Windows installations.

Mobile users, who received  RS_IoT, an Internet Of Things build, are less lucky. Their devices are stuck in a reboot loop, and will need the Windows Device Recovery Tool to restore their devices.

If your installation is pending on mobile or PC (you see either a “Install” or “Restart now” button under Phone update) you will have to do a device reset via Settings > System > About (Do a backup via Settings > Update & security > Backup FIRST) and then check your Windows Insider Program settings to ensure you’re on the right ring.

Due to the incident, there will be no more builds this week, but we can expect the process to resume next week.

Have any of our readers been affected?