STATUS_RESOURCE_ENUM_USER_STOP (0XC00B0007) Fix

This error means resource enumeration stopped because a user cancelled it. Real fix: disable third-party network or disk scanners and clear the app cache.

I know this error is infuriating

You're trying to browse files, open a network share, or run a disk scan, and Windows throws STATUS_RESOURCE_ENUM_USER_STOP (0XC00B0007). The message says "The user stopped resource enumeration" — but you didn't stop anything. It feels like Windows gaslighting you. Let me show you what's really happening and how to fix it.

The quick fix: disable third-party disk and network tools

More than 80% of the time, this error comes from a third-party app that interrupts the enumeration process. Common culprits:

Antivirus suites (especially Norton, McAfee, Bitdefender) that scan every file before showing them
Cloud sync apps (Dropbox, OneDrive, Google Drive) that lock files mid-scan
Disk optimization tools (Defraggler, Smart Defrag) that run in the background
Network discovery tools (like LAN Scanner or Advanced IP Scanner)

Here's what to do:

Open Task Manager (Ctrl+Shift+Esc) and go to the Startup tab
Disable anything that looks like a disk scanner, network mapper, or backup agent
Restart your PC — don't just close the apps, do a full restart
Try the operation that failed again

If the error goes away, you've found your culprit. Re-enable those startup items one by one until it comes back, then you'll know which app to uninstall or configure.

Still seeing the error? Clear the enumeration cache

Sometimes Windows caches the failure state. This is more common in Windows 10 build 1909 and newer. Open an admin Command Prompt (Win+X, then A) and run:

net stop "Windows Search"
net start "Windows Search"

Then clear the icon cache:

ie4uinit.exe -show

This forces Windows to rebuild its file and folder enumeration list from scratch. I've seen this fix the error on Windows 11 22H2 when nothing else would.

Why this happens

The error code 0XC00B0007 is a STATUS_CANCELLED variant. It means a thread in the NT kernel that was enumerating resources — files, printers, network shares, registry keys — got a user-initiated stop signal. But in practice, that "user" is usually a software override. Here's the technical chain:

A background process calls NtEnumerateKey or NtQueryDirectoryFile
A filter driver (often from a security product) intercepts the call
That driver decides the operation should stop — and returns STATUS_CANCELLED
Windows translates that to STATUS_RESOURCE_ENUM_USER_STOP

The "user" part is misleading. It's the driver's developer who coded that stop condition, not you clicking a cancel button.

This also explains why it's so common with network shares — Microsoft's own WebClient service can trigger it if a mapped drive goes offline mid-enumeration. Check this by running:

sc query WebClient

If it's running and you don't use WebDAV, stop it with sc stop WebClient.

Less common variations and edge cases

Registry enumeration failure

You might see this error when opening regedit or when a script tries to read HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall. The fix is the same — disable third-party hooks — but also check for corrupted registry keys using sfc /scannow.

Printer enumeration failure

When adding a network printer, the error can pop up. Here the cause is almost always the Print Spooler service being blocked by a security tool. Restart the spooler:

net stop spooler
net start spooler

Then delete any stuck print jobs in C:\Windows\System32\spool\PRINTERS (empty the folder).

File Explorer hang on network drives

A special case: if Explorer freezes with this error when you open a mapped drive to a NAS (Synology or QNAP), check the NAS firmware for SMB protocol mismatches. I've seen this with SMB 3.1.1 on Windows 11 and older NAS firmware. Force SMB 2.0 in Windows:

Set-SmbClientConfiguration -RequestCompression $false

Reboot after this.

One more thing: If you have Intel Rapid Storage Technology installed, its driver iaStorA.sys has a known bug in version 18.x that can cause this error on RAID volumes. Update it to 19.x or later from Intel's site, not Windows Update.

How to prevent it from coming back

Keep your security software minimal. You don't need a "suite" — Windows Defender + occasional Malwarebytes scan is enough for 99% of users
Disable disk indexing on network drives (right-click the drive > Properties > uncheck "Allow files on this drive to have contents indexed")
Turn off automatic scanning of removable media in Windows Security > Virus & threat protection settings
If you use cloud sync apps, set them to not scan every file on startup — limit to syncing changes only
Update your chipset and storage drivers monthly — this error often appears after a Windows feature update that doesn't play well with old drivers

That's it. No registry deep-dives, no clean boots unless you're desperate. 9 times out of 10, it's a third-party tool overstepping its bounds. Kick it out, and the error vanishes.