Welcome to Elderfield Won't Launch

Quick answer: When Welcome to Elderfield will not launch, install the latest Steam update, restart the device, close leftover nw.js, verify Steam files, and update the graphics driver before changing saves or AppData. The current announced build is v1.0.2 plus the September 23 Hotfix, checked October 2. Record the failure point before testing Proton 9.0-4 or 10.0-4.

Identify where the launch stops

Launch once without changing anything and write down the last visible state:

• No window appears: Steam, security software, a stuck process, or the packaged executable may be involved.
• A window appears and closes immediately: note whether an error flashes and whether nw.js remains in Task Manager.
• It closes after the Kwalee screen: record platform and Proton version; this symptom has received specific compatibility advice.
• It reaches the title or difficulty menu: this is an in-game crash, not a failure to start the executable.
• It fails only after loading one save: preserve that save and report the map, task, language, and last action.

Do not call all five states “the same crash.” The developer asks for the repeated location and any visible message because those details change the useful next step.

Run the low-risk checklist in order

1. Finish the Steam update. Restart the client and confirm no download is queued. Install v1.0.2 and the September 23 Hotfix before comparing your symptom with the current fixes.
2. Restart the device. This clears a stranded runtime or locked game file without changing data.
3. Close leftover nw.js. Open Task Manager after the failed launch. If nw.js is still running, end it and test once.
4. Verify the installation. Use Steam’s installed-files verification. If Steam reports a locked file, check whether the library is on an external, synced, or protected location before reinstalling repeatedly.
5. Update the graphics driver. Use Windows Update or the GPU manufacturer’s official tool, then restart.
6. Try the packaged executable. Open the installation directory and run the game executable directly. If this changes the error, include that difference in the report.
7. Try administrator mode once on Windows. This is a diagnostic test, not a reason to run every session elevated.

The pinned developer thread also suggests moving the game folder to the desktop and reinstalling. Use those only after the checks above, and keep the Steam-managed original until you know which copy you are launching.

Choose Proton only for a Proton launch problem

The current developer checklist names Proton 9.0-4 and 10.0-4 as versions to try. On Steam Deck or Linux, record the current compatibility tool, change to one listed version, launch once, and compare the last visible screen. Do not cycle through random Proton releases and combine their results.

For Steam Deck performance after the game opens, first use Full Screen ON and Stretch Screen OFF. Those are the v1.0.1 recommendations. A display-setting test answers a different question from a Kwalee-screen crash. The Steam Deck guide keeps the two paths separate.

If 9.0-4 and 10.0-4 both fail, restore the previous selection before reporting. Include SteamOS version, Deck model, whether the full game or Demo is installed, and the exact point where the window closes.

Crash when unlocking an achievement

v1.0.2 adds a potential fix for a crash when an achievement unlocks after Steam's connection has failed. Finish updating, restart Steam, confirm it is connected, and retest the same trigger once. If it still crashes, record the achievement and connection state with the error. Use the current patch guide before replacing runtime files or resetting AppData for this symptom.

Check the dedicated GPU only when the symptom fits

Some Windows laptops have an integrated GPU and a separate high-performance GPU. The developer says Chromium may choose the integrated device and documents a launch-flag workaround: changing --in-process-gpu to --force_high_performance_gpu in the game’s package configuration.

That change disables the Steam Overlay. Back up the file before editing, change only the named flag, and test once. If performance improves but launch behavior does not change, you found a GPU-selection issue rather than a universal crash fix. Restore the backup if you depend on the Overlay or if the change has no effect.

Prefer the normal Windows graphics preference or GPU-vendor control panel when it reliably selects the dedicated GPU without changing packaged files. The developer’s flag is a documented workaround for the Chromium/Overlay interaction, not proof that every laptop crash uses the wrong GPU.

Back up AppData and save data before a reset

The pinned thread distinguishes two later cases. A player migrating a Patreon alpha save may need to remove the old save folder if the game’s conversion fails. Separately, an AppData reset is presented after user reports that stale data prevented launch.

Before either test, close Steam, copy the complete target folder outside the live path, and label it with the date. Do not permanently delete it. Launch once with the folder moved or renamed. If the game starts, you have evidence that user data participates in the failure, but you have not yet proved which file is responsible.

Watch Steam Cloud carefully. If it asks whether to keep local or cloud data, do not guess. Preserve both copies and seek help before selecting an option that can overwrite progress. A new empty title screen is not a successful repair if the only save was destroyed.

Understand the NW.js replacement warning

The developer-maintained thread quotes players who solved launch failures by downloading Windows x64 NW.js files and overwriting the packaged runtime. Another player reported that achievements stopped working. This is useful diagnostic evidence, but it remains a community-reported file replacement.

Do not download a runtime from an unofficial mirror, do not mix x86 and x64 files, and do not present the replacement as required by v1.0.1. Replacing packaged files moves the installation away from the version Steam verifies. If every reversible step fails, post your hardware and error in the pinned thread and ask whether the current developer still recommends a particular official NW.js release.

The same rule applies to reports about Citrix DLL remnants: investigate them only if Citrix exists or existed on the machine. Removing unrelated software is not a general launch procedure.

Report the failure with enough detail

Use the official launch-issues thread or the Steam bug-report area. Include:

• the exact installed game version and whether the latest Steam update finished;
• Windows or SteamOS version and the full CPU/GPU names;
• last visible screen and exact error text;
• Proton selection, if applicable;
• whether a fresh save and existing save behave differently;
• results of the low-risk checklist in order;
• any AppData, save, runtime, GPU-flag, or Cloud change.

If the game opens and only one action crashes, review the latest player-impact guide and its linked v1.0.1 history. Compare the exact trigger with the named fix before reporting it as the same bug.

Sources and evidence levels

This guide was reviewed on September 19, 2026 against the developer’s pinned Solutions for Game Launch Issues, the developer’s Dedicated GPU workaround, and the official v1.0.1 announcements.

Steps explicitly written by the developer are identified as developer instructions. Quoted player successes remain community reports even when collected in the pinned thread. That distinction is why file replacement appears after backups and reversible checks rather than at the top of this page.