If the instance will not create
An instance creation failure can happen before Minecraft starts. Check that PineconeMC can write to the selected data directory, that the disk has free space and that the requested Minecraft version and loader metadata are available.
Avoid placing a new instance inside a read-only system directory or a folder controlled by a sync tool that is still changing files. Create a temporary test instance in a simple writable path and compare the result.
- Confirm the data directory exists and is writable.
- Check available disk space and file permissions.
- Verify the Minecraft version and loader are available.
- Use the current official PineconeMC release.
- Read the creation log for the first failed download or write operation.
If Minecraft closes during startup
- Launch a clean vanilla instanceA vanilla test tells you whether the launcher and Java path work without mods.
- Confirm JavaCheck the Java runtime selected by the instance and compare it with the Minecraft version's requirements. A Java error can appear as a generic crash screen.
- Check the loaderForge, Fabric and NeoForge instances use different mod ecosystems. Make sure every mod belongs to the selected loader and Minecraft version.
- Undo the last changeRemove the most recent mod, shader, resource pack or configuration change and reproduce the problem.
- Read the first exceptionThe first named mod, missing dependency or Java exception is usually more useful than the final exit code.
Mod, loader and memory checks
| Check | Common mistake |
|---|---|
| Minecraft version | A modpack or mod targets a different release. |
| Loader | A Forge mod is placed in a Fabric instance, or the reverse. |
| Dependencies | A library or API mod is missing or too old. |
| Java | The instance uses an incompatible or damaged runtime. |
| Memory | Too little memory causes loading failure; too much can starve the operating system. |
| Shaders and renderers | OptiFine, Iris or other renderers are mixed without compatibility. |
Logs, backups and recovery
Keep the failing instance and make a copy before deleting or rebuilding it. Open the instance folder from PineconeMC so you know which directory is being inspected. Save the latest log and crash report, then remove only the last change for the next test.
If a clean instance works but the original does not, rebuild the pack in a new instance and add content in small groups. If a clean instance also fails, focus on Java, permissions, the launcher release and the operating system rather than the mod list.
Practical summary
A controlled ElyPrismLauncher instance will not start recovery
ElyPrismLauncher instance will not start is a symptom, not a diagnosis. PineconeMC can create the instance correctly while Minecraft, Java, a loader, a mod, a shader or a permission later prevents the game window from opening. Start by deciding whether the instance cannot be created, stops before the game window, crashes during loading or opens and then closes.
If the phrase ElyPrismLauncher instance will not start appears after a mod or loader change, remove only the last change and reproduce the failure. Keep a clean vanilla instance as a comparison. If vanilla launches, the launcher, data directory and basic Java path may be healthy; focus on the changed loader, dependency, configuration or memory setting instead of reinstalling the application.
Check the exact Minecraft version and loader before changing Java arguments. Forge, Fabric and NeoForge can require different versions and dependencies, and a mod built for another patch may fail with a misleading crash code. Read the first named exception or missing dependency in the log. The final line often describes the shutdown rather than the original cause.
Permissions and paths matter when an instance will not create or update. Use a writable data directory, avoid a full cloud-sync folder during testing and confirm that antivirus or ransomware protection is not silently blocking file creation. Do not grant broad administrator access or whitelist unknown files simply because a forum post suggests it.
Memory settings should be tested conservatively. Too little memory can stop a large pack, but allocating nearly all system RAM can make the operating system unstable and cause a different failure. Follow the pack recommendation, close other heavy applications and compare with a small instance.
When ElyPrismLauncher instance will not start after a world or configuration change, export or back up the instance first. Test by moving one optional mod or configuration file at a time, never by deleting a world folder blindly. A reproducible report should include the release, Minecraft version, loader, Java version, last change and first useful log line.
If a clean data directory starts the same instance, compare Java path, memory, account, proxy, custom commands and instance location with the old profile. If the clean directory also fails, preserve the log and verify the official release, system architecture and platform before opening an upstream issue.
- Separate creation, loading, crash and post-launch symptoms.
- Use a clean vanilla instance as a baseline.
- Back up worlds and export the instance before removing files.
Implementation notes
Keep an instance failure reversible
When the instance will not start, preserve the failing state before removing files. Export the instance or copy the world, record the Java and loader versions and save the first useful log lines. Then remove the last change or test a duplicate instance.
A working vanilla comparison narrows the search quickly. If it launches, compare the failing profile's loader, mods, memory, path and custom arguments. If it does not, verify the official launcher build, Java path, permissions and Minecraft files before investigating mod conflicts.
After a fix, launch the same instance twice and close it normally. This checks that settings are written and that the result is not a one-time startup. Keep the known-good export so a future modpack update can be rolled back without losing the world.
- Export before deleting or replacing instance files.
- Compare the same version with and without mods.
- Confirm the fix survives a normal restart.
Common questions
Instance troubleshooting FAQ
Why will a new instance not create?
Check write permissions, free space, the data path, metadata access and the exact version or loader request.
Why does a modpack close before the menu?
Common causes include Java, wrong loader, missing dependencies, incompatible mods, memory settings or a renderer conflict.
Should I allocate all my RAM to Minecraft?
No. Leave enough memory for the operating system and other applications. Increase memory gradually while checking the pack's requirements.
What is the most useful part of a crash report?
The first named exception, mod, dependency or Java message is usually more useful than the final generic exit code.