Forspoken Keeps Crashing on Startup Fix

Forspoken, the hotly-anticipated open-world action-adventure game from publisher Square Enix, is finally out. The game has been met with a lot of criticism, much of which has been centered around the game’s technical issues. This especially applies to PC players. One of the biggest problems that PC players are facing is that the game keeps crashing on startup. Consequently, the game is not launching. So is there anything you can do to resolve this issue? We are going to go over several methods that can be used to fix the Forspoken keeps crashing on startup error right here.

How to Fix Forspoken Keeps Crashing on Startup

To begin with, why is this happening in the first place? Well, it appears that the game isn’t very well optimized for the PC. This, unfortunately, exacerbates these issues even more. So, let’s see what you can do on your end. First, try restarting your computer to see if the game will start after that. After that, go to the installation directory of the game. Find the application file itself and right-click on it. From there, go to Compatibility and turn on the “Run this program as an administrator” option. Next, try verifying your game files. To do this, go into Steam, and find Forspoken there in your list of games. Right-click on it, select “Properties” and then “Local Files” and choose “Verify integrity of game files.” Note that this can take a while.

If the problem is still persisting, you should check to see if you have the latest graphics drivers installed. For Nvidia GPUs, go here. And for AMD devices, here. In cases such as this, you should likewise always check to see if your Antivirus program is the one that is preventing the game from launching. If you are getting error messages such as “vcruntime140_1.dll missing”, or “MSVCP140.dll was not found”, the problem is down to you not having the required version of Visual Studio. You can download it here.

And if none of these methods are working, the only thing left is to wait until the developers have addressed these issues in a future patch. We hope that it is coming soon. If you have any other advice on how to fix this problem, then feel free to share your approach in the comments.