Wanted: Simple, Straightforward Logging of File Opens and File Closes Per This Specification -- Is Windows Capable of This?

Question

What is needed is for Windows to log every attempt to open any file on the system.  The log shall contain a timestamp, name of file, the type of access required
(read only, write only, read and write, exclusive use, non-exclusive use), and name of the process or service that wants the file open.  Also there must be a record of how the operating system disposed of the request.  If the open is successful,
say so. If not, say so, and why.  We had this info on the mainframe in 1972.  It would be useful to log file close events, as well.  The close event will disclose what the program did to the file.  For example, did the program write into
the file?  Did the program read from file?  Did the program truncate the file and write?  Did the program extend the file?  Did the program change the name of the file?   Did the program change any file attributes and, if so,
which ones?  A file can have multiple streams.  Disclose which streams were affected.
There is a Security Auditing feature in Windows that doesn't meet this specification.  So that is not the answer.   What is the answer? 
MARK D ROCKMAN

Answer 1

I have downloaded Process Monitor and tried it on my lab computer. It certainly is comprehensive in its output. I'm going to try it on the production machines in hope of catching clues as to who does what to whom in the file system that is causing
3rd party software to reboot the computer. The author of the troublesome program claims he must reboot the computer at the drop of a hat. For example, some file he must open right now is "locked" by some other program, not his program mind you, some
other program. Okay. So what else is running on the production system that may be doing this? Prove that some other program is doing this.  The fact that we must log all file system activity up to the moment of reboot poses a special issue.  
Will the Process Monitor log lose any file system events because it cannot properly close the log as the system is being rebooted?  It is interesting the Federal Government is fine with Microsoft delivering an operating system that has no comprehensive
file access logging capability.  Process Monitor may do it.  But one cannot run that behemoth 24/7/365.  (I hear you saying "Oh.  But we have Security Audits."  A CISSP may be impressed with that one.)
MARK D ROCKMAN