I can't launch any modpacks in the launcher.

  • Tech Support section is for getting help with FTB related problems. If there's a repeatable issue that can be labeled as a bug, then please use the issue tracker for the pack or the app at GitHub issue trackers - If there's no repository for a pack that means that the pack is old and/or will not be updated. Bugs for older packs will not be fixed, unless they are critical.
  • 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

Reign Dance

New Member
Jul 29, 2019
36
0
0
Title:
I can't launch any modpacks in the launcher.
Launcher Version:
1.4.8
Modpack:
Infitech 2
Modpack Version:
3.1.9
Log Link:
Details of the issue:
Any time I try to launch any mod packs, it won't work. It tells me the check help.mojang.com to make sure none of the services are down; but they're all working fine.
 

Reign Dance

New Member
Jul 29, 2019
36
0
0
It says there's no connection when I click on the "news" tab. There aren't any firewalls blocking the connection either. My Internet connection is working just fine.
 

Reign Dance

New Member
Jul 29, 2019
36
0
0
I figured out the solution. I was getting an "unrecognized windows socket error 10106. After spending a while trying to figure out how to fix this, I ended up running the command prompt as an administrator (type cmd in the search bar, right click the cmd program and run as administrator). I then typed in "netsh winsock reset" without quotes and then pressed enter. Then I restarted my computer. Everything works fine now.
 

jikuja

legacy FTB Launcher developer
Launcher Developer
Global Moderator
Dec 17, 2013
1,134
111
99
I figured out the solution. I was getting an "unrecognized windows socket error 10106. After spending a while trying to figure out how to fix this, I ended up running the command prompt as an administrator (type cmd in the search bar, right click the cmd program and run as administrator). I then typed in "netsh winsock reset" without quotes and then pressed enter. Then I restarted my computer. Everything works fine now.

Nice work. I recently found that solution also. Now I know it really might help => it goes in my knowledge base.