How to Audit File and Folder Deletion on Windows File Server

File and folder deletion auditing on Windows File Server is the process of tracking and logging when users delete files or folders from shared storage. This is accomplished by enabling object access auditing through Group Policy and configuring specific audit entries on the files and folders you want to monitor. When properly configured, Windows records deletion events in the Security log, allowing administrators to identify who deleted what and when.

Tracking who deleted files or folders on Windows File Servers is a vital part of both security and IT operations. If users are deleting files that contain sensitive information, they might be trying to hide something. Likewise, if important files are deleted, it could result in disruption to the business.

Either way, it’s important that you can audit file and folder deletion on File Server.

File and folder deletion auditing can be done for multiple file servers in your network by enabling object access auditing through GPO and then configuring auditing on the required files and folders that you want to audit.

Administrators, after that, can easily track these events in Windows security logs. You will have to follow these three steps:

  • Enable “Audit Object Access” through GPO.
  • Enable Auditing of Files and Folders
  • Track File and Folder Deletion Events in Event Viewer

Prerequisites

Before you begin, ensure you have the following:

  • Supported Windows Server versions: Windows Server 2012, 2016, 2019, 2022, or 2025
  • Required permissions: Domain Admin or equivalent privileges to modify Group Policy and folder security settings
  • Important: Auditing must be enabled before deletion events occur—Windows cannot retroactively log deletions that happened prior to enabling auditing

Key Event IDs for File Deletion Auditing

Event ID Description Key Fields to Check
4660 An object was deleted Includes object name, path, and user details; use with 4660 to identify deleted files
4663 An attempt was made to access an object Account Name, Caller Process Name
4659 A handle to an object was requested with intent to delete Logged for deletions from shared folders; includes object name

Step 1 – Enable “Audit Object Access”

Perform the following steps to enable this group policy.

  • On the primary domain controller, open “Group Policy Management”.
  • You have to edit either “Default Domain Policy” or create a new domain level policy and link it.
  • Edit the default or a customized Group Policy to access “Group Policy Management Editor”.
  • Go to “Computer Configuration” – “Windows Settings” – “Security Settings” – “Local Policies” – “Audit Policy” – “Audit object Access”.
    Audit Object Access
    Figure 1: Audit Object Access
  • Double-click this policy to open “Properties” window
    Properties of Audit Object Access
    Figure 2: Properties of Audit Object Access
  • Click the “Define these policy settings” checkbox.
  • Now, click “Success” and “Failure” under “Audit these attempts”.
  • Click “Apply” and “OK”.
  • Close “Group Policy Management Editor” and “Group Policy Management Console”.

Step 2 – Enable Auditing of Files and Folders

Perform the following steps to enable the auditing of selected files or folders.

  • In Windows File System, use Windows Explorer to select the folder that you want to audit.
  • Right-click it and select “Properties”.
  • Go to the “Security” tab.
    Security Tab of Folder Properties
    Figure 3: “Security” Tab of Folder Properties
  • Click “Advanced” to access “Advanced Security Settings”. In the “Advanced Security Settings” window, go to the “Auditing” tab. It displays the existing auditing entries (if there are any).
    Auditing tab in Advanced Security Settings
    Figure 4: “Auditing” tab in “Advanced Security Settings.”
  • To add a new entry, click “Add”. “Auditing Entry” window appears on the screen.
    Configuring auditing entry
    Figure 5: Configuring auditing entry

    Note: You can select ‘Change Permissions’ if you want to audit permissions changes. Learn more

  • Click “Select a Principal” to select users whose activities you want to track. If you want to audit all users’ activities, enter “Everyone” in the “Enter the object name” box.
    Select users for auditing
    Figure 6: Select users for auditing
  • Click “Check Names” to verify the provided input.
  • Click “OK” to select the object. It takes you back to the “Auditing Entry” window.
  • In “Type” field, select “Success”,” Fail”, or “All”.
  • In the “Applies to” field, select “This folder, subfolder, and files”. Then, all the subfolders and files within this folder will be tracked.
  • Click the “Show advanced permission” option in the permissions section to view all the permissions.
  • Here, select the activities that you want to audit. For tracking file and folder deletion, you will have to select the “Delete”, and “Delete subfolders and files” options.
  • Click “OK” to close “Auditing Entry” window. It takes you back to the “Auditing” tab of advanced security settings, which now displays the newly added user.
  • Click “Apply” and “OK” in “Advanced Security Setting” window.
  • Click “Apply” and “OK” to close the folder properties.

Step 3 – Search Relevant Event IDs in Event Viewer to Track Deleted Files and Folders

Open Windows Event Viewer – Go to “Windows Logs” – “Security” – “Filter Current Log” – Search Event ID 4660 for file and folder deletion.

In the following image, you can see the event id 4660 which has been logged after a folder has been deleted. However, the object’s name is not visible. In the next image, you can see the objects name as well which has been logged at the same time.

An object delete event is logged
Figure 7: An object delete event (4660) is logged

The delete event ID 4660 does not contain the object name, so you have to view event ID 4663 to get that information. In the following image, which shows event 4663 (folder delete event), the object name (C:\Documents\Projects) is also visible.

Folder delete event
Figure 8: Folder delete event (4663)

Here, you can see that time to log both event IDs 4660 and 4663 is the same.

Using PowerShell to Filter Deletion Events

You can also use PowerShell to filter Security logs for deletion events:

# Get Event ID 4660 (deletion occurred) Get-WinEvent -FilterHashtable @{LogName='Security';ID=4660} -MaxEvents 50
# Get Event ID 4663 (includes object name) Get-WinEvent -FilterHashtable @{LogName='Security';ID=4663} -MaxEvents 50
# Filter 4663 events for delete operations Get-WinEvent -FilterHashtable @{LogName='Security';ID=4663} | Where-Object {$_.Message -like "*Delete*"}

Troubleshooting Common Issues

If deletion events are not appearing in your Security logs, check the following:

  • GPO replication delays: Run gpupdate /force on the file server to immediately apply policy changes
  • Incorrect audit settings: Verify that both “Success” and “Failure” are enabled in the Audit Object Access policy
  • Auditing not enabled at time of deletion: Windows cannot log events retroactively; auditing must be configured before the deletion occurs
  • Log size limitations: The Security log may have reached its maximum size and is overwriting old events; increase the log size or archive logs more frequently
  • Missing folder-level auditing: Ensure auditing entries are configured on the specific folders you want to monitor (Step 2)

Native Auditing vs. Third-Party Tools

Aspect Native Windows Auditing Third-Party Auditing Solutions
Object name visibility Event ID 4660 lacks object name; must correlate with 4663 Full object details in single record
Log noise High volume of events requiring manual filtering Account Name, Caller Process Name
Reporting Manual Event Viewer searches Automated reports and dashboards
Alerting Requires custom scripts or SIEM integration Built-in real-time alerts
Storage Limited by Security log size Centralized, long-term storage

How Lepide File Server Auditor Tracks Files and Folders Deletion

As we’ve seen from the above, tracking file and folder deletion in File Server using native auditing is cumbersome, error-prone, and lacks critical audit information.

Thankfully, there’s a better way.

Lepide File Server Auditor effortlessly tracks file and folder deletions with proactive and continuous monitoring. The following image shows the files and folders deletion report. You can see all necessary information related to files and folders deletion is displayed in a single line record.

File and Folder deletion report - screenshot
Figure 9: File and Folder deletion report

The highlighted record, which shows “Projects” in the “Object Name” column shows the same event in Lepide File Server Auditor.

So, when it comes to tracking file and folder deletion, native auditing clearly doesn’t provide as much value as Lepide File Server Auditor. Don’t believe us? Start your own free trial today by filling in the form below:

Frequently Asked Questions

Which Event ID shows deleted file names?

Event ID 4663 includes the object name and path. Event ID 4660 confirms deletion but does not include the file or folder name, so you must correlate both events using their timestamps.

How long are deletion events retained?

Retention depends on your Security log settings. By default, Windows may overwrite events when the log reaches its maximum size. Configure log size and retention policies in Event Viewer under 'Log Properties' to ensure adequate retention for your compliance requirements.

Does auditing need to be enabled before the deletion occurs?

Yes. Windows can only log deletion events if auditing is enabled at the time of deletion. You cannot retroactively audit deletions that occurred before configuring audit policies.

Why do I see Event ID 4663 but not 4660?

Event ID 4663 logs access attempts including delete operations, while 4660 specifically logs object deletion. Both should appear with the same timestamp for a deletion event. If 4660 is missing, verify your audit policy settings.
Find Who Deleted Files and Folders with Lepide File Server Auditor
Fill in the rest of the form to
download the 20-day free trial
x