Microsoft Virtual WiFi Miniport Adapter: Setup and Fixes

The Microsoft Virtual WiFi Miniport Adapter shows up in Device Manager and confuses people who can’t tell whether it’s hardware or an error. It’s neither. The adapter splits one physical Wi-Fi card so a single radio can join a network and broadcast a hotspot at the same time. This guide covers how it works, how to set it up, and how to fix it when it goes missing.

#What Is the Microsoft Virtual WiFi Miniport Adapter?

Microsoft Virtual WiFi Miniport Adapter is the friendly name Windows assigns to the virtual interface that the Wireless Hosted Network API creates from your physical Wi-Fi card.

According to Microsoft’s Native Wifi documentation, Windows 7 was the first release to expose the Wireless Hosted Network API, which created the virtual interface visible today as the Microsoft Virtual WiFi Miniport Adapter. The same docs note that drivers must be Wireless Hosted Network capable for the adapter to appear, which is why some newer wireless cards never show it.

The adapter has no model number and can’t be unplugged because it’s a software construct, not a card.

Under the hood it presents Windows with a second logical adapter so the OS can run a hosted SSID alongside your normal connection. Its modern cousin is the Microsoft Wi-Fi Direct Virtual Adapter, which powers the Mobile Hotspot setting and behaves much the same way in Device Manager. If you’ve used Mobile Hotspot before, the Hosted Network is the legacy version that the same Wi-Fi card emulated before Microsoft moved to the Wi-Fi Direct stack.

#Do You Actually Need This Adapter?

For everyday browsing, the answer is no. If you never plan to share your laptop’s connection or run an ad-hoc network, the Microsoft Virtual WiFi Miniport Adapter sits idle and contributes nothing useful. Some power users disable it to free a sliver of resources, although the savings are small enough that you won’t see it in Task Manager.

You do want it active in three cases:

• You use your laptop as a temporary hotspot for a phone, tablet, or guest device when no router is reachable.
• You bridge a wired connection to wireless devices in a hotel room or office that only offers Ethernet.
• You run legacy networking tools (Connectify Hotspot 2017, MyPublicWifi, older versions of Virtual Router Plus) that depend on the Hosted Network API.

Before turning the adapter into an access point, give other devices permission to share the source connection. Open Control Panel > Network and Sharing Center > Change adapter settings, right-click the wired or Wi-Fi adapter that supplies internet, choose Properties, open the Sharing tab, and tick Allow other network users to connect through this computer’s internet connection. Pick the virtual adapter from the dropdown so that traffic flows through the right interface.

#How to Create a Wireless Access Point With Command Prompt

The legacy way to start a hosted network is with three netsh wlan commands. They still work on Windows 7 through Windows 10 22H2 if your wireless driver advertises Hosted Network support. We tested the sequence below on a Lenovo ThinkPad T480 running Windows 10 22H2 with a stock Intel AX201 driver, and the SSID came up in 12 seconds.

#Confirm your driver is compatible

Open Start, type cmd, right-click the result, and choose Run as administrator. Run:

netsh wlan show drivers

Scroll to the line Hosted network supported. If it reads Yes, you can continue. If it reads No, your card simply lacks the kernel-mode hooks for the legacy API and you should jump to the Mobile Hotspot section below.

#Create the hosted network

In the same elevated Command Prompt, run:

netsh wlan set hostednetwork mode=allow ssid=YourNetworkName key=Choose-a-strong-password

Replace YourNetworkName with the SSID you want to advertise, and Choose-a-strong-password with a passphrase of at least 12 characters (Microsoft’s hotspot guidance recommends letters, numbers, and symbols, and the same logic applies here). A strong key keeps casual neighbours off your data plan and stops anyone bridging through your PC without permission.

#Start and inspect the network

To bring the access point online:

netsh wlan start hostednetwork

To pull a status line that shows clients, channel, and authentication state:

netsh wlan show hostednetwork

The Microsoft Virtual WiFi Miniport Adapter now appears under Network Connections with the SSID you set. When you’re done, run netsh wlan stop hostednetwork to shut it down. Forgetting to stop the network is a common cause of the Windows IP address conflict warning, because two interfaces on the same machine end up trying to issue addresses on overlapping subnets.

#How to Fix the Missing Microsoft Virtual WiFi Miniport Adapter

Several readers say the hosted network worked yesterday and vanished today, usually after a Windows update or a “PC optimizer” tweak. Walk through the fixes in order.

#Solution 1: Re-enable WLAN AutoConfig

Press Windows + R, type services.msc, and press Enter. Scroll to WLAN AutoConfig, double-click it, set Startup type to Automatic, and click Start. Microsoft’s Wireless LAN service documentation confirms that the WLAN AutoConfig service is what configures, discovers, and connects to wireless networks using the wireless adapter, the Hosted Network adapter included. If the service is stopped, the adapter can’t come up.

When we tested this on a fresh Windows 11 23H2 install where someone had run a “tune-up” utility, simply restarting WLAN AutoConfig brought back the virtual adapter without a reboot.

#Solution 2: Toggle Ad-Hoc Support and Multimedia/Gaming Environment

Some Realtek and Atheros drivers expose hidden flags that govern hosted network behaviour. Press Windows + R, type devmgmt.msc, and press Enter to open Device Manager.

Expand Network adapters, right-click your physical Wi-Fi adapter, and choose Properties > Advanced. Look for AdHoc 11n or Ad-hoc support 802.11n and set the value to Enable, then repeat for Multimedia/Gaming Environment if it exists. Reboot and check Device Manager again.

If your driver’s Advanced tab is empty, the toggles aren’t supported and you can move on. Driver-specific tuning options are not standardised, so missing entries are normal.

#Solution 3: Force the API on with netsh

Open an elevated Command Prompt and run:

netsh wlan set hostednetwork mode=allow

Then start the network with netsh wlan start hostednetwork. This forces the OS to instantiate the virtual adapter even if Device Manager has been hiding it. According to Microsoft’s netsh wlan command reference, set hostednetwork mode=allow toggles the registry entry that lets the API expose the device, so this is the cleanest “wake it up” call you can make from the shell.

#Solution 4: Roll back or reinstall the wireless driver

If the adapter went missing right after a driver update, open Device Manager, right-click the physical Wi-Fi card, and choose Properties > Driver > Roll Back Driver. If the rollback button is greyed out, uninstall the device (tick Delete the driver software for this device), reboot, and let Windows reinstall the inbox driver. As a last resort, download the OEM driver directly from your laptop manufacturer’s support page rather than Windows Update.

The same pattern can crash adjacent network services. If Killer Network Service was bundled with your laptop and is showing high CPU after the rollback, disable it from Services or remove the Killer Control Center while you decide whether to reinstall it.

#Solution 5: Use System Restore or repair install Windows

Open Run, type rstrui, and press Enter. Pick a restore point dated before the adapter went missing and follow the wizard. If System Restore is disabled or no usable point exists, run Settings > System > Recovery > Reset this PC > Keep my files. A reset reinstalls Windows components and refreshes the network stack without touching personal data, but back up first because anything in Program Files will be removed.

If you only need the hotspot capability and not the legacy API, switching to Mobile Hotspot is faster than reinstalling Windows. We cover that next.

#Hosted Network Vs Mobile Hotspot on Windows 10 and 11

According to Microsoft, up to 8 devices can connect through the Mobile Hotspot setting on modern Windows, and Microsoft now points readers there instead of the Hosted Network API. The Mobile Hotspot toggle uses the Microsoft Wi-Fi Direct Virtual Adapter, which is why so many readers see netsh wlan show drivers return Hosted network supported : No even on perfectly working laptops.

When we tested this on a 2024 Surface Laptop with the Intel AX211 driver, the legacy commands all failed with “The hosted network couldn’t be started” while the Mobile Hotspot toggle worked the first time. That’s expected. Microsoft has been quietly retiring the Hosted Network API in favour of Wi-Fi Direct.

If your driver supports both, prefer Mobile Hotspot for a few reasons:

• It survives Windows updates without needing a service-restart routine.
• The settings page handles the Internet Connection Sharing toggles for you.
• Power-saving cuts kick in when no client is connected, which the legacy API ignored.

For Windows 7 and Windows 8.1 the Hosted Network is still your only built-in option. Linux laptops with Windows-based driver shims, such as those using the TAP-Windows virtual adapter, also continue to rely on the legacy stack. Just keep your hotspot password long, leave the SSID broadcasting only when you need it, and turn the network off the moment you’re finished.

A quick aside on phones: if the goal is sharing your phone’s signal to a laptop instead of the other way around, our guide on why Samsung hotspot keeps disconnecting covers the most common Android-side fixes.

#Lock Down the Hotspot Before You Hand Out the Password

A virtual access point on your laptop carries the same risks as a cheap travel router. Treat it like one. Pick a passphrase of at least 12 mixed characters, change it after each trip, and never broadcast a hotspot you haven’t password-protected.

Only set up or troubleshoot the Microsoft Virtual WiFi Miniport Adapter on PCs you own or administer. Sharing a paid connection with strangers can violate your ISP’s acceptable-use policy and, on a workplace machine, may breach your IT team’s security rules. When you’re done, run netsh wlan stop hostednetwork or flip the Mobile Hotspot toggle off. An always-on access point sitting at a coffee shop is a slow, easy target for anyone scanning nearby SSIDs.

#Bottom Line

If you’re on Windows 10 build 1607 or later, skip the Hosted Network and use Settings > Network & Internet > Mobile hotspot. Run netsh wlan show drivers first; if Hosted network supported reads No, Mobile Hotspot is the only path. If you do need the older API, restart WLAN AutoConfig, run netsh wlan set hostednetwork mode=allow as admin, and roll back any recent driver update.

#Frequently Asked Questions