Hi, i installed this game through Galaxy to my Windows 10 64bits
GeForce GTX 1060 Palit 6GbRAM
Intel i7 7700k
16Gb RAM DDR4

and, as many users, launching it don't works.
No screen, just a process named "FrostPunk" using about 200Mo, and 0% of the CPU

Waiting 10minutes without a change

Drivers up to date, .NET Framework too, directX too

Help needed :)
Regards.

Same problem here... Tried on two different computers : an Intel i5 running Win10 & an Intel i7 running Win8.1, and neither works. Crashing instantly on launch with a simple "Frostpunk has stopped working" error.

Does that count as a double upvote on this issue? =(

Same Problem. I'm not getting an error or anything. It quickly tries to sync saves, which there are none of, and that's it. It's like it doesn't even try to launch.

When I try from the actual folder location it throws a missing file error. Sent a note off to support.

To bad, looks like a great game...

Hey guys.

Thanks for posting. Please make sure that your drivers are up to date and that the game itself is updated. It has also been brought to our attention recently that the presence of Razer Chroma SDK on your PC prevents the game from launching - this is also the case with other games, including Overwatch, so please temporarily uninstall this software and the game should work as intended. Should it not, please get in touch with us at techsupport@11bitstudios.com, we'll do our best to help you. :)

Cheers!

Unfortunately, some of us have never gotten Frostpunk, in any iteration or version (I have tried, including with the latest Winterhome patch/DLC) to work. Can load up the main menu just fine, but as soon as we click "New Game" it crashes on the loading screen with a fatal appcrash in frostpunk.exe each and every time.

I personally tried each and every suggestion that I scoured the internet and forums far and wide with drivers, settings, updates, hotfixes, etc and nothing worked. Thankfully, I have an alternate place to play and enjoy the game...just not at home.

Interested? My tale of woe is here in another thread. Thanks for your work, Peter.