FileMonitor 5.1.6.1

dotnet add package FileMonitor --version 5.1.6.1                
NuGet\Install-Package FileMonitor -Version 5.1.6.1                
This command is intended to be used within the Package Manager Console in Visual Studio, as it uses the NuGet module's version of Install-Package.
<PackageReference Include="FileMonitor" Version="5.1.6.1" />                
For projects that support PackageReference, copy this XML node into the project file to reference the package.
paket add FileMonitor --version 5.1.6.1                
#r "nuget: FileMonitor, 5.1.6.1"                
#r directive can be used in F# Interactive and Polyglot Notebooks. Copy this into the interactive tool or source code of the script to reference the package.
// Install FileMonitor as a Cake Addin
#addin nuget:?package=FileMonitor&version=5.1.6.1

// Install FileMonitor as a Cake Tool
#tool nuget:?package=FileMonitor&version=5.1.6.1                

File Monitor Filter Driver SDK

The File Monitor Filter Driver SDK is a kernel-mode component that runs as part of the Windows executive above the file system. The file system filter driver can intercept requests targeted at a file system or another file system filter driver. By intercepting the request before it reaches its intended target, the filter driver can extend or replace functionality provided by the original target of the request. The EaseFilter file system filter driver can log, observe, modify, or even prevent the I/O operations for one or more file systems or file system volumes.

File Monitor

File I/O Monitor

The file I/O monitor can audit file access and change in Windows in Real-Time. With the file monitor you can monitor the file activities on file system level, capture file open, create, overwrite, read, write, query file information, set file information, query security information, set security information, file rename, file delete, directory browsing and file close I/O requests. You can create the file access log, you will know who, when, what files were accessed. You can get comprehensive control and visibility over users and data by tracking and monitoring all the user & file activities, permission changes, storage capacity and generate real-time audit reports.

Monitor the file changed I/O by registering the file change events.

You can get the notification when the managed files were changed by registering the file change events:

  • NotifyFileWasCreated: Fires this event when the new file was created after the file handle closed.
  • NotifyFileWasWritten: Fires this event when the file was written after the file handle closed.
  • NotifyFileWasRenamed: Fires this event when the file was moved or renamed after the file handle closed.
  • NotifyFileWasDeleted: Fires this event when the file was deleted after the file handle closed.
  • NotifyFileSecurityWasChanged: Fires this event when the file's security was changed after the file handle closed.
  • NotifyFileInfoWasChanged: Fires this event when the file's information was changed after the file handle closed.

Monitor all the file I/O by registering the I/O callback notification events.

You can register the file I/O events to monitor the file access I/O in the file filter rule. By registering the specific I/O events, you can get file I/O information in real time.

  • OnPostFileCreate: Fires this event after the file create IO was returned from the file system.
  • OnPostFileRead: Fires this event after the file read IO was returned from the file system.
  • OnPostFileWrite: Fires this event after the file write IO was returned from the file system.
  • OnPostQueryFileSize: Fires this event after the query file size IO was returned from the file system.
  • OnPostQueryFileBasicInfo: Fires this event after the query file basic info IO was returned from the file system.
  • OnPostQueryFileStandardInfo: Fires this event after the query file standard info IO was returned from the file system.
  • OnPostQueryFileNetworkInfo: Fires this event after the query file network info IO was returned from the file system.
  • OnPostQueryFileId: Fires this event after the query file Id IO was returned from the file system.
  • OnPostQueryFileInfo: Fires this event after the query file info IO was returned from the file system.
  • OnPostSetFileSize: Fires this event after the set file size IO was returned from the file system.
  • OnPostSetFileBasicInfo: Fires this event after the set file basic info IO was returned from the file system.
  • OnPostSetFileStandardInfo: Fires this event after the set file standard info IO was returned from the file system.
  • OnPostSetFileNetworkInfo: Fires this event after the set file network info was returned from the file system.
  • OnPostMoveOrRenameFile: Fires this event after the file move or rename IO was returned from the file system.
  • OnPostDeleteFile: Fires this event after the file delete IO was returned from the file system.
  • OnPostSetFileInfo: Fires this event after the set file info IO was returned from the file system.
  • OnPostQueryDirectoryFile: Fires this event after the query directory file info was returned from the file system.
  • OnPostQueryFileSecurity: Fires this event after the query file security IO was returned from the file system.
  • OnPostSetFileSecurity: Fires this event after the set file security IO was returned from the file system.
  • OnPostFileHandleClose: Fires this event after the file handle close IO was returned from the file system.
  • OnPostFileClose: Fires this event after the file close IO was returned from the file system.

Create C# file monitor example with SDK

This C# example creates a filter rule to watch the directory specified at run time. The component is set to watch for all file change in the directory. If a file was changed, the file name, file change type, user name, process name will be printed to the console. The component also is set to watch the file open and file read IO, the IO was triggered, the file open and file read information will be printed to the console.

Here is the output from the file monitor example.

File Monitor output

Read more about file monitor example

Product Compatible and additional computed target framework versions.
.NET net5.0 was computed.  net5.0-windows was computed.  net6.0 was computed.  net6.0-android was computed.  net6.0-ios was computed.  net6.0-maccatalyst was computed.  net6.0-macos was computed.  net6.0-tvos was computed.  net6.0-windows was computed.  net7.0 was computed.  net7.0-android was computed.  net7.0-ios was computed.  net7.0-maccatalyst was computed.  net7.0-macos was computed.  net7.0-tvos was computed.  net7.0-windows was computed.  net8.0 was computed.  net8.0-android was computed.  net8.0-browser was computed.  net8.0-ios was computed.  net8.0-maccatalyst was computed.  net8.0-macos was computed.  net8.0-tvos was computed.  net8.0-windows was computed. 
.NET Core netcoreapp2.0 was computed.  netcoreapp2.1 was computed.  netcoreapp2.2 was computed.  netcoreapp3.0 was computed.  netcoreapp3.1 was computed. 
.NET Standard netstandard2.0 is compatible.  netstandard2.1 was computed. 
.NET Framework net461 was computed.  net462 was computed.  net463 was computed.  net47 was computed.  net471 was computed.  net472 was computed.  net48 was computed.  net481 was computed. 
MonoAndroid monoandroid was computed. 
MonoMac monomac was computed. 
MonoTouch monotouch was computed. 
Tizen tizen40 was computed.  tizen60 was computed. 
Xamarin.iOS xamarinios was computed. 
Xamarin.Mac xamarinmac was computed. 
Xamarin.TVOS xamarintvos was computed. 
Xamarin.WatchOS xamarinwatchos was computed. 
Compatible target framework(s)
Included target framework(s) (in package)
Learn more about Target Frameworks and .NET Standard.

NuGet packages

This package is not used by any NuGet packages.

GitHub repositories

This package is not used by any popular GitHub repositories.

Version Downloads Last updated
5.1.6.1 283 3/2/2022

The File Monitor Filter Driver SDK is a kernel-mode component that runs as part of the Windows executive above the file system. The file system filter driver can intercept requests targeted at a file system or another file system filter driver. By intercepting the request before it reaches its intended target, the filter driver can extend or replace functionality provided by the original target of the request. The EaseFilter file system filter driver can log, observe, modify, or even prevent the I/O operations for one or more file systems or file system volumes.