Microsoft explains accidental release of internal Windows 10 builds for PC and Mobile

Microsoft accidently pushed a number of internal Windows 10 builds to Insiders last night, causing a plethora of problems for users. Today the company explains what happened, and how to fix your device if you were affected.

Microsoft's attempt at releasing new Insider Preview builds yesterday was thwarted at the last minute by an error which caused several internal, development builds of Windows 10 to be released in all the Insider Program rings. On PC, build 16212 from the rs_edge_case branch was released, and on Mobile, build 16212 from the rs_iot, rs_xbox and rs_devices branches were released.

These branches are not usually for the public, and in this case the Mobile build that was pushed actually caused a reboot loop when attempting to install it. If you're already stuck in this reboot loop, Microsoft says the only way to fix this issue is to restore your phone with the Windows Device Recovery Tool.

If you received this build (from RS_IoT) on Mobile: This build will not install on your device. If you installed this build, your device will be stuck in a reboot loop and the only way to recover is to use the Windows Device Recovery Tool and re-flash. After re-flashing, you can join the Windows Insider Program again on your device and choose your ring and be back on the right update path.

from Windows Central - News, Forums, Reviews, Help for Windows Phone http://ift.tt/2rM5WTM
via IFTTT