Launcher has stopped working

[Raliken]

Launcher Version: 7.2

Operating System: window 7 64 bit

Java Version: Java jre 6 and 7

Antivirus Program:

Description of Problem:

Every time I try to start the launcher, I get an error saying that the launcher has stopped working. I have read all the forums and tried doing everything. Uninstall and reinstalled both javas and the launcher, nothing. Tried to download the linux version and do all that and it failed as well.

Error Messages:

Technic launcher has stopped working

Error Log:

[Miningshades]

I seem to be having the same problem as well, after a long string of being unable to connect to my friend's sever and finally attempting to clear the cache

Description:

Stopped working

Problem signature:

Problem Event Name:CLR20r3

Problem Signature 01:techniclauncher.exe

Problem Signature 02:1.0.1.0

Problem Signature 03:5064acfd

Problem Signature 04:mscorlib

Problem Signature 05:2.0.0.0

Problem Signature 06:4ef6c7cc

Problem Signature 07:3452

Problem Signature 08:119

Problem Signature 09:System.IO.DirectoryNotFound

OS Version:6.1.7601.2.1.0.768.3

Locale ID:1033

[QueueQueue]

I have the same exact problem;

Description:

Stopped working

Problem signature:

Problem Event Name:CLR20r3

Problem Signature 01:techniclauncher.exe

Problem Signature 02:1.0.1.0

Problem Signature 03:5064acfd

Problem Signature 04:mscorlib

Problem Signature 05:2.0.0.0

Problem Signature 06:4ef6c131

Problem Signature 07:34a5

Problem Signature 08:119

Problem Signature 09:System.IO.DirectoryNotFound

OS Version:6.1.7601.2.1.0.768.3

Locale ID:1033

[Jorcer]

I seem to be having the same problem as well, after a long string of being unable to connect to my friend's sever and finally attempting to clear the cache

Description:

Stopped working

Problem signature:

Problem Event Name:CLR20r3

Problem Signature 01:techniclauncher.exe

Problem Signature 02:1.0.1.0

Problem Signature 03:5064acfd

Problem Signature 04:mscorlib

Problem Signature 05:2.0.0.0

Problem Signature 06:4ef6c7cc

Problem Signature 07:3452

Problem Signature 08:119

Problem Signature 09:System.IO.DirectoryNotFound

OS Version:6.1.7601.2.1.0.768.3

Locale ID:1033

I have the same exact problem;

Description:

Stopped working

Problem signature:

Problem Event Name:CLR20r3

Problem Signature 01:techniclauncher.exe

Problem Signature 02:1.0.1.0

Problem Signature 03:5064acfd

Problem Signature 04:mscorlib

Problem Signature 05:2.0.0.0

Problem Signature 06:4ef6c131

Problem Signature 07:34a5

Problem Signature 08:119

Problem Signature 09:System.IO.DirectoryNotFound

OS Version:6.1.7601.2.1.0.768.3

Locale ID:1033

This is not your thread. Just saying "Me To" Is not helpful and makes it more difficult to help the OP. Post your own bug report AFTER using the search button at the top of the site.

[Ashzification]

First check here:

http://forums.technicpack.net/threads/common-problems-and-solutions.10851/

Troubleshoot:

Make sure your anti-virus and firewalls are disabled while trying to connect to minecraft.net (while logging in, connecting to a server)

Uninstall Java, then delete your .techniclauncher folder. Restart your computer (it's not required, but it never hurts to give it a break)

Reinstall the correct version of Java for your computer (ensure the bit type matches)

Redownload the Launcher.

Try to run the .exe, if this does not work, look in your .techniclauncher folder, make sure you have a .jar file in there.

If you do not, and the .exe doesn't work, do this:

I am getting a “Technic Launcher has Stopped Working Error”!

If your launcher is encountering this error, a solution is to download the .jar file from http://www.technicpack.net/download/ (pick the third from the left (Linux/Jar)). If you are using Internet Explorer you will also need to change the file extension (the ending of the file) to .jar instead of .zip. Once you’ve done that, all you need to do is double-click on the file to run the launcher.

If double click doesn't work with the .jar:

Right click on the .jar file, open with Java.

If none of those work, try running as administrator.