Did you know? Microsoft added a new feature.

So if there is an IP conflict, our beloved Windows 10 doesn’t cry with an IP conflict error. Instead it sets an auto configured IP which doesn’t even connect to the network sending the user into confusion and a fit of rage.

Thanks Microsoft™

Also this

You mean the 169 network? That's been there since I can remember

@Jilano @netikras I remember in Windows XP it used to explicitly show an error when there was an IP conflict. If Windows 10 would have shown that error then the screenshot makes sense.

The guys at Redmond are amazing people, they think of everything...

I envy this man. It's 2019 and he's just now discovering APIPA. You lucky bastard.

Yeah I just noticed that a couple of days, too. I was expecting to see a nice little popup saying IP Conflict detected, when I reconnected my NAS, but instead I got assigned an APIPA adress. For some reason the network connection was still functional, partially. Everything worked magically except for discord auto update.
I think my Router (Fritz Box) was doing some routing trickery, otherwise I can't explain such behavior.

@2lazy2debug I'm on LTSC 1809 (I know it's silly, dont ask why) and I am not getting this said error message but instead an auto configured APIPA.
It may be a Bug, but who knows.