Sudden wifi issue - can't connect to regular wifi only hotspots

The symptoms fit two Windows-side scenarios from the troubleshooting guidance:

• Connection or authentication fails: Windows can see networks but fails during association or authentication.
• Issue started after an update or resume / driver change: the problem became worse after the adapter driver was removed and reinstalled.

The hotspot detail does not rule out an adapter or driver problem. The guidance specifically says to compare the current driver and firmware versions with the versions recommended by the device or adapter manufacturer, especially when behavior changes after driver work.

Recommended next steps:

1. Check whether the adapter is present and enabled
   • Open Device Manager and confirm the Intel(R) Wireless-AC 9560 160MHz adapter is present and not disabled.
   • If Wi‑Fi controls are missing, the troubleshooting guidance says to confirm the adapter is present and enabled and that the WLAN AutoConfig (WlanSvc) service is running.
2. Verify WLAN AutoConfig is running
   • The advanced troubleshooting guide notes that if WlanSvc is stopped, the Wi‑Fi control can be hidden and netsh wlan commands report that the service is not running.
   • If Wi‑Fi appears unstable or missing, this is a key check.
3. Collect basic wireless state before making more changes
   • Run these commands in Command Prompt:
     • netsh wlan show drivers
     • netsh wlan show interfaces
     • netsh wlan show networks mode=bssid
   • For this symptom set, the troubleshooting guide lists these as the main evidence to collect.
   • This helps determine whether the adapter is reporting supported bands correctly, whether radio state is normal, and whether Windows can fully enumerate nearby networks.
4. Check for recent changes and compare driver versions
   • Since the issue worsened after reinstalling the driver, compare the currently installed Wi‑Fi driver version with the version recommended by the laptop or adapter manufacturer.
   • The guidance explicitly recommends reviewing the device manufacturer’s support information for wireless driver, firmware, and BIOS updates or known compatibility issues.
   • Avoid repeated uninstall/reinstall cycles until the current baseline is recorded, because the troubleshooting guide warns that removing the adapter or driver can remove evidence or temporarily change behavior.
5. Test whether expected networks are being displayed correctly
   • The troubleshooting guide says that when expected networks are not displayed, check:
     • hardware and software radio state
     • WLAN AutoConfig service state
     • supported bands
     • whether other clients can see the same network
   • In this case, other devices can see and use the same Wi‑Fi, so the remaining focus is the laptop’s radio/driver state.
6. Try the standard setup-side checks again only where they still apply
   • Since already tried password, 2.4 GHz split, and other networks, the remaining supported checks are:
     • move closer to the router/access point
     • try the other frequency band if both are available
     • try a different trusted Wi‑Fi network
     • use Ethernet if the device can be connected that way, or with a USB-to-Ethernet adapter
     • if available, use cellular or hotspot temporarily
   • Ethernet is especially useful here because it separates “Wi‑Fi path is broken” from “general internet stack is broken.”
7. If no Wi‑Fi networks appear or the adapter state looks wrong, reinstall the Wi‑Fi adapter driver carefully
   • The setup guidance says that if no Wi‑Fi networks are listed and an error appears, download the necessary Wi‑Fi adapter drivers on another device, copy them to a USB flash drive, and make sure the .inf file is in the root of the flash drive.
   • This is the supported recovery path when the local driver state is damaged.
8. Do not change BIOS settings yet
   • There is no need from the provided guidance to start with BIOS changes.
   • The documented path is to first verify adapter presence, service state, wireless state, and manufacturer-recommended driver/firmware versions.

Based on the described behavior, driver corruption, adapter state problems, or a failing wireless adapter are all plausible, but the supported guidance points first to verifying adapter presence, WlanSvc, and manufacturer-recommended driver/firmware versions before concluding hardware failure. The fact that Bluetooth still works does not eliminate a Wi‑Fi-specific adapter or driver fault.

References:

• Advanced troubleshooting wireless network connectivity
• Get connected when setting up your Windows device