(only recently I upgraded to Windows 8.1 from Windows 7, though I still will continue to help out at SevenForums, exclusively... for now...)
I needed to reproduce UNI's findings as per post #25 in this thread at SevenForums. It involves viewing and editing just a few permission settings, all of which I usually like to do via the Command Prompt using the Icacls command.
So whilst in the process of doing my thing, I noticed some output from Icacls that wasn't quite right -- namely, inherited permissions weren't showing. Rather, they were showing but Icacls reports them inherited permissions as explicit permissions, i.e. the "(I)" before "(F)" is missing which isn't right.
If I were to go and update the NewFileICreatedJustThen.txt permissions in any way, then change permissions back to what it was, Icacls would then report the file's ACL correctly.
E.g. I'll disable then immediately enable inheritance for the file through Explorer, then run Icacls on it again --
(Above is the correct output: each ACE should have "(I)(F)", not just "(F)")
PowerShell's Get-Acl cmdlet always reports the permissions correctly. Something's up with Icacls - or my Windows 8.1 install. I'm just wondering if it's only me that has this problem, or if there's actually a bug with Icacls.exe in Windows 8.1 -- a bug that I can't seem to find any discussion about on the web.
Could somebody, anyone, here, using Windows 8.1 -- 1) create a new file on their Desktop folder,
2) run Icacls on it,
3) then post the command's output here.
I'd like to know if Icacls' behaviour is like what I describe, across all Windows 8.1 installs.
Thanks in advance,
Pyprohly
I needed to reproduce UNI's findings as per post #25 in this thread at SevenForums. It involves viewing and editing just a few permission settings, all of which I usually like to do via the Command Prompt using the Icacls command.
So whilst in the process of doing my thing, I noticed some output from Icacls that wasn't quite right -- namely, inherited permissions weren't showing. Rather, they were showing but Icacls reports them inherited permissions as explicit permissions, i.e. the "(I)" before "(F)" is missing which isn't right.
If I were to go and update the NewFileICreatedJustThen.txt permissions in any way, then change permissions back to what it was, Icacls would then report the file's ACL correctly.
E.g. I'll disable then immediately enable inheritance for the file through Explorer, then run Icacls on it again --
(Above is the correct output: each ACE should have "(I)(F)", not just "(F)")
PowerShell's Get-Acl cmdlet always reports the permissions correctly. Something's up with Icacls - or my Windows 8.1 install. I'm just wondering if it's only me that has this problem, or if there's actually a bug with Icacls.exe in Windows 8.1 -- a bug that I can't seem to find any discussion about on the web.
Could somebody, anyone, here, using Windows 8.1 -- 1) create a new file on their Desktop folder,
2) run Icacls on it,
3) then post the command's output here.
I'd like to know if Icacls' behaviour is like what I describe, across all Windows 8.1 installs.
Thanks in advance,
Pyprohly
My Computer
System One
-
- OS
- Windows 8.1 Professional