11.0.3
11 Jul 2026
Offline auth routing improvements, CurseForge CDN patch, and targeted crash fixes across the instance matrix.
Deployment console
Prism Launcher 11.0.3
Select platform channel · Released 11 Jul 2026 · GPL-3
Channelstable
Version11.0.3
LicenseGPL-3
PlatformsWindows · macOS · Linux
Platform nodes
Pull a build for your OS
Windows
Windows 10 / 11 · MSVC · x64 · ~22.8 MB · Version 11.0.3
macOS
DMG · ~42.7 MB · Apple silicon and Intel · Version 11.0.3
Linux AppImage
Portable AppImage · ~102.6 MB · Version 11.0.3
Linux Flatpak
Flatpak · ~40 MiB · Version 11.0.3
Prerequisites
Deploy checklist
- Legal Minecraft account for authenticated multiplayer
- Windows 10+, current macOS, or 64-bit Linux desktop
- Visual C++ 2022 redistributable on Windows if MSVCP140 is absent
- Free disk for instance nodes, Java runtimes, and modpack archives
- Network for first Microsoft login and mod-platform downloads
SmartScreen signal
Windows may gate unsigned installers behind a reputation prompt — not a malware verdict. Confirm the file came from the official release channel, then use More info → Run anyway only if you trust the source. See diagnostics for the full route.
Release log
Channel history
11.0.2
Prior patch
Stability pass and download-path corrections on the 11.0.1 line.
11.0.1
Prior patch
Patch cycle for the 11.0.0 feature baseline.
11.0.0
Major line
11.x baseline — refreshed pack deploy tooling and instance routing.
10.0.5
10.x maintenance
Final maintenance cut before the 11.0.0 channel opened.
Integrity handshake
Verify before deploy
Match SHA256 hashes published beside release assets. Hash mismatch means discard and re-pull from the official channel.
INTEGRITY PROTOCOL
SHA256
Compare hashes on the official 11.0.3 release page before you install.
Signature Prefer signed / notarized builds when available
Source Public repository · GPL-3
CHECK SmartScreen may appear on Windows
CHECK Quarantine flags on macOS Gatekeeper
Links route to official GitHub release assets. Cross-check hashes on the 11.0.3 tag page.
Post-deploy issues? Route through diagnostics or the signal cache.
