Monster Hunter Rise’s Steam save set is more than one numbered slot. The `win64_save` directory also contains shared/system data, so restoring one file in isolation can create mismatched revisions. For a dependable backup, archive the entire directory and keep the Steam account context. Microsoft Store/Xbox uses WGS, which is a separate storage model and should not be converted by renaming `.bin` files.
Known Monster Hunter Rise save-file structure
The researched filename or folder pattern is data00-1.bin
data001Slot.bin
data002Slot.bin
data003Slot.bin. File-extension context: .bin The documented format notes are: Steam PC save records live in win64_save. data00-1.bin is shared/system data while numbered Slot files represent save slots. Microsoft Store/Xbox uses WGS instead of the same file layout.
Why an extension is not enough
A save filename can identify a likely container, but it does not prove the internal schema, game version, checksum rules, encryption state, or editability. Slot files and shared/system data belong to one profile context. Mixing revisions can create a state the game did not produce. SaveEditor therefore separates file identification from Tool compatibility and only labels a game-specific Tool Verified when its exact profile/version evidence passes the runtime gate.
Where the format is stored
PC save locations: Windows: Steam: <Steam-folder>userdata<user-id>1446780remotewin64_save
Microsoft Store: %LOCALAPPDATA%PackagesF024294D.50755C2F12831_8fty0by30jknySystemAppDatawgs<user-id> | Linux / Steam Play: Steam Play: <SteamLibrary-folder>/steamapps/compatdata/1446780/pfx/. Storefront context: Steam, Microsoft Store / Xbox app. Steam and Microsoft Store use different containers. Steam remote storage exposes win64_save paths; WGS should be preserved and handled separately. This matters because two releases can use different containers or companion files even when the visible slot name is similar.
Back up before inspecting or editing
Copy the entire 1446780 remote/win64_save folder, not only one numbered slot. Keep data00-1.bin and all active slot files together. A read-only viewer is lower risk than a writer, but the live save should still be copied first. Cloud context also matters: Steam Cloud and Xbox Cloud are documented. Steam remote-storage downloads may prefix the folder path into downloaded filenames, so restoration should preserve the expected win64_save layout. Keep the original bytes available so any experiment can be reversed without relying on a cloud service or automatic backup.
What this reference does not claim
This page does not infer an undocumented checksum algorithm, encryption key, compression layer, or cross-store conversion from the file extension. Troubleshooting evidence: If the game reports no save data, preserve the local folder first and compare it with Steam remote storage. Do not overwrite every local file with one isolated cloud slot. Those questions require a verified parser/profile or a game-specific source, not a generic format guess.
Verification context: Steam and Microsoft Store paths were reviewed against current PCGamingWiki coverage. Current SteamDB and Steam community recovery documentation were used to cross-check the win64_save file set.