It’s quite common to login as admin on windows though (in home setups), you’ll still have to authenticate for administrative tasks (the UAC popups).
The issue here is mostly that the user has probably upgraded and windows changed their account, resulting in the files being owned by their old account.
In linux, that’s fixable with ‘sudo chmod -R’
In Windows, there’s no built-in way, you need the take ownership script.
It’s quite common to login as admin on windows though (in home setups), you’ll still have to authenticate for administrative tasks (the UAC popups).
The issue here is mostly that the user has probably upgraded and windows changed their account, resulting in the files being owned by their old account.
In linux, that’s fixable with ‘sudo chmod -R’
In Windows, there’s no built-in way, you need the take ownership script.
i mean, chown is just a binary. takeown is probably pretty similar, right?
Pretty much, yeah
I assume the equivalent would just be ‘takeown /r ’
As far as I can tell it always uses the currently logged in user as target though
I am the installer and only user of my pc, but Windows neeeds other users. Note: Phil is USERS not ADMIN! Not even Authenticated Users.