FTB modpacks crashing upon keyboard input

  • 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
S

Starckboy

Guest
Title:
FTB modpacks crashing upon keyboard input
Launcher Version:
Curse
Modpack:
All of them
Modpack Version:
N/A
Log Link:
Details of the issue:
The game and launcher crash whenever I push ANY button. A window pops up stating that Java has encountered an error. The thing is the regular version of Minecraft works without flaw. I can get FTB to load all the way up and I can do anything I want but as soon as I touch any keyboard buttons it crashes immediately.
 
  • Like
Reactions: StanleyMines
S

Starckboy

Guest
I found out it was the Windows 10 anniversary update... I reverted back and FTB works now. I hope whatever is causing the bug gets fixed soon, I liked that windows build.
 
  • Like
Reactions: Robijnvogel
S

StanleyMines

Guest
Title:
FTB modpacks crashing upon keyboard input
Launcher Version:
Curse
Modpack:
All of them
Modpack Version:
N/A
Log Link:
Details of the issue:
The game and launcher crash whenever I push ANY button. A window pops up stating that Java has encountered an error. The thing is the regular version of Minecraft works without flaw. I can get FTB to load all the way up and I can do anything I want but as soon as I touch any keyboard buttons it crashes immediately.
My friend @bbdog1771 is having the same problem.


I found out it was the Windows 10 anniversary update... I reverted back and FTB works now. I hope whatever is causing the bug gets fixed soon, I liked that windows build.
You said that it is the windows 10 update thing, how exactly did you fix that, other than "I reverted back"? Could you explain how to do that? Thanks!