From my experience, this seems to occur when you run a mod prior to running the vanilla version. You also have to run the vanilla version using the updated launcher, if you did it with the old one but not the new one, this happens. In addition, if you do it wrong once, the launcher sends up some sort of flag or something and the profile doesn't work any more. Here's how to fix: 1. Delete whatever profile you were using to run the mod. 2. Run the vanilla version that the mod uses. (ie. if you were running Forge 1.9.4, you would run Vanilla 1.9.4) 3. Close that. 4. Create a new profile with whatever modded version you were trying to run. 5. Run that new profile. This should fix your problem. If it doesn't, then follow the same steps as before but delete the modded version you were using between steps 1 and 2, and then re-install the modded version between steps 3 and 4.
Kacey Theobald
From my experience, this seems to occur when you run a mod prior to running the vanilla version. You also have to run the vanilla version using the updated launcher, if you did it with the old one but not the new one, this happens. In addition, if you do it wrong once, the launcher sends up some sort of flag or something and the profile doesn't work any more. Here's how to fix:
1. Delete whatever profile you were using to run the mod.
2. Run the vanilla version that the mod uses. (ie. if you were running Forge 1.9.4, you would run Vanilla 1.9.4)
3. Close that.
4. Create a new profile with whatever modded version you were trying to run.
5. Run that new profile.
This should fix your problem. If it doesn't, then follow the same steps as before but delete the modded version you were using between steps 1 and 2, and then re-install the modded version between steps 3 and 4.