SoylentNews is people
SoylentNews
Many Windows 10 users are suffering from a bug which causes wi-fi connections to disconnect.
Recently, some users have noticed (probably abruptly) that their Wi-Fi dropped out, with Windows complaining about an invalid IP configuration. Microsoft released a patch just the other day (who enjoyed a good ol' fashioned forced reboot from it?) that could have fixed the issue, but didn't.
Speculation at this point says the disconnect results when a machine performs a fast startup, setting the machine's IP address to 169.x.x.x. It's an old problem, but somehow it's come back in spades in the past two days. I have no idea what triggered the sudden outbreak, as there were no Win10 1607 patches issued on Dec. 6, 7 or 8.
This scoop was sent from my ArchLinux laptop connected through wifi. It's hard not to be a little smug about it. ;-)
(Score: 2) by tibman on Monday December 12 2016, @08:17PM
Maybe Windows needs a better init system? I've heard linux was recently eaten by one. They should all get in touch.
SN won't survive on lurkers alone. Write comments.
(Score: 0) by Anonymous Coward on Tuesday December 13 2016, @04:33AM
It has an excellent startup system. Unless you muck the registry dependency items up. The equiv init.d way would be to put dhcpd after the network startup script. Most network managers handle that sort of thing for you in linux. In windows it still is 2 separate things.