Fix Error 0x8007003b on Windows 10 & 11

Error 0x8007003b (ERROR_NETWORK_BUSY) usually appears when copying, moving, or syncing files over a network, and it means the server or shared folder is temporarily too busy to handle the request. The fix typically involves waiting a moment, restarting the network connection, or adjusting the file-sharing settings on the Windows machine that hosts the files. Below are the most effective ways to resolve it on Windows 10 and Windows 11, starting with the simplest and moving to more advanced steps.

What Causes Error 0x8007003b?

This error is not a corruption of your files—it’s a network communication problem. Windows reports it when a file operation (copy, move, delete, or backup) is interrupted because the remote computer or the network resource is busy. Common triggers include:

• Another process (like a backup job or antivirus scan) is using the same files or folder.
• The network connection is unstable or has high latency.
• The SMB (Server Message Block) protocol version mismatch between devices.
• Windows Firewall or third-party security software is blocking the transfer.
• Power settings on the host computer put the hard drive to sleep.

Understanding the cause helps you pick the right fix—most of the time it’s a temporary issue that clears up on its own, but if it persists, you’ll need to adjust settings.

Quick Fixes to Try First

Before diving into advanced settings, try these simple steps—they resolve a surprising number of cases:

1. Wait a few seconds and retry. The server may be momentarily overloaded. If the error appears once, a simple retry often works.
2. Restart the network connection. Disable and re-enable your Wi-Fi or Ethernet adapter, or unplug and replug the network cable.
3. Reboot both computers. A fresh start clears temporary glitches and releases any stuck file locks.
4. Check if the file is open elsewhere. Make sure no one else is using the file on the shared folder. Ask them to close it.
5. Run Windows Update. Install pending updates on both the client and the host—Microsoft often fixes network bugs in cumulative updates.

If none of these work, move on to the more targeted fixes below.

Adjust Network Sharing Settings on the Host

Since the error often comes from the computer that shares the folder, tweaking its sharing settings can help. On the host machine (the one with the files):

1. Open Control Panel → Network and Sharing Center → Advanced sharing settings.
2. Under All Networks, enable Turn on file and printer sharing (if it’s off).
3. Also under All Networks, select Turn off password-protected sharing if you’re on a trusted home network—this removes authentication overhead.
4. Click Save changes and retry the transfer.

If you’re using a work or domain network, check with your admin before disabling password protection. On Windows 11, the path is the same, but the settings are also accessible via Settings → Network & internet → Advanced network settings → Advanced sharing settings.

Change Power Settings to Keep the Hard Drive Awake

A common culprit is the host computer’s power plan turning off the hard drive after a period of inactivity. When you try to copy a large file, the drive spins up but takes a moment, causing the network request to time out with error 0x8007003b. To fix this on the host machine:

1. Open Control Panel → Power Options.
2. Click Change plan settings next to your active plan.
3. Click Change advanced power settings.
4. Expand Hard disk → Turn off hard disk after and set it to 0 (meaning never).
5. Click Apply and OK.

If you’re on a laptop, also check the Sleep settings—set sleep to Never when plugged in if you’re the one sharing files.

Disable IPv6 or Configure SMB Protocol

Sometimes the error is caused by IPv6 negotiation issues or an SMB protocol mismatch. Here are two adjustments that often resolve persistent cases:

• Disable IPv6 on the network adapter. Open Control Panel → Network and Sharing Center → Change adapter settings. Right-click your adapter, select Properties, uncheck Internet Protocol Version 6 (TCP/IPv6), and click OK. Restart the adapter. This forces IPv4, which is more reliable for local file sharing.
• Enable SMB 1.0 (not recommended unless necessary). If the host is an older device (like a Windows 7 or a NAS), it might be using SMB 1.0. On Windows 10/11, go to Control Panel → Programs → Turn Windows features on or off and check SMB 1.0/CIFS File Sharing Support. However, SMB 1.0 is insecure and should only be enabled temporarily if you must connect to an old device.

For most home networks, disabling IPv6 is safe and can resolve the error. If you use IPv6 for other purposes, you can re-enable it later.

Check Firewall and Antivirus Settings

Security software can block file transfers, especially if it inspects network traffic. To rule this out:

1. On the host machine, open Windows Defender Firewall (or your third-party firewall).
2. Look for rules related to File and Printer Sharing. Ensure they are enabled for Private networks.
3. If you have a third-party antivirus, temporarily disable its firewall or real-time protection (just for testing) and retry the transfer.

If the transfer succeeds with the firewall off, add an exception for the specific app (like Explorer or your backup software) and re-enable the firewall. Never leave the firewall disabled permanently.

Use a Different Transfer Method

If the error persists, the issue might be with the SMB protocol itself. Try an alternative to move your files:

• Use a cloud service (OneDrive, Google Drive, Dropbox) to sync the files instead of direct network copy.
• Use an external USB drive to physically move the data.
• Compress the files into a ZIP archive before copying—this reduces the number of file operations and can bypass the busy condition.
• Use a different protocol like FTP (if you have an FTP server) or a tool like Robocopy with the /R:3 /W:10 flags to retry automatically.

These workarounds don’t fix the root cause, but they get your data moved reliably.

Frequently Asked Questions

Is error 0x8007003b a sign of a failing hard drive?

No, it’s a network error, not a disk error. It indicates the remote server is busy or unreachable, not that your drive is failing. If you see it repeatedly, check the network connection and the host’s resource usage, not the disk health.

Does this error occur on Windows 10 and Windows 11 the same way?

Yes, both operating systems use the same SMB networking stack, so the error and the fixes are identical. The only difference is the location of some settings in the newer Settings app, but the Control Panel paths still work on both.

Why does the error happen when copying large files but not small ones?

Large transfers take longer, increasing the chance that a temporary network hiccup or a drive sleep cycle interrupts the operation. Small files complete before the problem manifests. The fixes above—especially keeping the hard drive awake—address this.

Can I fix this by changing the SMB version?

Yes, but it’s not the first thing to try. If the host is an old device, enabling SMB 1.0 might help, but it’s insecure. Modern Windows uses SMB 3.0 by default, which is more robust. If you have a NAS, check its settings to ensure SMB 3.0 is enabled.

Will disabling IPv6 affect my internet speed?

No, disabling IPv6 on your local adapter only affects IPv6 traffic. Most internet connections still work fine over IPv4, and you’re unlikely to notice any difference in speed or functionality. You can re-enable it later if needed.

What if none of these fixes work?

If the error persists after trying all the steps, consider resetting the network stack on both computers. Open Command Prompt as administrator and run netsh int ip reset and netsh winsock reset, then restart. If it still fails, the issue may be with your router or switch—reboot your network hardware and try again.

Related

• Restore a Lost Snapchat Streak Without Losing Progress
• How to Improve Voice Memo Audio on iPhone
• Why Does My iPhone Randomly Vibrate? Fixes