Solution:
Root Cause: Corrupted or missing wlansvc binaries after a Windows Update A failed cumulative update, an interrupted upgrade, or disk errors can leave wlansvc.dll, wlanapi.dll or the Native Wi-Fi components damaged or missing from the component store. The Service Control Manager then fails with errors such as 1068 (dependency failure), 1053 (no timely response) or 126 (module not found), and Windows hides the Wi-Fi option entirely. This is a servicing-stack problem, not an adapter problem.
Diagnostic Verification: Run sc query wlansvc. The error 1060 ('The specified service does not exist') confirms a missing service registration. Check that C:\Windows\System32\wlansvc.dll exists, using Test-Path C:\Windows\System32\wlansvc.dll. Review C:\Windows\Logs\CBS\CBS.log for 'cannot repair' entries after running SFC. Step-by-Step Fix: 1 Repair the component store:
Run the following in an elevated terminal and wait for completion.
Copy
powershell
DISM /Online /Cleanup-Image /RestoreHealth
2 Repair protected system files:
Copy
powershell
sfc /scannow
3 Re-check the service:
Run sc qc wlansvc and confirm the service is registered, then run net start wlansvc. 4 Roll back a bad update if the problem began right after patching:
Go to Settings > Windows Update > Update history > Uninstall updates and remove the most recent update. 5 As a last resort, run an in-place repair upgrade:
Mount the Windows 11 ISO, run setup.exe, and choose Keep personal files and apps. Prevention & Long-Term Monitoring: Back up with a system image or restore point before major feature updates. Run chkdsk /scan periodically to detect file-system corruption. Keep at least 20 GB of free space on the system drive so servicing can complete.