A shift will not load after changing versions

If you rolled back after saving in 1.0.4

Close the game and preserve a copy of the shift files before experimenting with other builds. A save written by 1.0.4 cannot be opened by an earlier build. Return to the version that wrote the save before testing that slot again. If you need to play on an older installation, use a separate copy that was actually saved on that earlier version.

If the current build can open the slot, check the shift objective and the last purchase you remember. This gives you a checkpoint before you save again.

If you loaded successfully but progress looks older

When the current save is damaged, 1.0.4 can load the previous backup automatically. An earlier objective or a missing recent purchase is consistent with that fallback, although selecting a different manual slot can look similar. Check the selected slot and compare a recognizable checkpoint before deciding which file failed.

Preserve both the loaded state and any separate dated copy. Record the build, slot and last action you expected to see. The studio does not specify a guaranteed backup interval, so use the last checkpoint you can actually verify when describing lost progress.

No Load entry after a first-session crash

First establish whether you ever made a manual save. In the Steam report, the player crashed before creating their first save and later identified that as the reason the menu did not show Load. If this was your first session and you have no earlier progress, start a new shift, save it manually, and check that the slot appears when you return to the menu.

If a slot you previously loaded is now missing, copy the save folder before starting another shift. The developer asked the player to update past the damaged-save fixes in 1.0.3 and send Player-prev.log if the slot still failed to appear. This avoids writing a test save over progress you already had.

Developer reply and player follow-up after a first-session crash ↗

Golden Horn Studios: hotfix 1.0.3 ↗

An item from the old shift appears in a fresh New Game

The 1.0.4 notes list a fix for old items showing up in a new game. Check the version on the main menu first. Preserve the existing saves, start a fresh shift in a separate slot, and look for the specific old object before buying or unlocking anything. Compare it with the same object in the previous shift. If the problem remains, name the object and the two slots in a report and keep the old and new files separate. A deliberate return to the hangar through Continue Playing is expected to retain the finished shift.

Golden Horn Studios: patch 1.0.4 ↗

Golden Horn Studios: logs and reporting address ↗

Dying early takes you into someone else’s shift progress

A fix in patch 1.0.4 concerns an early death that loaded another run’s save. If the room or objective after respawning belongs to a different run, avoid manually saving over it. Return to the menu, check the version, then select your intended shift by its slot and compare an identifiable objective or purchase. Keep copies of both slots if the mix-up happens again. Tell support which slot you started from, how early the death happened, and what proved the loaded shift was the other one.

Golden Horn Studios: patch 1.0.4 ↗

Golden Horn Studios: logs and reporting address ↗

Switch between active shifts without sharing the latest autosave

A player revisited an old shift and lost the newer shift’s autosave. Before switching, save the active run to its own numbered manual slot. Keep a different slot for the other run and note one recognizable objective from each. When you return, choose the numbered slot for that run. The newest autosave follows the session you last played. A player reply identifies five numbered slots, which lets you keep both active shifts apart from the finished archive.

A player opening an old shift reports overwriting a newer autosave ↗

PCGamingWiki: contributor inspection of settings, controls, save files and Steam Input ↗

Golden Horn Studios: 1.0.3 completion slots and Windows graphics changes ↗

Only steam_autocloud.vdf is left in the save folder

A contributor inspecting Potato Please found steam_autocloud.vdf beside the game’s binary .sav files. The VDF is Steam’s Auto-Cloud metadata; the manual slot and autosave are the actual shift data. Leave the VDF alone. Check the correct Windows user, your dated copy and the signed-in Remote Storage listing for a .sav with the expected name and timestamp. Renaming the metadata file to slot_1.sav cannot reconstruct the missing progress.

PCGamingWiki: contributor inspection of settings, controls, save files and Steam Input ↗

Public Steam application configuration for game 5266240 ↗

Player opens a save folder and sees only steam_autocloud.vdf ↗

Valve: signed-in remote files for Potato Please ↗

An older build is missing from the version picker

Right-click Potato Please in Steam, open Properties > Game Versions & Betas, and inspect the builds offered to your account. On November 14, the public configuration for retail app 5266240 listed only public, build 26529021. No public branch named 1.0.3 was listed. Valve lets studios choose which branches to expose. A patch announcement or an older build number does not give you a selectable release. Keep a pre-update save if you depend on that format.

Valve: choosing a game branch in Properties, with an illustrated example ↗

Retail app 5266240: current Steam Cloud rules and public branch metadata ↗

Golden Horn Studios: patch 1.0.4 save format and backup behavior ↗

Understand a delayed update before recording an old-build run

Open Properties > Updates in the game's library entry. The launch-only setting delays automatic downloading until you launch. If an update is available, launching the game can install it before the shift starts. Record your current build and make a copy of your local shift while the game is still closed. For a version-specific comparison, check whether the studio actually offers the matching branch and record the build that ran after the download.

Valve: manage game downloads and per-game update choices ↗

Valve: choosing a game branch in Properties, with an illustrated example ↗

Golden Horn Studios: patch 1.0.4 save format and backup behavior ↗

Prepare the game for an offline trip before losing the connection

While connected on the laptop you will take, finish Steam's pending downloads and launch Potato Please once. Load a shift you recognize, close normally, and let Steam finish its sync. In the Steam menu choose Go Offline, then try launching the game and opening that same slot on the laptop. A successful offline test establishes that this installation and save are ready. Keep a local copy before travelling and reconnect that laptop before starting the shift on another device.

Valve: preparing an installed game for Offline Mode ↗

Valve: Steam Cloud conflicts, lost progress and log files ↗

Retail app 5266240: current Steam Cloud rules and public branch metadata ↗

A verified installation still has the wrong shift

When Verify integrity completes, Steam has checked the installed program files. The player who lost an hour after revisiting an old shift had an overwritten autosave, not a missing game executable. Check your separate numbered slot, an external dated copy, or a previously configured File History backup. For a damaged rather than overwritten save, the developer says version 1.0.4 can fall back automatically. The checkpoint in the loaded slot is the test of restored progress.

Valve: verifying installed game files ↗

Golden Horn Studios and player discuss overwritten autosaves and separate slots ↗

Golden Horn Studios: patch 1.0.4 save format and backup behavior ↗

A recovered copy belongs to a different slot on the destination PC

With the game closed, keep separate copies of both complete Windows game-data folders outside LocalLow. A matching filename such as slot_1.sav identifies the slot number, not the person or the run. To inspect the recovered game independently, sign into a separate Windows user profile, keep the game's Steam Cloud disabled for that test, and place a copy under that profile's GoldenHorn\PotatoPlease\saves path. Confirm the expected objective through Load. Leave the original user's files in place; re-enable sync only after deciding which files belong to the active Steam account.

Windows retail files inspected by a PCGamingWiki contributor ↗

Retail app 5266240: current Steam Cloud rules and public branch metadata ↗

Valve: Steam Cloud conflicts, lost progress and log files ↗

Golden Horn Studios and player discuss overwritten autosaves and separate slots ↗

Keep both copies when two PCs advanced the same slot

If the same numbered slot advanced independently on two PCs, do not choose a winner before keeping a copy of each machine's saves outside the live folder. Write the objective or upgrade you remember next to each backup. Valve's conflict choice selects a file version; it cannot combine the in-game purchases from the two files. Decide which checkpoint you will continue, and keep the other intact if you want to replay it later.

Valve: Steam Cloud conflicts, lost progress and log files ↗

Windows retail files inspected by a PCGamingWiki contributor ↗

Golden Horn Studios and player discuss overwritten autosaves and separate slots ↗

Restore a zipped shift backup that the Load menu cannot see

Keep the ZIP as your archive and extract it into a separate folder. In File Explorer turn on File name extensions and locate the actual numbered .sav under the extracted saves directory. If the archive contains a whole PotatoPlease folder, avoid placing that entire folder inside the active saves folder. With the game closed and the destination backed up, copy the recovered slot to the same relative path and filename it originally used. Confirm the slot and a familiar objective in Load before saving again.

Microsoft: extract a Windows ZIP archive ↗

Microsoft: reveal filename extensions and identify file types ↗

Windows retail files inspected by a PCGamingWiki contributor ↗

Retail app 5266240: current Steam Cloud rules and public branch metadata ↗