Old News
WTF ?
I have fixed multiple systems over the past year with this exact issue, computer is connected, be it wifi or ethernet, and you get a 169.254.x.y IP address ... the solution ?
netsh winsock reset
Problem solved ... I had it on my Window 8 (about 8 months ago) and Windows 10 (two weeks ago) boxes, and have helped acquaintances with this ... reboot does NOT help, a winsock settings cockup, and no, I had not changed any network settings.
Mind, the other day I changed the docker virtual switch to connect to the internet directly, to use hyperv, and I had 93% packet loss (from within the VM, 0% [as in, no problem at all] from within the host) ... not sure about the reliability of the Windows 10 TCP/IP stack ...
Biting the hand that feeds IT
