Request FTB Infinity Lite and Direwolf20 1.10 not launching

[Darks_Anthro]

I've redownloaded the launcher several times and the "curse" launcher keeps sending me to vanilla launcher 1.6.70 where it sends me to the log in screen but it continues to present me with "Sorry, but we couldn't connect ourservers. Please make sure that you are online and that Minecraft is not blocked. (SocketTimeoutExeption: connect timed out)"

I've changed my mojang password three times. THREE TIMES IN ONE DAY! The non-curse client for FTB lets me use my account but it will not launch 1.10. It will however launch 1.7. How can I play the new Direwolf20 or Infinity for 1.10 if I can't even get it to launch from either launcher?

My system specs are as follows.
CPU: AMD FX-8350 Eightcore 4GHz
GPU: EVGA GTX 970 4GB FTW
Ram: Corsair Vengeance Pro 4x8G 32Gs total DDR3 1600MHz
OS: Windows 7 SP1
Due to an issue I was forced to reinstall my OS of Windows 7 SP1 but was out of the free upgrade date for Windows 10 even though before reinstalling Windows 7. I was using Windows 10.

Is 1.10 not compatible for Windows 7?

 

[erindalc]

Did you make sure Java was allowed through your firewall?

 

[Darks_Anthro]

Java is allowed by my Avast Firewall

 

[Henry Link]

We really will need the console log and maybe the crash report to help you. Can you copy the log file to http://paste.feed-the-beast.com/. The copy the URL out of your address bar and post it here. For the log if you open the folder for your instance there is a logs directory. The latest.log is what we are looking for.

 

[Darks_Anthro]

Well it doesn't crash..... The game doesn't even launch!
Here's what the console says: Exception in thread "main" com.beust.jcommander.ParameterException: Can only specify option --width once.
at com.beust.jcommander.ParameterDescription.addValue(ParameterDescription.java:235)
at com.beust.jcommander.ParameterDescription.addValue(ParameterDescription.java:210)
at com.beust.jcommander.JCommander.processFixedArity(JCommander.java:867)
at com.beust.jcommander.JCommander.processFixedArity(JCommander.java:849)
at com.beust.jcommander.JCommander.parseValues(JCommander.java:721)
at com.beust.jcommander.JCommander.parse(JCommander.java:281)
at com.beust.jcommander.JCommander.parse(JCommander.java:264)
at net.ftb.legacylaunch.Launch.main(Launch.java:41)

 

[Henry Link]

That isn't the full console log. Please use the steps I gave you to post the full log. Since you are using the legacy launcher it is even easier. Just the the "Upload Log" button the on console. Then copy the URL in the address bar here.

 

[Darks_Anthro]

YES! I got it to work! I removed all traces of ftb off my hdd and reinstalled the correct legacy launcher. Now it's launching. Apparently I was using a launcher that wasn't legacy. I see what you where saying now. If I have any issues with it. I know where to get the log.