Minecraft Bedrock 26.40.31 Patch Notes (14th July 2026)

Posted: 14 July 2026

Information on Minecraft Preview and Beta:

• These work-in-progress versions can be unstable and may not be representative of final version quality
• Minecraft Preview is available on Xbox, PlayStation, Windows, and iOS devices. More information can be found at aka.ms/PreviewFAQ
• The beta is available on Android (Google Play). To join or leave the beta, see aka.ms/JoinMCBeta for detailed instructions

It's time for another Preview and Beta release! For the full list of goodies, browse the changelog below. And as always, we’re keen to get your feedback on these new features at feedback.minecraft.net, and you can report any bugs you find at bugs.mojang.com.

Items

• Arrows of Harming no longer bounce off entities and are now correctly removed on hit (MCPE-239756)

  Developer's Note: We saw community discussion around this change and wanted to provide some additional context. We know this fix may affect existing mob farms, but after reviewing the issue we felt that resolving the bug was the best decision for the game long-term. Two primary elements factored into our decision: From a technical perspective, this bug only existed due to a fundamental issue in how minecraft:projectile used to process its sub-components - an issue we were not comfortable preserving or introducing exceptions to support. Fixing that system-level issue implicitly removed the 'arrow killer' functionality that some mob farms made use of. From a design perspective, allowing a single arrow to infinitely kill mobs without despawning wasn't an intended mechanic, and not one we felt comfortable preserving long-term.

Stability and Performance

• Fixed several crashes that could occur during gameplay
• Fixed a bug where an incorrect device tier was selected on some devices, preventing players from turning on Vibrant Visuals (MCPE-239742)

Networking

• When connecting to a dedicated server, the client probes the server for NetherNet support with a 3 second timeout. WinHTTP does not honor this timeout in the following situation:
  • The client connects to the server by URL instead of IP.
  • The server hostname's DNS record contains multiple IP addresses.
  • The server is behind a firewall that drops the client's probe TCP packets instead of responding with an RST.
• Instead of a 3 second timeout for the entire connection attempt, WinHTTP enforces a (3 seconds) * (number of IP addresses in DNS record) timeout.
• This bug has been fixed by enforcing an overall 3 second timeout.