Songs of Glimmerwick save location: check a missing demo autosave

Find the folder for the Windows user who played

1. Check whether you are signed into the same Windows user account used for the demo. Eastshade asked this first when investigating the missing autosave.
2. Open File Explorer and enter %USERPROFILE%\AppData\LocalLow\Eastshade Studios\Songs of Glimmerwick in the address bar. This Windows shortcut substitutes the current user directory into Eastshade’s documented path.
3. If you played under a different Windows account, check that account’s corresponding directory instead.
4. Preserve a copy of the folder’s files before attempting changes. Leave the original files in place while you compare what Load shows.

This directory was also supplied by Eastshade in a September 23 invisible-character report. It is a Windows location; these sources do not establish a Steam Deck/Linux path.

Finding files does not prove they can restore progress

The reporting player found files named Player, Player-prev and steam_autocloud.vdf, then copied them into Steam demo installation folders. Their next reply said progress still would not load. The developer requested the Player and Player-prev files for investigation; that request is not a demonstrated import method. Do not rename those files as saves or assume a Steam Cloud metadata file contains your playable progress.

What to send in a missing-save report

Record the demo version, the Windows account used, the folder you inspected, the visible filenames and the Load-screen result. Eastshade requested diagnostic files at [email protected] in the September thread. The page gives you a documented investigation route, not a promise of recovered progress. The demo-to-full-game save answer covers the separate launch commitment; a file existing here does not establish the launch build’s migration mechanism.