Fix Windows 11 Cannot Connect to Hidden Wi-Fi Networks
🔍 WiseChecker

Fix Windows 11 Cannot Connect to Hidden Wi-Fi Networks

Quick fix: Open Settings → Network & internet → Wi-Fi → Manage known networks. Click Add network. Enter exact SSID, security type, password. Tick Connect automatically and Connect even if this network is not broadcasting. Click Save. Network joins. If still fails: check Wi-Fi adapter advanced settings for “Hidden SSID” or similar option.

Hidden Wi-Fi networks don’t broadcast their SSID. To connect: manually configure with correct SSID + security type + password. Some Wi-Fi adapters and Windows builds have issues connecting reliably.

Symptom: Windows 11 won’t connect to a hidden Wi-Fi network.
Affects: Windows 11 (and Windows 10).
Fix time: ~10 minutes.

ADVERTISEMENT

What causes this

Hidden networks aren’t a real security measure (anyone can detect them with a sniffer), but they require explicit configuration. Issues arise when:

  • SSID typed wrong (case-sensitive, spaces matter).
  • Wrong security type (WPA2 vs WPA3, AES vs TKIP).
  • Wrong password.
  • Adapter driver doesn’t support connecting to non-broadcasting networks.
  • 5GHz hidden network on a 2.4GHz-only adapter.

Method 1: Add hidden network manually

The standard route.

  1. Open Settings → Network & internet → Wi-Fi → Manage known networks.
  2. Click Add network.
  3. Fill in:
    • Network name (SSID): exact, case-sensitive.
    • Security type: WPA2-Personal AES (most common). Use exact match.
    • Encryption type (if shown): AES or TKIP.
    • Password: exact.
  4. Tick Connect automatically.
  5. Tick Connect even if this network is not broadcasting. (Crucial for hidden networks.)
  6. Click Save. Network joins.
  7. If first attempt fails: Manage known networks → click the new network → Forget. Re-add.
  8. Common error: missed the “Connect even if not broadcasting” tick — Windows won’t actively probe; relies on broadcast.

This is the standard setup.

ADVERTISEMENT

Method 2: Add network via netsh (precise control)

For when GUI fails.

  1. Open Command Prompt (Admin).
  2. Create a profile XML file. Save as hidden-profile.xml:
    <?xml version="1.0"?>
    <WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1">
        <name>MyHiddenNetwork</name>
        <SSIDConfig>
            <SSID>
                <name>MyHiddenNetwork</name>
            </SSID>
            <nonBroadcast>true</nonBroadcast>
        </SSIDConfig>
        <connectionType>ESS</connectionType>
        <connectionMode>auto</connectionMode>
        <MSM>
            <security>
                <authEncryption>
                    <authentication>WPA2PSK</authentication>
                    <encryption>AES</encryption>
                    <useOneX>false</useOneX>
                </authEncryption>
                <sharedKey>
                    <keyType>passPhrase</keyType>
                    <protected>false</protected>
                    <keyMaterial>YourPassword</keyMaterial>
                </sharedKey>
            </security>
        </MSM>
    </WLANProfile>
  3. Replace MyHiddenNetwork with actual SSID and YourPassword with actual password.
  4. Import:
    netsh wlan add profile filename="hidden-profile.xml" user=current
  5. Connect:
    netsh wlan connect name=MyHiddenNetwork
  6. For WPA3: change authentication to WPA3SAE in XML.
  7. For Enterprise (EAP): different XML structure.

This is the precise route.

Method 3: Update Wi-Fi adapter driver and check Advanced settings

For when configuration looks right but still fails.

  1. Open Device Manager. Expand Network adapters.
  2. Right-click Wi-Fi adapter (e.g., Intel Wi-Fi 6 AX201) → Update driver. Pick Search automatically.
  3. If no newer driver: download from Intel/Realtek/Qualcomm site directly. Manufacturer drivers often better than Microsoft generic.
  4. Reboot. Test connection.
  5. For adapter Advanced tab settings:
    • Right-click adapter → Properties → Advanced tab.
    • Find Roaming Aggressiveness: set to Medium-High.
    • Find Wireless Mode: set to allow 802.11ax/ac/n/g/b/a.
    • Find SSID Hide / Non-Broadcast: ensure not disabled.
    • Find U-APSD support: try disabling if connection drops.
  6. For 5GHz networks: confirm adapter supports 5GHz. Some older adapters are 2.4GHz only.
  7. For older router (WEP, WPA-PSK): older security types may not be supported by recent Windows versions. Update router firmware or change to WPA2 / WPA3.
  8. For corporate Wi-Fi (802.1X): need a different config. Provide certificate or username/password as required.

This is the driver and advanced approach.

How to verify the fix worked

  • Wi-Fi icon in system tray shows connected.
  • Network listed in “Manage known networks” with auto-connect enabled.
  • Internet accessible.
  • netsh wlan show profiles shows the profile.
  • netsh wlan show interfaces shows current connection details.

If none of these work

If still won’t connect: Router has MAC filtering: add your PC’s MAC address to router’s whitelist. Router uses 802.11ax-only mode: older adapters can’t connect. Enable 802.11ac compatibility on router. Hidden SSID with WPA3: some adapters don’t support both WPA3 + hidden. Use WPA2 or unhide. For routers with specific channel restrictions: some channels (DFS) need 1-minute scan before connecting. Wait. For Wi-Fi adapter not turning on: airplane mode? Function key disable? Re-enable in Settings → Network & internet → Wi-Fi. For chronic disconnects after connecting: power-save in adapter Properties → Power Management. Untick Allow Windows to turn off. Last resort: unhide the SSID: hidden SSID isn’t real security. Unhide via router admin and connect normally. Re-hide later if you must.

Bottom line: Settings → Wi-Fi → Manage known networks → Add network. Enter exact SSID, security type, password. Tick “Connect even if this network is not broadcasting.” Use netsh profile XML for precise control or driver/Advanced tab for adapter-level fixes.

ADVERTISEMENT