Connecting to Wi-Fi via CMD: A Complete Guide with Commands and Tips

Connecting to a wireless network via Windows command line (CMD) may seem like a daunting task for beginners, but it's actually one of the most reliable ways to manage network connections. This skill is especially useful when the Windows graphical interface isn't working correctly, the adapter drivers are corrupted, or you're setting up a remote computer without desktop access. Unlike the standard connection via the Wi-Fi tray icon, the method using netsh and other commands gives you more control: you can save passwords, manage network profiles, and even diagnose problems without additional utilities.

This article is suitable for both Windows 10/11, as well as for server versions of the system, where the graphical interface is often disabled. We'll cover not only the basic connection commands, but also look at common errors (for example, Error 0x8007048f or absence of networks in the list), as well as alternative methods through PowerShell And WLAN APIIf you're an admin, a systems engineer, or just someone who likes to automate routine tasks, bookmark this guide.

Why Connect to Wi-Fi via CMD: 5 Real Reasons

Many users don't even realize that the command line can replace the graphical interface for Wi-Fi management. Here are some situations where this method becomes indispensable:

• 🖥️ There is no graphical interface: for example, on server versions of Windows (Server 2019/2022) or in mode Safe Mode with Networking.
• 🔧 Driver failures: when the Wi-Fi icon in the tray disappears, but the adapter is physically intact.
• 📡 Connection automation: creating scripts for quickly switching between networks (for example, in the office and at home).
• 🔒 Hidden networks (SSID): connecting to access points that do not broadcast their name.
• 🛠️ Problem diagnosis: commands like ping or ipconfig help to identify the reason for the lack of Internet.

In addition, knowledge of commands will come in handy if you administer several computers remotely via RDP or SSHIn such cases, opening a graphical interface on each device is inconvenient—it's much easier to send a single command and get a result.

Preparation: Checking the adapter and administrator rights

Before entering any commands, make sure your Wi-Fi adapter is enabled and recognized by the system. To do this:

1. Open device Manager (devmgmt.msc through Win + R).
2. Expand the branch Network adapters and find the device with the name Wireless, Wi-Fi or 802.11 (For example, Intel Wi-Fi 6 AX200).
3. If there is an exclamation mark next to the adapter, update the driver or reinstall it.

Also check if the service is running WLAN AutoConfig:

sc query wlansvc

If the status is not RUNNING, run it with the command:

net start wlansvc

⚠️ Attention: All Wi-Fi management commands require permissions administratorRun CMD as administrator (right-click the icon → "Run as administrator").

The adapter status has been checked in Device Manager|

WLAN AutoConfig service started|

CMD opened as administrator|

The SSID and password of the target network are recorded-->

Basic Wi-Fi Control Commands in CMD

All the magic happens through the utility netsh (Network Shell), which is included with Windows. Below are the key commands with explanations.

netsh wlan show interfaces

netsh wlan show networks mode=bssid

netsh wlan connect name="MyWiFi"

netsh wlan add profile filename="C:\wifi.xml"

To see full list of commands For netsh wlan, enter:

netsh wlan /?

Step-by-step instructions: connecting to Wi-Fi via CMD

Now let's get practical. Let's say you want to connect to a network named "HomeWiFi" and password "SecurePass123"Here is the algorithm of actions:

Step 1: View available networks

Enter the command to scan the air:

netsh wlan show networks

If your network isn't visible, make sure the adapter is turned on and within range of the router. For hidden networks (where the SSID isn't broadcast), you can skip this step.

Step 2: Create a network profile

Generate an XML file with network settings (replace SSID And keyMaterial to your data):

netsh wlan set profileparameter name="HomeWiFi" connectiontype=ESSID ssidname="HomeWiFi" networktype=infrastructure authentication=WPA2PSK encryption=AES keyMaterial="SecurePass123"

For open networks (no password) use:

netsh wlan set profileparameter name="FreeWiFi" connectiontype=ESSID ssidname="FreeWiFi" networktype=infrastructure authentication=open

Step 3: Connect to the network

Now connect to the profile you just created:

netsh wlan connect name="HomeWiFi"

If everything went well, you will see a message "Connection to the HomeWiFi network successful."

⚠️ Attention: If you are connecting to corporate network with certificates (for example, WPA2-Enterprise), teams netsh may not work. In this case, use PowerShell or specialized utilities like WiFi Commander.

Troubleshooting: Why Wi-Fi Won't Connect via CMD

Even if you enter the commands correctly, the connection may not work. Let's look at common errors and their solutions:

• 🚫 Error 0x8007048f: service WLAN AutoConfig disabled. Run it with the command net start wlansvc.
• 🔍 Network not found: The adapter doesn't see the access point. Check if Wi-Fi is enabled on the laptop (sometimes it can be turned off by pressing the [key] Fn + F2/F12).
• 🔑 Incorrect passwordWhen creating a profile, make sure your password is correct. To check, delete the profile and create a new one.
• 📡 Weak signal: If the signal level is below 20%, try moving closer to the router or use the command netsh wlan show interfacesto see the current level.

For in-depth diagnostics, use the following commands:

ping 8.8.8.8

(checking connection to Google DNS)

ipconfig /all

(view current IP settings)

If ping It works, but the internet still doesn't work—the problem is with DNS. Set Google's DNS manually:

netsh interface ip set dns "Wi-Fi" static 8.8.8.8

Alternative methods: PowerShell and WLAN API

If netsh seems outdated, can be used PowerShell — a more modern tool with advanced capabilities. For example, to connect to a network, run:

$profile = [Wlan.WlanProfile]::Create("HomeWiFi", "SecurePass123", [Wlan.WlanAuthentication]::WPA2PSK, [Wlan.WlanEncryption]::AES)
[Wlan.WlanClient]::Connect($profile)

This will require a module NativeWiFi, which can be installed through Install-Module -Name NativeWiFi.

Another option is - WLAN API through C++ or PythonThis is relevant for developers who want to integrate Wi-Fi control into their applications. Here's a Python example:

import pywifi
from pywifi import const

wifi = pywifi.PyWiFi()
iface = wifi.interfaces()[0]
iface.connect("HomeWiFi", key="SecurePass123")

These methods are more complex, but provide more flexibility. For example, through PowerShell You can automate connections to different networks depending on your location (home/office).

Saving and exporting Wi-Fi profiles

If you frequently reinstall Windows or set up multiple computers, it's helpful export Wi-Fi profiles into XML files. This will save time when reconfiguring.

To export a profile:

netsh wlan export profile name="HomeWiFi" folder="C:\WiFi_Backup\"

File HomeWiFi.xml will appear in the specified folder. It can be imported on another PC:

netsh wlan add profile filename="C:\WiFi_Backup\HomeWiFi.xml"

Please note: In the XML file the password is stored in in encrypted form, but it can be extracted using utilities like WirelessKeyView (from NirSoft). Never transmit XML profile files over unsecured channels (such as email or instant messaging) – this compromises the security of your network.

⚠️ Attention: Starting from Windows 11 24H2The XML password storage format may change. Before deploying profiles en masse, test them on a test device.

FAQ: Frequently asked questions about connecting to Wi-Fi via CMD

netsh wlan add profile filename="C:\hidden.xml" user=current

<SSIDConfig>
<SSID>
<name>HiddenNetwork</name>
</SSID>
<nonBroadcast>true</nonBroadcast>
</SSIDConfig>

netsh wlan show profiles

netsh wlan delete profile name="OldNetwork"

for /f "tokens=2 delims=:" %a in ('netsh wlan show profiles ^| find "All user profiles"') do netsh wlan delete profile name="%a"