Skip to content

Diagnostics

Route faults without nuking your stack

Status-board troubleshooting for SmartScreen gates, VC++ runtime gaps, Java node mismatches, MultiMC imports, mod loader drift, and antivirus noise.

LauncherOK
JavaCHECK
AccountOK
Mods2 ISSUES
ImportMultiMC

Windows

SmartScreen blocks deploy

Signal: Windows protected your PC
01

Verify release channel

Pull the installer from the official 11.0.3 release page — not an unverified mirror.

02

Expand the gate panel

Open More info on the SmartScreen dialog to surface Run anyway.

03

Override only if verified

Proceed when source and hash check out, then finish the installer.

Resolved: Reputation gates fade as more operators run the same unsigned build.

Windows

MSVCP140.dll missing on launch

Signal: The program can't start because MSVCP140.dll is missing
01

Install VC++ redistributable

Deploy the latest Microsoft Visual C++ Redistributable (x64) for your Windows build.

02

Reboot if required

Some systems need a restart before the runtime path registers.

03

Relaunch the control plane

Start Prism Launcher from Start menu or desktop shortcut.

Check: Use Microsoft's official redistributable — never a third-party DLL drop.

Runtime

Assign the correct Java node

01

Open instance shell settings

Select the target instance — settings apply to that node only, not the global matrix.

02

Bind a Java runtime

Point to JDK or JRE matching the Minecraft version (Java 17 or 21 for most modern packs).

03

Tune memory ceiling

Raise max RAM for heavy packs but leave headroom for the host OS.

Resolved: Wrong global Java is the top cause of crash loops on legacy packs.

Migration

Import MultiMC instance nodes

01

Preserve source folder

Keep the MultiMC instance directory intact before migration.

02

Run Prism import route

Use Add instance → MultiMC-compatible import in the launcher.

03

Rebind Java and accounts

Verify loader version, Java path, and Microsoft account on the imported node.

Check: Worlds and mods should remain under the new instance shell path.

Gameplay

Mod lane mismatch

Signal: Game boots vanilla or dies during mod init
01

Confirm loader alignment

Forge jars need Forge nodes; Fabric jars need Fabric nodes. Mixed lanes fail hard or silently.

02

Match Minecraft version

A 1.20.1 mod will not run on a 1.21 shell without a compatible build.

03

Parse the instance log

Remove the first missing dependency or corrupt jar the log names.

Resolved: Clean pack deploys from Modrinth or CurseForge reduce version drift.

Security tooling

Antivirus quarantines the binary

01

Restore from quarantine

If AV removed Prism.exe, recover it from the quarantine panel first.

02

Add a scoped exclusion

Exclude only the verified install folder — not an entire drive or Downloads root.

03

Re-run integrity check

Compare SHA256 from the 11.0.3 release page before keeping the exclusion active.

Check: Heuristic engines often flag game launchers. Source audit details live on the trust protocol page.

Fault still open?

Query the signal cache for short answers, or review the trust protocol for license and source notes.

Download