Quick answer
Quit the game, check that the drive holding the save folder has free space, then open your antivirus or Windows ransomware-protection history and look for a blocked Silksong write. If you add an exception, limit it to Team Cherry’s documented Silksong save folder. Afterward, change one harmless in-game setting or make one normal save, quit, and confirm that userX.dat has a new modification time.
First, prove whether the file can change
- Exit Silksong and confirm the drive containing the save folder has free space.
- Open the official save location for your operating system and confirm the folder exists.
- Check antivirus, ransomware protection, controlled-folder access, and similar security tools for a blocked Silksong write.
- Add an exception only for the documented game save folder, following your security tool’s own instructions.
- Before launching, note the modification time shown beside the affected userX.dat.
- Launch the game, make a harmless change, save and quit, then check whether that time advanced.
- Restart the game and confirm the change remains. A newer timestamp plus a surviving change is the result you want.
Read the result of that test
If the timestamp does not move, the game is not updating that file. Check free space, security blocks, and whether you opened the folder for the correct Windows account or Steam ID.
If the timestamp moves but old progress returns only after Steam sync runs, preserve the local and cloud candidates separately and use the reset guide. If the game cannot open the existing profile at all, use Auto Saves or a preserved backup instead of treating this message as proof of JSON corruption.
Security exceptions should stay narrow
- Use only the official Silksong save-folder path for your platform.
- Do not disable all antivirus protection merely to test the game.
- Do not grant broad access to Downloads, Documents, or an entire drive when a folder exception is sufficient.
- If the folder belongs to another operating-system account, use the correct account instead of changing ownership blindly.
What to do after writes work again
Create an untouched backup before restoring an Auto Save or replacing the current file. Then make one normal in-game save and verify it survives a complete restart.
Only use the editor after the game can write reliably. Otherwise a perfectly encoded edited file may load once and then appear to “reset” because the underlying write problem was never fixed.
Preserve the original before testing
Work on copies, change one thing at a time, and keep the original until the chosen save opens, saves normally, closes, and opens again.
Silksong “Save Could Not Be Written” Fix Guide FAQ
Can Silksong Save Editor fix “Save Could Not Be Written”?
Not directly. The message normally concerns storage or permission to write the folder, which must be fixed outside the save data.
Does this error prove my userX.dat is corrupted?
No. A readable save can still fail to update when security software or a full drive blocks writes.
Should I turn off antivirus completely?
No. Prefer a narrow exception for the official save folder and follow the security product’s documentation.
Sources and evidence
Official guidance defines the safe baseline. Community links document real player cases, but a successful report is not a universal or version-independent fix.
Official: Team Cherry: “Save could not be written” guidance