How to Enable WiFi in Windows Server: Step-by-Step

Windows Server doesn’t enable WiFi by default, even if the wireless adapter is installed. This guide walks you through installing the driver, enabling the WLAN service, and connecting to a network using both the GUI and command line. You’ll need administrator access and a wireless adapter that is physically installed.

What You’ll Need

A Windows Server machine (2016, 2019, or 2022) with a wireless adapter installed.
Administrator credentials.
WiFi network name (SSID) and password.
Access to the internet or a driver CD to download the wireless driver if not already present.

Step-by-Step

Check if a wireless adapter is present. Open Device Manager (right-click Start > Device Manager). Expand “Network adapters.” If you see an adapter with “Wireless,” “WiFi,” or “802.11” in its name, it’s detected. If not, install the driver from the manufacturer’s website or CD, then reboot.
Enable the WLAN AutoConfig service. Press Win+R, type services.msc, and press Enter. Scroll to “WLAN AutoConfig.” If its status is not “Running,” right-click it and select “Start.” Then right-click again, select “Properties,” set Startup type to “Automatic,” and click OK.
Verify the wireless adapter is enabled. In Device Manager, right-click the wireless adapter and select “Enable” if it’s disabled. If it’s already enabled, skip this step.
Add the WiFi feature (if missing). Some Server editions don’t include the Wireless LAN Service feature. Open Server Manager, click “Add roles and features,” go through the wizard until “Features,” check “Wireless LAN Service,” and click Install. Reboot if prompted.
Connect via the taskbar (if available). Click the network icon in the notification area. If you see a list of WiFi networks, select yours, enter the password, and connect. If you don’t see the icon, proceed to the command-line method.
Connect via command line (if no GUI icon). Open Command Prompt as administrator. Run netsh wlan show interfaces to confirm the adapter is up. Then create a profile file. Type netsh wlan show profiles to see existing profiles. To add a new one, create a text file named wifi.xml with the following content, replacing YourSSID and YourPassword:

<?xml version="1.0"?>
<WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1">
  <name>YourSSID</name>
  <SSIDConfig>
    <SSID>
      <name>YourSSID</name>
    </SSID>
  </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>

Then run: netsh wlan add profile filename="wifi.xml" and netsh wlan connect name="YourSSID".

Confirm the connection. Run netsh wlan show interfaces again. The state should show “connected.” Test with ping google.com.

Common Mistakes

Skipping the WLAN AutoConfig service. Without it, the adapter won’t scan for networks, even if the driver is installed.
Forgetting to install the Wireless LAN Service feature. On some Server editions, this feature is not installed by default, and the network icon won’t appear.
Using the wrong XML security settings. If your router uses WPA3 or WPA2-Enterprise, the above profile won’t work. Check your router’s security type.
Not running commands as administrator. netsh commands will fail with “Access denied” if you’re not elevated.

Tips

Use a wired connection for initial setup if possible; it’s more reliable for downloading drivers.
If you have multiple wireless profiles, use netsh wlan set profileorder name="YourSSID" interface="WiFi" priority=1 to set priority.
For enterprise networks (PEAP, MSCHAPv2), use the GUI to connect once, then export the profile with netsh wlan export profile name="YourSSID" folder=C:\ for reuse.
Keep the wireless driver updated from the manufacturer’s site, not Windows Update, for best stability.

Troubleshooting

No WiFi adapter in Device Manager: The adapter might be disabled in BIOS. Reboot, enter BIOS (usually F2 or Del), and look for “Wireless LAN” or “WLAN” option—set it to Enabled. Also check if the adapter is physically seated in a PCIe slot or USB port.

WiFi networks not showing: First, ensure the WLAN AutoConfig service is running. Then run netsh wlan show drivers to see if the driver supports WLAN. If it says “Hosted network supported: No,” that’s fine, but if “Wireless LAN Service” is missing, install the feature as described.

Connection fails with “Cannot connect to this network”: Check the password and security type. Run netsh wlan show profiles to see if the profile is correct. Delete and re-add the profile if needed. Also, ensure the router isn’t set to a channel that the adapter doesn’t support (e.g., 5GHz on an older adapter).

WiFi works but internet doesn’t: The adapter may have obtained an IP but no DNS. Run ipconfig /all and check the DNS servers. If they are empty, set them manually with netsh interface ip set dns "WiFi" static 8.8.8.8 (or your preferred DNS).

After reboot, WiFi doesn’t auto-connect: The profile’s connection mode might be set to manual. Edit the XML file and set <connectionMode>auto</connectionMode>, then re-add the profile. Also, ensure the WLAN AutoConfig service startup type is Automatic.

Frequently Asked Questions

Can I use WiFi on Windows Server Core?

Yes, but you must use command-line tools like netsh or PowerShell. The steps are the same, but there’s no GUI for connecting.

Why is the WiFi icon missing from the taskbar?

This usually means the Wireless LAN Service feature isn’t installed, or the WLAN AutoConfig service isn’t running. Install the feature and start the service.

Is it better to use WiFi or Ethernet on a server?

Ethernet is generally more stable and faster. Use WiFi only when wired is impossible, and expect higher latency and potential interference.

Can I connect to a hidden SSID?

Yes. In the XML profile, add <hidden>true</hidden> inside the <SSID> element. Then add the profile and connect.

How do I remove a WiFi profile?

Run netsh wlan delete profile name="YourSSID" in an elevated command prompt.

Does Windows Server support WiFi Direct or hotspots?

Windows Server can act as a hotspot using the hosted network feature, but it’s deprecated. Use the Mobile Hotspot feature in Settings if available, or use a third-party solution.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →