This Friday, Microsoft released the Windows 11 Insider Preview Build 25136 version update to the Dev channel, starting to roll out updates such as the File Explorer Tab tab to Windows Insiders.
While it’s true that the new features have been pushed to all previewers in the channel, Microsoft points out that they’ve decided not to make them available to all testers anymore. Although Microsoft does not officially open it to everyone, as long as Windows updates the file resources, you can still force it to open through the registry and other methods.
In simple terms, this means that even if you are a preview tester on the Dev Channel, there is a chance that you won’t get the feature, while the rest of the Dev Channel will. At present, Microsoft has not disclosed the proportion of people who can get new features. The official explanation they gave is:
We’ve pushed this feature to the Dev channel, but it’s not yet available to all Insiders in the channel, as we plan to see what the feedback is before releasing it and decide to roll it out to everyone depending on the outcome.
Foreign media believe that this is actually meaningless to some users who voluntarily join the development channel. After all, every user who is actively trying to adopt the new system is already psychologically prepared to deal with the unstable new system. Have you tried new features before? After all, who would test for a pointless test?
They say Microsoft wants to split the Dev Channel into two categories, so that some Insiders on the Dev Channel can start testing a feature before other Insiders see it, avoiding irreparable damage. But even after agreeing to these conditions, it is still difficult for people to accept that they cannot experience all the new features in the same Dev channel.
Neowin co-founder Steven Parker also said how speechless a Windows insider in the development channel is when he hears that his Dev experience may be different from others. Of course, this solution does not seem to be a matter of differentiated treatment for users. Foreign media pointed out that Microsoft still lacks transparency, and the logic itself is flawed.
Staggered deployment only makes sense when it is cross-channel. For example, Dev Channel Insiders received a tabbed file explorer and upgraded to Beta after initial testing, then to Release Preview, which was eventually rolled out to the public.
However, in the current model, the Dev channel is further split into A/B testing, and considering that Microsoft could achieve the same by collecting metrics from other channel users who don’t have a “file explorer tab”, this situation should not exist.
If you like our news and you want to be the first to get notifications of the latest news, then follow us on Twitter and Facebook page and join our Telegram channel. Also, you can follow us on Google News for regular updates.