STATUS_NETWORK_BUSY (0XC00000BF) — Fix It Now

You're working on a file server, and suddenly you get STATUS_NETWORK_BUSY (0XC00000BF). The typical trigger: you're copying a big file over SMB to a network share, or you're trying to print to a shared printer, and Windows just sits there, then throws this error. It happens most often when you've got multiple file transfers running at once, or when an old mapped drive hasn't been disconnected properly. The network itself might be fine — ping works, other machines are reachable — but that one connection is stuck in a busy state.

Why This Happens

The culprit here is almost always a saturated SMB session. Windows uses SMB (Server Message Block) to talk to network drives and printers. When you send a request and the server doesn't respond fast enough (maybe because it's handling too many requests, or the network is actually congested on that specific path), Windows marks the connection as busy. The error code 0XC00000BF is the kernel's way of saying, "I can't process this right now — the resource is locked."

Don't bother checking your firewall or antivirus first. It rarely helps. The real problem is usually one of three things: a stuck NetBIOS session, an orphaned SMB connection that didn't close cleanly, or network congestion on the switch port. Sometimes it's just a flaky cable on a busy line.

Step-by-Step Fix

Step 1: Kill Stuck SMB Sessions

1. Open a command prompt as administrator.
2. Type net use and press Enter. Look for any connections that show "Unavailable" or "Disconnected".
3. For each one that looks stuck, run: net use * /delete (this deletes all network connections). Or delete individually with: net use X: /delete (replace X with the drive letter).
4. After that, force the SMB client to reset: net stop server followed by net start server.
5. Wait 30 seconds, then reconnect your drives normally.

Step 2: Reset the Network Adapter

If Step 1 didn't work, the SMB stack itself might be hanging. Here's the blunt fix:

1. Open Device Manager (Win+R, type devmgmt.msc).
2. Find your network adapter under Network adapters. Right-click it and select Disable device.
3. Wait 10 seconds, then right-click and Enable device.
4. This drops all active sessions. You'll lose network for a moment, but it clears the jam.

Step 3: Clear the NetBIOS Cache

If the error came after an IP change or a DNS hiccup, the NetBIOS cache might be holding a stale entry:

1. Open command prompt as admin again.
2. Run nbtstat -R (capital R — this purges the remote cache).
3. Then run nbtstat -RR (releases and refreshes all names).
4. Finally, run ipconfig /flushdns.

Step 4: Check SMB Settings

Older Windows versions sometimes struggle with SMB2 or SMB3 negotiation. If you're on an old NAS or printer, try forcing SMB1 (only if needed — it's insecure):

1. Open PowerShell as admin.
2. Run Get-SmbServerConfiguration to see current settings.
3. If you need to enable SMB1 (not recommended), run: Set-SmbServerConfiguration -EnableSMB1Protocol $true.
4. Or, disable SMB2/3 temporarily to test: Set-SmbClientConfiguration -EnableSMB2Protocol $false (then reboot). Re-enable after testing.

Step 5: Reset the Winsock and TCP/IP Stack

This is nuclear, but it works when nothing else does:

1. Open command prompt as admin.
2. Run these three commands in order:

netsh winsock reset
netsh int ip reset
ipconfig /release
ipconfig /renew

3. Reboot your machine.

If It Still Fails

If none of that worked, you've got a deeper problem. Check these:

• Switch port congestion. Run a continuous ping to the server while the error happens. If you see packet loss, the switch port is saturated. Move your cable to a different port or ask your network team to check for errors on that port.
• Server-side limits. On the server (if you have access), check the SMB server for open sessions. Run net session on the server to see if there are too many active connections. Windows can handle lots, but cheap NAS units often have a hard limit of 10-20 concurrent SMB sessions.
• Driver or firmware issue. Some Realtek and Broadcom NICs have known bugs with SMB large sends. Update your NIC driver from the manufacturer's site — not Windows Update.
• Replace the cable. Seriously. I've seen bad Cat5e cables cause intermittent BUSY errors that look like software issues. Swap it out with a known good cable.

One last thing: if you're on a VPN, disconnect and reconnect. VPN tunnels can cause SMB to timeout and leave connections in a busy state. That's a whole other can of worms, but the fixes above handle it too.