Mobile hotspot not working on Windows 11 usually means one of two things: the hotspot isn’t starting at all, or it starts but connected devices can’t reach the internet. The fix is different for each, so confirm which situation you’re in before trying anything. For the bigger picture, our Complete Guide to Fixing Windows, Browser, and Software Errors pulls everything together.
Hotspot won’t start → Settings → Network and internet → Mobile hotspot → the toggle either does nothing or shows an error. Check whether airplane mode is on. Check whether Wi-Fi is on — mobile hotspot requires an active Wi-Fi connection to share from (unless you’re sharing from Ethernet or cellular). If those are fine: Fix 1 below.
Hotspot starts but devices can’t connect or get internet → Devices can connect to the hotspot SSID but show “No internet” or can’t load anything. Fix 4 below.
Fix 1: The most effective reset — network adapter restart
Settings → Network and internet → Advanced network settings → More network adapter options → find “Microsoft Wi-Fi Direct Virtual Adapter” → right-click → Disable → wait 10 seconds → right-click → Enable. This restarts the virtual adapter that hosts the mobile hotspot without affecting other network connections. After re-enabling, try the hotspot toggle again.
Also check: Settings → Mobile hotspot → the “Share my internet connection from” dropdown. If it shows “Ethernet” but no ethernet cable is plugged in, or “Wi-Fi” but Wi-Fi is disconnected: change to the connection you’re actually using. The hotspot can only share an active connection.
Fix 2: The WLAN AutoConfig service
WLAN AutoConfig manages both Wi-Fi connections and virtual hotspot adapters. When it’s stopped or in a bad state: the hotspot toggle appears but does nothing. Win + R → services.msc → “WLAN AutoConfig” → confirm Running and Startup type is Automatic. Right-click → Restart even if it appears running — a service that’s stuck responds to a restart.
Fix 3: Driver issue with the virtual adapter
Device Manager → Network Adapters → look for “Microsoft Wi-Fi Direct Virtual Adapter” — if it has a yellow warning triangle or is missing: the hotspot virtual adapter has a driver problem. If missing: Action → Scan for hardware changes. If warning triangle: right-click → Update driver.
If the adapter isn’t visible at all with “Show hidden devices” enabled: the hotspot infrastructure may need a fresh install. Administrator Command Prompt:
netsh wlan set hostednetwork mode=disallow
netsh wlan set hostednetwork mode=allowThese commands disable and re-enable the hosted network mode that mobile hotspot relies on, forcing Windows to re-register the virtual adapter.
Fix 4: Internet Connection Sharing
When the hotspot starts but connected devices can’t reach the internet: Internet Connection Sharing (ICS) may not be enabled correctly on the source connection. Settings → Network and internet → Advanced network settings → More network adapter options → right-click the connection you’re sharing from (Wi-Fi or Ethernet, whichever has internet) → Properties → Sharing tab → check “Allow other network users to connect through this computer’s Internet connection.” If already checked: uncheck → Apply → recheck → Apply → try the hotspot again.
Fix 5: Firewall blocking hotspot traffic
Windows Defender Firewall occasionally blocks traffic between the hotspot’s virtual network and the internet-connected adapter. Administrator Command Prompt:
netsh advfirewall set allprofiles state offTest whether hotspot devices can reach the internet with the firewall temporarily off. If they can: re-enable the firewall → create exceptions for the hotspot virtual adapter. This is rare but explains “hotspot connects but no internet” situations that ICS configuration doesn’t resolve.
Network stack reset for persistent issues
netsh winsock reset
netsh int ip reset
ipconfig /flushdns
ipconfig /release
ipconfig /renewAdministrator Command Prompt, then restart. This clears any accumulated state in the network stack that might be preventing the hotspot’s DHCP from assigning addresses to connected devices or preventing traffic forwarding.
Device limit reached
Windows mobile hotspot supports up to 8 connected devices. If 8 are already connected, any additional device can’t join. Settings → Mobile hotspot → shows the number currently connected. Disconnect unused devices through the hotspot settings or through the connected device’s Wi-Fi settings to free a slot.
Corporate machines and hotspot restrictions
Group Policy can disable mobile hotspot on managed devices. If the hotspot toggle is greyed out and can’t be turned on: navigate to chrome://policy/ (or check gpedit.msc → Computer Configuration → Windows Settings → Network → Prohibit use of Internet Connection Sharing on your DNS domain network). IT manages this. If mobile hotspot is needed for a work reason: request IT to enable it for your account.
Our guide on Wi-Fi not working on Windows 11 covers the WLAN AutoConfig service and Wi-Fi adapter driver issues that affect the connection you’re trying to share. For the Internet Connection Sharing configuration in more depth, our IP configuration guide covers the DHCP and routing settings. Microsoft’s mobile hotspot documentation covers the group policy restrictions, the maximum device count, and the compatibility requirements for the physical Wi-Fi adapter to support hosted network mode (not all adapters support it).
Adapter doesn’t support hosted network mode
Not all Wi-Fi adapters support the virtual adapter required for mobile hotspot. Most modern adapters do, but some cheap or older adapters don’t implement the infrastructure mode required for the hotspot virtual interface. Check: administrator Command Prompt → netsh wlan show drivers → look for “Hosted network supported: Yes.” If it shows “No”: the physical Wi-Fi adapter doesn’t support hotspot functionality and no software fix resolves this. A different USB Wi-Fi adapter that supports hosted networks is the hardware solution.
Hotspot band selection and 5 GHz compatibility
Settings → Mobile hotspot → Edit → Network band. Windows allows choosing between 2.4 GHz, 5 GHz, or “Any available.” Some older devices (older tablets, IoT devices, budget phones) can’t connect to 5 GHz hotspots. If devices that should connect aren’t appearing in the hotspot’s device list: change to 2.4 GHz and test. 2.4 GHz has longer range and broader device compatibility; 5 GHz provides higher throughput but shorter range and narrower compatibility.
Sleep and hotspot disconnection
Windows typically stops the mobile hotspot when the machine enters sleep. Connected devices lose their connection and must reconnect when the machine wakes. For continuous hotspot availability: Settings → System → Power → Screen and sleep → set “When plugged in, put my device to sleep after” to “Never” while using the hotspot as an internet sharing point.
Also: Settings → Mobile hotspot → “When no devices are connected, automatically turn off mobile hotspot” toggle. If this is On and all devices disconnect briefly (during sleep, or when they go to standby), the hotspot turns itself off and requires manual re-enabling. Turning this off keeps the hotspot running even when temporarily device-free.
Speed issues with the hotspot
Connected devices that reach the hotspot but get very slow speeds: the bottleneck is usually the internet connection being shared, not the hotspot itself. Running a speed test directly on the Windows machine (not through the hotspot) shows the available bandwidth. Whatever the Windows machine gets is the maximum that all hotspot-connected devices share.
If the Windows machine’s direct connection is fast but hotspot-connected speeds are slow: the virtual adapter’s throughput may be limited. Checking whether the Windows machine’s Wi-Fi is on 2.4 GHz (slower) while the hotspot could benefit from 5 GHz (faster) — unfortunately you can’t easily split one Wi-Fi adapter to connect on 5 GHz for incoming and broadcast on 5 GHz for the hotspot simultaneously, since both share the same physical radio. Ethernet as the source connection (and sharing from Ethernet rather than Wi-Fi) eliminates the Wi-Fi half-duplex limitation and typically provides the best hotspot speeds.
When hotspot shows connected but no DHCP assignment
A device that connects to the hotspot (shows “Connected” on the device) but gets an IP starting with 169.254.x.x (APIPA self-assigned) means the hotspot’s DHCP server didn’t assign an IP. This is the ICS problem from Fix 4 — the Internet Connection Sharing DHCP server isn’t running.
Additional check: on the Windows machine running the hotspot → administrator Command Prompt → ipconfig /all → look for the “Local Area Connection* X” adapter (the hotspot virtual adapter) → it should show an IP in 192.168.137.x range with DHCP server details. If it shows no IP or a different range: ICS isn’t initialised correctly. Disabling and re-enabling ICS (Fix 4) typically resolves this by restarting the ICS DHCP service.
Third-party VPN and hotspot conflict
VPN clients often install their own virtual network adapters that can conflict with the hotspot’s virtual adapter. When both are active: the hotspot may start but traffic routing fails because the VPN redirects all traffic through its tunnel, preventing ICS from forwarding hotspot device traffic correctly.
Test: disconnect the VPN completely → test the hotspot. If it works without VPN: the VPN is interfering with ICS routing. Some VPN clients have a “local network” or “split tunneling” option that excludes local network traffic from the VPN tunnel — enabling this for the hotspot network (192.168.137.0/24 is the default ICS range) allows both VPN and hotspot to coexist. This is a VPN configuration rather than a Windows hotspot configuration change.
Mobile hotspot via cellular
If the machine has a cellular modem (4G/5G PC): Settings → Mobile hotspot → “Share my internet connection from” → change to “Cellular.” This shares the cellular data connection rather than Wi-Fi or Ethernet. Cellular-based hotspot has the same setup requirements but requires the cellular connection to be active and the cellular plan to allow tethering (hotspot sharing). Some cellular plans block tethering or charge extra — if the hotspot starts but cellular-connected devices can’t reach the internet, the cellular carrier may be blocking tethering on the plan.
Security settings for the hotspot
Settings → Mobile hotspot → Edit → Security type. WPA2 is the default and recommended. Some legacy devices (very old laptops, some IoT devices) only support WPA or even Open (no security). If a specific device can see the hotspot but fails to connect despite the correct password: try changing Security type to WPA or even Open temporarily to confirm whether the legacy device is the incompatible element. Revert to WPA2 after testing — running an open hotspot is a security risk that should only be a temporary diagnostic step.
For persistent hotspot issues after trying everything above: the most reliable reset is a complete network stack rebuild. Settings → Network and internet → Advanced network settings → Network reset → Reset now. Warning: this removes all network adapters and reinstalls them, resets all network settings to defaults, and requires re-configuring Wi-Fi passwords, static IPs, and VPN configurations. Use this as the last resort — it works when accumulated network configuration state is the problem, but it’s disruptive enough that it’s not the first thing to try.
After the Network Reset, Windows reinstalls all network adapters including the Microsoft Wi-Fi Direct Virtual Adapter, clears all network-related registry entries, and restores default firewall rules. The mobile hotspot typically works immediately after this reset and subsequent restart — it’s starting completely fresh.
Hotspot for sharing Ethernet to wireless devices
A useful and often overlooked use case: a laptop connected via Ethernet in a hotel room or office where only wired internet is available, sharing that connection as Wi-Fi to a phone or tablet that only has wireless. The hotspot feature handles this perfectly — set “Share my internet connection from” to “Ethernet” and the hotspot broadcasts the Ethernet connection wirelessly. This requires the laptop’s Wi-Fi adapter to be enabled (even though it’s not connected to a network) since the Wi-Fi radio is used to create the hotspot broadcast. If Wi-Fi is disabled to “save” the wired connection, the hotspot can’t broadcast.
Quick troubleshooting reference
Toggle does nothing → check Wi-Fi is on, check WLAN AutoConfig service, restart Microsoft Wi-Fi Direct Virtual Adapter. Hotspot starts but device can’t connect → check hotspot password, check band compatibility (try 2.4 GHz), check device is in range. Device connects but no internet → check ICS is enabled, check which connection is being shared, try the ICS disable/re-enable cycle. Hotspot randomly stops → disable auto-turn-off setting, disable sleep. Speed is slow → check source connection speed, consider sharing from Ethernet instead of Wi-Fi.
One pattern worth knowing for corporate environments: some companies configure Windows through Intune or Group Policy to prevent mobile hotspot creation because it bypasses network security controls — a laptop on the corporate network creating a hotspot that non-corporate devices connect to is a potential data exfiltration risk. If the hotspot toggle appears but immediately reverts, or shows as a managed setting, IT has intentionally locked it. The mobile data approach (using the phone’s built-in hotspot rather than the Windows laptop’s) avoids this restriction while achieving the same result. Our guide on Printer Not Working on Windows 11 covers an adjacent issue.
