Cannot Leave Minecraft Beta - Windows 10

Try the steps below.

• Cancel your participation in the beta program on the Xbox Insider Hub app.

• Uninstall Minecraft for Windows 10 using the Add or Remove Programs system application.

• Run PowerShell as administrator. To do this, you can press the Windows key + X keyboard shortcut and select the appropriate item from the menu.

• Run the command: Get-AppxPackage -allusers "*minecraftUWP*" | remove-appxpackage -allusers

• Close PowerShell and install Minecraft from the Microsoft Store.

Enjoy the release!

duplicate MCPE-33270 😉

Try the steps below.

• Cancel your participation in the beta program on the Xbox Insider Hub app.

• Uninstall Minecraft for Windows 10 using the Add or Remove Programs system application.

• Run PowerShell as administrator. To do this, you can press the Windows key + X keyboard shortcut and select the appropriate item from the menu.

• Run the command: Get-AppxPackage -allusers "*minecraftUWP*" | remove-appxpackage -allusers

• Close PowerShell and install Minecraft from the Microsoft Store.

Enjoy the release!

duplicate MCPE-33270 😉

I have tried all that multiple times and still on the beta🤣 that's why I reposted a duplicate post because nothing I'm trying is working. Before you ask I only have the 1 account signed up to the beta. No other accounts are on my PC or anything like that.

I have tried all that multiple times and still on the beta🤣 that's why I reposted a duplicate post because nothing I'm trying is working. Before you ask I only have the 1 account signed up to the beta. No other accounts are on my PC or anything like that.

@unknown: THANK YOU! Another moderator noticed that your instructions mentioned that asterisks in the command had caused it to fail. On checking, we discovered that the asterisks had likewise caused the command to be rendered incorrectly on the Xbox page intended for troubleshooting this problem. We had not been aware that the command there was incorrect, and that the way it was rendered would cause Powershell to run without an error, but also without performing the intended fix. That fix was meant to be a brute force, last resort solution to the problem that should fix even in the worst case, so Mojang has been stumped about why it wasn't working. We are passing this information to Community Management, who will have the Xbox team fix the problem on the troubleshooting page.

Meanwhile, I modified your comment to include the command in a form that shouldn't cause a problem when copied and pasted. For future reference, the backslash "\" character can be used as an escape character in Mojira to prevent special characters such as * and _ from being interpreted as text formatting codes. I also enclosed the "minecraftUWP" string in double quotes because canonical Powershell syntax expects that. (It will usually work without the quotes, but it's safer to include them.)

@unknown: THANK YOU! Another moderator noticed that your instructions mentioned that asterisks in the command had caused it to fail. On checking, we discovered that the asterisks had likewise caused the command to be rendered incorrectly on the Xbox page intended for troubleshooting this problem. We had not been aware that the command there was incorrect, and that the way it was rendered would cause Powershell to run without an error, but also without performing the intended fix. That fix was meant to be a brute force, last resort solution to the problem that should fix even in the worst case, so Mojang has been stumped about why it wasn't working. We are passing this information to Community Management, who will have the Xbox team fix the problem on the troubleshooting page.

Meanwhile, I modified your comment to include the command in a form that shouldn't cause a problem when copied and pasted. For future reference, the backslash "\" character can be used as an escape character in Mojira to prevent special characters such as * and _ from being interpreted as text formatting codes. I also enclosed the "minecraftUWP" string in double quotes because canonical Powershell syntax expects that. (It will usually work without the quotes, but it's safer to include them.)

I've just tried the modified command and it hasn't worked. I'm at a loss for what's going on

I've just tried the modified command and it hasn't worked. I'm at a loss for what's going on

@unknown

I'm a little surprised!

@unknown

I'm a little surprised!

@unknown

You can link to the xbox site with a solution to this problem. I can't find something.

@unknown

You can link to the xbox site with a solution to this problem. I can't find something.