Skip to content
A painted Planet Zoo 2 promotional scene with a tiger family, a toucan and a zoo aquarium
Updates and TroubleshootingConfirmed

Planet Zoo 2 Crashing: PC Checks

Quick Answer

For Planet Zoo 2 crashes on PC, check requirements, game files, drivers and overlays, then match repeatable actions to Frontier’s issue list. Save manually; fixes listed as being tested are not released patch notes.

On this page

If Planet Zoo 2 keeps crashing on PC, first separate a launch failure from a crash tied to one action in a zoo. Check your system against the published requirements, verify the game files and review drivers and overlays. When the same action repeatedly triggers the crash, check Frontier's current issue status before rebuilding your zoo or assuming that your hardware is responsible.

These checks follow Frontier's PC troubleshooting article. They are diagnostic options, not guaranteed fixes, and they do not establish a console-specific repair.

Identify the failure before changing settings

What happensStart hereRecord before retrying
The game fails to launch or closes before you can playRequirements, game-file verification, drivers and overlaysExact message or error code, launcher and when it closes
It closes during an otherwise running zooCompare the circumstances with Frontier's known issuesThe selected tool, objects or animal action immediately before the crash
It freezes without closingCheck whether the action is listed as a soft lockWhich tool stopped responding and whether the same action repeats it
A “Failure to Save” message appearsFollow the separate saved-folder guidance belowExact message and whether Windows can find Saved Games

A crash, a soft lock and a save error can require different investigations. Do not treat a missing save folder as proof that a driver reinstall will help, or treat a listed tool problem as a universal explanation for every crash.

Check the latest published issue status

Frontier's Under Investigation notice, last updated 20 October 2026, named 1.0.5, released 16 October, as its latest game update. It described fixes being tested for the next update, explicitly warning that the list was not final patch notes.

That notice listed crashes linked to:

  • Multi-selecting grid pieces.
  • Releasing animals into Franchise Wildlife Reserves.
  • Selecting recent colours in the flexicolour menu.

It also listed soft locks associated with the path stamp tool and switching from the terrain tool to another tool with a controller. Match the specific trigger rather than treating all construction or all Franchise play as broken.

The planned update window was a target, not a confirmed release. Use the published update list to check whether a later release actually includes your fix. This page does not turn “testing a fix” into “fixed in the version you have installed.”

Protect your progress before reproducing a crash

The same investigation notice described an autosave timer problem when entering Planet Hub. Frontier recommended saving manually frequently and loading through My Saves on the main menu to avoid overwriting an autosave.

Planet Zoo 2 Load window with saved zoo cards and their timestamps

Check the zoo and timestamp on the save you intend to load.

Use that advice before repeatedly testing the action that causes your crash. Write down what you changed and compare one relevant setting or condition at a time; this is a troubleshooting method, not a published game requirement. If you cannot get far enough to save, skip to the launch checks and report that limitation.

Work through the PC checks in a useful order

  1. Check the published requirements. Compare the operating system, CPU, memory, GPU, DirectX and free storage with the configuration guide. Meeting a specification does not prove that an unrelated tool crash is fixed.
  2. Verify your game files through your launcher. Frontier lists file-integrity verification among its initial checks. Complete that check before making several unrelated changes at once.
  3. Review the graphics driver. Frontier recommends updating drivers or making a clean reinstall. If the failure began with a driver update, its guidance also allows testing an older driver that previously worked; that is an option for that circumstance, not a reason everyone must downgrade.
  4. Update Windows and test without overlays. Frontier specifically names Steam, Xbox, Discord and GeForce overlays. It also suggests closing background programs that add recording or overlay features. Compare the same launch or in-game action after the change.
  5. Review antivirus handling. If the game is being wrongly flagged, use the application's specific allow-listing process. This does not require leaving protection disabled for normal use.
  6. If you can reach the game, test its display settings. Frontier lists full-screen mode and lower graphics quality as possible troubleshooting measures. A temporary resolution change is another published option, not a promised performance fix.

Stop treating the checklist as a race once you have a reproducible difference. Record the result so that a support request can distinguish an action-specific failure from an overlay or driver-related change. There is no verified universal preset or launch option here that prevents every crash.

Handle “Failure to Save” separately

Frontier says this specific error can occur when the game cannot locate the default Windows Saved Games folder. Its support article gives the path as C:\Users\%username%\Saved Games.

Enter shell:SavedGames in File Explorer to locate the folder. If it is missing, Frontier provides a Restore_Saved_Games_Default_Location.bat attachment in the official support article. Use that original support source and its instructions; this site does not host a replacement script. If the error continues, include it in your support request rather than assuming that a successful graphics check resolved it.

Send a report that can be investigated

If the game prompts you to send a crash report, Frontier asks you to select Submit. For a persistent problem, use the request link in its PC troubleshooting article or the Planet Zoo 2 issue tracker for the appropriate report.

Include the action leading to the failure, whether it happened the same way before, any unusual behaviour beforehand, and whether other programs or games have also crashed. Attach the requested DxDiag and relevant screenshots or footage. Frontier also asks for your Steam64ID to help connect submitted crash reports: open your Steam account menu, choose Account details, and find the 17-digit SteamID below the username. Send account and diagnostic information through the support form rather than a public comment.

A well-described report does not guarantee a repair date. It gives support a clearer starting point than “it crashes sometimes” and avoids treating an older Planet Zoo issue as evidence about the sequel.