Microsoft Accidentally Delivers Insider Builds to PCs, Phones (Updated)

UPDATE: Microsoft has now publicly addressed this issue. See the addition at the end of the post. –Paul

If you’re a Windows Insider, be careful not to install any new builds today: An internal mishap at Microsoft has triggered an errant release.

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday — and get free copies of Paul Thurrott's Windows 11 and Windows 10 Field Guides (normally $9.99) as a special welcome gift!

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Dona Sarkar has addressed this issue on Twitter:

Windows Insiders: pls do not install any builds being offered til you hear from us with a blog post. If you have installed, reset with WDRT [Windows Device Recovery Tool].

It’s not clear what happened yet, but it appears that Windows Insiders with Windows phones were offered an internal build of the system that is not actually designed for phone. This build was pushed to all Windows Insider rings—Fast, Slow, and Release Preview—and apparently even went out to the production channel as well.

The enthusiast community reacted with the usual grace.

Holy fuck the boot loop build is being pushed to PRODUCTION on Mobile too. NORMAL PEOPLE are receiving this broken build.

Zack, Zack. Normal people don’t use Windows phones. Come on.

Or, as Rafael noted:

LIVE at Microsoft

The bigger issue, of course, is that build 16203 went out to some PCs as well. And that is not OK. Normal people do use PCs.

Just kidding. But you get the idea: Be careful.


In a post to the Windows Experience Blog last night, Microsoft’s Dona Sarkar addressed what she called the “unintentional” release of insider builds.

“Builds from some of our internal branches were accidentally released for PC and Mobile,” she explains. “This happened because an inadvertent deployment to the engineering system that controls which builds/which rings to push out to insiders. The team was quick to revert the deployment and put blocks in place to stop these builds from going out to more people. Our analysis shows only a small portion of folks got these builds.”

Of course, if you did install one of your builds, you’re going to want to know what to do.

On PC, you should be OK: The unintentional build was an internal build, and it may be less stable than previous builds, but—who knows—it may also reveal some new Fall Creators Update features. On phone, you’re in the trouble (for more than the usual reasons), and you will need to reset your device with the WDRT. Ms. Sarkar’s post explains this.

Regardless, there will be no more (official) Windows 10 Insider Preview builds this week, Microsoft says.


Tagged with

Share post

Please check our Community Guidelines before commenting

Conversation 14 comments

  • lprell

    01 June, 2017 - 6:36 pm

    <p>And that folks is why We all want Windows Server Insiders… LOL</p>

  • jimchamplin

    Premium Member
    01 June, 2017 - 7:22 pm

    <p>I wonder if this was one of Winston's pranks…</p><p></p&gt;

  • Dan1986ist

    Premium Member
    01 June, 2017 - 7:23 pm

    <p>Thank goodness for the option to pause downloading and installation of Insider builds for upto seven days. </p>

  • skane2600

    01 June, 2017 - 7:46 pm

    <p>It's "One Windows" so surely there can't be any problem. </p>

    • BoItmanLives

      01 June, 2017 - 9:56 pm

      <blockquote><a href="#121602"><em>In reply to skane2600:</em></a></blockquote><p>Notice how Xbox One isn't affected. Xbox Division keeps the "one windows" nonsense far away from it's pristine, proprietary ecosystem.</p>

  • bbold

    02 June, 2017 - 12:22 am

    <p>I happily use an Idol 4S on fast ring and no new updates, but thanks for the heads up! </p><p>I'm also HAPPILY abnormal 😀 *F* Normal!</p>

  • Dan

    02 June, 2017 - 1:13 am

    <p>Best article ever.</p>

  • napkatz

    02 June, 2017 - 8:50 am

    <p>This stunk for me. I turned off my Lumia 650 last night to avoid getting the build, but apparently it auto-started when I plugged it in to charge. Installed the tainted build, and not there's the whole recovery process/setup process to go through. I'm pretty sure I was on "Release Preview", the least risky branch.</p>

  • Narg

    02 June, 2017 - 1:35 pm

    <p>"Zack, Zack. Normal people don’t use Windows phones. Come on." Are you assuming Insiders are normal??? ;)</p>

  • Waethorn

    02 June, 2017 - 2:24 pm

    <p>Another day, another laundry list of Microsoft f* ups that keep my computer service business running.</p>

  • JaviAl

    Premium Member
    05 June, 2017 - 11:01 am

    <p>My Windows Server 2016 is trying to update to Windows 10 Creator's Update.</p>

Windows Intelligence In Your Inbox

Sign up for our new free newsletter to get three time-saving tips each Friday

"*" indicates required fields

This field is for validation purposes and should be left unchanged.

Thurrott © 2024 Thurrott LLC