- Why is this needed?
- Patch any applicable Minecraft for Windows executable with an updated public Xbox Live authentication key (with one major caveat)
- The default installation directory where the
Minecraft.Windows.exeexecutable is stored is heavily (and obnoxiously) protected by Windows - One problem lies within the inability of 3rd party programs to write anywhere inside the WindowsApps folder by default. This makes the patching process extremely inconvenient
- Additionally, even if write restrictions were bypassed, applying changes to the contents of an appx requires sideloading, or else the app will fail to run due to mismatching hashes
- By default, the contents of Minecraft appx files are installed in
%ProgramFiles%\WindowsApps\Microsoft.MinecraftUWP_*_8wekyb3d8bbwe, where*will vary depending on your installed Minecraft version - For example, if you have the 64 bit version of Minecraft v1.16.40 installed, the directory would be
%ProgramFiles%\WindowsApps\Microsoft.MinecraftUWP_1.16.4002.0_x64__8wekyb3d8bbwe - Note that you will be denied viewing access if you have not explicitly taken ownership of the WindowsApps folder, but you don't need to do that in order to use the patcher
- 3rd party tools, such as mc-w10-version-launcher can be used to sideload appx files (which may or may not have modified contents)
- This tutorial assumes you are familiar with sideloading appx files and/or using 3rd party version managers for Minecraft for Windows
- I recommend using mc-w10-version-launcher as I believe it is the most straightforward and reliable
- By using this launcher (and more generally speaking, sideloading Minecraft for Windows), your installation path is in a write-accessible directory and changes can be easily applied without hassle
- The location of the
Minecraft.Windows.exeexecutable in this custom installation path is the same path you will specify when running the patcher
- Make sure Minecraft for Windows is closed beforehand
- Download the latest release of the patcher here
- Follow the steps described in the Workarounds header
- You may need to run the patcher with administrator permissions
- Follow the prompts in the console as required
- GPLv3
- However, you are not permitted to put this tool behind some sort of paywall, such as a 3rd party link shortener or other paid product
- I am aware that the process to apply a seemingly simple patch is quite complex for the majority of users who do not use version managers, but this is largely due to Microsoft's restrictive UWP application ecosystem
- There may be better ways to streamline this entire process, so contributions are welcome and encouraged