Hollow Knight provides four clear profile files and also creates useful backup copies, making it a strong candidate for careful manual recovery. The key is to keep the entire LocalLow folder rather than only user1.dat: each slot can have a .bak file, older-version backups may appear after patches, and some global preferences/unlocks live elsewhere. SaveEditor therefore describes both the slot files and the boundary of what they do not contain, which avoids misleading a user who restores progress but still sees old global settings.
Prepare the source PC
On the source system, identify the actual Hollow Knight save root: Windows: %USERPROFILE%AppDataLocalLowTeam CherryHollow Knight ; Microsoft Store progress can also involve the package WGS area documented by PCGamingWiki.. The expected file/folder pattern is user1.dat through user4.dat; user#.dat.bak1 backup files and older-version copies may also exist.. Close the game, let the active launcher finish writing and synchronizing, then make a complete offline copy rather than transferring a file that may still be open.
Preserve storefront and profile identity
Documented storefronts: Steam, GOG, Microsoft Store. The main Windows profile files are under LocalLow. Some preferences/unlocks are stored separately, so replacing user1.dat does not necessarily reset every game-wide flag. A transfer between two PCs is simplest when both systems use the same storefront/account/profile context. If the destination uses a different store or container, treat that as a migration problem rather than an ordinary restore.
Move the complete save boundary
Back up the entire Hollow Knight LocalLow directory, not only one user#.dat. Keep the corresponding .bak files so the game-created recovery copies remain available. Put the copied data on the destination only after confirming the destination save path. If the game creates a new empty save first, keep that new folder as another backup so you can compare structures and revert.
Handle cloud sync deliberately
Steam Cloud, GOG Galaxy, and Xbox Cloud are documented. Decide whether the local transferred copy or cloud copy should be authoritative before launching the game. If possible, preserve both. After the transferred save loads correctly, make a fresh in-game save and let the launcher synchronize normally.
Check compatibility before blaming the transfer
The four player profiles are individual user#.dat files. The game also keeps automatic backup/older-version files, while some unlock/preferences data lives outside the main save files. Compatibility note: A profile file is not the whole application state. Steel Soul/Godseeker-style unlocks and settings can be stored outside the slot file, so slot restoration may not reproduce or erase those flags. If the destination does not see the transferred progress, If a profile is corrupt or missing, try the matching game-created .bak only on a copy and preserve the current directory first. Verify the slot number before renaming files. Verify game edition/version, store, profile IDs, redirected folders, and mod/DLC dependencies before editing the save itself.
Verification context: Reviewed against current PCGamingWiki Hollow Knight data plus the Hollow Knight Wiki Save Data page for user#.dat and .bak naming.