Microsoft created its Windows Insider Program so enthusiastic users, developers, and IT admins could preview upcoming features and give feedback while software is still in development. The program made its debut in October 2014 with the Windows 10 technical preview, and it has run continuously ever since — giving participants early access to new capabilities across every Windows 10 and Windows 11 release through what are known as Insider Preview Builds.
That said, the program has changed dramatically in recent years. Earlier this year Microsoft carried out what it called its biggest overhaul ever, with the stated goal of making the Insider experience less confusing. Whether it fully succeeded is debatable, but one thing is certain: if you haven’t checked the Insider settings recently, the channel system you remember may no longer match what you’ll find. This guide covers the current state of the Windows Insider Program on Windows 11, and it’s split into two parts — one for individuals and one for IT administrators.
One important note up front: you must be running Windows 11 to participate. There is no longer an Insider program for Windows 10.
A warning before you join
Before you enroll, take a moment to think carefully about where you’ll install preview software. Preview builds are, by design, work in progress. The features they introduce may not work properly, may not work at all, or may behave differently than Microsoft documents. The operating system itself can become unstable, and applications running on top of it can crash or freeze. In the worst cases, a preview build can harm your system.
For that reason, Microsoft and experienced testers alike recommend against installing Insider preview builds on your primary PC. You’ll be far safer using a spare second or third machine, or by running Windows 11 inside a virtual machine and updating that sandboxed copy instead. Treat any preview build as experimental software, and keep a recent backup of anything important before you start testing.
How to join the Windows Insider Program
Enrolling is free and straightforward. Head to the Windows Insider Program page and click the Join Windows Insider button, then click Register now on the page that appears. You’ll need a Microsoft account to participate, and once you follow the on-screen instructions you’re officially part of the program.
Signing up only registers you, though. It doesn’t automatically put any of your computers onto preview builds. You’ll need to configure each PC individually, which also means you can choose to get Insider builds on some machines while leaving others on stable, public Windows. And you can even point different PCs at different Insider channels, so a spare testing rig can live in the Experimental channel while your work machine stays on Release Preview.
Configure a PC and choose a channel
To put a specific PC onto Insider builds, open its Settings app and navigate to Windows Insider Program > Get started, then follow the prompts. You may see a message telling you to link your Microsoft account to the Insider program — if so, just follow the simple instructions to connect them.
There’s one requirement you can’t skip: Microsoft requires that you allow your PC to send specific diagnostic data if you want to test Insider builds. To enable this, go to Settings > Privacy & security > Diagnostics & feedback and move the Send optional diagnostic data slider from Off to On. Once that’s done, return to Settings > Windows Update > Windows Insider Program and you’ll be able to make your channel and version choices.
The three Insider channels
When you reach the Windows Insider Program settings, you’ll be asked to pick one of three channels. Each serves a different audience, and Microsoft is explicit about the trade-offs involved.
- Experimental channel: This is where Microsoft first introduces new features and ideas, many of which have long lead times and may never actually ship. Microsoft says the channel is best for “tech enthusiasts” and warns that “you should expect some rough edges and variable stability in this channel.”
- Beta channel: If you want to see updates before the general public but prefer more reliability, this is the middle ground. It previews fixes and features that have been tested but aren’t quite ready for prime time. Microsoft describes it as being “for early adopters and IT professionals who want to see what we plan to ship in the coming weeks and validate the latest Windows updates and features, but still need reliable updates.”
- Release Preview channel: This gives you (and IT admins) a chance to preview an upcoming Windows update just before it reaches the public — essentially the final version of an update that will go out in a matter of days.
By default, the Release Preview channel doesn’t appear as an option when you’re choosing. To reveal it, click the down arrow next to Advanced options and move the Show Release Preview slider to On.
Choosing the right Windows 11 version
After selecting a channel, you’ll also need to make sure you’re receiving updates for the correct Windows 11 version. Click the down arrow next to Advanced options and pick a version. As of now, the available options are:
- Windows 11, version 25H2/26H2: This covers Windows 11 25H2 — the standard version most people run today — along with its successor, Windows 11 26H2, which is beginning to roll out. This is the selection most people will make.
- Windows 11, version 26H1: This is a separate branch from the mainstream 25H2/26H2 line. It’s intended only for PCs with Qualcomm Snapdragon X2 Series processors purchased in 2026. Users on 25H2 or 26H2 can’t switch to 26H1 because their hardware won’t support it, and those on 26H1 can’t switch back to 25H2 or 26H2.
- Future Platforms: Available for both 25H2/26H2 and 26H1, but only if you’re in the Experimental channel. Aimed at developers and highly sophisticated technical users, this is the bleeding edge of Windows and can be highly unstable. Microsoft notes that these builds “represent platform changes early in the development cycle” — including major changes to the Windows kernel and new APIs — and “should not be seen as connected to any specific retail release of Windows.”
If you combine one of these version options with the Experimental channel, you’re placed in a specialized sub-channel. For example, choosing Experimental with the standard Windows 11 version puts you in the main Experimental channel, while choosing Experimental with Future Platforms puts you in a channel called Experimental (Future Platforms). It’s worth noting that this added complexity is a little at odds with Microsoft’s stated goal of making the channel system less confusing.
Testing builds and giving feedback
Once you’ve chosen a channel and version, you’ll start receiving updates for it through Windows Update. Each build comes with release notes hosted in the Insider Flight Hub, and Microsoft’s Windows Insider Blog typically announces each batch of new builds as they roll out, with direct links to the release notes for every channel’s latest build.
As you test, you’ll be invited to report problems and share your thoughts through Microsoft’s Feedback Hub app. Microsoft maintains a “Deeper look at feedback” page that walks through how the feedback system works, and your reports help engineers prioritize fixes before features ship.
Understanding controlled feature rollouts and feature flags
One of the most common sources of confusion for Insider testers is this: you might read about a feature in a build’s release notes, yet not actually see it on your machine. The reason is a process Microsoft calls controlled feature rollouts (CFRs). Rather than flip a new feature on for everyone at once, Microsoft releases it to a subset of devices it considers best able to handle it, monitors how it performs, makes tweaks as needed, and eventually rolls it out to the whole channel.
From Microsoft’s perspective, this staged approach reduces risk. From a tester’s perspective, it can be frustrating, because there’s no reliable way to know when an announced feature will finally appear on your PC.
There is one bit of good news: Microsoft no longer uses CFRs in the Beta channel. If you’re in the Beta channel, you should have access to every feature mentioned in a build’s release notes.
The Experimental channel still uses CFRs, but there’s a possible workaround. You can often turn delayed features on manually using a setting called feature flags. Feature flags also let you turn off experimental features you don’t want to deal with. To use them, before installing a new Experimental channel update go to Settings > Windows Update > Windows Insider Program > Feature flags. You’ll see a list of features you can toggle on or off, and Microsoft says you can use these flags to “even if CFR is being used to gradually roll out that feature.”
Two caveats apply. First, feature flags aren’t available for every feature in a build — only the ones Microsoft chooses to expose. Bug fixes and general system improvements typically don’t come with toggleable flags. Second, once you change a flag, you can always flip it back from the same page later.
Switching between Insider channels
You can switch channels, but only to a limited extent. You can move between channels only for your current Windows version — right now either Windows 11 25H2/26H2 or 26H1 — and you can’t switch in or out of the Experimental (Future Platforms) channel.
So you can go directly from Release Preview to Beta or Experimental, or from Beta (26H1) to Experimental (26H1) or Release Preview (26H1). To make a change:
- Go to Settings > Windows Update > Windows Insider Program.
- Select Choose your Insider settings.
- Click the button next to the channel you’d like to switch to. You’ll receive updates for your new channel the next time one is ready.
There’s an important catch if you’re in the Experimental channel: you can’t move directly out of it to another channel. If you want to leave Experimental, you’ll first have to wipe your PC, reinstall Windows, and then re-enroll in a different channel. That’s a significant step, so it’s another reason to think carefully before committing to the Experimental channel in the first place.
IT administrators: the Windows Insider Program for Business
IT administrators need to know what’s changing in Windows before it happens, so they can prepare their environments ahead of time. To support that, Microsoft offers a separate Windows Insider Program for Business, which adds enterprise-focused features and tools on top of the standard program. Admins can install preview builds on individual PCs or virtual machines for testing, or centrally manage builds across many devices in the organization using a range of management tools.
To get started, visit the Windows Insider Program for Business page, click Register, and follow the instructions. Microsoft’s “Start running Windows Insider Preview Builds as a business” documentation walks through setting up individual PCs or virtual machines, while “Manage Insider Preview builds across your organization” covers registering your Entra ID domain and managing test devices through Group Policy, Intune, and other management tools.
When it comes to choosing channels for test devices, IT has the same three options as individuals. But Microsoft offers some additional guidance for the enterprise audience:
- Experimental channel: Not usually the best fit for IT, and not just because it’s the buggiest. Microsoft introduces features and settings here that it later discards, which means admins could waste time checking out and preparing for capabilities that will never reach their environment.
- Beta channel: Often the best choice for IT. It tends to be fairly stable, and by the time a feature reaches Beta it’s intended for the next Windows release rather than some distant, uncertain date. Admins get a genuine heads-up on what’s coming soon, without chasing features that may never ship. Because they’re commenting on features and bugs while they can still be changed, admins also get the most influence over the direction of Windows.
- Release Preview channel: The most conservative option, and the most stable. What you see here ends up in the next Windows update, so IT can confirm that their applications and infrastructure are ready before the update ships publicly. Microsoft’s “Validate upcoming releases in the Release Preview Channel” page provides more detail.
One last resource worth bookmarking is the Windows Insider Program Tech Community forum, where IT professionals around the world post feedback, share tips, and discuss problems and workarounds for the builds they’re testing.
What this means for you
For the everyday Windows user, the practical takeaway is simple: preview builds are a great way to try new features early, but they come with real stability risks, so keep them off your main machine. If you do want to experiment, the Beta channel is the sweet spot for most people — it gives you upcoming features and fixes without the rough edges of the Experimental channel, and because Microsoft has dropped controlled feature rollouts there, you’ll actually see everything the release notes promise.
For IT admins, the Beta channel is generally the most efficient place to test, since it balances stability with a genuine view of what’s shipping next. Reserve the Release Preview channel for final validation of your applications before a public update goes out, and treat the Experimental channel with caution unless you specifically need to weigh in on very early-stage work.
How to get started
To begin, make sure you’re on Windows 11, then sign up on the Windows Insider Program page with your Microsoft account. Enable optional diagnostic data in Settings, then configure each test PC through Settings > Windows Update > Windows Insider Program, choosing your channel and version. From there, updates arrive through Windows Update, and you can report issues through the Feedback Hub. If you’re setting up test machines for an organization, register through the Windows Insider Program for Business page and consult Microsoft’s business flighting documentation for Group Policy, Intune, and Entra ID setup.
Source: Computerworld
Over to you: Are you testing in the Beta channel for stability, or pushing into the Experimental channel for the latest features?
