NERR_CfgCompNotFound (0X00000862): Quick Fix Guide

1. Corrupted Network Configuration Registry Key (Most Common)

Eight times out of ten, this error shows up after a network driver update or uninstall that went sideways. The HKLM\SYSTEM\CurrentControlSet\Services\ key for your network adapter gets left in a half-baked state. You'll see it right after boot or when trying to use wi-fi or ethernet in Windows 10/11.

The real fix is restoring that registry key from a backup. If you don't have a manual backup, you can use a Restore Point that predates the problem. Here's the drill:

1. Hit Win + R, type rstrui.exe, and hit Enter.
2. Pick a restore point from before the error started — ideally 2–3 days prior. If you don't see one, move on to step 3.
3. If System Restore fails or isn't available, open an admin Command Prompt and run: sfc /scannow. Let it finish, then reboot. This fixes corrupted system files, not always the registry directly, but it's worth the 10 minutes.
4. If SFC finds nothing, run: DISM /Online /Cleanup-Image /RestoreHealth. This repairs the component store that SFC uses. Reboot after.

Still broken? Then we'll nuke the network stack and rebuild it.

2. Winsock and Network Stack Corruption

Second most common culprit: the Winsock catalog gets scrambled by a misbehaving app or driver. I've seen VPN clients, antivirus with network filters, and even third-party firewall software do this. Error 0X00000862 pops up because the system can't find the AFD (Ancillary Function Driver) component when it tries to load networking.

Skip the netsh int ip reset alone — that rarely fixes this specific error. Instead, run these three commands in order from an admin command prompt:

netsh winsock reset catalog
netsh int ip reset reset.log
ipconfig /flushdns

Reboot after. If it still fails, the problem is deeper — likely a missing driver entry in the registry or a physically missing .sys file.

3. Missing or Corrupt Network Driver Entry in Registry

This happens when a network driver uninstall tool (looking at you, Intel and Realtek) doesn't fully clean up. The NERR_CfgCompNotFound error maps to the NERR_CfgCompNotFound constant in lmconfig.h — it literally means "the configuration component was not found." In plain English: the registry key for your network adapter's driver is there, but the driver file itself is gone or the values point to a nonexistent path.

Here's the manual fix I've used on at least 50 machines:

1. Identify the broken service. Open Event Viewer (eventvwr.msc) → Windows Logs → System. Look for errors with source Service Control Manager around the time the error appears. Note the service name — usually something like e1dexpress or rtwlan.
2. Check the registry path: HKLM\SYSTEM\CurrentControlSet\Services\[service name]. Look at the ImagePath value. If it points to a non-existent file (e.g., system32\drivers\missing.sys), you've found the problem.
3. Restore the driver. Either reinstall the network driver from the manufacturer's site (not Windows Update — it often grabs a generic one), or if you have a known-good backup of the .sys file, copy it back to C:\Windows\System32\drivers\.
4. Delete and recreate. If reinstall doesn't work, uninstall the network adapter from Device Manager (View → Show hidden devices), check the box to delete the driver, then scan for hardware changes. Let Windows reinstall the driver fresh.

I've also seen this happen when someone manually deleted a third-party firewall's driver without using its uninstaller. The ImagePath still points to the firewall's .sys, but it's gone. In that case, you can disable the service (set Start to 4 in the registry) and reboot. That stops the error, but the network adapter itself will still work if the real driver is intact.

Quick-Reference Summary Table

If none of these work, you're looking at a corrupted OS installation. At that point, a repair install via Windows Media Creation Tool (keep files) or a clean install is your last resort. But honestly, I've only had to go that far twice in 14 years — the steps above cover 99% of cases.