Windows 10: Inherit permissions when moving files

Can anyone please tell me how I can set Windows 10 up, so moved files will inherit the permissions from the destination folder?

I enabled the inheritance option on the parent folder and that works when copying files, but not when moving files.

In previous versions of Windows I could resolve this issue, by adding MoveSecurityAttributes in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer (as described in the article below), but this does not seem to have any effect in Windows 10.

https://support.microsoft.com/en-us/kb/310316

Any help really appreciated and thanks in advance *Smile

/

:)

 

lost file properties

You neglected to mention what 'properties' you're talking about.

With respect to access permissions: Folders and files inherit their access permissions from their parent folder, including the root folder of a drive. You can break the inheritance if you wish and determine your own access permissions if you feel confident
in your knowledge. However, as soon as you move a folder or file to a new parent folder, the parent folder's access permissions once again take over.

This is how the Windows operating system has always worked and it's how organizations are able to assign access permissions across a network in a consistent and predictable manner.

Therefore, the first thing to do before moving folders and files to a new partition - like when I moved all my user data (documents, pictures, email, etc.) to a new partition - is to setup the permissions as you wish on the root of the new partition. Then
move your folders and files.

In general, it's best to adhere to Microsoft's default access permissions for files of the same type you want to move, as I did. Access permissions are complex and have far-reaching ramifications. Microsoft has had many years to carefully think this through
and configure appropriate permissions.

 

why since switched to windows 10 got extra user

Well it certainly seems like some "interesting" things are going on, and my best guess as to why would be something happened during the upgrade. One of the many reasons I like to do clean installs.

Anyways first off the default location for the pictures is on the C drive, in:

C:\Users\USERNAME\Pictures

But it can be moved.

If you right click on Pictures -> Location, it will show where it is. If it is not on the above path that could certainly be the cause of permission problems. For instance my Pictures are stored on a server and as such the server has a lot to do with what
permissions might be there. But if it was just say on D drive, I wouldn't really expect all this strangeness.

The "inherited from" does mean that the folder listed is controlling the permissions.

That was in fact what we were trying to do with the "Replace all child permissions..." setting, for the folders below.

For each of the permissions listed on a file/folder it possible that the permission is "local" or inherited from the folder above it. This inheritance can go all the way up to the top of the drive, adding different permissions.

Basically you mostly want permissions to be inherited. For instance when you created the test folder under Pictures, what should its permissions be? It should get the inheritable permissions. That way you don't have to set permissions every time you create
a folder, they just naturally take on the permissions of the parent. And only when you have a special case do you override these inherited permissions.

On the " I see a new user group (I guess this user is inherited from C with same name as I login to the computer". This isn't a group, this is your user account. And yes by default your account should be on all the files from C:\Users\USERNAME on down.

I'm glad you found a combination works for you, but I also think that maybe you should check who owns the Pictures folder. If you go into the advanced permissions, it will show who owns it. If your Pictures folder is on a local drive it certainly should
be your username (the one you log in with).

 

Hi, did you find a solution to this?

 

Sadly no - im still hoping someone have a solution for this.