Hello Tommy, :)
Did you also take ownership of the "win32" folder?
In addition, manually check your permission settings for this folder to see what they show.
Change Permissions of Objects for Users and Groups in Windows 10 User Accounts Tutorials
....... thanks for your reply.
I applied Take Ownership before the MusicBee install.
After install I checked permissions for:
C:\Program Files\WindowsApps\50072StevenMayall.MusicBee_3.1.35.0_x86__kcr266et74avj
This is the folder which contains the win32 folder in question and when I checked the Advanced Security Permissions I saw the owner was SYSTEM.
Then I took ownership and it showed my admin user account as owner with full control permissions, this also was automatically applied to all the sub folders.
Still unable to paste into this directory.
Any idea what I should try next ...?...
It appears to be a protected system folder then.
Are you sure that your settings for apps are not in the "C:\Users\<username>\AppData\Local\Packages" folder instead?
....... yes they are except for my custom folders which include certain audio codecs and icons for my custom skin.
These folders must be in the installation folder to be recognized by the program.
Why can't I take full control of the win32 folder for which I'm the owner now with full control ?
By the way, I tried to create a folder in other app folders inside WindowsApps folder and I can't do this either.
Do I have to give up on this or is there another possibility that I can try like remove SYSTEM for example ...?...
....... alright, thanks.
I'll try to talk to the app developer, maybe he's able to do something about this.
The big plus for this music app is that it is highly customizable which works great with the portable and desktop version.
Anyway, thanks for trying to help .......
I ran the Add Take Ownership reg and then moved a file to my desktop and it was invisible, but I could see it using "file explorer". So I ran it again. I hope I did not create any problem by running it twice from the desktop. Please advise.
Hello Eddo, :)
I'm not sure I understand what you mean about the file. Does refreshing (F5) your desktop help show it?
Running the .reg file will only merge it to add "Take Ownership" to your context menu. It won't hurt anything if you run it again.
Hello, I'm a software engineer and use take ownership quite often in my line of work and noticed a slight quirk/issue with the way you have the ICACLS command set up. When I use your Take Ownership from the context menu, while it recursively does takeown properly, it only applies the ICACLS command to the root folder and not for subdirectories. So what happens is even after Take Ownership is ran, the user can still encounter this popup on sub-directories:
https://i.gyazo.com/a8d0910adaca75b6...7cd9920557.png
The issue is that the OWNER RIGHTS group doesn't get added to subdirectories. This is because the /t flag is missing from ICACLS and should be added to your registry file for this to work properly. I'm not sure if it worked without the /t flag on older versions of Windows but this is how it needs to be done on Windows 10 at least to mitigate that popup. While omitting the /t flag doesn't hinder the user from entering the folder as they can click Continue on the popup, it becomes annoying when dealing with deeply rooted subdirectories.
Screenshot of a sub-directory's permissions after your Take Ownership is run from the root: https://i.gyazo.com/7637a10a85f01867...0873ad5eca.png
Screenshot of the same sub-directory after I added the /t flag to ICACLS: https://i.gyazo.com/dead81d6a585e9d4...ab6a772f89.png
Hope you will take this into consideration.
Quote