Windows will auto connect to WiFi after a 1 minute delay from sys boot

Since I updated Windows to April 2018 version 1803, an annoying behavior started happening.
Whenever Windows start, instead of instantly auto connecting to my home wireless network, it takes 65 to 70 seconds to do so. There is no error message, the wifi adapter is instantly operational, wifi networks are instantly discoverable and my wifi network is "connect-able" if I manually click to connect. The only issue I have is that Windows will always auto connect to my home wifi specifically with a delay. If I create hotspots with my mobile devices, I cannot reproduce the problem. Windows will instantly connect to those networks (on system boot) but not to my internet wifi router.

The things I tried are: Uninstalling the wifi adapter. Deleting the network and reconnecting (with auto connect box ticked). Deleting the profile from folder ProgramData\Microsoft\Wlansvc\Profiles. Prioritizing my wifi network with command "netsh wlan set profileorder name="wifi-name" interface="interface-name" priority=#" and probably other things I can't remember.

I've given up hope that this can be fixed since I tried almost any solution I've found and none worked but I'm posting this here in case other people have the same issue and it catches Microsoft's attention.

Hey there! I had the same exact issue. I think it has to do with the June 12, 2018—KB4284835 (OS Build 17134.112) update. I troubleshot all morning and fixed it.

Forget the wireless SSID of your home network and reboot. Upon boot, reconnect to your SSID and make sure auto-connect is checked. Then open up the Command Prompt (make sure to open it with admin rights) and type in ipconfig /release. Then type in ipconfig /renew. Then type in ipconfig /flushdns. Repeat the ipconfig /flushdns like 10 times (just habit). Reboot the system and voila! I rebooted like 5 times just to make sure, and my problem is fixed.

Hm... maybe it's actually not fixed. I just powered up from a prolonged shutdown and the problem persisted.

I've been troubleshooting for days but I didn't come across the solution you suggested. Unfortunately it didn't work. At the moment I found a workaround but it is still a workaround and not a solution to the problem. And it most certainly cannot be used by other people with the same issue. I still consider it a bug that needs to be checked and fixed by Microsoft.

In case other people come across this thread I'll write a few more things I tried but didn't work (since I cannot edit my initial post).
I made sure that Hibernation and thus Fast Startup is indeed disabled.
I tried the commands that are used to repair system files, like DISM and sfc /scannow.
I tried both enabling and disabling the option “Allow the computer to turn off the device to save power”.
I tried the suggested solution below:

On the other hand, we suggest that you manage the Group Policy settings to check if the issue is not related to it. To do this, you may follow the steps below:

1. Click Start, type Run, and then press Enter.
2. On the Run command window, type gpedit.msc and click OK.
3. On the left-side pane of the Local Group Policy Editor window, navigate to the following folders: Computer Configuration > Administrative Templates > System > Internet Communication Management > Internet Communicating Settings.
4. On the right-side pane of the window, double-click on the Turn off Windows Network Connectivity Status Indicator active tests option to open its properties.
5. Select Not Configured and click OK to save the changes.
6. Once you’re done, you may check if you’re able to automatically connect your device to the Internet through Wi-Fi.

I created a registry entry with name fMinimizeConnections under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WcmSvc\GroupPolicy since there was not one there.

Navigate to the GroupPolicy key and in the right pane click on empty space and choose New > DWORD (32-bit) value. Enter fMinimizeConnections as the name of the new DWORD.

Other things that I forgot to mention is that my wifi adapter is using the Atheros AR5005G, the default Windows drivers are used (not drivers from manufacturer's site or other sources) and I have not installed any app that manages wireless networks like the apps that come bundled with the drivers in a cd.

It's strange - my solution seems to fix it for me for a while, but it creeps back eventually. Also interesting that you can toggle airplane mode on/off quickly, and it connects to wifi instantly.

Until this bug is fixed, here is a workaround which will automatically connect to a remembered wi-fi network when you log onto windows:


1) Create a text file located in C:\ directory and put the following script, changing the wifi network:

Code:

netsh wlan connect name="MyWifiNetwork" ssid="MyWifiNetwork"

Save the text file, and then change the name and file extension to "wifi-connect.bat". This script will connect to the wifi network when run.


2) Create another text file in the same place, and put the following script:

Code:

CreateObject("Wscript.Shell").Run "C:\wifi-connect.bat", 0, True

Save the text file, and then change the name to "wifi-connect.vbs". This script will run the previous script in the background, avoiding black command prompt window from popping up every time.


3) Open Task Scheduler (start menu -> type "task scheduler") and click "Create Task". Use the following settings:

Code:

General: Name - Wifi connect fix
Triggers: New -> Begin the task at log on
Actions: New -> Start a program -> C:\wifi-connect.vbs
Conditions: If on a laptop, uncheck "Start the task only if the computer is on AC power"

Click OK. This will run the script every time you log onto windows.


4) Restart your computer, and when logging on it should automatically connect to the wi-fi network you entered in the bat script.