Welcome to Elderfield Technical Support

Quick answer: If Welcome to Elderfield will not launch or crashes, install the latest Steam update, restart Steam and the device, close any stuck nw.js process, and record the failure point. As of October 2, the latest announced update is v1.0.2 plus the September 23 Hotfix. Use the matching launch or Steam Deck guide before changing save data.

Match the guide to the symptom

“The game crashes” is not one diagnosis. Choose the description closest to what you actually see:

Do not apply every fix from every row. A Proton setting cannot explain a Windows-only driver issue, and deleting user data cannot prove why one map crashes after a save loads.

Start with the current build and reversible checks

Steam should install updates automatically, but a client left open can hold a queued download. Restart Steam, open the game’s Properties, and confirm that no update is pending. Version v1.0.1 addresses crashes tied to storage movement, radio playback, some fog and dust scenes, non-English animal interactions, and an options menu with no active selection.

Next restart the device and open Task Manager or the SteamOS system monitor. If nw.js remains after the game closed, end that process and launch once more. This follows the developer’s pinned checklist and avoids changing files.

If the symptom survives, keep the next test equally narrow: verify or reinstall the Steam copy, update the graphics driver through the manufacturer or operating-system path, or run the packaged executable directly to see whether Steam itself is part of the failure. Record what changed and whether the failure moved to a different point.

Protect saves before advanced troubleshooting

Reinstalling the application and deleting user data are not equivalent. A reinstall normally replaces program files; an AppData or save-folder change can remove settings or progress from the location the game reads. Steam Cloud can then ask which copy to keep.

Before touching any save or user-data folder:

1. close the game and Steam;
2. locate the folder named by the developer’s current instruction;
3. copy it to a clearly named backup outside the active game directory;
4. keep the original until the test result and Cloud state are understood;
5. move or rename only the targeted folder, then test once.

The pinned launch thread mentions a save-folder removal specifically for Patreon-alpha migration and an AppData reset as a later workaround. Those are not first steps for an ordinary Steam install. If you cannot identify which folder contains settings and which contains progress, stop and ask for support rather than guessing.

Treat community file replacements as advanced evidence

The developer’s pinned thread also collects player reports about Citrix remnants and replacing packaged NW.js files. Their presence in a developer-maintained thread makes them relevant evidence, but it does not turn every quoted user result into a universal, risk-free fix.

Replacing runtime files can change Steam integration, disable achievements or Overlay behavior, introduce an architecture mismatch, or leave a local installation that differs from what Steam verifies. This site therefore does not place that step in the normal checklist. If the reversible path fails, attach your system details to the official thread and ask whether a current runtime replacement is still recommended for your installed build.

The same caution applies to security software. A report involving Citrix is useful only if Citrix or related remnants exist on the affected machine. Do not uninstall unrelated software because another player happened to have it.

Separate performance from launch failure

A game that opens and runs at a low frame rate has already passed the launch stage. Record resolution, display mode, GPU, driver version, map, and whether the problem is constant or tied to transitions. On Steam Deck, use Full Screen ON and Stretch Screen OFF before testing Proton. On a dual-GPU Windows laptop, confirm which GPU is active before editing a launch flag.

The planned low-FPS page is not published as a speculative hardware table. Until current multi-device measurements are available, use official requirements, current in-game settings, and the developer’s specific dedicated-GPU note rather than an invented “best settings” preset.

Send a bug report that can be acted on

Include the following in an official Steam bug report or support message:

• installed game version and whether Steam finished updating;
• Windows or SteamOS version, CPU, GPU, memory, and Deck model where relevant;
• exact last visible screen, map, menu, task, or error text;
• whether the issue occurs on a new save, one save, or every save;
• the single test performed and its result;
• whether files, AppData, Proton, or Cloud data were changed.

A screenshot of the error and a short reproduction sequence are more useful than a long list of unrelated fixes. Never publish a save containing personal paths or account information in a public thread without checking what it contains.

Sources and support boundary

This hub was reviewed on September 19, 2026 against the developer’s pinned launch-issues thread, the dedicated-GPU workaround, and the official v1.0.1 announcements.

The linked Steam material can change as the developer learns more. The focused pages preserve which steps are official, which are symptom-specific, and which are only community-reported so that a useful workaround is not overstated.