Internet Diagnostic Service not executing.

See option #3 in this tutorial:
SFC /SCANNOW Command - System File Checker

Please attach the file named sfcdetails.txt to your next post - using these steps:
Screenshots and Files - Upload and Post in Seven Forums

Everytime I try that command it tells me that it can't find the specified route, that ""[SR]"" isn't a recognized internal or external command, or an outright "access denied"

Please post a screenshot of the cmd window rather than typing out the error that you see.



You should be able to copy the command line from the tutorial and paste it into the cmd window.
findstr should be the first part of the command, not "[SR]".

Maybe need to run cmd as admin if you skipped that step.

T7388 said:

WLAN AytoConfig is started without problem, thanks for the .reg file GokAy

Second sfc /scannow result is:

Windows resource protection encountered damaged files and repaired them correctly. To obtain more details, consult CBS.Log.

Problem still persists.

Which problem still persists?
The Wi-Fi problem or the SFC problem?
Or both?

T7388 said:

Got it.

As I'm on a mobile, the forum will only allow pictures to be attached so I'll find a way to upload said file shortly.

The file mentioned in the scan results should have no impact on the Wi-Fi problem. The SFC issue can be dealt with after the Wi-Fi issue is fixed.

WiFi problem still persists. I can see WiFis, just when I try to connect it says I'm connected but doesn't really connect.

Are you still getting a "169" IP address?

Code:

Adaptador de LAN inalámbrica Conexión de red inalámbrica:

   Sufijo DNS específico para la conexión. . :
   Dirección IPv6 . . . . . . . . . . : ::885f:7a34:a72b:469
   Dirección IPv6 temporal. . . . . . : ::7442:55c8:2c14:aaff
   Vínculo: dirección IPv6 local. . . : fe80::885f:7a34:a72b:469%10
   Dirección IPv4 de configuración automática: 169.254.4.105
   Máscara de subred . . . . . . . . . . . . : 255.255.0.0
   Puerta de enlace predeterminada . . . . . :

IPv4 address is exactly the same.

Just as a test:
If you know what the IP range is supposed to be, manually assign the wireless network adapter a static IP in that range and see if Internet connectivity is restored.