If you've been having issues with your Windows 10 machines not connecting for a minute or even at all after a boot or reboot, you may have been hit with a bug that has affected Windows 10 since version 1709 rolled out. Even if you have a network SSID set to "Connect Automatically," Windows would not connect reliably after a cold boot. This would affect users using pre-shared keys and also 802.1x policies (for example using RADIUS or Windows NPS Server) and all flavors of Windows including Home, Professional, Enterprise, & Education editions.
One way to fix this is by disabling the "Microsoft Wi-Fi Direct Virtual Adapter" in Device Manager, but this came with some side-effects such as disabling the ability to wirelessly project through Miracast (also Intel's WiDi). Those who couldn't or didn't want to do that have had limited success making the issue less likely to occur by disabling the "EnableActiveProbing" registry parameter and/or using Group Policy to enable the "Turn off Windows Network Connectivity Status Indicator Active Tests" & "Do Not Show the Local Access Only Network Icon" policies.
Fortunately, Microsoft has just released a cumulative patch for Windows 10 1803 that seems to have fixed the Wi-Fi issue introduced with the 1709 feature upgrade. It is the October 24, 2018—KB4462933 (OS Build 17134.376) update. Microsoft also recently released an update for Windows 10 1709, but we have not yet tested to see if it fixes this issue. As for the recently released Windows 10 1809, we do not recommend upgraded to that feature update quite yet due to the major issues that still need to be resolved.
Please comment below and let us know if you have had success with the KB4462933 update!