I’d be rich if I had a penny for every time a savegame or config file is stored somewhere totally whack.
Fun thing of you enable protected folders on windows: No app can get write access your Documents folder (or Images or Videos or…) unless you put them explicitly on the whitelist. That means you get to experience all the programs that are crashing or hanging or… just because they’re simply assuming that that’s the best place to dump data and because these folders always exist, you don’t need proper error handling in case you cannot access them…
IIRC the default for the root of the drives in Windows is an analog to Linux / which should be root:root 755.
The difference: When Windows displays the UAC dialog and asks you to elevate, it will (mostly?) just add your user to the ACL list instead of elevating your file browser while you access the drive. If ACLs are inherited from other folders below, that can have serious side effects…
Fun thing of you enable protected folders on windows: No app can get write access your Documents folder (or Images or Videos or…) unless you put them explicitly on the whitelist. That means you get to experience all the programs that are crashing or hanging or… just because they’re simply assuming that that’s the best place to dump data and because these folders always exist, you don’t need proper error handling in case you cannot access them…
Once Microaoft/Windows blocked access to the Root path of one of my drives.
That was surprising.
IIRC the default for the root of the drives in Windows is an analog to Linux / which should be root:root 755.
The difference: When Windows displays the UAC dialog and asks you to elevate, it will (mostly?) just add your user to the ACL list instead of elevating your file browser while you access the drive. If ACLs are inherited from other folders below, that can have serious side effects…