Microsoft mistakenly releases broken Windows 10 build

Francis Harris
June 3, 2017

Windows 10 Mobile users are potentially in for bigger headaches. If Windows 10 testers installed the mobile build it forced phones into a reboot loop and bricked the device. Also, it is said that the speaker may have initially been created to be a part of the Windows 10 PC's ecosystem, but it has since been developed in a way that it can function independently as well.

Non Windows-Insiders may have also seen the unintentional build, but Dona Sarkar assures these users that the build in question will not install on devices which are not joined to the Windows Insider Program.

Those Insiders, who received the internal build on PC, note that they include issues which impact the usability of the PC.

After knowing about the accidental release, Microsoft quickly reverted the issue and placed blocks to make sure that the builds don't reach more users. Anyone on the Creators Update or newer will find these builds waiting for them - including those in the Slow and Release Preview rings - and your phone might even try to install them automatically if you're not paying attention.


For anyone who isn't familiar with the Windows Insider Program: It's an opt-in program that offers early access to upcoming versions of Windows 10, with the caveat being that these pre-release builds aren't as stable as official updates.

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.

The normal tease was tweeted by Windows Insider Chief Dona Sarkar and we knew at that point it was time to get ready for the first new testing builds in over two weeks. It was also confirmed that the new feature does not need to connect to a Windows 10 PC tin order to experience a complete intelligent speaker. As per Microsoft, 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. 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.

"We apologize for this inconvenience and thank you for being a Windows Insider!".

Other reports by TheDigitalNewspaper

Discuss This Article

FOLLOW OUR NEWSPAPER