Problem when lauching a modpack (lwjgl.dll: Can’t load IA 32-bit .dll on a AMD 64-bit platform)

  • 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

TyrantRC

New Member
Jul 29, 2019
2
0
0
Title:
Problem when lauching a modpack (lwjgl.dll: Can’t load IA 32-bit .dll on a AMD 64-bit platform)
Launcher Version:
1.4.8
Modpack:
Any from what I have seen
Modpack Version:
N/A
Log Link:
Details of the issue:
Whwn I try to launch any modpack I get that error message

I tried the basic troubleshooting guide, since this is my first time trying to run ftb since like 2 years ago I'm not really trying to load any old save or anything, everything is new, even the java installation and I have no idea what to try now.

I also tried updating my AMD video drivers and didn't do anything.
 

Moasseman

New Member
Jul 29, 2019
1,679
-2
1
Try going to elevated cmd (right-click cmd.exe -> run as admin) and inputting

sfc /scannow

SFC stands for System File Checker, and it basically just checks for corrupted/broken system files

Make sure not to close the CMD window before the scan is complete (100%)
 

TyrantRC

New Member
Jul 29, 2019
2
0
0
Try going to elevated cmd (right-click cmd.exe -> run as admin) and inputting

sfc /scannow

SFC stands for System File Checker, and it basically just checks for corrupted/broken system files

Make sure not to close the CMD window before the scan is complete (100%)

I did what you said and I got this message

Windows Resource Protection found corrupt files and successfully repaired
them. Details are included in the CBS.Log windir\Logs\CBS\CBS.log. For
example C:\Windows\Logs\CBS\CBS.log

It seems like it repaired something, I try to launch the pack after that and it went ok, I haven't play yet, but at least I can enter the minecraft main screen now, thanks for your help dude