Slashdot Mirror

← Back to Stories (view on slashdot.org)

Microsoft Accidentally Released Internal Windows 10 Development Builds (theverge.com)

Posted by BeauHD on from the whoopsie-daisy dept.

Microsoft is apologizing for mistakenly releasing some confidential and internal Windows 10 builds to the public. "Builds from some of our internal branches were accidentally released for PC and Mobile," reveals Dona Sarkar, Microsoft's head of its Windows Insiders program. "This happened because an inadvertent deployment to the engineering system that controls which builds / which rings to push out to insiders." The Verge reports: 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. Worryingly, the accidental mobile build even reached retail devices outside of Microsoft's Windows Insiders testing. If Windows 10 testers installed the mobile build it forced phones into a reboot loop and bricked the device. Testers will have to recover and wipe the device using the Windows Device Recovery Tool. Windows 10 testers that installed the PC build, an internal Edge branch, will have to wait for Microsoft to publish a newer build or roll back using the recovery option in Windows 10 settings.

7 of 76 comments (clear)

  1. "Bricked" - you keep using that word... by davecotter · · Score: 2

    I don't think it means what you think it means...

    1. Re:"Bricked" - you keep using that word... by Khyber · · Score: 2

      That you don't know about something as basic as JTAG means you have zero credibility here to talk about anything.

      That's my 29 years of experience (out of almost 35 years of life, now) with computers talking, CHILD.

      --
      Still waiting on Serviscope_minor to wake up to fucking reality and realize that Jessica Price isn't going to fuck him.
  2. The build bricks the devices? by Opportunist · · Score: 5, Funny

    Gee, if you didn't tell us it wasn't intentional, we probably wouldn't have been able to distinguish it from any other update.

    --
    We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
  3. Well, that explains it by roc97007 · · Score: 5, Funny

    I must have been using an accidentally released internal build all these years.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.
  4. Debug Symbols? by bill_mcgonigle · · Score: 5, Interesting

    Did the builds have debug symbols? That would be a goldmine for reverse-engineers.

    --
    My God, it's Full of Source!
    OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
    1. Re:Debug Symbols? by Anonymous Coward · · Score: 3, Informative

      You can get Public symbols for most builds via http from Microsoft. These contain enough information to get you a stack trace but not local variables or source code file/line index information. Consult the Debugging Tools for Windows documentation if you want the nitty-gritty details.

  5. Re:Microsoft is evil by roc97007 · · Score: 2

    Well, it's great for the developers. They get instant feedback from the user community on new releases.

    Ok, most of that feedback is unprintable, but still, it is feedback, of a sort.

    --
    Oliver's law of assumed responsibility: If you're seen fixing it, you will be blamed for breaking it.