Fix ERROR_NOTIFY_ENUM_DIR (0x000003FE) in File Explorer

What's Triggering This Error

You're seeing ERROR_NOTIFY_ENUM_DIR (0x000003FE) when Windows tries to track changes in a folder—usually a network share, external drive, or a local folder hammered by too many file modifications. The OS can't enumerate the changes fast enough, so it bails. Common scenarios: saving large files to a mapped network drive, running a build script that creates/deletes temp files, or using an app that monitors a folder (like a sync tool).

I've seen this most often on Windows 10 22H2 and Windows 11 23H2 with SMB shares. Antivirus real-time scanning is a frequent accomplice—it locks the directory during the enumeration call.

Here's the troubleshooting flow. Start with step 1 and stop when the error's gone.

Fix 1: Restart the Windows Notification Service (30 seconds)

Open a command prompt as admin (Win+R, type cmd, Ctrl+Shift+Enter). Run:

net stop WSearch && net start WSearch

That restarts the Windows Search service, which handles file change notifications for Explorer. Also restart the Workstation service if you're on a network drive:

net stop workstation && net start workstation

Check if the error's gone in your problematic folder. If it persists—and it often does with persistent triggers—move on.

Fix 2: Disable Antivirus Real-Time Scanning (5 minutes)

If you're on a network share or external drive, antivirus real-time scanning is a prime suspect. It intercepts the notification call and delays the enumeration. Temporarily disable your antivirus (Windows Defender or third-party) for the affected folder.

• Windows Defender: Open Windows Security > Virus & threat protection > Manage settings > Real-time protection > toggle Off.
• Third-party (Norton, McAfee, etc.): Right-click the tray icon > Disable until next restart.

If the error stops, add an exclusion for that folder in your antivirus settings. Don't leave real-time protection off long-term—that's asking for trouble.

Fix 3: Registry Tweak to Increase Notification Buffer (15+ minutes)

This is the real fix for persistent cases. Windows has a hidden buffer size for directory change notifications. When it's too small, you get 0x000003FE. I've bumped this on dozens of machines running build servers or heavy file syncing.

Warning: Editing the registry can break things. Back it up first (File > Export).

1. Open Regedit (Win+R, type regedit, Enter).
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.
3. Right-click in the right pane > New > DWORD (32-bit) Value. Name it DirectoryNotificationBufferSize.
4. Set its value to 65536 (decimal). That's 64 KB—double the default 32 KB. For extreme cases (like build scripts creating 10k+ files), try 131072.
5. Restart your computer.

After the reboot, test the folder. If the error's gone, you're set. If not, try increasing the value to 128 KB or 256 KB. I've never needed more than 256 KB in 14 years.

Fix 4: Check for Shell Extension Conflicts (15+ minutes)

Third-party shell extensions (from apps like Dropbox, Google Drive, or 7-Zip) can interfere with directory change monitoring. Use ShellExView (free tool from NirSoft) to disable non-Microsoft extensions.

1. Download ShellExView and run it.
2. Sort by Type—focus on Context Menu handlers and Property Sheet handlers.
3. Select all non-Microsoft entries (hold Ctrl, click each).
4. Right-click > Disable Selected Items.
5. Restart Explorer (Task Manager > Windows Explorer > Restart) or reboot.

If the error disappears, re-enable extensions one by one until it comes back. That's your culprit. Uninstall the offending app or leave the extension disabled.

Fix 5: Network Drive-Specific Fixes (SMB Shares)

If this only happens on a mapped network drive, check these:

• Disable offline files: Go to Control Panel > Sync Center > Manage offline files > Disable offline files. Restart.
• Increase SMB credits: On the file server, open PowerShell as admin and run: Set-SmbServerConfiguration -EnableCreditsOnAllInterfaces $true. Then restart the server.
• Switch to SMB 3.0: If the server's running Windows Server 2012 or newer, make sure SMB 1.0 is disabled. Run Disable-WindowsOptionalFeature -Online -FeatureName smb1protocol on both sides.

I've seen these steps fix the error on corporate file servers with heavy write loads.

When to Give Up and Reimage

If none of the above works after a full reboot, the issue might be a corrupted system file. Run sfc /scannow from an admin command prompt. If that finds corrupted files but can't fix them, run DISM /Online /Cleanup-Image /RestoreHealth. If both pass and the error persists, it's likely a hardware issue (failing drive, bad network card) or a deeply entrenched driver problem. A clean install of Windows usually nukes it—but that's a last resort.