Fallout 4’s location is straightforward, but modded restoration is not. A base .fos file can reference content from plugins, and F4SE can add a paired cosave. The safest archive therefore includes the full save directory plus enough information to rebuild the mod environment. A failed load after moving PCs is not automatically evidence of file corruption; missing plugins, changed load order, or an absent cosave can be the real cause.
Start with the least destructive explanation
When Fallout 4 progress appears missing, first verify the active PC location: Windows: %USERPROFILE%DocumentsMy GamesFallout4Saves | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/377160/pfx/. Expected files/folders: *.fos
*.f4se (when created by F4SE). Many apparent save failures are actually profile, storefront, path-redirection, or cloud-selection problems rather than damaged game data.
Preserve every surviving copy
Copy the complete Saves directory. On F4SE setups, keep matching .fos and .f4se files together and record the installed mod/load-order state. Before renaming, moving, replacing, or opening candidate backups, copy them outside the live directory. Do not use the only surviving file as the test specimen for repair or editing.
Check launcher and cloud state
Storefront context: Steam, Microsoft Store / Xbox app. The standard Documents path is the primary Windows reference. Microsoft Store packaging can differ, so locate the active edition before restoring a file. Cloud notes: Cloud behavior depends on storefront. OneDrive may also synchronize the Documents tree if Windows folder backup is enabled. A sync client can reintroduce an older or newer version after a manual restore, so recovery work should keep local and cloud copies conceptually separate until the wanted progress is confirmed.
Use format and compatibility clues
Base Fallout 4 saves use .fos. F4SE-enabled installations can create companion .f4se cosaves; preserving only one side of a modded save may remove script-extender state. A clean base-game save and a heavily modded save have very different restoration requirements even if both use .fos. If the file exists but is ignored, compare the complete directory structure, slot/profile naming, game edition, mods/DLC, and any companion metadata. Do not assume an extension change or generic checksum tool can repair a game-specific container.
Game-specific troubleshooting
If an apparently valid save crashes on load after migration, verify missing plugins and script-extender dependencies before replacing more files. Also check whether Documents is redirected by OneDrive. If a known-good backup works, preserve it and create a fresh in-game save before further experiments. If no copy works, prefer read-only inspection and source-backed game-specific tooling over repeated writes.
Verification context: The standard Windows and Steam Play save locations were reviewed against current PCGamingWiki coverage. Format notes distinguish base .fos saves from optional F4SE cosaves.