Quick answer
Open Command Prompt as admin and run netsh wlan delete profile name="YourProfileName" or netsh lan delete profile name="YourProfileName" depending on your connection type, then reconnect.
What's going on here?
This error means Windows saved a network profile—could be WiFi or Ethernet—that's gone bad. The profile stores settings like SSID, security keys, DHCP config, and proxy info. When that file gets corrupted, Windows can't load the connection properly. I've seen this happen after a failed Windows update, a sudden power loss while connected, or third-party VPN software messing with the stack. Had a client last month whose entire print queue died because of a corrupted wired profile—turns out a QuickBooks update hosed the network config. The fix is simple: nuke the broken profile and let Windows rebuild it fresh when you reconnect.
Fix steps
Step 1: Identify the broken profile
Open Command Prompt as administrator. Run:
netsh wlan show profilesLook for the network name that's failing. If it's a wired Ethernet connection, run:
netsh lan show profilesNote the exact profile name. If you don't see it there, check the registry:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\ProfilesEach GUID under that key is a profile. Click through them and look for the ProfileName value matching your network.
Step 2: Delete the profile
For WiFi, run:
netsh wlan delete profile name="YourProfileName"For Ethernet (wired):
netsh lan delete profile name="YourProfileName"If netsh doesn't work or the profile is stubborn, delete the registry key directly. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\ProfilesRight-click the GUID folder for your broken profile and choose Delete. You can also check HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList\Signatures\Unmanaged and delete any matching entries—sometimes the profile is stored twice.
Step 3: Reconnect
Click the network icon, find your network, and reconnect. Enter the password if asked. Windows creates a fresh profile. Test by browsing a site or pinging 8.8.8.8. If the error comes back, the problem might be your network adapter driver or a deeper OS issue.
Alternative fixes if the main one fails
- Reset network stack: Run these commands as admin:
netsh int ip reset,netsh winsock reset,ipconfig /release,ipconfig /renew. Reboot. - Uninstall and reinstall the network adapter: Open Device Manager, find your network adapter under Network adapters, right-click and Uninstall device. Reboot. Windows reinstalls the driver.
- Run the Windows Network Troubleshooter: Go to Settings > Network & Internet > Status > Network troubleshooter. It sometimes catches lingering profile corruption. It's a long shot but doesn't hurt.
Prevention tip
Don't let third-party network management tools (looking at you, Intel PROSet, some VPNs, and older Cisco AnyConnect) save profiles over the Windows native settings. They often write bad data. Stick to Windows' own network profile storage. Also, before a major Windows update, temporarily delete any profiles you don't need—less clutter, less chance of corruption. And if you use a wired connection, avoid yanking the cable during a power outage; that can corrupt the Ethernet profile. Tell your users to shut down properly.