What Was Happening
The Wi-Fi had stopped working — no networks were appearing in the list at all, even though the laptop’s Wi-Fi was switched on. Around the same time, the user had got locked out of their Windows account after forgetting the password and exhausting the on-screen reset options.
Two faults at once is harder than one, because the temptation is to do a fresh install to “fix everything at once”. That works but loses the user’s data. We diagnosed each fault separately and chose the right approach for each.
Our Diagnosis
Wi-Fi first (which we could check without needing to log in to Windows):
- Booted from a diagnostic USB. Tested the Wi-Fi hardware from a clean Linux environment that ignored the existing Windows installation. Wi-Fi adapter visible, networks listed, connection successful. That confirmed the Wi-Fi hardware was healthy.
- Conclusion on the Wi-Fi side: the fault was Windows-side. Driver corruption or misconfigured network profile. Both routinely fixable once we could get into Windows.
Password situation:
- Established what type of account it was. Booted Windows to the login screen, checked the account type from the indicator below the username. Local account, not a Microsoft account.
- Local accounts have limited recovery options. A Microsoft account password can be reset online via account.microsoft.com — straightforward. A local account password has no online reset; the only built-in options are:
- The password hint (sometimes enough to jog memory)
- Security questions (if set up during account creation)
- A password reset disk (if created in advance, which most users haven’t)
- In some cases, a Microsoft account linked to a Local account that allows recovery through that
- Checked all of the above. Hint didn’t help. No security questions set. No reset disk. No linked Microsoft account.
- Final route: with no available recovery method, the choice is either to live without that account (set up a new one with the same data) or to do a clean install. In this case the user wanted a fresh start anyway, so a clean install with data preservation was the right call.
How We Fixed It
The order mattered — protect data first, fix Wi-Fi after.
Drive image first. Connected the drive to our imaging setup via a write-blocked interface and made a complete bit-for-bit image. The image gave us a safe copy of the user’s Documents, Pictures, Downloads, Desktop and other personal data even though we couldn’t log into the account itself.
Verified the image. Browsed the user profile from the image. All personal data folders intact and readable.
Clean Windows install on the wiped drive after the image was safely stored. We left the Wi-Fi work until after the install because a clean install resets all driver state — which would have undone any Wi-Fi fix done before.
Wi-Fi setup on the new install:
- Let Windows install its generic driver first to get basic connectivity
- Installed the proper Asus driver bundle for this model — chipset, network, sound, system management
- Configured the Wi-Fi network correctly with the user’s home network credentials
- Verified connection speed and reliability
Restored user data from the image into the new user profile. Documents, Pictures, Downloads, Desktop folders all back where they belonged. Browser bookmarks where credentials allowed.
Set up the new user account properly to avoid a repeat of the password problem:
- Recommended (and configured, with the user’s agreement) a Microsoft account so future password issues could be recovered online
- Set up Windows Hello with a PIN so the everyday login isn’t via the long password
- Documented the recovery method so the user has a clear path back if anything similar happens again
The Result
Laptop back with the user, Wi-Fi working reliably, all personal data restored, account set up with proper recovery options. The user briefed on what to do differently going forward so they don’t end up locked out again.
Why This Happens
Microsoft’s design choices on this have changed over the years and the current state is:
- Microsoft account passwords can be reset online from any device via account.microsoft.com. The recovery email or phone number you set up when creating the account is the route. This is the recommended account type for most users.
- Local accounts are entirely self-contained on the laptop. The password isn’t synced anywhere, isn’t recoverable through Microsoft, and the only recovery options are the ones you set up at account creation or before forgetting the password.
Local accounts are useful in specific situations (corporate laptops, family-shared computers, privacy-focused setups) but they don’t have the recovery safety net most home users assume.
If you’re using a local account, the things to set up:
- A password hint that actually jogs your memory rather than something cryptic
- A password reset disk (Control Panel → User Accounts → Create a password reset disk) — easy to do, almost nobody does it
- Security questions — Settings → Accounts → Sign-in options
Without at least one of these, a forgotten password usually means a fresh install with data preservation as the recovery route.
Why This Happens
The most common causes we see for a Wi-Fi adapter that “doesn’t see any networks”:
- A Windows Update that included a Wi-Fi driver update that was incompatible with the specific adapter chipset
- A third-party VPN install that left driver residue affecting the network stack
- A failed adapter driver update from the Asus updater or Windows Update
- Corruption from an aborted Windows update
- A specific Wi-Fi adapter firmware bug that needs the manufacturer’s updated firmware to fix
The fix is almost always the same: clean removal of the existing driver, fresh install of the correct manufacturer driver. We use the laptop manufacturer’s curated driver bundle (Asus’s MyAsus app for current models) rather than letting Windows install a generic driver — the manufacturer’s version includes manufacturer-specific firmware updates that the generic driver doesn’t.
Local Help in Putney SW15
Wi-Fi connectivity faults usually trace back to one of a small number of causes — and a workshop diagnostic separates them quickly.
We diagnose router-side issues, laptop-side network stack damage, leftover-software conflicts and full home or office Wi-Fi setups from our Putney workshop.
Drop in to SW15, call 020 7610 0500, or contact us to discuss.