I have been encountering many folders for which the Security dialog produces an error reading: "Windows Security <information icon> The permissions on <folder name> are incorrectly ordered, which may cause some entries to be ineffective. OK" I believe this error is being caused by an interaction with the "Share with" feature of Windows Explorer. When I grant a user Read permission via the "Share with" tool I find that some of the subfolders of the target of that grant report this error. The error dialog is produced when I right-click on the Folder in Windows Explorer and select Properties. I then select the Security tab. The selection of the Security tab produces the Windows Security dialog. In all cases I see the Owner is set as expected. In addition the grantee is properly listed with an Allow permission entry for Read & execute. Oddly two groups are listed, Everyone and None. Everyone has a Allow Special permission and None has Allow and Deny Special permissions. Has anyone else seen this behavior and identified a root cause? What are the specific Permission entries that are being set when the "Share with" feature of Windows Explorer is used? - What are the Deny entries and why are they created? Test system: Windows 7 Professional x64, member of a Homegroup, not a member of a Domain. File system is NTFS.

That is by design. Because the user you share with already has permissions on these folders. Please check them.Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

I now believe the errors I was seeing were a result of permissions entries created by Cygwin and the copy of rsync distributed via Cygwin. I had been using an environment variable, CYGWIN=nontsec, which disabled Cygwin's managment of permissions entries. A new version of Cygwin, version 1.7, changed the configuration and I had to use a different mechanism to disable Cygwin's management of the permissions entries. More information on the change is available online at [http://i-cat.blogspot.com/2010/01/cygwinnontsec-in-cygwin-17-speak.html]. Now that I have re-disabled Cygwin's setting of permission entries I think the folders are behaving as expected. Therefore this is not an issue with the Windows Explorer File Sharing tool but rather an issue with how Cygwin was managing access control list (ACL) entries.