Windows Insider Switches to Channels Today

Posted on June 29, 2020 by Paul Thurrott in Windows 10 with 9 Comments

Two weeks after it announced the change, Microsoft is switching the Windows Insider program from rings to channels today.

“Channels have arrived,” the Windows Insider account tweeted today. “Expect the changes to land in your Windows Insider settings over the next few hours.  Remember, we’ve done the mapping for you, so there’s no direct change you need to make.”

As I wrote at the time of the original announcement, this change is largely symbolic, with Microsoft claiming that it’s moving to a “quality-based” build model. But it’s really just a name change. The Fast ring is being renamed to the Dev Channel without any other changes, the Slow ring is being renamed to the Beta channel without any other changes, and the Release Preview ring is being renamed to the Release Preview channel; here, there is one change, but it’s only for businesses: Microsoft will support businesses that deploy the Release Preview channel to some of their users.

I assume that today’s note means that we’ll see the channel language used in Windows Insider settings (Settings > Update & Security > Windows Insider Program).

Join the discussion!


Don't have a login but want to join the conversation? Become a Thurrott Premium or Basic User to participate

Comments (9)

9 responses to “Windows Insider Switches to Channels Today”

  1. red77star

    DOA. They should close Windows Insider program, hire professional QAs and have beta release for general public followed by final release like it should be.

  2. JH_Radio

    First Channel Daily? :)

  3. sentinel6671

    Put my Surface Pro 3 in the Beta Channel. I like what Paul said on Windows Weekly last week. The best thing an individual can do, if they want a voice in the process, is to participate.

  4. saint4eva

    Channels make much sense, and easier to relate with.

  5. ghostrider

    The 'Insider' program has failed time and again. The majority of Insiders, ie unpaid lackies, don't have the Q&A methodical testing skills - or time, or inclination required to do the necessary testing. Most get a new build and deploy it as a VM, have a quick look, and move on. Who has the spare time to deploy and re-deploy and test thoroughly new builds? They're not getting anything really from MS to make it even partially worth their time and effort.

    MS need to get their own internal team back up to spec. Stop expecting devs to do all the first pass testing - MS internal builds should be handed over to a dedicated team who have the tools to do the job. MS should also only ship finished builds when they're actually signed off by Q&A and are deemed stable. Keeping to a fixed release schedule is always going to mean bugs are released into the wild, so just ship when ready. If that means 6, 12 or 18 months between major releases, so be it.