STATUS_BAD_REMOTE_ADAPTER (0XC00000C5) Fix: Remote Adapter Not Compatible

You're staring at error 0XC00000C5, and it's a pain. Let's cut through the noise and fix it.

This error usually pops up when you're trying to connect to a network share, a printer, or a remote service over SMB (Server Message Block). It's Windows saying "I tried to talk to that remote adapter, but it didn't understand me." The most common trigger? An old or mismatched network driver on your PC, or a remote system that's running a very old SMB version.

The Real Fix: Update Your Network Adapter Driver

In 8 out of 10 cases, I've seen this fixed by updating the network driver on your local machine. Not the remote one — yours. Here's the exact steps.

1. Open Device Manager. Press Windows Key + X and choose Device Manager from the menu that pops up.
2. Expand "Network adapters." You'll see a list of all your network hardware — Wi-Fi, Ethernet, Bluetooth, maybe virtual adapters.
3. Find your active adapter. If you're on Wi-Fi, look for something like "Intel(R) Wi-Fi 6 AX200" or "Realtek PCIe GbE Family Controller". Right-click it and choose Update driver.
4. Select "Browse my computer for drivers." Then pick "Let me pick from a list of available drivers on my computer."
5. Uncheck "Show compatible hardware." This is the key step most folks skip. You'll see a list of every network driver Microsoft has. Scroll down and pick the newest one from your adapter's manufacturer — usually Intel, Realtek, or Qualcomm. Click Next.
6. Wait for the install. After it finishes, you'll see a prompt to restart. Don't skip the restart — Windows needs to reload the driver stack.

Expected outcome: After the restart, try connecting to the remote resource again. If the error's gone, you're done. If it's still there, move on to the next fix.

Why This Works

Error 0XC00000C5 often comes from a mismatch in the way your network adapter handles data frames — specifically, large send offload (LSO) or checksum offloading. Older drivers might send packets in a format the remote adapter can't parse. A newer driver from the manufacturer fixes these bugs. Windows Update's driver might be old or generic — that's why we picked from the full list.

Second Fix: Disable IPv6 (Temporary Test)

Some remote adapters (especially older NAS devices or printers) struggle with IPv6. Let's rule that out fast.

1. Open Control Panel > Network and Sharing Center > Change adapter settings.
2. Right-click your active connection (Wi-Fi or Ethernet) and choose Properties.
3. Uncheck "Internet Protocol Version 6 (TCP/IPv6)." Don't touch anything else.
4. Click OK, then close the window.

Test immediately: Try the connection that was failing. If it works now, you've found the culprit. You can leave IPv6 off, but I'd recommend turning it back on later and checking for a driver update for the remote device instead — IPv6 isn't the real problem, it's just a symptom of bad negotiation.

Third Fix: Restart the SMB Service

This one's quick, and it's helped me with stubborn cases where the driver was fine but the SMB stack got stuck.

1. Open an administrator Command Prompt. Press Windows Key + X, choose Windows Terminal (Admin) or Command Prompt (Admin).
2. Type these two commands one at a time, pressing Enter after each:

net stop lanmanserver
net start lanmanserver

That restarts the Server service, which handles SMB connections. You won't lose any shares — it's just a refresh.

Expected outcome: The services stop and start without errors. Try your remote connection again.

Less Common Variations

1. Remote Adapter Is Dead or Mismatched Hardware

I once spent an hour on this error only to find the remote NAS box had its Ethernet adapter fried. If you've tried the above, check the remote device's own network settings. Can you ping it? If you can't even get a ping reply, the remote adapter is offline or physically broken. Swap the cable or the device.

2. SMB Protocol Version Mismatch

Windows 10/11 have SMB 3.0 by default. Some old devices (like a 2008-era NAS) only speak SMB 1.0. That's a known cause of 0XC00000C5. To check:

On your PC, open PowerShell as admin and run:

Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol

If it shows False, SMB1 is off (good security practice). But if the remote device needs it, you'll get this error. I don't recommend turning SMB1 back on — it's a security risk. Instead, upgrade the remote device's firmware or replace it.

3. Third-Party Firewall or VPN Interference

Some VPN clients (especially OpenVPN or Cisco AnyConnect) inject virtual adapters that conflict. Temporarily disable the VPN and try again. If the error goes away, the VPN's virtual adapter is to blame. You can try updating the VPN client or excluding file sharing traffic from the VPN tunnel.

Prevention: Keep Your Drivers Current

The number one way to avoid this error again: update your network driver from the manufacturer's website every six months. Don't rely on Windows Update alone — it's slow to push new drivers. Go to Intel, Realtek, or your laptop maker's support page and grab the latest. Set a reminder in your calendar for twice a year. That's 10 minutes of work that saves you hours of frustration.

Also, if you run a mixed environment with old and new hardware, keep a note of each device's supported SMB version. A quick compatibility check before connecting saves you from this error every time.