Despite there being endless duplicate threads on this same subject, and numerous posts in each thread outlining the situation to varying degrees of verbosity … somehow … the basics are continually skipped over.
There is a new module in new kernels ntfs3 … in the past ntfs-3g was used.
ntfs-3g would more or less use --force by default … meaning it would mount ntfs partitions even if they were marked dirty.
You can go back to using ntfs-3g by making sure it is installed and blacklisting the new module.
But in most cases this is likely just willfully ignoring the real problem (and possibly causing continual harm to your partition and its data).
Its quite possible there are situations where the new ntfs3 is failing for no good reason.
I dont use the proprietary filesystem enough to have much of an opinion on the new module.
But complaining that ‘something broke because of an error from the update’ is missing the mark on numerous counts - and quite possibly facilitates continued bad practice.
( use the corpo OS, or a derivative like Hirens, and run chkdsk on the problematic partitions, then treat them correctly moving forward, like properly unmounting, and disabling ‘fast startup’ in windoze and so on )