Then you use udisks2 as backend. ntfs3 is the default there. And yes the error is somewhat misleading, but it has to do with ntfs being in a dirty state from windows.
There are 2 drivers: ntfs-3g and ntfs3. Both are different
ntfs-3g
- userspace driver
- force remove dirty bit by default
- has default option which is called
recoverand this removes the dirty bit instantly.
ntfs3
- kernelspace driver
- doesn’t remove dirty bit by default
- has an equivalent parameter to recover option:
force. That means it will ignore the dirty bit, but disabled by default.
Note that both approaches can be dangerous, since this dirty bit is meant for checking the FS on the next mounting process, so usually on Windows. Linux does not and is not able to check the consistency of your data when using ntfs.