This issue has been happening to me and many other friends that I know where after a reboot, the laptop doesn't connect automatically to the Wireless Network. At first, I thought it may be a bug which may be fixed with future updates but even after the latest CU the issue is still there. I have a Killer 1550 Wireless card in my laptop and only installed the INF driver without the bloated Killer Performance Suite and I do have the latest drivers which were just released 2 days ago but still no luck. Does anyone have a similar issue?
I do, but not all the time. Sometimes it just sits there and doesn't show any attempts to connect, but as soon as I open the WLAN menu it starts connecting. It's acting like it's being lazy, and won't do s**t unless someone is watching lol.. I will do a reinstallation of Windows in a few days, hoping that it'l fix it.
Oh I forgot to mention that if I manually hit connect, it connects instantly, as if it were connected but just like frozen. It doesn't happen a lot when I first format, but then it starts doing it more and more it's driving me crazy. I can tell you it's not a driver issue as I've tried more than 5 different drivers including the latest ones released by Riva Networks (Killer Networking) just a couple of days ago. It's a Windows 10 Spring Creators Update bug.
Same here. Besides, I have an Intel WLAN card, so if we both are having issues then I guess your're right, it's not a driver issue (unfortunately). I've had this issue since at least 1703 tho.
yes this issue is known on last win10 builds, from what i read on other forums, you have to wait for about 1 minute so that the wireless connection connects automatically after the reboot.
This ^. Also, as strange as it sounds my wifi connects faster with 1803. It used to be a problem with 1709 and before. I had to wait a minute or two or connect manually.
u are aware that u must tic on the connect automatically on the wifi menu in win10 so each time u log in theirs no need to type in your wifi pass.
This is a hardware+driver limitation on many wireless cards, and it has been known since the XP days, it's not a "Windows 10" thing. A delay is visible in Linux too, it's just that everything is loaded in text mode very early. OEMs used to provide a startup program to accelerate stuff after login, and it usually helped, but now such solution is mostly discontinued in favor of letting Windows managing connections alone. 1803 definitely tries to load the network stack and trigger radios faster (both Wireless and Ethernet), and is seconds quicker (or better) than older versions. At least that's what I've seen on few dozen machines. Also, don't forget about that piece of s**t "99 problems" fast startup function, and automatically continue activities. Disable them like the plague.
That sounds like DHCP issue. I always disable it, because it only causes problems along with IPv6, especially on wifi. I have IP/DNS setup manually and internet works ASAP.
How old is your machine maybe older wifi cards have issues like that in win10, that usually happens when your coming out sleep mode HW must turn on and yours have issues connecting, try this go into your power options and choose when computer goes to sleep and click on never and see if that solves it for.
Did a clean install on my test notebook the other day - same thing as you. This is the 1st time I've seen this behavior. The notebooks got an Intel 8260. Are you running KB4338548 (OS Build 17134.83)? This was my 1st install with this build...