its fixed in 1903 update
Dear Allan_AU,
Please forgive my scepticism but, I earlier couldn't found any reference to this problem in MS documentation, although I'm one of the several victims of this undocumented issue which has a long history. And I still can't find any reference in MS related documentation that this issue has been fixed in 1903 update of Windows 10.
Can you please refer to any MS related documentation, etc. showing they accepted this as an issue and fixed it in 1903. Life with Windows 10 becomes unbearable and I'm looking for options like rolling back to pre-1803 W10 or moving my data from NTFS to other OSes and filesystems.
Your response is very important to finalize my decision.
Best regards,
Cagatay