v4.9.31

Installer fix: the game file is the only copy that keeps the winmm.dll name.

• The download staging folder and the offline cache now store the file as payload-x64.bin (and payload-arm64.bin on the ARM path), so no copy the installer creates outside the game folder can be picked up by another program in that folder.
• An offline copy left by an older install is renamed instead of deleted when it matches the expected hash, so the offline install keeps working. A copy that does not match is removed.
• The failure report has a new [stray] line listing what was renamed or removed.
• README, README_PT-BR and the troubleshooting FAQ now explain why the file must stay only where the installer puts it, and ask you to delete any copy you downloaded by hand.
• Scripts only. The unlocker binary is unchanged, so an already unlocked game needs nothing.

v4.9.30

Installer fix for machines where the game files are not in the default folder.

• The installer now looks at the folder the registered game package points to, and at every XboxGames folder on the fixed drives of the PC.
• Fixes the case where the content sits in C:\XboxGames\Minecraft for Windows_1\Content or on another drive, which ended in "Minecraft package found but the game executable is missing" plus a request to reinstall.
• The failure report now records where the package points (target= in [pkg]) and marks linked folders in the candidate list, so this case can be told apart from a broken installation.
• Scripts only. The unlocker binary is unchanged, so an already unlocked game needs nothing.

v4.9.29

Binary update. The installed DLL now only acts inside the Minecraft process, so an install can no longer interfere with another game that shares the same folder.

• Refreshed winmm.dll
• Menu, version and checksum pins updated for v4.9.29
• Install steps are unchanged, reinstall to pick up the new binary

v4.9.28

Scripts only. The unlock binary and install.bat are unchanged, so an install that already works does not need to be redone.

• When the game closes with exit code 0x87E50035, the installer now explains that Windows could not activate the app, that the unlock is not the cause, and what to do about it
• The failure report now records the package scope (allusers=), which is what tells a package registered for another user apart from no package at all
• The report also records whether the folder it launched from is the official install even when the game starts as a plain executable
• Troubleshooting page gained a section for this exit code

v4.9.27

v4.9.27

Installer release, same winmm.dll as v4.9.26, no reinstall needed if you are already unlocked.

• The installer no longer warns about a third-party launcher when the game folder is the real Microsoft Store package folder
• The game version is now read from the package folder name when the executable and the registered package do not report it, so the version check no longer gives up on those installs
• The failure report records the raw version value when it cannot be parsed

install.bat sha256:43b80e435c16db56b8560f587ef2f3a632254977cb9ac3189bac7fcbda13fe01
winmm.dll sha256:9371baf3b6ad442f2694e62449f0991805fa941e0281cbabcec3585d54fbd299

v4.9.26

Installer release, same winmm.dll as v4.9.25, no reinstall needed if you are already unlocked.

• The installer now checks the game folder before touching it and asks for confirmation when that folder is not the official Microsoft Store or Xbox App installation
• The message explains that a third-party launcher is not supported and that the unlock can break it
• When the game does not start after the install, the message tells you to open it through your launcher instead of the Start menu
• The failure report records why the automatic start failed (executable present or missing, start error, result of the fallback) and whether the folder was the official installation

v4.9.25

Installer release, same winmm.dll as v4.9.24, no reinstall needed if you are already unlocked.

• The download of winmm.dll now tries two alternative addresses when the first one fails, so a temporary server error no longer stops a fresh install
• More tries and longer waits on a failing download, and the Retry-After header of the server is honored when it sends one
• The offline copy already verified in %LOCALAPPDATA%\mbu-cache is used before the alternative addresses
• The failure report now lists every download attempt with the address, the HTTP code and the error text
• New message for the case where the installer cannot reach the server at all, separated from the temporary server error message

v4.9.24

Fixes the Defender exclusion on installs where the game folder is a junction (Xbox app installs).

• The installer now also excludes the real folder behind the junction, which is the path Windows Defender reports.
• If Defender flagged winmm.dll and is asking for a restart, run the installer again before restarting.
• No change to install.bat or to release/winmm.dll.

v4.9.23

Builds newer than the verified one no longer block the installation. The installer now checks a minimum supported version instead of an exact list.

• Any Minecraft for Windows build from 1.26 on is accepted, including a build released after this version.
• Only builds older than that floor are refused, with the update instructions on screen.
• Failure reports record which build was used, so a newer build that misbehaves shows up in the diagnostics.
• Docs updated (README, README_PT-BR, TROUBLESHOOTING). The unlock binary is unchanged (9371baf3...).

v4.9.22

Some Minecraft installs fail to start because a Windows component the game needs is missing or damaged, and the exit code alone told the user nothing. The installer now explains that case and the failure report carries more context.

• When the game exits with code 0x80070424 (a Windows component it needs is missing), the menu explains the cause and how to fix it, in the eight supported languages.
• Failure reports now record whether the game package is registered in Windows and how the game was launched (store activation or executable).
• New troubleshooting entry for that exit code, with the repair steps for that component.
• Both official entries are unchanged and the unlock itself is unchanged. The binary is the same as v4.9.21 (9371baf3...).