FIX: Insiders not able to switch channels - **UPDATED 8/3/2021**

للاسف لايزال المشكل قائما

نتمنى منكم ايجاد حل وفتح الحسابات مرة أخرى

<Translated using Edge>

unfortunately, the problem still exists.

we hope you find a solution and open the accounts again

Again, isn't this something the Insider Team can do by using my email address (my Microsoft account) and setting my participation to Beta? We were able to do that in 06 so I assume it's only gotten better since. Or one would hope.

If you can address the last issue I'd appreciate it.

Hello Richard,

That is something that is not possible to do. Like yourself, we are all Insider volunteers trying to help others with any issues as there is no official support. We are not MS.

Another example of this is the verify issue. This was fixed by MS back with build .71. Some are still facing this. They refuse to start fresh, so not much one can do. I have done over 30 clean installs in past couple months in the 8 vm's and couple spare laptops. It verifies the account every time. Originally had same issue.

Did a clean install again today, to my surprise, all 3 channels were open and selectable. Put this one in Release Preview as have not heard that was officially done other than for commercial.

This just might be the best way for you going forward. You can also run W11 without joining Insider if you prefer, you still get the CU updates, but not all the Store updates as in new Snipping Tool. They will all come after Oct 5th if not sooner. I personally have found doing the upgrade from W10, system never worked as well compared to the clean.

A clean install takes me about 7-10 minutes to run. only use a few programs on test machines so after setting my preferences, winrar, an uninstaller and a utility program, said and done in under 30 minutes. Faster than doing a major build upgrade.

On the working desktop, even though all data is stored on secondary drives, it can take me days to install everything I use. Especially the big stuff such as Autocad and Photoshop, Office etc.

I highly recommend going this route, you have already spent enough time on this issue. Nothing ever beats a clean install to get system working at its peak. The Insider Beta ISO of 22000.132 most likely be the same as Release ISO as MS did with 21H1. They will only compress install.wim to install.esd for MCT so consumers can fit on flash cards. Have already done that for bootable flash. One can split the install.wim file as well to fit on flash FAT32.

Good luck on whatever you decide. Take care.

Regards,

Thanks, Johnny. I did an entire RESET a few weeks ago so I'm not sure what difference it would make to install from an ISO. I could try it - I have disk space. It would be interesting if I could change it in the new install, then boot into the current install to see if it picked up the changes.

As for using Dev builds, I used to work on a TAP team as the lead for Windows ro drive adoption within MS-IT, so I know the drill. I generally don't use a production machine for those builds. However, with Win10, the core codebase was solid, so changes rarely created needing anything more than the occasional Roll Back. Even then, before every upgrade, I run a disk clone just in case.

With Win11 that was the main reason I wanted to switch channels as recommended. However, I can't. I should note that I'm not the only one reporting the exact same problem - all channels show up but you can't change from the one you're in, to another.

Again, isn't this something the Insider Team can do by using my email address (my Microsoft account) and setting my participation to Beta? We were able to do that in 06 so I assume it's only gotten better since. Or one would hope.

If you can address the last issue I'd appreciate it.

Hello Richard,

In your case as all normal fixes are not working, suggest first trying an in-place upgrade with the Beta ISO. Mount the ISO in windows and run setup.exe. You can get Security updates for Defender directly in the App itself.

If the in-place upgrade does not fix whatever is corrupt with your system, suspect your only alternative is to total clean install W11 deleting all partitions and start new. Ensure you backup all important files first, preferably off system to external drive.

You should not have been using Dev builds on working computers for daily use. At a minimum, if one does, at least have an image backup of your system prior to joining Insider program. This is all clearly stated in the Insider Agreement that most users never bother to read.

Regards,

By The Way, it has been more than 10 days since I downloaded Windows 11, and don't want to go back to windows 10 and etc. if there is any fix to this problem please let me know

at first, downloading windows 11 I used the dev channel then later changed it to beta, the 22000 updates switched back my choice from beta to dev I have no idea why this happened.

so please let me if there is anything I can do. that doesn't involve me doing a clean reset of the device and start the progress of downloading windows 11 from the beginning

Hello RNG,

When you switched to Dev, you ended up doing what we call a major upgrade, rather than the CU updates in Beta. Dev channel (which is not tied to any specific build) is now running version 22xx. Beta is running version 21H2, they are entirely different versions. Thus your options are greyed out. If you go to Settings, Update, Recovery, you will see an option to roll back to previous version, which would be Beta. You have 10 days from installing the Dev build to do so. Then ensure your Insider Settings is set to Beta.

As per previous pic you posted, it displays 22449 which is a Dev build. The only way back to 22000.xxx you have some time left to roll back. Dev channel is now a point of no return to Release for over a year minimum. If you ran disk cleanup and deleted the windows.old folder, you will not be capable of rolling back. Here your only option is to clean install. Doing a reset keeps your current version so that will not work.

This is why MS has been sending out several emails notifying Insiders on Dev channel to switch to Beta channel while you still had the opportunity to do so. Once on the new build of 22449 you have moved on to future builds. This is not next months Release version that you are currently running.

Bottom line, if you cannot roll back, you have to start fresh using the ISO for Beta or remain in Dev for another year.