Win10 Wifi Still not staying connected, despite trying multiple fixes.

Hi, I upgraded to windows 10 from windows 7. I have tried numerous fixes to get it to stay connected but it just doesn't seem to work.
I have done all the well documented fixes including registry edits, changing the power management settings on my network device and it just doesn't seem to help. The longest I have managed to stay online in one session is about 45 minutes, but more often than not, it doesn't stay connected longer than 15.

Once the connection is lost, the network cannot connect, or even be found on occasion. This forces me to restart the computer to re-establish the connection.

Does anyone have any ideas, as it's getting to the point where I am tempted to just bin the thing and get a new computer with a version of windows 10 that is not upgraded from an old OS.

Superfly said:

Nope, but a long-shot:

ipconfig /flushdns


Could be due to corrupted config.

Cool, that's not something I've tried yet. I'll give that a go after work.

Have you googled your network device and driver to see whether it may be linked to these? Some people have had driver issues with wifi.

how old is your router? Sometimes the older routers can't keep up with the newer stuff.

linw said:

Have you googled your network device and driver to see whether it may be linked to these? Some people have had driver issues with wifi.

I have the correct drivers, made sure I didn't have the ones that were causing these problems elsewhere.

play2mefish said:

how old is your router? Sometimes the older routers can't keep up with the newer stuff.

I believe it's a BT homehub 3, may be a 4. Whichever one was the first to be /n compatible

Open a admin cmd prompt keep it open then type these cmds
ipconfig /all >reg.txt
netsh wlan show networks mode=bssid >> reg.txt
netsh wlan show profile >> reg.txt
netsh interface ipv4 show subinterfaces >>reg.txt
netsh int tcp show globa >>reg.txt

notepad reg.txt

post results of reg.txt

Superfly said:

Nope, but a long-shot:

ipconfig /flushdns


Could be due to corrupted config.

This did the trick, thank you.