Script required to automatically connect to specific Wi-Fi network

W10 Tweaker said:

OK, new vbs code set and I did include the last line for potential future diagnostics.

I ran the task manually and it scored 10 successful network connects for 10 attempts. Bravo and thanks for your continued support.

I'll start and maintain a new reliability summary in this post.



2 successful auto-connect to Wi-Fi out of 4 attempts.

The 2 previous attempts to connect after returning from sleep failed and produced an 'Error code: 1'.

In "C:\Scripts\WLAN\Netsh.vbs", replace the original code with the following:

Code:

Set X=CreateObject("WScript.Shell"):Do:Return=X.Run _
("%WinDir%\System32\netsh.exe wlan connect ""[ssid]"" ""{profile name]"" ""Wi-Fi""",0,True)
If Return = 0 then WScript.Quit 
Attempts = Attempts + 1 : Loop until Attempts = 4
X.Run"C:\Scripts\WLAN\Testing.cmd":MsgBox "Error code: "&Return

Copy the following code into "C:\Scripts\WLAN\Testing.cmd", which will be run only if VBScript has failed to start the connection.

Code:

@echo off
Netsh WLAN connect "[ssid]" "{profile name]" "Wi-Fi"
Echo The errorlevel is %errorlevel%
Netsh WLAN show interfaces
Netsh WLAN show networks
Netsh WLAN show drivers
Netsh WLAN show profiles
pause>Nul

Hopefully, it will show the culprit.

zebal said:

I figured this out after googling from one screenshot HERE

By googling, I found the following example:

Code:

Mon Nov 18 17:15:25 2013 ERROR: netsh command failed: returned error code 1
Mon Nov 18 17:15:29 2013 MANAGEMENT: Client disconnected
Mon Nov 18 17:15:29 2013 NETSH: command failed

Source: [Closed] ERROR: netsh command failed: returned error code 1 - OpenVPN Support Forum

zebal said:

Error code 1 if it's related to netsh.exe means:
I figured this out after googling from one screenshot HERE

If so and unless I'm wrong capturing logs (and reasons for failure) can be done also with netsh:
https://docs.microsoft.com/en-us/win...-manage-traces

Thanks for the info zebal and contributing.

Matthew Wai said:

In "C:\Scripts\WLAN\Netsh.vbs", replace the original code with the following:

Code:

Set X=CreateObject("WScript.Shell"):Do:Return=X.Run _
("%WinDir%\System32\netsh.exe wlan connect ""[ssid]"" ""{profile name]"" ""Wi-Fi""",0,True)
If Return = 0 then WScript.Quit 
Attempts = Attempts + 1 : Loop until Attempts = 4
X.Run"C:\Scripts\WLAN\Testing.cmd":MsgBox "Error code: "&Return

Copy the following code into "C:\Scripts\WLAN\Testing.cmd", which will be run only if VBScript has failed to start the connection.

Code:

@echo off
Netsh WLAN connect "[ssid]" "{profile name]" "Wi-Fi"
Echo The errorlevel is %errorlevel%
Netsh WLAN show interfaces
Netsh WLAN show networks
Netsh WLAN show drivers
Netsh WLAN show profiles
pause>Nul

Hopefully, it will show the culprit.



By googling, I found the following example:

Code:

Mon Nov 18 17:15:25 2013 ERROR: netsh command failed: returned error code 1
Mon Nov 18 17:15:29 2013 MANAGEMENT: Client disconnected
Mon Nov 18 17:15:29 2013 NETSH: command failed

Source: [Closed] ERROR: netsh command failed: returned error code 1 - OpenVPN Support Forum

Excellent! Thanks again for your continued perseverance.

Hopefully, this will produce a clue as to where the failure is happening.


I've updated the Netsh.vbs file and added the 'Testing.cmd' file.




2 successful auto-connect to Wi-Fi out of 2 attempts.