My Launcher Wont Start?

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord

ouubanter

New Member
Jul 29, 2019
7
0
0
I am on Windows 8 64bit and have just updated to the new launcher but when i open up the .exe nothing happens, I have also tried using the .jar but no luck.When i have been previously using the old launcher it was working Fine?

Thanks for your time.
 

zzZombie

New Member
Jul 29, 2019
10
0
0
Are you seeing these errors in your console?

rom Console: Exception in thread "AWT-EventQueue-0"
From Console: java.lang.NumberFormatException: For input string: "0-oem"
From Console: at java.lang.NumberFormatException.forInputString(Unknown Source)
From Console: at java.lang.Integer.parseInt(Unknown Source)
From Console: at java.lang.Integer.parseInt(Unknown Source)
From Console: at net.ftb.util.winreg.JavaInfo.<init>(JavaInfo.java:60)
From Console: at net.ftb.util.winreg.JavaFinder.findJavas(JavaFinder.java:93)
From Console: at net.ftb.util.winreg.JavaFinder.parseWinJavaVersion(JavaFinder.java:128)
From Console: at net.ftb.gui.panes.OptionsPane.<init>(OptionsPane.java:128)
From Console: at net.ftb.gui.LaunchFrame.<init>(LaunchFrame.java:504)
From Console: at net.ftb.gui.LaunchFrame$1.run(LaunchFrame.java:274)
From Console: at java.awt.event.InvocationEvent.dispatch(Unknown Source)
From Console: at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
From Console: at java.awt.EventQueue.access$200(Unknown Source)
From Console: at java.awt.EventQueue$3.run(Unknown Source)
From Console: at java.awt.EventQueue$3.run(Unknown Source)
From Console: at java.security.AccessController.doPrivileged(Native Method)
From Console: at java.security.ProtectionDomain$1.doIntersectionPrivilege(Unknown Source)
From Console: at java.awt.EventQueue.dispatchEvent(Unknown Source)
From Console: at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
From Console: at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
From Console: at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
From Console: at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
From Console: at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
From Console: at java.awt.EventDispatchThread.run(Unknown Source)

If so you should try the steps in this guide. I had the same issue and uninstalling all versions of Java and only installing the latest build of Java 7 fixed my issue.
 

ouubanter

New Member
Jul 29, 2019
7
0
0
Are you seeing these errors in your console?



If so you should try the steps in this guide. I had the same issue and uninstalling all versions of Java and only installing the latest build of Java 7 fixed my issue.

No I am not there is no console or anything that shows up.
 

Wagon153

New Member
Jul 29, 2019
3,148
-3
1
Not sure if this is the same for windows but I occasionally get this on my linux OS. Make sure everything has permission to execute the file.
 

Zaflis

New Member
Jul 29, 2019
184
0
0
Would you open command prompt and type "java -version", then copy here what it prints.
 

Zaflis

New Member
Jul 29, 2019
184
0
0
I assume youre replying to me, in which case no. I mean the log from your FTB console
I meant it for OP. It is relevant to know if the OS environment variables have correct java path set to 64-bit binaries. Doing java -version tells all that, if it fails to run at all, it would be no wonder launcher won't start.
 

bajansam

New Member
Jul 29, 2019
74
0
0
I meant it for OP. It is relevant to know if the OS environment variables have correct java path set to 64-bit binaries. Doing java -version tells all that, if it fails to run at all, it would be no wonder launcher won't start.
This shows up in the FTB logs, which is why its always best to provide the pastebin from FTB :p But yeah, this could be the reason for the problem.
 

ouubanter

New Member
Jul 29, 2019
7
0
0
'java-version' is not recognized as an internal or external command,
operable program or batch file.

If you didn't understand the original post i meant that no ftb launcher even opens up and the ftb console dosen't open eiter
 

Zaflis

New Member
Jul 29, 2019
184
0
0
'java-version' is not recognized as an internal or external command,
operable program or batch file.

If you didn't understand the original post i meant that no ftb launcher even opens up and the ftb console dosen't open eiter
There should be a space between "java" and "-version" as i typed in my posts, because it is a command parameter.

I understood perfectly, ftb launcher will not even open if you don't have java installed properly. It wouldn't even write a log for you to copy, because that too requires java.
(You still didn't try to look for the log to copy here anyway?)

There are some guides around the net to set the environment path
http://www.java.com/en/download/help/path.xml
And java may install itself 32-bit and 64-bit versions.
64-bit version is by default in
C:\Program Files\Java\jre7\bin
and 32-bit is in
C:\Program Files (x86)\Java\jre7\bin
(Don't make the mistake to include x86 path)
 
Last edited:

ouubanter

New Member
Jul 29, 2019
7
0
0
There should be a space between "java" and "-version" as i typed in my posts, because it is a command parameter.

I understood perfectly, ftb launcher will not even open if you don't have java installed properly. It wouldn't even write a log for you to copy, because that too requires java.
(You still didn't try to look for the log to copy here anyway?)

There are some guides around the net to set the environment path
http://www.java.com/en/download/help/path.xml
And java may install itself 32-bit and 64-bit versions.
64-bit version is by default in
C:\Program Files\Java\jre7\bin
and 32-bit is in
C:\Program Files (x86)\Java\jre7\bin
(Don't make the mistake to include x86 path)
java version "1.7.0_60-ea"
java<TM> SE Runtime Enviroment <build 1.7.0_60-ea-b01>
java HotSpot <TM> 64-Bit Server VM <build 24.60-b03,mixed mode>
 

Zaflis

New Member
Jul 29, 2019
184
0
0
You are using so called "Early access" version of Java, which is kind of a beta release. Things may work or not, but the launcher is built for latest stable Java that is update 45 (yours is 60). We still don't know if this is the cause, just finding out things that seem unusual.