VoidLauncher Not Working / Not Installing Correct Version

The VoidLauncher can often fail to update itself correctly and this will lead to it installing older versions of modpacks or failing to install them at all. If you suspect that the VoidLauncher has found itself in this state then a complete re-install of the Launcher is probably your best option:

  • Delete the VoidLauncher Config Files
  • Download the Latest VoidLauncher
  • Run the New Launcher


Delete the VoidLauncher Config Files

Sometimes old config files will cause newer versions of the Launcher to malfunction. It's easier to delete them:

  • Open VoidLauncher
  • Click the Cog icon at the very top right of the Launcher
  • Make a note of the 'ModPack Installation Directory'
  • Close the Launcher
  • Use Explorer/Finder to browse to the 'ModPack Installation Directory'
  • Delete the folder named '.VoidLauncher'
Please note that this will remove your Minecraft login details from the launcher, so make sure you have them handy for later.

Download the Latest VoidLauncher

Run the New Launcher

  • You will need to re-enter your Minecraft login details at the bottom
  • Go to the 'Modpacks' tab
  • Find and click on the Modpack that you are playing
  • Click on the 'Re-Install' button
  • 7 Users Found This Useful

Was this answer helpful?

 Print this Article

Also Read

Ender Storage in Deep Dark Prevents Server Start

The following error occurs when the server starts: java.lang.NullPointerException at...

Diagnosing lag issues with a Timings report

If you are running a server with many plugins it can be very difficult to diagnose performance...

Enabling Disabled mods

Some modpacks do not have all the mods enabled by default, this guide explains how to enable...

Client crash when joining server - Ticking Screen - Map Writer config error

This crash has been observed on Yogscast Complete but is not limited to that modpack Symptoms...

Server is still starting! Please wait before reconnecting.

If you have recently updated a modpack to a newer version, you may receive the above message...