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.
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.