NTFS file systems aren't Linux native (obviously), so a third party plugin is used for writing (ntfs-3g), it's the same across all Linux distro's .. it is very good at what it does and problems are rare, but you have to accept it's probably not as robust as Windows own NTFS support.
Again I'd expect it to amplify already existing NTFS file system problems, where Windows may be able to work around them .. so if the Windows file system already has minor errors ntfs-3g may make things worse.
On top of that you were using a Windows application to write to a Windows file system, but through first a compatibility layer (WINE),, and then through ntfs-3g.
Personally if I were ever to use a Windows app in WINE, I'd copy any files to be manipulated to Linux partition/file system first, run the Windows app on them, then once finished, copy them back to the Windows partition.
ie. .. take WINE out of the loop as far as copying to the Windows file system goes.
This can't really be a "Peppermint specific" problem .. it's either going to be an ntfs-3g issue, a WINE issue, or an already corrupt file system issue .. or more likely some combination .. there is nothing Peppermint specific involved here.
When getting Linux to deal with Windows (and vice versa) .. probably best try to keep it as simple as possible .. eg. not letting the Windows app running in WINE
directly write back to the Windows partition (as it would need to do this through TWO interpreters if you get my meaning).
And if you're going to use WINE a lot .. check the Windows file system (in Windows) a lot too.
Besides this hiccup, I'm glad you're enjoying Peppermint, and that you managed to recover your files
