Windows Insider Dev Channel Moves to New Branch

Microsoft released a new Windows 10 Insider Preview build to the Dev channel with no new features. But there is one oddity worth noting.

“Starting with today’s build, Windows Insiders will notice that the name of the branch we are releasing builds from has changed to FE_RELEASE,” the firm notes. “Just like we did back in May when we released builds from the MN_RELEASE branch, we are practicing our ability to change which branch flight builds from.”

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.

Ok, that’s nonsensical. I think what they’re trying to say is that Microsoft is “practicing its ability to change the branch that builds flight from.” Which is still a bit tough grammatically, even when you get past the terrible “flighting” language that Microsoft uses to describe its Windows build process. Microsoft simply testing its ability to change the branch from which builds are delivered. And we’re the guinea pigs!

But I digress.

Because of this change, Insider will notice some undesirable regressions compared to previous Dev channel builds: “Some features like the updated emoji picker, redesigned touch keyboard, voice typing, theme-aware splash screens, and others have been removed temporarily.” Microsoft says it will try to bring back these features “in the future.”

As was the case with Dev channel builds before, builds from the FE_RELEASE branch are not matched to a specific Windows 10 release, Microsoft adds.

 

Share post

Please check our Community Guidelines before commenting

Conversation 4 comments

  • dmitryko

    30 October, 2020 - 6:37 am

    <p><em>Microsoft simply testing its ability to change the branch from which builds are delivered…</em></p><p><em>builds from the FE_RELEASE branch are not matched to a specific Windows 10 release</em></p><p><br></p><p>Microsoft nonsense. They just cancelled 21H1 Iron, just like they cancelled 20H2 Manganese previously. <span style="color: rgb(0, 0, 0);">There were significant changes in the Insider SDK/WDK for each of these (non-)releases – why bother with API versions, magic numbers and codenames if they always intended to skip these releases?</span></p><p><br></p><p><span style="color: rgb(0, 0, 0);">I suppose they just didn't have the resources to test the new features because of the pandemic crisis. The quality of recent releases starting from 20H1 has decreased considerably, even though there were much smaller changes – and if they won't get their act together, I predict that Cobalt 21H2 will suffer the same fate. They simply need to reinstate their specialist team of beta testes, which was dismised in 2014 and replaced by Insider Preview testing.</span></p>

  • hlbuck

    30 October, 2020 - 10:25 am

    <p>Would this enable someone on the Dev branch to hop back to the Beta branch and eventually to Release (leaving the Insider Program), once 21H1 is released?</p>

    • dmitryko

      02 November, 2020 - 8:10 am

      <p>You can only leave the Dev Channel (previously Fast Ring) when your Dev Channel branch moves to the Beta Channel (previously Slow Ring) – but since there will be no 21H1 release, the Iron branch won't actually move to the Beta Channel.</p><p><br></p><p><span style="background-color: rgb(255, 255, 255);">If you want to leave the Dev channel immediately, the only option is clean install, since y</span>ou cannot repair-install a Beta or a Release over a Dev build. </p><p><a href="https://docs.microsoft.com/en-us/windows-insider/flighting&quot; target="_blank" style="background-color: rgb(255, 255, 255);">https://docs.microsoft.com/en-us/windows-insider/flighting</a></p><p><br></p&gt;

      • hlbuck

        02 November, 2020 - 8:08 pm

        <blockquote><em><a href="#590216">In reply to dmitryko:</a></em></blockquote><p>got it, thanks. I've been putting off doing that because I have dozens and dozens of Win32 apps that I'd have to reinstall. Oh well!</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