Chris Walsh

So I went through the enrol/unenrole steps leaving 12+ hours between each step. Didn't fix the problem.

I've since also tried signing out of XBox and PlayStore and logging in with my son's account and then installing Minecraft.  This also installed the Beta!
Whatever the problem is, I am convinced it is some latent stuff physically stored on my PC (outside of my profile) that is causing this to happen.  The PC (different user accounts and different windows profiles are ALL installing the Beta.  The only thing it is limited to is my PC (our laptop doesn't have this occur).

Thanks for your help Auldrick.  It's much appreciated.   I'll keep the local user account open and wait to see if I hear anything via email.
I'm going to carefully read through and retry the revised instructions. (I've already started retrying the reenrol/unenrol process, leaving 12-24 hours between each step in case of delays in inter-system messages causing the problem.).  If a permanent fix finally occurs, I'll report back here.  Thanks.

Hi Auldrick,
(Sorry, I don't know how to quote within this forum)

> Auldrick: "I didn't think it was possible to have both regular and Beta releases installed on the same PC at the same time, because the executables have the same name and are stored in the same folder in Program Files. But I believe you because you're a developer and I expect you to know how important it is to give complete, accurate descriptions."

You're correct, that you can't have a beta and regular release installed at the same time.  I probably didn't make it clear but prior to creating a new local user account, I uninstalled Minecraft from my main profile and installed it fresh in the new one.

This new install in a new fresh Windows 10 profile did in fact install the regular version of Minecraft.  It lasted two days, but, when I logged in just now, I've found that that too has reverted once again to the beta version!  Grrrrr! 😞

> Auldrick: "I believe your MS account (or a Store account that's in a one-to-one correspondence with it, probably) has a toggle that identifies you as a Beta member. "

Yes, I think you are correct.  

> Auldrick: "When you join or leave the Beta, the Insider Hub is supposed to fire off transactions to the Store, Xbox Live, and probably other services that support installing and playing Minecraft. In the Store's case, that transaction sets or resets the toggle."

Yes, that makes sense.

> Auldrick: "1. The Insider Hub failed to kick off the Store update to reset the toggle when you left the Beta. This could be due to a network problem, for example. This can usually be solved by re-joining and re-leaving the Beta, so try that if you haven't yet."

I've done full enrol/unenrol cycle about six times to date across a series of months (each one followed by an uninstall and reinstall of MC via the Store).  If it was a network problem, it appears to be permanent - except that I would then expect ALL beta insiders to have this problem which I'm assuming they don't - otherwise there will be more uproar about this issue than there is.

> Auldrick: "2. The Insider Hub kicked off the Store update to a different account than the one you use to download Minecraft. "

This now sounds much more plausible.  I have a number of Microsoft accounts for work, MSDN, Partner Center, Office 365 as well as personal/family accounts for my two children.  I've always tried to keep my personal XBox account separate from my work one but TBH, I've had a myriad of issues with Microsoft accounts over the years often with advise from Microsoft to "just create a new Hotmail account" (which IMHO has made things worse - if not just more confusing).

As far as I can possibly tell, I'm using the same Microsoft account in XBox, Insider and Store.  (However these Universal Windows Platform (UWP) apps such as XBox and Insider give limited information on what's going on in the background). 

> Auldrick: "The fact that your local user account downloaded the regular release tells me that it isn't signing into the Store with the same account your normal user account is signing in with. If you can explain why that is, it may be the key to resolving your problem."

Well, as my local user account version has now "upgraded" to the beta version (albeit after two days) I assume must have been using my same Microsoft/Xbox account (I am consistently logging into Xbox the same creds)

> Auldrick: "Also, the fact that your local user account downloaded the regular release might mean that you now have the regular release in your normal user account, if I'm correct that it's impossible to have both versions installed on the same PC at the same time. Have you tried starting the game on your normal user account since then?"

So as soon as I discovered that my local user account had auto-"upgraded" to beta, I uninstalled it (from local user account) and logged out of it.  I'll install it now on my "normal" windows user account: ... installing... (378.7MB [this is going to be the beta, I know!] ... launching... BETA - straight away. Humm.

I don't get why my local user account installed the regular version where as my normal account installs beta from the off.  I suspect at this point on, my local user account will install the beta from the off too.

Is there anyone, anywhere that would be able to:

1. Check my Microsoft/XBox account to see if the "Minecraft Beta" flag is enabled in the store?

2. Switch off the "Minecraft Beta" flag if it is?

I contact number or email address would be very much appreciated.

It sounds like it should be a really straight forward thing for a Microsoft engineer to do.  I'm a developer for a number of platforms that we've built and I could do a similar check/correction in a matter of minutes.  This however, has been going on for months and I can't work on my main Minecraft world in a beta for obvious reason.

Thanks, Chris

Thanks Vincent.  I'm not prepared to reset my Windows OS for a bug in an Application.  Although the VM method worked for me, it is pretty unplayable.  Last night I created myself a separate local user account in Windows and installed Minecraft in there.  I can live with logging into a separate user account to play Minecraft vs everything else that I use my computer for. Touch wood, Minecraft in this separate user account is running the non-beta version and hopefully it won't get infected by this ridiculous Minecraft Beta bug.

So I've created a new install of Windows 10 in a Hyper-V virtual machine and installed Minecraft onto it using the same user account.  No BETA.
As I used the SAME user account to log into XBox for both my broken "beta-only" PC and the virtual machine running the same OS and install of Minecraft... is there anything I can do to copy or overwrite the packages/registry on my main PC from the virtual Windows to make my main PC run Minecraft in non-beta mode?

Surely this must be down to either:
a) Some setting stuck in the registry or filesystem on my PC; or
b) some setting within XBox related to my user account AND device (PC) combo that always insists on installing the beta-only version?

I'm leaning on the side of option (a) above.  Surely this is something that Mojang/Xbox can both reproduced AND debug and identify the root cause and issue a proper fix?

Thanks for the suggestion @Arturo but I've tried this and much more dozens of times.  I'm well past that stage!  

Please refer my opening comment here.

Can you clarify what you mean by Factory Reset?  I hope you don't mean Windows?  That's a pretty drastic step for a long-standing bug that should be fixed within XBox? Insider Hub? Minecraft?  (Ha! I don't even know which component is at fault here)  Can someone not reset my XBox account - clear out any beta crap from it?
Thanks.

So I've unenrolled from the beta -> Uninstall Minecraft (for all users and backup any saves first) > Run (Win+R)  andn ran wsreset from the command prompt.  This opened Microsoft Store after around 10 to 15 seconds as you say.  Installing Minecraft STILL installs the beta though. (I could tell before even launching the game because the download size is 378.7MB and the version is 1.16.200.53). 

Looking at my order history, I purchased Minecraft for Windows 10 Starter Collection in 23rd June 2019 and Minecraft for Windows 10 on 1st April 2020 (for my child).  Could the problem be related to the fact that I've purchased the same product twice?  I'm clutching at straws here but no suggestions have been successful to date.

Still can't play the game.

I've been trying repeatedly for months to get shot of the Beta version.  I've gone through the "Solution A B and C" about a dozen times, done reinstalls about 40 times now.  Tried the "@unknown" fix (which is just Solution C anyway).  Tried completely shutting down and recreating my Insider account.  I've only got one user account.  I am so fed up with this.  I'm a software developer for 20 years now and NEVER have I seen such a shambles as not being able to play the commercial product because a BETA keeps getting reinstalled instead of the normal game.  Come on - why can I not at least select which version I want to install  - or at least have BETA and PRODUCTION installed side-by-side like any other software would allow.  Can't get any direct call support either which just rubs salt into the wombs.  Bring back traditional installs (appwiz.cpl) for Windows 10 - this xbox stuff is such a step backwards.