Re: I see this BS because of minimal trust for Microsoft domains
>The correct way to detect no connections, should be continuous failure to connect to any internet address, during a set time period, a good one can be the time server, if set to an internet address. <
This is the way Win10 detects internet connection failure, and up until now has been the reason for this bug. You get a routing failure, and Windows labels that as an Internet connection failure, and that affects routing....
It's been a problem with Win10 for some time, -- IPV4 standards/RFCs never really caught up with multi-homed systems and multi-homed systems are subject to corner-case routing failures. It should be fixed by total system conversion to IPV6 protocols (but of course will probably be broken by the transition).
And no, "IPV6" doesn't just mean IPV4 with more bits.