Microsoft accidentally releases test build of Windows 10 to Insiders

Kristi Paul
June 3, 2017

Surprisingly, the bad build also extended to some Windows phones that aren't registered in the Insider program, though it won't install unless you register as an Insider. The immediate result of the update was bricked PC/laptops and smartphone running on Windows 10. However, the company ended up accidentally releasing build 16212 to phones and 32-bit PCs instead.

As Dona Sarkar, head of the Windows Insider Program at Microsoft, explained: "If you are not a Windows Insider, your device may have seen one of these builds offered". For Windows Insiders who are concerned about stability and buggy behavior, be advised that you might be running a preview build that was not yet ready for testing.

By now many of you are already aware of the situation that occurred last night just as the Windows Insider team was about to release a Redstone 3 and Feature 2 build update for PC and Mobile devices respectively.

Microsoft says it quickly reverted the issue and put blocks in place to ensure these development builds didn't reach more people, but a "small portion" of Windows 10 users still received them. If we find any results that are different from before, we'll keep you updated. The fix involves using the Windows Device Recovery Tool and re-flashing your handset. "We will not be releasing new builds to any of the rings this week", Microsoft added.

"You have up to 10 days to roll-back and this will only work if you did not do Disk Cleanup to remove your previous Windows installation", she noted.

Microsoft's Dona Sarkar has confirmed in a blog post that they will not be releasing new builds for Windows 10 and Windows 10 Mobile this week.

Now, less than four hours later, new builds are showing up on Windows phones.

Windows 10 testers on PC, who installed the build, will now have to wait for Microsoft to push a newer build or rollback by using the recovery options available in the Settings menu on Windows 10. But you'd have to be daft to run an Insider build on a 16GB tablet too, so all is fair and all that. My monitoring of social media showed that quite a few users were unable to stop their own download/install processes with this incorrect build and now had mobile devices stuck in a boot loop.

Other reports by VideoGamingPros

Discuss This Article