How Are These Files <b>in</b> The Empty Folder (Hidden Files Visible)?

How windows really works; with, files that don't display even when [View > Show > Hidden Items] is active?
They don't even add up in the "empty" space calculator.

~~winver 18362.1082~~ ~

Explorer will lie to you, and tell you a folder is empty, if your user account does not have
access permissions. Taking ownership of a file or folder does not change the permissions,
that is a separate action.

To show what's going on, from an administrative command prompt:

Code:

c:\Windows\ServiceState\EventLog\Data>attrib *
A  SH                C:\Windows\ServiceState\EventLog\Data\lastalive0.dat
A  SH                C:\Windows\ServiceState\EventLog\Data\lastalive1.dat

c:\Windows\ServiceState\EventLog\Data>icacls *
lastalive0.dat NT AUTHORITY\SYSTEM:(I)(R,W,D)
               BUILTIN\Administrators:(I)(R)
               NT SERVICE\EventLog:(I)(R,W,D)

lastalive1.dat NT AUTHORITY\SYSTEM:(I)(R,W,D)
               BUILTIN\Administrators:(I)(R)
               NT SERVICE\EventLog:(I)(R,W,D)

So they are hidden files, and ordinary users or non-elevated administrators can't read them.

Explorer isn't suitable for viewing these things because it can't normally be run elevated. If you want to list files regardless of permissions you need to enable backup privilege. A simple way to do this is to use robocopy with the /b (for backup privileges) and /l (for list only) options. As an example try running

Code:

robocopy C:\ProgramData\Microsoft\Windows\SystemData\ c:\dummy  * /b /s /l

(after you've checked the syntax for robocopy!)
to show you the lock screens on your system. Unless you've been messing with the permissions you can't see them using dir from an elevated command prompt. If you omit /l and choose a real directory in your profile you'll copy the files but not the security, so they'll be accessible to you.

[QUOTE=MisterEd;2590164]To show the "super hidden" files and folders uncheck this box.
[/QUOT]

I delete all sorts of other system files, I can rend my installation like a cat shredding toilet paper. Why are those files exposed and vulnerable to tweaking, are they not "protected operating system files"?

What makes one worthy of "hidden"; another worthy of "protected" (super hidden); and all the ones I usually hunt and delete (causing major O.S. disabilities) "visible".

The "visible" files are easily accessed, modified, or deleted; however, they probably shouldn't be visible and should be protected - otherwise we wouldn't always get warnings from people not to mess with them.

The terms chosen to describe these files are ...murky. In my opinion (how about bit of a rant) -- Visible files should, for most users, be limited to the apps and program-specific files such as .exe .jpeg etc.. Hidden files "should" be the ones most users are not interested in (all O.S. files). Protected files ought to be the ones that need to exist for the O.S. to work.

Maybe I'm missing something with the complexities of having "System" and "TrustedInstaller"; instead of only one System to handle everything not done by the user and the user's programs. Those permissions policy interfaces are the most asinine Machiavellian user interface. They make sense if your on compnay copmuters with an I.T specialist who comes in and sets things up so your manager can spy on your work from their desk and keep you off the companies secrets, but really...

Hidden files for tweaking.
Protected for red button "touch this and the O.S dies" files.
Visible for things a user would use.

1 User
1 System (non user permission level).