It would be really nice if there was some site that kept an up-to-date database listing of all the KBXXXXXXX update numbers that include this crap (up-to-date being the key here since Microsoft actually renames old KBXXXXXXX numbers every once in a while to include the same crap the old KBXXXXXXX did).
――――――
¹ — http://www.eightforums.com/windows-updates-activation/66805-...
Possibly of interest?
That does not seem very smart to me. I think personally that Microsoft is adding telemetry to make Windows more secure and compete with Apple and Google who do the same. But if you don't trust it, it seems better no not use it at all.
Yes all this is somehow true, yet they offer an opt-out in Settings that doesn't change with updates behind your back. I'm sure you'll understand by now what I'm pointing at with recent MS practices.
This is what is causing the issues that the OP is about: new hardware (both x86 and ARM) comes with new features in power management and virtualization (i.e. connected standby) which Windows needs to abstract and they find it too hard/risky to backport the OS and driver changes to every device now running Windows 7.
They ask about it in the welcome wizard. Once the preference is set, it is not changed behind your backs by updates.
Microsoft plays catch up, and then everyone loses their minds about it.
What? I use Little Snitch to monitor all outgoing connections. I don't see a log of outgoing connections to Apple outside my iCloud account, location services (which has to be enabled explicitly during the installation) and Spotlight searches. And these are easy to disable. In fact, Preferences App has the obvious Security & Privacy prefpane:
If userland: Little Snitch loads a kernel extension and monitors every userland process.
If kernel: The XNU kernel is open source, so you can check that it doesn't work around Little Snitch and Apple doesn't do telemetry in the kernel (which would be... weird).
Of course, theoretically, Apple could work around this using e.g. malicious code in the EFI firmware. But I am pretty sure that someone would've already found this by monitoring at a router.