Hm? I think you missed my point; as far as data anonymity goes, that is irrelevant as it is not why I mentioned conspiracy territory. You previously wrote that "Even though the telemetry comes up as disabled, it is hard to prove that it has actually been disabled." Could this same statement be said about telemetry in previous versions of Windows? If so, at what point then, does one determine that telemetry actually has been disabled, if the user does not believe the operating system statement that it is disabled?
I still miss that Start menu. Too bad Windows 7 removed it for no apparent reason, even though it essentially had the same Start menu that Windows Vista does, and the latter allowed one to use either menu.
Thank heaven that Classic Shell allows one to use it, the Windows XP style, or the Windows 7 style, if preferred, and it also offers more options for all of these than their native counterparts.
Relevant: The Windows 95 User Interface: A Case Study in Usability EngineeringWindows 95 Product Guide
And this is the telemetry feature that I previously referred to. Are you again going to tell me that WER isn't disabled when the policies are active? In spite of all the evidence to the contrary?
I am tired of how you keep changing the subject when you are shown to be wrong. In the OP you referred to WER, then you switched to compatibility, then you switched to the telemetry feature, and then back to WER, and then back to compatibility, and now—for good measure, apparently—we are back at the telemetry feature.
I just showed you a screenshot where WER is disabled in Windows 10 because of Group Policy. There is no prompt to submit information about an application crash to Microsoft when WER is disabled. Security and Maintenance (formerly Action Center) reports that it will not check for solutions (i.e., submit information to Microsoft).
I am well aware of Microsoft's commitment to compatibility, but this does not have anything to do with what you previously stated:
That doesn't make any sense! How can you be referring to WER when you previously stated, "Check through the group policy view, it tells you the setting is ignored if you are not on windows 10 enterprise"? This is not the case with the WER policy that you just listed or even the WER policy that I previously posted.
Please refer to the entire post written above. That the policy you just posted applies only to Windows XP and Server 2003 is irrelevant; the one that I previously posted applies to Windows Vista and later.
You are apparently not referring to what I am speaking of. I am not referring to the telemetry feature unique to Windows 10, but to the Windows Error Reporting feature.
The very policies that pertain to WER include no mention of what you speak of and do allow you to disable WER. The terminology used in the screenshot that I previously posted is consistent with previous versions of Windows when WER is disabled; are you going to say that it is not truly disabled in those versions as well? If WER does not check for solutions, then why do you think that problems are submitted?
Observe what happens when an application crashes in Windows 10 when WER is disabled via Group Policy. There is no option to check for solutions and no mention of this.
Not a new feature. Possible since Windows Vista. Also, it is possible to disable Windows Error Reporting (e.g., through Group Policy or the Windows Registry). The options are just not exposed through the UI.
Windows Vista was not a joke. Rather, a major and powerful release.
Note also that options to collect personalization information are not new as similar services have existed in prior versions of Windows. The Tablet PC Input Panel, for example, could optionally send handwriting samples to Microsoft, and Windows Speech Recognition included an option for a user to allow it to analyze documents and e-mail to improve accuracy of the local recognizer, and as of Windows 7, includes an option to submit speech information to Microsoft to improve future versions of the feature.
That BitLocker can store backup keys in the cloud is not new; even Windows Vista could optionally backup BitLocker keys (and EFS recovery certificates) in a user's Digital Locker at Windows Marketplace if a user had the Secure Online Key Backup update installed.
I assume that if a user does not want BitLocker to automatically archive keys, that said user should use a local account and should not link to a Microsoft Account or OneDrive.