The workaround is to log in as an administrator and give his user account the permission to modify the files. Why is it not standard procedure? Because giving normal users the permission to edit everything by default instead of just files that they own is how people used to be able to delete system32 and brick their windows install.
Right?
This reeks of inexperience.
We lock things down because a malicious program can easily be “owned” by the user through stupid choices. And now you got viruses.
This is a way to stupid proof things. And the workaround isnt difficult, but it’s to stop people like Andrew. And so far, success.
Why are you assuming so much about Andrew?
What are these workarounds? And why are they workarounds and not standard procedures?
The workaround is to log in as an administrator and give his user account the permission to modify the files. Why is it not standard procedure? Because giving normal users the permission to edit everything by default instead of just files that they own is how people used to be able to delete system32 and brick their windows install.
I understand all that. After all, Andrew is asking for the power to become an admin.
But given your reply, it seems like Andrew is asking for that power from the get-go which, of course, is a no go.