If you’ve tried to reboot your computer or your router, or even checked your Wi-Fi connection and still find your computer stuck on 169 IP address, try the other solutions outlined in this article.
Some computer users have made configuration changes to their systems either by updating their operating system version, upgrading to a major OS release, migrating to a new system, or by performing a system restore from backup.
This is not a serious problem, as far as I know, but it certainly clutters my Windows logs!
Digging for an unrelated problem, I noticed hundreds of these errors in my Win 10 "Administrative Events" log - Event ID 1001: Your computer was not assigned an address from the network (by the DHCP Server) for the Network Card with network address 0x02004C4F4F50. Your computer will continue to try and obtain an address on its own from the network address (DHCP) server.
Built using Microsoft Visual Studio 2017 (VC 14.16, build 27030).
Running on 64-bit Windows 10 (1803), build 17134, with Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz (with SSE4.2), with 8117 MB of physical memory, with locale English_United States.1252, with Npcap version 0.9983, based on libpcap version 1.9.1-PRE-GIT, with Gnu TLS 3.6.3, with Gcrypt 1.8.3, without Air Pcap, binary plugins supported (14 loaded).That's the NPCAP address: Ethernet adapter Ethernet 3: Connection-specific DNS Suffix . : fe80::60af:c8fe:3fff%(Preferred) Autoconfiguration IPv4 Address. This can only be done if the network port detects a genuine and proper hardware connection but still can’t communicate with the DHCP server to get an IP address.In this case, the most likely culprit is the system’s firewall.The 169 IP range of addresses is reserved by Microsoft for private network addressing, so if your computer is set to obtain an IP automatically, then you’ll get one.When this happens, the APIPA (automatic private IP addressing) checks to configure itself automatically with an IP address and a default class B subnet mask. But some days I only see the hibernate / wake instances... The ~2 minute intervals began again on every wake from hibernation. Maybe all those other things are stubs in case somebody plugs in the USB to Ethernet dock? If I disable or uninstall them, it eventually puts them back... I do have Glass Wire as well as Wireshark and (Ze)Nmap installed... Windows is continually creating more things like: Wireless LAN adapter Local Area Connection* 6: And shows the above "Ethernet 4" in my system tray list of Wi-Fi APs... There is no hardware connection on a Surface Book, only the one Wi-Fi adapter.