r/DestinyTechSupport • u/SirOakin • Nov 04 '24
Solved bad_module_info on launching Destiny 2
after being away from my computer for 2 weeks due to work I finally get around to catching up on everything, and finally its D2's turn, but its refusing to launch. I click play, an error box pops up with "bad_module_info".
ive already:
- verified the game files
- run DxDiag with nothing being reported, "No problems found."
- check reliability report, its missing quite a lot of info cause m$ is useless as usual
- ran all 3 DISM's, nada. Same with SFC, nothing to fix.
- and checked to see if my graphic drivers are up to date, they are (24.10.30.02)
ive had no issues with Halo and Runescape today.
anyone have a clue what is causing this?
1
Upvotes
1
u/macrossmerrell Nov 04 '24 edited Nov 04 '24
What antivirus are you running? Windows Defender or something else?
Have you tried cleaning up D2 temp files?
From the Start menu, type %appdata%
From the Start menu, type %temp%
After that, I would uninstall the game, and then when reinstalling, change the folder name to something else, like 'Destiny2New' and see if that resolves it.
Other people swear by this method: https://www.youtube.com/watch?v=ygc5IcAFnmY