Is this issue equivalent of setuid 4701 on executable owned by root in Linux?
What's the easiest way to scan whole windows file system for directories with this issue?
What's the easiest way to scan whole windows file system for directories with this issue?
tree c:\ /f prn
Source: https://docs.microsoft.com/en-us/windows-server/administrati...