Not sure when Micro$oft can stop such abusive moves. Why the user have to be able connect to your endpoint to prove they are connected? Why keep nagging me to set active hours coz I regularly use my computer 8am to 6pm?
You can disable the checks if you want. Any application that uses the operating system API/DBus to evaluate network connectivity rather than building its own bespoke online check will probably break if you do, though.
Because all of these have to use HTTP, you can also easily override the standard network addresses in your hosts file and pick your own server if that's what you prefer.
I don't want that sh*t to be there in the first place.
No one knows better than the end user. And also, if the user could not reach some M$ server does not mean users' network was not connected to the internet.
Anyway, won't be a trouble for me much longer. Retiring all my Windows instances, had enough.
It's crazy, everyone else is just letting M$ control the narriative and falling for it.
Micro$oft is trying to define what is and is not 'internet' access, eg. they turn the definition of 'internet' to mean unfettered access to the micro$oft servers is and you're ability to send personal information over to them.
Anyway, won't be my problem much longer.