Why Fast Startup in windows can corrupt file systems?

Question

linux

Usually, in manuals for using several operating systems and data access tools like paragon hfs + and others, it is recommended to disable fast startup in order to avoid data corruption. What causes problems?

Answer 1

Because when Windows goes into hibernation, it creates a page on the NTFS partition that it marks as start speedup cache . This page contains a cache of metadata for a quick start, so as not to read them again at the start and not be stupid.
This cache for Linux does not make any sense. Moreover, the partition is seen as broken when mounted, because it is marked with a bunch of its flags. Modern versions of NTFS-3g warn about this and ask you to boot back into Windows so that it restores this cache. The nuclear ntfs driver does not yet know about this at all, and can silently write something over, and then your Windows will no longer boot.
This is about NTFS.
There is still a chance to break the EFI partition. At this point, I don’t know what Windows does with it, but at the time of hibernation, it also leaves something on it in an inconsistent state, and with further mounting in Linux, this section seems to be broken. If at this moment you write something on it or try to "fix" it, then all your operating systems will not be able to boot.
In fact, you can not disable this fastboot. You just need to constantly remember: did your computer accidentally turn off when you were in Windows hibernation. Like there, the light blinked, or the cleaner processed the surge protector with a mop, or you messed it up yourself.