Crashes & launch errors
Fixes and next steps when Horses of Hoofprint Bay crashes, will not start, or shows a black or grey screen.
If Horses of Hoofprint Bay crashes or will not start, first update the game and restart Steam. For crashes, the developer asks players to send a bug report with F8 in game, or email the log files to support@thoglistudios.com. For the Windows error “an application control policy has blocked this file (0x11C7)”, players suggest checking the .exe properties and running it as administrator.
Report the crash to the developers#
The developer’s advice for crashes is to send a bug report with more information using the F8 key in game, or to send your log files to support@thoglistudios.com. The log files are called player.log and player-prev.log. For the demo, the developer gave the folder C:\Users\USERNAME\AppData\LocalLow\ThogliStudios\Horses of Hoofprint Bay Demo; the full game is likely in a similar ThogliStudios folder.
“Failed to start process” (0x11C7) on Windows#
Some players see “failed to start process for this game: an application control policy has blocked this file (0x11C7)” on Windows 11. A community helper suggests it is likely a permission problem: open the properties of the game’s .exe and try launching it as an administrator. If Windows security policies are managed by your workplace or school, you may not be able to change this yourself.
Black or grey screen#
In the February demo, a bug froze the first riding lesson on a grey screen for fresh installs of version 0.1.8; players report it was fixed by an update. On Linux and Steam Deck, players with black screens suggest reinstalling and setting the compatibility tool to Proton Experimental.
Crashes when starting a new day#
Players reported the game crashing when loading the next day after riding or training. A community helper replied on November 6, 2026 that the bug had been identified and a small patch released, so update the game first. One player says the crash came back a day later; if it happens to you, send a bug report with F8.
“Failed to load il2cpp”#
Since a recent update, some players see “Failed to load il2cpp” when starting the full game, sometimes with a Windows message that the game is not signed correctly. No official fix has been posted yet. One player suggests rolling back NVIDIA graphics drivers, which helped with a similar error in another game. As general Steam troubleshooting, you can also verify the integrity of the game files in Steam. Report the error with your log files so the developers see it.
What still needs verification
An official fix for crashes when loading a new day, and the exact log folder name for the full game, need confirmation.
This page reflects official information and Steam Community answers reviewed on November 6, 2026. Player answers are identified as community reports in the text and sources. It has not been verified against a specific playable build. Suggestions are editorial guidance, not tested outcomes.
Frequently asked questions
How do I report a bug?+
Press F8 in game, or email your log files to support@thoglistudios.com, as the developer recommends.
Where are the log files?+
In the ThogliStudios folder under AppData\LocalLow, named player.log and player-prev.log.
My whole PC restarts when I launch the game. Is that the game?+
Other players had not seen it in the demo. It may be specific to your computer; a bug report helps the developers check.
What does “Failed to load il2cpp” mean?+
The game cannot load part of its engine. No official fix yet; verify the game files, consider your graphics drivers, and report it.
Sources
- Steam discussion: Is anyone else experiencing crashes? (developer reply) ↗
- Steam discussion: game failed to start process (player answers) ↗
- Steam discussion: Linux/SteamOS & controller Support? (player answers) ↗
- Steam discussion: new days not loading (community helper reply) ↗
- Steam discussion: um how do u start up the game — “Failed to load il2cpp” (player reports) ↗
Game: Horses of Hoofprint Bay · Release: November 4, 2026 · Images © Thogli Studios. Editorial policy