It’s a seven step process if you include steps like “log in”.
The problem isn’t the steps themselves, it’s that very few users understand file system permissions.
These errors occur when you’re trying to access a profile folder of a user from another install. Most folders don’t have restrictions like these. However, going into a user folder and changing ownership isn’t something you want someone to do accidentally (because you can easily break a second user account that way).
For Microsoft, the three options seem to be “add a magic button that probably breaks something”, “disable ACLs by default”, or “guide users through the advanced interface”. I think they’ve made the right call here, this is an issue a tiny sliver of their user base will ever run into.
It’s a seven step process if you include steps like “log in”.
The problem isn’t the steps themselves, it’s that very few users understand file system permissions.
These errors occur when you’re trying to access a profile folder of a user from another install. Most folders don’t have restrictions like these. However, going into a user folder and changing ownership isn’t something you want someone to do accidentally (because you can easily break a second user account that way).
For Microsoft, the three options seem to be “add a magic button that probably breaks something”, “disable ACLs by default”, or “guide users through the advanced interface”. I think they’ve made the right call here, this is an issue a tiny sliver of their user base will ever run into.