Sorry for the catastrophically delayed reply... I had kinda lost track of my Communities notifications.

I have quickly tested with a Workstation 17.0.0 VM running a fresh install of Windows 10 Enterprise, and my VM can happily load the read-write NTFS driver from that page, and I can access the guest's NTFS volume in read-write mode – the "vol" command shows that it is "(rw)" and I can create files on that filesystem and read them back.

We have not made any changes to Workstation specifically to address the problem you report.  There really is not much we could do to influence the driver's behavior here other than through changes to the platform's power state support seen by the OS, and I can not immediately think of anything we have changed in that regard.

The "Fast Startup"/"Fast Boot" feature of Windows is dependent on the platform supporting the hibernate power-save mode, and VMware virtual machines do not support it, which is almost certainly why the option is not in the Windows user-interface... because Windows can not activate that feature in the virtual machine anyway.

If the problem is still occurring, it might be worth inspecting the Windows event logs to see what it is doing at OS shutdown/start, specifically to see if there are any clues about which power state it thinks it is going into, and to see whether there are any warnings from the OS NTFS driver during boot which might be linked to the EFI NTFS driver's inability to mount the volume read-write.  That's about all I can think of.