How to fix Error 745 on Windows 11

by

Windows 11 Error 745 Troubleshooting Guide

Why This Error Happens

Error 745 (ERROR_NOTIFY_CLEANUP) is a system-level notification indicating that a directory change notification request (used by applications to monitor file/folder changes via ReadDirectoryChangesW or similar APIs) was terminated because the handle associated with that request was closed—either intentionally by the application or forcibly due to a crash, timeout, or resource cleanup. This is often not a “true” error but rather an informational status code that gets misinterpreted as a fault, typically triggered by improperly closed file handles, abrupt application termination, or antivirus/EDR software interfering with file system monitoring hooks. It can also surface when a network share or mapped drive being monitored becomes unavailable, forcing Windows to clean up the pending notification request.

Step-by-Step Resolution Guide

  1. Identify the source application: Open Event Viewer (eventvwr.msc) → navigate to Windows Logs > Application and System, filter by Event ID 745, and check the “Source” column to determine which process or service triggered the notification cleanup.

  2. Update or reinstall the affected application: If the error correlates with a specific app (e.g., backup software, sync clients like OneDrive/Dropbox, or antivirus), go to Settings > Apps > Installed Apps, locate the app, and select Advanced options > Repair, or download the latest version from the vendor.

  3. Check for handle leaks using Process Explorer: Download Process Explorer from Microsoft Sysinternals, run it as Administrator, and use Find > Find Handle or DLL to search for handles tied to the affected directory. If a process is holding a stale or orphaned handle, terminate it via right-click → Kill Process.

  4. Disable third-party antivirus/EDR temporarily: Some security tools hook into NtNotifyChangeDirectoryFile calls. Temporarily disable real-time protection (Settings → Privacy & Security → Windows Security → Virus & threat protection → Manage settings) and check if the error persists.

  5. Verify network share stability: If the monitored path is a mapped network drive, open File Explorer, right-click the drive → Properties, and confirm connectivity. Re-map the drive using net use Z: \\server\share /persistent:yes if disconnections are frequent.

Alternative or Verification Steps

  • Verify the fix: Reopen the application that triggered the notification and monitor Event Viewer for 24 hours to confirm Event ID 745 no longer appears, or use Process Monitor (ProcMon) from Sysinternals to confirm directory change notifications complete without unexpected handle closures.
  • Alternative fix: If the issue persists only on network drives, switch from SMB-based directory monitoring to a polling-based file watcher in the affected application’s settings (if configurable), which avoids reliance on persistent notify-change handles.