FileMon for Windows v7.04

Introduction

Note: Filemon and Regmon have been replaced by Process Monitor on versions of Windows starting with Windows 2000 SP4, Windows XP SP2, Windows Server 2003 SP1, and Windows Vista. Filemon and Regmon remain for legacy operating system support, including Windows 9x.

FileMon monitors and displays file system activity on a system in real-time. Its advanced capabilities make it a powerful tool for exploring the way Windows works, seeing how applications use the files and DLLs, or tracking down problems in system or application file configurations. Filemon\'s timestamping feature will show you precisely when every open, read, write or delete, happens, and its status column tells you the outcome. FileMon is so easy to use that you\'ll be an expert within minutes. It begins monitoring when you start it, and its output window can be saved to a file for off-line viewing. It has full search capability, and if you find that you\'re getting information overload, simply set up one or more filters.

FileMon works on NT 4.0, Windows 2000, Windows XP, Windows XP and Windows Server 2003 64-bit Edition, Windows 2003 Server, Windows 95, Windows 98 and Windows ME.

Installation and Use

If you have questions or problems please visit the Sysinternals Filemon Forum.

Simply run FileMon (filemon.exe). You must have administrator privilege to run FileMon. When FileMon is started for the first time it will monitor all local hard drives. Menus, hot-keys, or toolbar buttons can be used to clear the window, select and deselect monitored volumes including network volumes (Windows NT/2K/XP), save the monitored data to a file, and to filter and search output.

If you\'ve specified filters then FileMon will ask you to confirm filters used from the last session each time you start it. To start FileMon without it prompting you specify the /q switch on the command line. When FileMon starts it automatically captures file system activity. To start it with capture disabled use the /o switch on the command-line.

As events are printed to the output, they are tagged with a sequence number. If Filemon\'s internal buffers are overflowed during extremely heavy activity, this will be reflected with gaps in the sequence number.

Each time you exit FileMon it remembers the filters you\'ve configured, position of the window and the widths of the output columns.

Filtering

Use the Filter dialog, which is accessed with a toolbar button or the Edit|Filter/Highlight menu selection, to select what data will be shown in the list view. The \'*\' wildcard matches arbitrary strings, and the filters are case-insensitive. Only matches shown in the include filter, but that are not excluded with the exclude filter, are displayed. Use \';\' to separate multiple strings in a filter (e.g. \"filemon;temp\"). Windows NT/2000 note: because of the asynchronous nature of file I/O, its not possible to filter on the result field.

For example, if the include filter is \"c:\\temp\", and the exclude filter is \"c:\\temp\\subdir\", all references to files and directories under c:\\temp, except to those under c:\\temp\\subdir will be monitored.

Wildcards allow for complex pattern matching, making it possible to match specific file accesses by specific applications, for example. The include filter \"Winword*Windows\" would have FileMon only show accesses by Microsoft Word to files and directories that include the word \"Windows\".

Use the highlight filter specify output that you want to have highlighted in the listview output. Select highlighting colors with Edit|Highlight Colors.

Additional filter options select or deselect read, write or open operations. In many troubleshooting scenarios only open operations are of interest, for example.

Selecting Volumes (Windows NT/2K/XP/2K3)

The Volumes menu can be used to select and deselect monitored volumes. Select the Network menu item to monitor accesses to any network resources, including remote shares and UNC path name accesses to remote volumes.

Limiting Output

The History Depth dialog, accessed via toolbar button or the Edit|History menu item, allows you to specify the maximum number of lines that will be remembered in the output window. A depth of 0 is used to signify no limit.

Searching the Output

You can search the output window for strings using the Find menu item (or the find toolbar button). You can repeat the search in the forward direction with the F3 key and in reverse with Shift+F3. To start a search at a particular line in the output, select the desired line by clicking on the far left column (the index number). If no line is selected a new search starts at the first entry in searching down, and at the last entry for searching up.

Options

FileMon can either timestamp events or show their duration. The Options menu and the clock toolbar button let you toggle between the two modes. The button on the toolbar shows the current mode with a clock or a stopwatch. When showing duration the Time field in the output shows the number of seconds it took for the underlying file system to service particular requests. The Options|Show Milliseconds menu entry lets you add millisecond resolution to times presented when FileMon shows clock times.

You can toggle FileMon to always remain a top window with the Options|Always On Top menu item. In addition, you can toggle FileMon not to scroll the listview via the Options|Auto Scroll menu item or corresponding toolbar button.

Named Pipes and Mail Slots

Starting in version 4.1 FileMon is able to monitor named pipe and mail slot file system activity on Windows NT/2K. Named pipes are commonly used as a communications mechanism in NT/Win2K by core subsystems like the Local Security Authority Subsystem (LSASS), and are used by DCOM. They are also used by network components such as the Browser service. To see named pipe activity with FileMon select Named Pipes in the Drives menu and perform an operation on a shared network resource, or open an application such as Regedt32 that interacts with the security subsystem.

How FileMon Works

For the Windows 9x driver, the heart of FileMon is in the virtual device driver, Filevxd.vxd. It is dynamically loaded, and in its initialization it installs a file system filter via the VxD service, IFSMGR_InstallFileSystemApiHook, to insert itself onto the call chain of all file system requests. On Windows NT the heart of FileMon is a file system driver that creates and attaches filter device objects to target file system device objects so that FileMon will see all IRPs and FastIO requests directed at drives. When FileMon sees an open, create or close call, it updates an internal hash table that serves as the mapping between internal file handles and file path names. Whenever it sees calls that are handle based, it looks up the handle in the hash table to obtain the full name for display. If a handle-based access references a file opened before FileMon started, FileMon will fail to find the mapping in its hash table and will simply present the handle\'s value instead.

Information on accesses is dumped into an ASCII buffer that is periodically copied up to the GUI for it to print in its listbox.

More Information

The following serve as additional sources of information on the Windows 9x file system:

• The Windows 95/98 DDK
• \"Examining the Windows 95 Layered File System,\" by Mark Russinovich and Bryce Cogswell, Dr. Dobb\'s Journal, December 1995
• \"Systems Programming for Windows 95,\" by Walter Oney, Microsoft Press, 1996 (a must-have for VxD writers)
• \"Inside the Windows 95 File System,\" by Stan Mitchell, O\'Reilly and Associates, 1996

These are sources of information on the Windows NT/2000 file system and/or FileMon:

• Inside Windows 2000, 3rd Edition by David Solomon and Mark Russinovich, 2000
• \"Examining The Windows NT File System,\" by Mark Russinovich and Bryce Cogswell, Dr. Dobb\'s Journal, Febrary 1997
• \"Inside NT Utilities,\" Windows NT Magazine, February 1999
• \"Windows NT File System Internals,\" by Rajeev Nagar, O\'Reilly and Associates, 1997
  

Microsoft Filemon KB Articles

These KB articles reference Filemon to help diagnose or troubleshoot various problems:

• 830903: A file in a network folder opens as read-only or returns an error message that the file type cannot be recognized
• 319844: ACC2002: Error Message: ActiveX Component Can\'t Create Object
• 830761: Best practices for deploying Visual Basic 6.0 applications
• 837932: Event ID 2108 and Event ID 1084 occur during inbound replication of Active Directory in Windows 2000 Server and in Windows Server 2003
• 819612: FIX: Slow Performance When the Browser Capabilities Evaluator Is Removed from the Cache
• 286198: HOWTO: Track \"Permission Denied\" Errors on DLL Files
• 308940: HOWTO: Troubleshoot Error 1928 \"Error Registering COM+ Application\"
• 814774: HOW TO: Troubleshoot Site Deployment Issues in Microsoft Content Management Server 2002
• 198038: INFO: Useful Tools for Package and Deployment Issues
• 319440: Logon Delays Over Slow Links if Oplock Is Not Granted for the Policy File
• 260513: PRB: An Error Occurs When You Install Visual Studio Products
• 306269: PRB: Error 80004005 \"The Microsoft Jet Database Engine Cannot Open the File \'(Unknown)\'
• 306386: PRB: FileMon Shows That DAO360.dll Fails to Load MSJet49.dll, MSJet48.dll, and Other MSJetxx.dll Files
• 243583: PRB: Mib.bin Causes Visual Studio Setup to Fail
• 310586: The Exchange MSSearch instance does not come online on a cluster and event IDs 3055 and 10006 are logged
• 555069: Top 10 Potential Problematic Security Settings for Microsoft Windows XP Professional Edition and Microsoft Windows Server 2003
• 196453: Troubleshooting NTVDM and WOW Startup Errors
• 318746: XADM: Error Message: Error 123: The Filename, Directory Name, or Volume Label Syntax Is Incorrect
• 296136: XADM: Event ID 3036 and 3026 Messages Occur When You Populate Mailbox Store
• 830075: Winmgmt.exe uses more CPU resources than you expect
• 867651: You cannot add a TLS certificate to a computer that is running Office Live Communications Server 2003
• 319844: You receive a \"ActiveX component can\'t create object\" error message when using Access

link: http://technet.microsoft.com/en-us/sysinternals/bb896642.aspx