Crash when creating/joining games

When attempting to create or join a game through the client the game instantly crashes(before Forged Alliance visually starts). The error message is consistent. "Forged Alliance terminated with exit code -1073741701" , but that doesn't really help address the issue.

I just reinstalled FAF Sunday evening, and I tried reinstalling Forged Alliance to see if that was the issue.

Any idea about how to address this?

Here's what I think is the relevant section of the log, though I'll attach a complete log as well.

2022-01-25 21:01:37.734 INFO 1644 --- [Thread-74] c.f.client.fa.relay.ice.IceAdapterImpl : Starting ICE adapter with command: [e:\indie\faf\faf client\jre\bin\java.exe, -jar, E:\Indie\FAF\FAF Client\natives\faf-ice-adapter.jar, --id, 30334, --login, Tavar, --rpc-port, 51246, --gpgnet-port, 48278]
2022-01-25 21:01:39.285 INFO 1644 --- [Thread-74] c.f.client.fa.ForgedAllianceService : Starting Forged Alliance with command: [C:\ProgramData\FAForever\bin\ForgedAlliance.exe, /init, init.lua, /nobugreport, /log, C:\ProgramData\FAForever\logs\game_16214138.log, /gpgnet, 127.0.0.1:48278, /mean, 1114.49, /deviation, 93.484, /savereplay, gpgnet://127.0.0.1:61954/16214138/Tavar.SCFAreplay, /country, US, /clan, SB, /numgames, 84, /numgames, 76] in directory: C:\ProgramData\FAForever\bin
2022-01-25 21:01:39.423 INFO 1644 --- [ForkJoinPool.commonPool-worker-15] com.faforever.client.game.GameService : Forged Alliance terminated with exit code -1073741701
2022-01-25 21:01:40.177 INFO 1644 --- [Thread-74] c.f.client.fa.relay.ice.IceAdapterImpl : ICE adapter terminated normally

client.log

Before you do anything else - make sure that you have started the game through Steam at least once. The installation process may not be complete: additional packages are downloaded on your first launch through Steam.

If that doesn't help, you can review the steps to attach the debugger here:

Report back with the complete game log.

A work of art is never finished, merely abandoned

Thanks for the directions. With the download I was able to identify the issue: there were still some files from a very old version of FAF still around, including an older version of the executable of the game, and the client seems to have been trying to start that one. Fully deleting the older files has resolved the issue.