Field notes · Troubleshooting

Planet Zoo 2 won’t launch on PC: what to check

Use the trigger to choose a next step, and keep a record of what actually changes. A longer list of unrelated tweaks is not a diagnosis.

The short answer

First separate a Play button that resets from a crash that began after changing display settings. Check the current game update and verify the files before trying the matching reported workaround. The Visual C++ repair below has both a success and a failure in the same thread; none of these steps is a guaranteed fix.[1][2]

Start with the crash trigger: Play returns to Play: Check files, then the, reported runtime repair.; After display changes: Preserve settings; review, the configuration report.; Crash inside a zoo: Record the exact action, and submit the crash report.
Field Guide editorial diagram. This is a decision aid, not the game interface.

Start with the official checks

  1. Confirm your PC meets the game’s requirements and finish any pending game update.
  2. In Steam, open the game’s Properties → Installed Files → Verify integrity of game files.
  3. Review the GPU driver and Windows update state. If an issue began immediately after a driver update, tell support the previous and current driver versions rather than assuming that “newest” proves compatibility.
  4. Temporarily close overlay or recording software and retry once with the same launch conditions.

These are checks in Frontier’s PC troubleshooting guidance, not evidence that every startup crash shares one cause. If an error or crash-report window appears, retain its wording and submit the report.

[1]

Frontier Support · PC launch and crash troubleshooting ↗ (external site, opens in a new tab) is the appropriate action page for error-specific help.

Play resets: the reported Visual C++ repair

In the 13 October Steam thread, summraes reported success after repairing the installed Microsoft Visual C++ x64 redistributable. The original questioner, 岑冠希, explicitly said that the same repair did not resolve their problem.[2]

  1. Open Windows Settings → Apps → Installed apps.
  2. Find the installed Microsoft Visual C++ v14 x64 redistributable; its label may include 2015–2022.
  3. If it offers Modify → Repair, run that repair, restart Windows and retry the game.
  4. If it makes no difference, record that outcome. Do not repeatedly repair it or install runtime files from an unverified download site.

Evidence: one reported success and one reported failure in the same thread. This is a narrowly scoped community workaround, not a confirmed fix for everyone.

A crash after switching to full screen or 120 Hz

Longjumping-Call2594’s launch-window report describes a crash after display changes and then repeated startup failures. A reply from NewAd1135 suggested recreating graphics.config under the Frontier Developments local app-data area.[3]

The directly opened source did not establish a confirmed success for the questioner. Treat this as a configuration hypothesis: close the game, preserve a backup, and ask support to identify the relevant settings file if you cannot confidently distinguish it from saves. Do not delete the whole Frontier Developments folder.

There is a useful limit here: generic advice to switch to full screen is a poor first experiment if full screen was the change immediately preceding your failure. Tell support the trigger, refresh rate and display mode instead of repeating that change.

When to stop and send a useful report

If a repeatable launch still fails after the matching checks, collect your platform/store, CPU/GPU/RAM, Windows and driver versions, exact trigger, error text and the result of each attempted step. Keep launch crashes separate from an in-zoo crash after an action such as entering the Hub.

Frontier’s 1.0.4 notes list stability and crash changes. They do not establish that a particular player’s earlier launch failure is fixed. Check which build you are actually running before comparing outcomes.[4]

Frontier Support · troubleshooting and request options ↗ (external site, opens in a new tab)

Sources & verification

  1. Frontier Support · PC launch/crashing issues ↗ (external site, opens in a new tab) — Official checks; updated 14 Oct 2026. Broad troubleshooting is not a diagnosis.
  2. Steam · Game failed to launch ↗ (external site, opens in a new tab) — 13 Oct 2026; same-thread Visual C++ success and failure.
  3. Reddit · Game Crashing ↗ (external site, opens in a new tab) — Display-setting trigger and a single-source configuration suggestion; no personal testing.
  4. Frontier on Steam · Update 1.0.4 ↗ (external site, opens in a new tab) — Official crash/stability changes; individual older reports have unknown builds.

Checked 15 October 2026. Research-based guidance; we have not personally tested these setups or fixes. Earlier player reports may describe an older build.

Back to guide ↑