It’s been a few hours since the launch of the highly anticipated looter shooter, The First Descendants, but not all players can play the game. Many players are reporting that they cannot launch the game at all. The issues reported with the game are The First Descendant crashing at startup, not launching, and being stuck on the loading screen. If you have run into any of these issues, here are some things you can do.
The First Descendant Crashing and Launch Issues Fix
Fixing a launch problem with a game is not easy and requires some severe troubleshooting due to the sheer number of reasons that can lead to the problem, but here are some things that we think should help and, with some luck, get you playing the game.
Reboot the PC and Attempt to Launch the Game
If you have just downloaded the game and have not rebooted the PC after, try to do it now. More often than not, a simple reboot of the PC can fix various issues with games. So, go ahead and restart the PC. Once the PC restarts, try playing the game.
Verify the Integrity of Game Files
Once you have booted the PC, if the game fails to launch, there may be issues with the game files, such as corruption or missing files; try to run the Steam Verify Integrity of Game files. If you don’t know, then > go to Library > right-click on The First Descendant > Properties > Local Files > Click on Verify Integrity of Game Files. Wait for the process to complete and try to run the game.
Update the Game
The devs released a small patch for the game as we were writing the article. Ensure that you have the latest patch. If the update fails to appear, close the Steam client and restart Steam. You should not be able to see the download.
Here are some other general fixes you should consider:
- Update the graphics card drivers
- Install the game on an SSD and preferably the same place where the Steam client is installed.
- Allow the game in your antivirus or firewall software.
Unfortunately, if the First Descendant is still failing to launch, there is nothing more you can do now. The issue seems to be quite widespread. We will update this post if we find a new solution.