Scroll through any tech forum and you’ll find the same complaint: the laptop’s mobile hotspot either won’t turn on, turns on but no device can connect, or connects and then drops every few minutes. It’s one of those Windows features that works beautifully until the day it doesn’t — and when it breaks, the error messages are somewhere between vague and nonexistent.

The collective wisdom from thousands of these threads boils down to a short list of real causes. The hotspot depends on a chain: your Wi-Fi adapter must support hosted networks, its driver must be healthy, Windows’ sharing service must bind correctly, and nothing (VPN, firewall, power saving) may interfere. This guide walks that chain in order, starting with the thirty-second checks and ending with the driver surgery that fixes the stubborn cases. Most people find the break in the first three steps — the rest of the guide is there for the genuinely tricky ones where two problems overlap, like a VPN conflict hiding behind a stale driver.

Why this happens

  • Wi-Fi driver lacks hosted network support: Generic or outdated drivers may not implement the SoftAP feature Windows needs to broadcast a hotspot, leaving the toggle dead.
  • Internet Connection Sharing binding breaks: The ICS service can lose its binding to the Wi-Fi adapter after updates, so the hotspot broadcasts with no internet behind it.
  • VPN clients hijack the network stack: VPN software reroutes traffic and blocks the NAT translation the hotspot requires — the single most common cause in forum reports.
  • Power management disables the adapter: Windows’ power saver can shut the Wi-Fi radio down mid-hotspot, especially on battery, killing connected devices’ access.
  • Stale hotspot configuration: Corrupted saved settings for the hotspot SSID and password prevent the virtual adapter from starting cleanly.
  • Bluetooth coexistence interference: On some wireless cards, Bluetooth activity degrades the hosted network, causing drops and failed connections.
  • Windows update replaced the driver: Feature updates swap in generic wireless drivers that drop hotspot capability until the manufacturer’s driver is reinstalled — the same pattern behind vanishing Wi-Fi after updates.
  • Firewall blocking DHCP: Third-party firewalls can block the hotspot’s built-in DHCP server, so phones connect to the Wi-Fi but never receive an IP address.

How to fix it

Work through these in order — diagnose first, then act.

Fix 1: Verify hosted network support

  1. Open Terminal as administrator (Win+X > Terminal (Admin)).
  2. Run netsh wlan show drivers and look for the line Hosted network supported.
  3. If it says Yes, your hardware can do this — continue with the software fixes. If No, your adapter physically can’t host; skip to Fix 7 for the USB adapter workaround.

Fix 2: Toggle and reconfigure the hotspot cleanly

  1. Go to Settings > Network & internet > Mobile hotspot and turn it Off.
  2. Change the Share my internet connection from dropdown to your active connection explicitly (don’t leave it on automatic).
  3. Change the network name and password to something new — this clears any corrupted saved configuration.
  4. Turn the hotspot back on and test with your phone. If devices connect now, stale settings were the whole problem — and to prevent recurrence, avoid renaming the hotspot SSID from the quick-settings flyout, which is a known source of the corrupted configurations this step clears.

Fix 3: Disable VPN and test

  1. Disconnect and fully quit any VPN client (not just disconnect — exit the application).
  2. Disable third-party antivirus/firewall real-time protection temporarily.
  3. Turn the hotspot on and test. If it works, you’ve found the conflict — check your VPN’s settings for split tunneling or a “allow local network” option as a permanent fix.
  4. Re-enable your security software immediately after testing.

Fix 4: Reinstall the Wi-Fi driver

  1. Open Device Manager (Win+X > Device Manager) and expand Network adapters.
  2. Right-click your Wi-Fi adapter, choose Uninstall device, and tick Attempt to remove the driver for this device.
  3. Restart. Windows will reinstall a driver; then install the latest from your laptop manufacturer’s site for the full-featured version.
  4. Check netsh wlan show drivers again to confirm hosted network support is back, then retry the hotspot. The step-by-step hotspot guide covers driver variants per manufacturer in more detail.
  1. Press Win+R, type services.msc, and press Enter.
  2. Find Internet Connection Sharing (ICS), right-click, and choose Restart (or Start if stopped). Set its startup type to Automatic.
  3. Do the same for Windows Mobile Hotspot Service if present.
  4. Toggle the hotspot off and on again in Settings.

Fix 6: Reset the network stack

  1. In an admin terminal, run: netsh winsock reset, then netsh int ip reset, then ipconfig /flushdns.
  2. Restart the laptop.
  3. Set up the hotspot fresh with a new SSID and password. This clears corrupted virtual adapter states that survive simple toggles. Microsoft’s Windows support pages document these netsh commands as the standard network reset procedure.

Fix 7: Use a USB Wi-Fi adapter as the hotspot radio

  1. If netsh reported Hosted network supported: No, get a dual-band USB Wi-Fi adapter that lists hotspot/AP mode support.
  2. Plug it in, install its driver, and in the hotspot settings choose the USB adapter as the shared connection source.
  3. This bypasses the internal card’s limitation entirely and usually delivers a more stable hotspot anyway.

Closing

Mobile hotspot failures look mysterious, but they follow a short script: confirm the hardware can host, clear stale settings, remove VPN and firewall interference, fix the driver, and reset the stack. Worked in order, these steps resolve essentially every hotspot failure that isn’t a hardware limitation — and for the hardware-limited cases, a USB adapter is a ten-minute permanent fix. Your phone will be online through your laptop again before you’ve finished your coffee, and you’ll know exactly which link in the chain was broken.

Frequently asked questions

Why does my mobile hotspot turn on but devices can't connect?
This usually means the hotspot’s virtual adapter started but the internet sharing binding failed. The hosted network is broadcasting, but traffic has nowhere to go. Re-selecting the shared connection in the hotspot settings, resetting the network stack, or reinstalling the Wi-Fi driver typically restores the binding. Bluetooth interference and VPN software are the other common culprits.
Why is the mobile hotspot toggle greyed out?
A greyed-out toggle means Windows can’t access the Wi-Fi adapter’s hosted-network capability. The Wi-Fi driver may be missing, outdated, or a generic Microsoft build that lacks hotspot support. Check Device Manager for your wireless adapter’s status and install the manufacturer’s driver. Some adapters also disable hotspot mode when power saving is aggressive.
Can antivirus or VPN software break the mobile hotspot?
Yes, both are frequent offenders. VPN clients reroute all network traffic and often block the NAT that the hotspot depends on. Third-party firewalls can block the hotspot’s DHCP server, so connected devices get no IP address. Temporarily disabling them for testing is the fastest way to confirm — just remember to re-enable protection afterward.
Does my Wi-Fi adapter need to support hosted networks?
Yes. The adapter must support the hosted network (SoftAP) feature for Windows’ mobile hotspot to work. Most modern adapters do, but some older or budget cards don’t. You can check by running netsh wlan show drivers in a terminal and looking for Hosted network supported: Yes. If it says No, a USB Wi-Fi adapter with hotspot support is the practical fix.