It was yesterday when we saw how Microsoft was alerting users that are part of the Windows Insider Program on how builds could have more bugs since they start testing with the 22H2 branch. It was recommended to the most prudent, move from Dev Channel to Beta Channel, something that apparently not everyone can do.
And it is that some users who warn that when trying to jump to the Beta Channel, less advanced and more conservative, they find that the option appears deactivated and they cannot select it within Windows Update in the section dedicated to the Insider Program.
Stuck in the Dev Canal
So far, Windows 11 and the released builds are showing very stable behavior. The reason is that both the Dev Channel and the Beta Channel are based on the build that will generally arrive in the fall to all users. From that point, the Beta Channel will focus on improvements that will come to this version while the Dev Channel will remain to test what should arrive in autumn 2022.
{“videoId”: “x827oo9”, “autoplay”: true, “title”: “WINDOWS 11 IS OFFICIAL !: ALL about the NEW MICROSOFT OPERATING SYSTEM in 4 MINUTES”}
At this point, many have found it advisable to take their foot off the gas and switch to the Beta Channel, which will feature a more settled foundation and safer upgrades. For this they have entered the current route that passes by going to “Setting”, “Windows Update” and “Windows Insider Program”. At that point you can choose between Channel Dev, Channel Beta and Channel Preview (in the photo the latter is disabled since it does not appear in Windows 11).
The problem is that some users cannot make the jump and go to the Beta Channel down a step. This option appears but it does so in gray, which indicates that it is disabled in Windows Update Settings.
On HTNovo propose the already known trick to use the Registry Editor and thus change the channel, but apparently and according to MSPU It does not work, because after leaving the Dev Channel those who have tried it end up in the Preview Channel.
The steps to try to go down to the Beta Channel using the Registry Editor “go through opening the editor by typing” Regedit “and looking for the paths:
HKEY_LOCAL_MACHINE SOFTWARE Microsoft WindowsSelfHost UI Selection
HKEY_LOCAL_MACHINE SOFTWARE Microsoft WindowsSelfHost Applicability
In the first it is due change the value of Dev in Beta to UIBranch while in the second it is due make the same change but in the BranchName section.
At that point it only remains to confirm the changes, close the “Registry Editor” and restart Windows 11 to check if the changes have been applied. But as we say, it seems this trick doesn’t always work.
However, the problem is not generic, as we have just checked it and in our team it is possible to go from one channel to another without problems. A failure that for now has no solution and we may have to wait for a new compilation of Windows 11 to be solved on the computers that are affected.
Via | HTNovo
(function () {window._JS_MODULES = window._JS_MODULES || {}; var headElement = document.getElementsByTagName (‘head’)[0]; if (_JS_MODULES.instagram) {var instagramScript = document.createElement (‘script’); instagramScript.src = “https://platform.instagram.com/en_US/embeds.js”; instagramScript.async = true; instagramScript.defer = true; headElement.appendChild (instagramScript); }}) ();
was originally published in
Engadget Windows
by
Jose Antonio Carmona
.
