Beta Channel
11 TopicsWanted to join Beta Channel, ended up forced to upgrade to Windows 11 Insider Preview, how to stop?
So, it all started with me wanting to join the Beta Channel for Excel since I wanted to have the new features available there. So, in Excel I couldn't find the Insider Button at Account menu even though I am a MS365 Subscriber. So, I thought I had to go to Windows Settings -> Update & Security -> Windows Insider Programme to use it. After I registered there, instead of showing me in Excel Beta Channel it now is downloading and installing Windows 11 Insider Preview, what I don't want and theoretically shouldn't be able to get since my processor is too bad, it tells me that in the same window at the right side. (I am currently on Windows 10 Home 22H2-19045.3324) I have already tried to leave the program and i am getting different response to that, the Windows Insider Programme in the settings tells me that I am still set to get Insider Preview builds and the Windows Update menu also. But when I click on Leave the Insider Programme in Windows Insider Programme it directs me to a page which says This email address is not registered as a Windows Insider.... And yes it's the same E-Mail address that's linked to the program and which was connected to the page that told me the E-Mail address is not registered. Also, Sidenote: Many buttons are not responding at all, clicking on fix the problem (see image) doesn't work, before that, changing Channels, adding E-Mail all did not work first time. And In Office clicking on Join MS365 Insider doesn't do anything either. This whole program seems verry unstable. My questions are: 1. How to undo all that so I don't must upgrade to Windows 11 Insider Preview 2. How to join Office Beta Channel the correct way?Solved4.1KViews2likes8CommentsSeamless Android App Integration for Windows: A Game-Changer
I propose a game-changing feature: Seamless integration of Android apps into the Windows ecosystem. Here’s the vision: One-Click Conversion: - Developers import Android projects into Visual Studio. With a single click, their apps transform into the Appx Windows Store format. Google Play APIs Bridge: - Microsoft reimagines Google Play APIs in C# or .NET, making them accessible within Windows development tools. Cross-Platform Harmony: - Android apps run natively on Windows, leveraging Windows Runtime Environment. Direct Publishing: - Developers publish Android-converted apps directly to the Windows Store. **Challenges** API Translation: - Rewriting Google Play APIs for Windows. Runtime Adaptation: - Bridging Android’s runtime with Windows’ .NET. User Interface: - Adapting layouts and interactions. User Demand: - Many developers and users crave this integration. - It’s a win-win for both ecosystems. Let’s collaborate to turn this vision into reality! 🌟498Views1like0CommentsNot recieving Beta-Channel Updates and Insider Site not working
Hello! It´s been 4 Months since I recieved my last update in the beta channel, currently being on Build 22635.2921. Windows Update´s Insider Tab shows me that I am not on the newest Build, but automatic update just doesn´t provide it for me. So today I went ahead and wanted to upgrade to the https://aka.ms/wipISO But then I got another issue. The whole https://www.microsoft.com/de-de/windowsinsider/ doesn´t work for me when i am logged in. I can browse it normally on Edge, Opera and even my Phone but as soon as I log into my account it just loops infinitely with the spinning blue circle. Is there a fix for any of my issues? Thanks in advance!518Views1like1CommentUnable to Switch Dev Channel to Beta (A Solution)
I got into the Beta Channel a little while ago and things have been going well - but then - I noticed an app I wanted to tinker with but couldn't gain access. So, my bright self-did the next logical thing. Update to the faster Dev Channel. The update went well, and I soon realized the new build was set to expire and potentially leave me without a working OS. No Bueno. I backed up all of my files, and instead of a clean install I just used the reset option, and it allowed me to revert back to the Beta Channel again (a seemingly happy middle ground for now). Now the Windows 11 Insider Preview 23545.1000 (ni_prerelease) is appearing as an available download in the Windows Update Center - but with an Install Error - 0x80242016. It is my assumption that this error is occurring because that build is for the Dev (fast) Channel, yet I am set on Beta. If that is the case, this Error is good for my current goal. So, then the question becomes that if I am currently set into the Beta Channel, will the install error for the Dev channel persist indefinitely until I move back up to the Dev channel? Or will windows force the update back into the Dev Channel build should the update at any point not produce the same error? Will deleting the corresponding files in the Software Distribution stop the update from trying to run and appearing in the list? - Assuming that deleting those files will equate to this resolution. If so -- how do I identify which folders correspond to which build update? I do not want to stop receiving builds because I would like to stay in Beta (for now) - and receive those builds. I'm still a little new to the Insider Community, and this will be my first post. Has anyone tried leveling down without a clean install before? Wise advice for anyone > Research your new channel before joining it. Don't learn things the harrowing way like me. UPDATED SOLUTION To remove the error code, I paused the updates and immediately restarted them to refresh the list. Prerelease build no longer appears and nor does that error code. Thanks for the reads 🙂2.6KViews1like5CommentsUnable to launch app on Windows 11
Hello. I am Beta tester on the Windows insider community, and I currently have version 22631.2271 ni_release build installed on my computer. I am unable to launch certain applications on my computer, including Microsoft Office 365 application and Adobe Acrobat reader. I also have issue with the search bar, as is it very unresponsive. I have contacted Microsoft Support and they have directed me to the insider community, and I hope that I can find answers and help here. Looking forward to getting the much needed help here. Thanks.1.5KViews1like2CommentsCan't Move from Release Preview to Beta Channel
!!! SOLVED: After a day and a restart, Beta and DEV Channel are now selectable. Thanks!!! Hi. Is anyone able to help me? I remember selecting the Beta Channel (as it is considered recommended) back when I upgraded from windows 10 to 11. However, I'm receiving a popup message right now stating that my insider build would expire soon. After viewing the Windows Insider program in settings, I noticed that I'm in the Release Preview channel and both Beta and Dev Channel were greyed out. I wanted to move on to Beta or Dev channel to remove this popup expiration message. What should I do? For context, here are my PC Specs: Windows 11 Single Home Language Ryzen 5 3400G Processor 16GB RAM Secureboot Enabled TPM 2.0 Enabled Here's a preview of what I'm talking about: https://imgur.com/ahOkyKh If someone could help me out. Please do so. Thank you!2KViews1like4CommentsQuick settings and Notification Center stay on top of auto-hidden taskbars
As you can see from the image below, quick settings and the notification center overlap the taskbar, if auto-hide taskbar is enabled. It's a small, but annoying bug, because it prevents you from clicking on the buttons below, so, I first have to click outside the box to make it disappear and to be able to access the icons that were previously hidden behind it. For clarity, I link two videos. The sequence is: Quick settings -> Notification Center -> Quick settings -> Volume Mixer. Auto-Hide Taskbar ON: https://imgur.com/a/GSU7djZ Auto-Hide Taskbar OFF (No bug): https://imgur.com/a/eINXALI In the last video, the experience is certainly smoother and faster. Is there any setting, registry key, or third-party program I can use to fix this bug, other than disabling auto hide taskbar? Or should I just wait and hope for an update from Microsoft? Currently, I am using build 22621.160 on the Beta Channel, Windows Insider, but I am aware of users on the official release (Windows 11 21H2) experiencing the same problem. This bug was temporarily fixed with build 22581 (here the official response from Microsoft: https://aka.ms/AAh8b8n), but returned with 22621. Windows 11, Build 22621.160, Beta Channel726Views1like1Comment