4

Why is it that windows 10's network adapter takes so fucking long in order to work and connect to the internet!!

Does anyone know a way to trace back what's causing it? And why it takes like full 15 minutes for the Ethernet or wifi drivers to even work? (I'm not even sure if this is something with the drivers or the way windows's network adapter way of working)

I couldn't find Jack shit on the internet (most of them are ghetto do this and that and hope it works) I want something more advanced so I can figure out for once why this happens on numerous windows computers

(Linux people, I understand you, please don't rant your stuff here, this is a bit serious issue, thx)

Comments
  • 2
    No idea, maybe your network is taking forever to assign IP addresses (i.e. issues with DHCP)?
  • 0
    Windows wireless drivers are garbage I think, constantly disconnects or introduces bad latency until restart
  • 1
    So yesterday I tried to configure a router, attached it to lan port but the wifi won't go and it kept connection to wifi because it had internet. Turned off wifi and it was still showing globe icon in tray. So i checked the lan cable if it was working. Turns out it was connected to router but wont show connection. Later when i turned wifi on, it wont search any so I had to restart the fucking computer to make it work again.
    When will Microsoft understand you dont need to fuck up with these forced and shitty updates.
    Dont start with linux suggestions please, I would use it if I had a choice.
  • 2
    Older windows versions had status updates in adapter window which used to show what is the adapter doing at the time. Like getting dhcp settings, finding a gw, testing gw, testing internet conn, stc. If w10 still has this, maybe you could pin-point which action is taking so long and then you'd know where to dig further.
  • 1
    I had that issue recently too. It always took 5 min for me. Now it's magically solved. Interestingly enough, all websites didn't work except for Google services 🤔
  • 1
    Welp, after almost a month, I think the issue was caused by Hyper-V, disabling that restored the normal behaviour in windows, thanks docker
Add Comment