Fix 0X80340019: NDIS Unsupported Media Error

Why You're Seeing This Error

This one's a real pain. You plug in an Ethernet cable and get nothing — or Windows throws 0X80340019 in Event Viewer right after a driver update. The culprit here is almost always a mismatch between your network adapter and the physical media. I've seen it most often after upgrading to Windows 11 22H2 with older Intel I219-V NICs, or when someone plugs a Cat7 cable into a 1GbE port.

The Fix That Works 90% of the Time

Skip the Windows Network Troubleshooter. It's useless here. Do this:

Open Device Manager. Find your network adapter under Network Adapters.
Right-click it, go to Properties → Driver tab.
Click Roll Back Driver. If it's greyed out, go to step 4.
If rollback isn't available, go to the adapter's manufacturer site and download the previous major version of the driver. For Intel, that's often the 25.x series instead of 26.x or later. For Realtek, grab the Win10 driver even if you're on Win11.
Install it manually via Device Manager → Update Driver → Browse my computer → Let me pick.

Apply, reboot. 9 times out of 10, the error disappears on next boot. If not, move to the media fix below.

Forcing the Link Speed (Plan B)

If the driver rollback didn't fix it, the problem is likely auto-negotiation failing on the physical layer. Here's how to brute-force it:

Open Network Connections (ncpa.cpl).
Right-click your Ethernet adapter → Properties → Configure.
Go to the Advanced tab.
Find Speed & Duplex and set it to a fixed value. Start with 1.0 Gbps Full Duplex. If that doesn't stick, try 100 Mbps Full Duplex.
Click OK and reconnect the cable.

This forces the NIC to skip negotiation and use a known-good setting. I've had to do this with some cheap switches that don't handle 2.5GBase-T or 5GBase-T properly. Works on Dell Optiplex 7080s with Realtek 2.5GbE NICs all the time.

Why This Happens

The NDIS driver layer in Windows 10/11 has a few bugs with newer media types. When the adapter detects a cable that supports higher speeds (like Cat6A or Cat7), it tries to negotiate a speed the hardware can't actually handle — or the switch can't offer. The driver panics and throws 0X80340019. Rolling back the driver removes the code that's doing the bad negotiation. Forcing speed overrides the auto-negotiation entirely.

Another less common cause: NetAdapterCx drivers (the newer Windows Driver Framework) are more sensitive to cable length and shielding. I've seen this with the Microsoft-provided driver for Intel X550-T2 cards. Switching to the legacy NDIS 6.x driver from the OEM fixed it every time.

Less Common Variations

Virtual Machines

If you see this in Hyper-V or VMware, it's usually a virtual switch misconfiguration. Set the virtual NIC to use the Intel PRO/1000 MT adapter type instead of VMXNET3 or the default. It's less performant but stable.

USB 3.0 to Ethernet Adapters

Realtek RTL8153 and ASIX AX88179 adapters are notorious for this error. The fix is simpler: unplug the adapter, go to Device Manager, show hidden devices, and delete all entries under Network Adapters. Reboot and plug it back in. Windows will reinstall the driver fresh.

Windows PE or Preboot Environments

In a bootable USB environment, this error pops up when the NIC driver isn't loaded. Your fix is to inject the correct driver into the WinPE image using dism /Add-Driver. Don't bother with the built-in generic driver — it doesn't support newer Realtek or Intel chipsets.

Prevention Going Forward

Three things to stop this from coming back:

Lock your driver version. Use Group Policy or the Windows Update for Business to prevent driver updates. The ExcludeWUDriversInQualityUpdate registry key works in Windows 10 Pro and higher:
```
reg add "HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate" /v ExcludeWUDriversInQualityUpdate /t REG_DWORD /d 1 /f
```
Know your cable. Don't use Cat7 or Cat8 cables on consumer 1GbE gear. They're shielded differently and cause negotiation failures. Stick to Cat5e or Cat6.
Check your switch. Broadcom and Marvell switch chips have a bad rep for NDIS errors with certain Intel NICs. If you have a managed switch, try turning off Energy Efficient Ethernet (EEE) or Green Ethernet in the switch config.

That's it. This error is a driver or negotiation problem, not a hardware failure. Fix the driver first, then the speed, and you'll be back online.