The game fails to start on Killing Floor 2.
The game fails to start on Killing Floor 2.
I've got Killing Floor 2 set up again. It's a new install since it didn't load before, and I transferred it to an SSD. For some reason it's not starting. Steam displays it as launching but nothing happens. The game ran smoothly before. After playing the last time, I upgraded my CPU and BIOS.
It didn’t work initially, so I reinstalled the game again but still nothing happened. I just updated the drivers. At least the Killing Floor start screen appeared. PCPartPicker list shows the following components: CPU – AMD Ryzen 7 5700X 3.4 GHz 8-core ($189.25 on Amazon), Motherboard – ASRock Fatal1ty B450 Gaming-ITX/ac Mini ITX AM4 ($145.59 on MemoryC), RAM – Corsair Vengeance RGB Pro 16 GB (2 x 8 GB) DDR4-3000 CL16, Storage – Intel 660p 1.02 TB M.2-2280 PCIe 3.0 X4 NVME SSD ($79.50 on Amazon), and a 2 TB 2.5" Crucial MX500 SSD ($127.19). The hard drive is Seagate BarraCuda 1 TB 3.5" 7200 RPM (internal, $63.59). I also added an XFX RX 5700 8 GB graphics card and a Fractal Design Define Nano S mini case. The power supply is SeaSonic FOCUS SGX 650W, certified for SFX, $192.74. For display, I got the LG 25UM58-P 25.0" 2560x1080 monitor at 75 Hz and the LG 34WN80C-B curved model at 3440x1440 at 60 Hz. The total comes to about $1433.85, including shipping and taxes. All prices are from PCPartPicker as of March 1, 2024.
A user shared a similar issue on Steam and offered potential solutions. The advice involves locating the KF.exe file in your Steam installation directory, right-clicking it, selecting properties, and enabling the "run as admin" option. Running games this way may require admin rights, which can affect compatibility. You can try launching the game through Steam or directly via the .exe file while Steam is active.
Thank you for the guidance. One of the ideas was to remove the config file in the My Documents folder for KF2. Eventually it helped, but I couldn't delete it because it was linked to another drive. For anyone encountering this, I had to check the drive settings and exclude that folder from backups. After that, it worked.