Stuck on Identifying Network in Windows 11

Windows 11 stuck on “Identifying network” — the status bar shows this indefinitely while the internet doesn’t work, or the connection flips between “Identifying” and “No internet” — is a networking issue that almost always resolves with one of a handful of targeted fixes. If you want the full context, see our Complete Guide to Fixing Windows, Browser, and Software Errors.

The “Identifying” state means Windows successfully connected to the network at the physical layer (your Wi-Fi or Ethernet is up) but can’t complete the higher-level network identification process — usually because DHCP failed, DNS is unreachable, or the network profile needs to be reset.

Quick fix: release and renew the IP address

When “Identifying” is stuck: the most likely cause is a failed DHCP lease. Administrator Command Prompt:

ipconfig /release
ipconfig /flushdns
ipconfig /renew

After ipconfig /renew: Windows requests a fresh IP address from the router. If DHCP succeeds, “Identifying” clears and the connection status updates to the correct state within 30-60 seconds. If /renew hangs or fails: the DHCP server (usually the router) isn’t responding — try restarting the router.

Network profile reset

Windows maintains a list of known networks with their profiles (Public, Private, Domain). If the current network’s profile becomes corrupted or incorrect: “Identifying” can loop indefinitely while Windows tries to re-evaluate the network type. Administrator PowerShell:

Get-NetConnectionProfile | Set-NetConnectionProfile -NetworkCategory Private

This forces the current connection to “Private” network profile, which may break the “Identifying” loop. After running: check whether the status resolves. Also try: Settings → Network and internet → your connection → Properties → change between Public and Private profile type.

NCSI — the network identification test

Windows runs a Network Connectivity Status Indicator (NCSI) probe to identify the network. It sends a small HTTP request to a Microsoft server and checks a DNS record. If this probe fails (server unreachable, DNS not working, or the probe is blocked by firewall): Windows stays “Identifying” indefinitely even when the network is actually working.

Test: open a browser and try loading a website while “Identifying” is shown. If websites load: the network works but NCSI’s probe is failing — a false positive. The fix: Administrator Command Prompt → reg add "HKLMSYSTEMCurrentControlSetServicesNlaSvcParametersInternet" /v EnableActiveProbing /t REG_DWORD /d 1 /f → restart. This re-enables NCSI’s active probing if it was disabled.

Full network stack reset

When targeted fixes don’t clear “Identifying”: reset the entire network stack. Administrator Command Prompt:

netsh winsock reset
netsh int ip reset
netsh int ipv6 reset
ipconfig /flushdns
ipconfig /registerdns

Restart after running all commands. This rebuilds the TCP/IP stack and DNS cache from scratch. Most networking issues including stuck “Identifying” clear after this reset.

DNS configuration

NCSI’s probe includes a DNS lookup. If DNS is broken or pointing at an unreachable server: the probe fails and “Identifying” persists. Settings → Network and internet → your connection → DNS server assignment → Manual → set DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) rather than automatic. After changing: ipconfig /flushdns → test whether “Identifying” clears.

Corporate network and domain considerations

On domain-joined machines: “Identifying” sometimes persists because the machine is trying to contact a domain controller to classify the network as “Domain” profile but the DC is unreachable. This is common when working from home without VPN — the machine knows it joined a domain but can’t reach it from the home network.

The fix: connect to the corporate VPN first → once domain classification succeeds → VPN-connected work with full domain network profile. Alternatively: gpedit.msc → Computer Configuration → Windows Settings → Security Settings → Network List Manager Policies → configure the specific network as “Private” permanently to bypass the DC lookup.

Our guide on internet connectivity problems covers the broader network fix approach when “Identifying” is part of a larger connectivity failure. For DNS issues that block the NCSI probe, our DNS troubleshooting guide covers the DNS server configuration and testing. Microsoft’s NCSI documentation covers the registry entries that configure NCSI’s probe behaviour and the specific URLs it uses to test connectivity.

Identifying on only one network

If “Identifying” appears on a specific network (home Wi-Fi) but not others (phone hotspot, office network): the problem is specific to that network’s configuration interacting with your Windows machine — not a system-wide issue. Common causes:

• Router DHCP is full (no IP addresses available to assign) — check the router’s DHCP client list and the DHCP pool size
• IP conflict — another device has the same IP your machine last used, preventing successful DHCP
• The router’s MAC address filter is blocking your machine — check the router’s access control list
• The router needs a restart — cached state is preventing correct IP assignment

Testing on a different network (phone hotspot) immediately confirms whether the issue is machine-wide or network-specific. This single test takes 30 seconds and prevents the wrong troubleshooting path.

IPv6 and Identifying network

Windows’ “Identifying” state can be triggered by IPv6 identification failing even when IPv4 works correctly. NCSI checks both IPv4 and IPv6 connectivity. If the router or network doesn’t correctly handle IPv6 (common on older or budget routers): NCSI’s IPv6 probe fails and Windows may display “Identifying” even though IPv4 internet access is working.

Test: disable IPv6 on the adapter. Device Manager → Network Adapters → right-click the adapter → Properties → uncheck “Internet Protocol Version 6 (TCP/IPv6)” → OK. After unchecking: does “Identifying” clear? If yes: the router’s IPv6 configuration is the problem. Either configure IPv6 correctly on the router, or leave IPv6 disabled on this adapter if IPv4-only is sufficient for your needs.

VPN adding a “Identifying” network adapter

Many VPN clients add a virtual network adapter when connected. When the VPN is active: Windows sees two network connections — the real one (Ethernet/Wi-Fi) and the VPN tunnel. If the VPN adapter shows “Identifying” in the network status area: this is the VPN adapter itself failing to identify — not the underlying real connection. The real connection may work fine.

Check: Settings → Network and internet → Advanced network settings → look at each adapter’s status. If the physical adapter (Wi-Fi or Ethernet) shows “Connected” and only the VPN adapter shows “Identifying”: the VPN has a configuration issue, not the underlying network.

Windows event log for network identification failures

Event Viewer → Windows Logs → System → filter for Source “NCSI” or “NLA” (Network Location Awareness). Events from these sources show exactly what step of network identification failed and what the system tried. Common events:

• NLA Event ID 4004: Indicates the network location aware service failed to determine the network type — confirms NLA/NCSI is the issue
• NCSI: “Network connectivity is now confirmed as connected to X” or “NCSI: Probing failed” — shows whether the connectivity probe succeeded

The event log timestamps show when the “Identifying” started and what exactly was tried before it got stuck.

Static IP as a DHCP bypass

If DHCP consistently fails on a specific network (particularly after power outages or router resets): setting a static IP on the Windows machine eliminates the DHCP dependency entirely. Settings → Network → your connection → IP settings → Manual → enter:

• IP: 192.168.1.50 (or any IP in your router’s subnet outside the DHCP range)
• Subnet: 255.255.255.0
• Gateway: 192.168.1.1 (your router’s IP)
• DNS: 1.1.1.1 / 8.8.8.8

With a static IP: Windows doesn’t need to request an IP from DHCP, so the “Identifying” loop from DHCP failure doesn’t occur. The trade-off: if the router changes (replaced or reconfigured with a different subnet), the static IP needs updating manually.

Network troubleshooter

Settings → System → Troubleshoot → Other troubleshooters → Internet Connections → Run. The built-in troubleshooter checks DHCP, DNS, and network adapter configuration, and sometimes automatically applies fixes for “Identifying” states. It’s worth running before manual investigation — it’s faster and occasionally catches specific issues (like disabled DHCP client service) that aren’t obvious from a surface inspection.

The “Network 2” or “Unidentified Network” variant

A related issue: the network shows as “Network 2” or “Unidentified Network” rather than by name, and shows Public profile regardless of settings. This is Windows assigning a new identity to what it thinks is a new network — this happens when the router’s MAC address changed (replaced router, factory reset) or when a VPN changes the network signature. Fix: Settings → Network → Properties → change to Private profile. The “Unidentified Network” label persists but the profile change resolves permission and firewall issues caused by the Public profile assignment.

“Identifying network” is one of Windows’ more confusing states because the description doesn’t tell you what’s actually failing. The ipconfig /release → /renew sequence resolves the most common cause (DHCP failure) in under 60 seconds. The NCSI probe test (opening a browser while “Identifying” is shown) takes 10 seconds to confirm whether internet is actually working despite the status indicator. These two quick checks direct all subsequent investigation without guesswork.

One pattern worth knowing: “Identifying” that appears briefly on every connection and then resolves is normal — Windows takes a few seconds to identify any network. Only “Identifying” that persists for minutes or indefinitely is a problem worth investigating. If you’re seeing the “Identifying” state for 5-15 seconds before connectivity works: that’s NCSI’s normal probe timing, not a failure that needs troubleshooting.

Hyper-V and virtual network adapters

Installing Hyper-V (Windows 11 Pro’s virtualisation platform) creates virtual network adapters that appear alongside real network adapters. These virtual adapters sometimes show “Identifying” indefinitely because they’re internal virtual switches rather than external network connections. If “Identifying” appears in the network status and you have Hyper-V installed: check whether the adapter showing “Identifying” is a Hyper-V virtual adapter (named “vEthernet” in Settings → Advanced network settings) rather than a real physical adapter. Virtual switch adapters showing “Identifying” is expected and not a problem if your real adapter is connected and working.

After a Windows 11 Update

Persistent “Identifying” that started after a specific Windows Update: the update may have changed network adapter settings (particularly driver configurations or NCSI settings). Check whether the issue appeared immediately after a specific cumulative update. Network adapter driver rollback (Device Manager → Network adapters → right-click → Properties → Driver → Roll Back Driver) sometimes resolves post-update network identification issues when the updated driver has a regression in the network identification code path.

For advanced users diagnosing persistent “Identifying” that doesn’t respond to standard fixes: the NLA (Network Location Awareness) service is directly responsible for network identification. Restarting it clears accumulated state: Administrator Command Prompt → net stop nlasvc && net start nlasvc. This is more targeted than restarting Windows and sometimes resolves stuck identification without requiring any other changes.

Network adapter power management causing repeated Identifying

Adapters configured to suspend during low activity sometimes re-enter the “Identifying” state each time they wake from their low-power suspension, creating repeated brief “Identifying” periods throughout the session. Device Manager → Network Adapters → right-click → Properties → Power Management → uncheck “Allow the computer to turn off this device to save power.” After disabling power management: the adapter stays active and doesn’t repeatedly re-identify the network, which eliminates the repeated brief “Identifying” appearances during normal use.

Putting it all together: “Identifying network” is a status message from two Windows services working together — NLA classifies the network type, and NCSI validates internet connectivity. When either service can’t complete its check, the status stays stuck. The fastest diagnosis is: (1) try a browser to see if internet actually works despite the status, and (2) run ipconfig /renew to see if DHCP succeeds. These two actions in 2 minutes tell you whether the problem is NCSI false-positive, DHCP failure, or something deeper — directing every subsequent step rather than trying fixes randomly.

For networks where “Identifying” occurs consistently but internet works: configuring a static IP (eliminating DHCP) and setting DNS to public servers (eliminating DNS resolution failures for NCSI) permanently resolves the false-positive identification stuck state without requiring the network stack to successfully complete its full probe on every connection. This configuration is stable and appropriate for home networks where the router’s IP and subnet don’t change. Related: Windows 11 Network Adapter Keeps Disabling.