Guides
SmartScreen scares, missing VC++ runtimes, Java mismatches, MultiMC imports, silent mod failures, and over-eager antivirus — solved step by step.
Windows
Check the link
Use prismlauncher.io download buttons — they point at GitHub release assets, not random mirrors.
Reveal Run anyway
Click More info on the SmartScreen sheet.
Proceed deliberately
Run anyway only when you trust the file, then finish the installer.
Windows
Install Microsoft VC++
Grab the latest Visual C++ Redistributable (x64) from Microsoft for your Windows version.
Reboot if prompted
Some systems need a restart before the DLL path updates.
Launch again
Start Prism Launcher from the Start menu or desktop shortcut.
Runtime
Open instance settings
Highlight the instance — settings apply to that folder only.
Pick a Java build
Modern packs often want Java 17 or 21; older Forge may differ.
Allocate RAM wisely
Raise max memory for heavy packs but leave breathing room for the OS.
Migration
Back up the folder
Keep the original MultiMC instance directory until import succeeds.
Import in Prism
Add instance → choose the MultiMC-compatible import route.
Revalidate loader + login
Confirm Java path, loader version, and Microsoft account after the move.
Gameplay
Match the loader
Forge jars on Forge, Fabric on Fabric — cross-loader mixes fail fast or fail weird.
Match game version
A 1.20.1 mod will not run on a 1.21 instance without a compatible release.
Read the crash log
Open the instance log and remove the first missing dependency or corrupt jar.
Security tooling
Restore from quarantine
If AV removed PrismLauncher.exe, pull it back from the quarantine list.
Add a tight exclusion
Allow only the Prism install directory you trust — not whole drives.
Re-hash the file
Compare SHA256 on the GitHub 11.0.3 release page before keeping the exclusion.
Try the FAQ for quick hits, Trust for licensing context, or re-fetch the download if files look tampered.
Download
