I'm planning to make Linux my primary operating system while keeping Windows available for a few applications that don't work properly under Linux. My preferred setup is Linux on one drive, Windows on another, a shared game drive, and a separate shared data drive containing documents, photos, spreadsheets, and a KeePass database.
Can Windows and Linux safely read and write the same personal files on an internal drive? I'm especially concerned about opening a document in one operating system, saving it, and then editing it from the other without corruption or data loss. I had a few files damaged years ago while experimenting with dual boot, although I never determined whether that was caused by the operating systems or by something I did.
What filesystem would you recommend for the shared data drive? Would NTFS or exFAT be more appropriate? Are there settings, such as disabling Windows Fast Startup or hibernation, that are necessary? I'm also curious whether sharing a Steam or Epic games drive between Windows and Linux is practical, and whether Linux drives can be mounted automatically at startup.
4 Answers
Use NTFS for the shared personal-data drive if Windows needs full access. exFAT can work for simple cross-platform storage, but it has fewer filesystem protections and is not my first choice for important everyday data.
A shared game library is more complicated. Windows games can generally use NTFS, but Linux games running through Steam Proton or Wine may run into permission, symlink, and launcher problems on an NTFS library. A Linux-native filesystem such as ext4 is usually more reliable for games used primarily from Linux, although Windows will not use it without additional software. Keeping separate libraries for each operating system is often the least troublesome approach.
If the files are genuinely important, plan for more than filesystem safety. Use versioned or offline backups, and consider keeping multiple copies of the KeePass database. Also avoid having the same document open for editing in both operating systems at once. File corruption from dual boot is not an inherent requirement, but interrupted writes, forced shutdowns, failing disks, and Windows hibernation are common causes of trouble.
The Linux filesystem can simply remain unrecognized by Windows, which is generally fine; Windows will not modify an ext4 partition just because it is present. In Linux, you can configure the game or data drive to mount automatically at startup using its UUID in /etc/fstab, or let the desktop’s disk utility handle mounting it. Just make sure it is mounted before launching software that expects files there.
For ordinary documents and photos, a shared NTFS data partition is usually the practical choice because both Windows and modern Linux distributions can read and write it. The operating systems should not corrupt files merely because the files were accessed from both systems, assuming the drive is healthy and both systems are shut down cleanly.
Disable Windows Fast Startup and hibernation. Otherwise, Windows may leave the NTFS filesystem in a partially hibernated state, and Linux may refuse to mount it or risk damaging it. Keep a real backup of important files too—especially the password database—because a shared drive is not a backup.
Modern Linux systems normally support NTFS without much extra work, but that does not make every Proton or Wine game compatible with an NTFS library. Game-specific behavior can still vary.