Unidentified Network on Windows 10/11 — Real Fix for NLA

You plug in an Ethernet cable, the icon shows a globe or a red X, and hovering over it says Unidentified Network or No Internet Access. This happens most often after a Windows update (especially 22H2 or 23H2), after waking from sleep, or when you swap between a dock and direct cable. The network itself is fine — your router's working, other devices connect. Your PC just can't figure out what type of network it is.

Root Cause — NLA's Stuck on an Old Profile

Windows uses the Network Location Awareness (NLA) service to identify networks. It stores that info in a cached profile — name, type (Public/Private/Domain), and whether Internet access is available. When that profile gets corrupted or the NLA service crashes, Windows falls back to "Unidentified Network". It literally can't tell if it's your home network or a coffee shop's. The culprit here is almost always a stale profile combined with the NLA service not restarting properly. Don't bother reinstalling drivers or running the Windows Network Troubleshooter — those rarely fix it.

The Fix — Step-by-Step

These steps work on Windows 10 (all versions) and Windows 11. You don't need admin rights for step 1, but you will for steps 2–4.

1. Restart the NLA and ICS services
   Open services.msc (Win+R, type it). Find Network Location Awareness. Right-click, select Restart. Do the same for Internet Connection Sharing (ICS). Yes, ICS — even if you're not sharing your connection. The NLA and ICS services depend on each other. If one's hung, the other is too.
2. Delete the cached network profile
   Open Settings > Network & Internet > Status. Click Properties under your active Ethernet connection. Scroll down, click Forget. This deletes the corrupted profile. If you don't see a named network, open a Command Prompt as admin (cmd right-click > Run as administrator) and run:
   

   netsh wlan delete profile *

   
   That clears all Wi-Fi profiles. For Ethernet, use:
   

   netsh int ip reset
   netsh winsock reset

   
   Then reboot.
3. Re-enable the network adapter
   Go to Control Panel > Network and Sharing Center > Change adapter settings. Right-click your Ethernet adapter, select Disable. Wait 10 seconds, then right-click again and Enable. This forces the adapter to renegotiate the link and pick up a fresh profile.
4. Run the built-in network reset (Windows 10/11)
   Open Settings > Network & Internet > Advanced network settings > Network reset. Click Reset now. This is the nuclear option — it reinstalls your network adapters and resets all settings. You'll need to reconnect to Wi-Fi and re-enter passwords. But it works when nothing else does.

Still failing? Check these

1. The cable and port

Try a different Ethernet cable. I've seen a single bent pin cause this. Also try a different switch port. Unlikely but cheap to test.

2. DHCP is handing out a different subnet

Open Command Prompt and run ipconfig. If your IP starts with 169.254.x.x, you've got an APIPA address — Windows assigned one because DHCP failed. That's a separate issue. Check your router's DHCP server is on, or set a static IP.

3. Third-party firewall or antivirus

Norton, McAfee, and sometimes even Bitdefender can block NLA's network discovery. Temporarily disable your firewall. If the network shows as "Identified" immediately, that's your culprit. Re-enable and add an exception for svchost.exe hosting the NLA service.

4. The NLA service is set to manual

In services.msc, check Network Location Awareness — its Startup Type should be Automatic, not Manual or Disabled. If it's Manual, set it to Automatic, then restart. Same for Network List Service and Network Store Interface Service — both should be Automatic.

One last thing: If you're on a corporate domain and getting Unidentified Network, your PC might not be able to reach the domain controller. Check your DNS. Run nslookup yourdomain.local — if it fails, fix DNS first. The NLA service waits for a domain response before labeling the network.

That's it. I've used this exact sequence on dozens of Dell OptiPlex and Lenovo ThinkCentre machines. Nine times out of ten, step 1 or step 2 fixes it. The tenth time is the network reset. You're welcome.