Quote:
Originally Posted by Pisces
It's not that simple. There is more going on than NTFS file/folder permissions restrictions when you want to modify things in Program Files. User Account Control: https://docs.microsoft.com/en-us/win...-control-works
Windows doesn't even take administrator-users at face value when they want to modify files and folders. They have to acknowledge that they want their admin-cap on (get an administrator access token to elevate their rights) to do things. If not they are regarded just as any other common user. If not acknowledged it out right fails the action or the change is virtualized stored in the user's profile but not actually applied to the filesystem in Program Files.
https://blogs.msdn.microsoft.com/old...02-00/?p=91681
Installing old games outside of Program Files solves a lot of problems. Same goes for SC and DW. Saving games in the Scenario folderbeing the first one. It doesn't solve all problems, but many. Also execute old installer.exe or setup.exe executables as administrator thesedays. Or parts of their tasks will not succeed. |
All right then, I have resolved some similar issues by adjusting the permissions. But mostly for programs that want their plugins etc in the program folder or something.
These days windows actually asks something to the effect of "do you want to give yourself permanently access to this folder" when you go poking somewhere "protected".
If you really wanted to be difficult you could try moving the folder and making a link to the program files that points to it. Not sure how windows permissions handle these cases, on *NIX links do not have restrictions but the targets obviously do.