Fix Error 0X00003B02: User Stopped Resource Enumeration

What actually triggers this error

You're browsing network shares in File Explorer, or you're running a script that lists resources on a remote server, and suddenly you see it: ERROR_RESOURCE_ENUM_USER_STOP (0X00003B02). The system tells you the user stopped resource enumeration. But you didn't stop anything. In most cases, this happens when Windows tries to enumerate shared folders or printers on a remote machine, and something cuts the connection mid-stream.

I've seen this on Windows 10 and 11 mostly, but also on Server 2019 and 2022. The classic scenario: you open Network in File Explorer, wait for it to populate, then the error pops. Or you're using net view \\server and it returns this error. Another common trigger: a scheduled task or backup script that lists network paths fails with this code.

Why it happens

Under the hood, Windows sends out a resource enumeration request using the SMB protocol. The remote machine replies with a list of shares, printers, and other resources. But if the remote machine is slow, or if your local firewall or security software kills the connection prematurely, Windows interprets that as "user stopped it." It's a misleading error message — the user didn't do anything. The real culprit is usually a timeout or a permission denial that looks like a cancellation.

The most common causes I've run into:

Network timeout: The remote server takes too long to respond, and the client gives up.
Firewall or security software: Third-party antivirus or the Windows Firewall itself might block the enumeration packets.
Credential issues: The remote machine rejects the user's token, and Windows cancels the request instead of showing a clear access denied.
SMB version mismatch: Older servers (like Windows 7 or Server 2008) using SMBv1, but newer Windows clients have SMBv1 disabled. The negotiation fails, and it looks like a user stop.

Step-by-step fix

Check your credentials for the remote machine. Open a command prompt and run net use \\remote-pc\ipc$. If it asks for a password, put in the right one. If it says access denied, you need to fix permissions or supply the correct username/password. Had a client last month whose print queue died because the admin password had changed and nobody updated the stored credentials.
Disable IPv6 temporarily. IPv6 can cause odd enumeration failures. Go to Network Settings > Change adapter options > Right-click your adapter > Properties > Uncheck Internet Protocol Version 6 (TCP/IPv6). Reboot. Test. If it works, consider keeping it off or troubleshooting IPv6 further.
Turn off third-party antivirus temporarily. I know it's a pain, but many security suites (especially McAfee and Norton) interfere with SMB enumeration. Disable the firewall or web protection for 5 minutes and test.
Enable SMBv1 on the client as a test. This is a last resort because SMBv1 is insecure. But if you're hitting an old server, you might need it. Open PowerShell as admin and run:
```
Set-SmbServerConfiguration -EnableSMB1Protocol $true
```
Reboot. Test. If it fixes the issue, start planning to upgrade the server instead of leaving SMBv1 on.
Increase the network enumeration timeout. Registry edit:
```
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters
```
Create a DWORD called SessionTimeout and set it to decimal 120 (or higher, like 300). Reboot. This gives the remote machine more time to respond.
Flush DNS and reset NetBIOS cache. Run as admin:
```
ipconfig /flushdns
nbtstat -R
nbtstat -RR
```
Then try the enumeration again.

If it still fails

Check the Event Viewer on both machines. On the client, look in Applications and Services Logs > Microsoft > Windows > SMBClient > Operational. You'll see event IDs 1024 or 1025 with more detail. On the server, check SMBServer > Operational. The error might point to a specific share or permission that's failing.

Also try a different method to list resources: net view \\remote-pc versus File Explorer. If one works and the other doesn't, you've got a client-side issue (like Explorer caching bad data). I've had to clear the Network list cache by deleting %appdata%\Microsoft\Windows\Recent\AutomaticDestinations contents — messy but effective.

Last resort: run wmic /node:"remote-pc" path Win32_Share get Name. This uses WMI instead of SMB. If that works, the problem is SMB-specific, not network connectivity. Good luck.