• MS-DEFCON 1: Beware of Win10 build 16212

    Posted on June 1, 2017 at 18:49 CDT by • Comment in the Forums

    There’s a lot of confusion at the moment, but it looks like Microsoft released a “rogue” version of Windows to at least some Win10 PCs and many phones.

    The bad version is identified as 16212.1001.rs_iot.170531-1800

    You’re glad that you have automatic updating turned off, yes?

    The problem started appearing about an hour ago. Dona Sarkar, the head Windows Insider spokesperson, tweeted

    #WindowsInsiders: pls do not install any builds being offered til you hear from us with a blog post. If you have installed, reset with WDRT.

    The implication is that the problematic build is only going out to Windows Insiders – people who are actively beta testing new versions of Windows 10. Since the Windows Device Recovery Tool is only used for Windows phones (er, Mobile devices), there’s a secondary implication that the bad build is only going out to phones.

    Both of those implications appear to be false, at least in some cases.

    @tfwboredom tweeted less than an hour ago that he had a production (which is to say, non-Insider) x86 (which is to say, not mobile) machine that was being pushed build 16212.1001.rs_edge_case.170531-2234 (UUP-CTv2)

    It’s not clear what build 16212 does to PCs, but mobile devices are getting hit hard. Wayne Williams at Betanews reports:

    Build 16212 for Windows 10 Mobile has been sending phones into a loop.

    Until Microsoft gets its act together, you would be well advised to avoid Windows Update entirely.

    Accordingly, I’m moving us to MS-DEFCON 1: Current Microsoft patches are causing havoc. Don’t patch.

    If you’ve already installed 16212 on a phhave to wipe it out completely, using WDRT.

    If you’ve already installed 16212 on a PC, I’d sure like to hear from you! At this point, the only advice I can give is to bend way over and kiss your keester goodbye.

    UPDATE: Dona Sarkar advises that those outside of the Insider Program (which is to say, those not beta testing the next version of Windows) may see 16212, but they won’t be able to install it.

    We’re continuing to work on our build release situation. For non-Insiders, you might see the build being offered, but it will not install

    And now the final story  https://blogs.windows.com/windowsexperience/2017/06/01/note-unintentional-release-builds-today

    Windows Patches/Security , ,
DON'T MISS OUT!
Subscribe to the Free Newsletter
We promise not to spam you. Unsubscribe at any time.
Invalid email address

View the Forum

  • Recent Replies
  • My Replies
  • My Active Topics
  • New Posts in the Last day
  • Private Messages
  • Knowledge Base
  • How to use the Forums
  • All Forums

    • Recent Topics

    My Profile

    May 2025
    S M T W T F S
     123
    45678910
    11121314151617
    18192021222324
    25262728293031

    Remembering Woody

     

    Want to Advertise in the free newsletter? How about a gift subscription in honor of a birthday? Send an email to sb@askwoody.com to ask how.

    Mastodon profile for DefConPatch
    Mastodon profile for AskWoody

     

    Home • About • FAQ • Posts & Privacy • Forums • My Account
    Register • Free Newsletter • Plus Membership • Gift Certificates • MS-DEFCON Alerts

    Copyright ©2004-2025 by AskWoody Tech LLC. All Rights Reserved.