Windows 10 Privacy - Keylogger


Recommended Posts

Previous versions of Windows used to gather data anonymously and I remember Microsoft explicitly stating that the data collected was anonymous and not used to identify you.

But now Microsoft has seen how much revenue can be generated by having every information of their users down to the last keystroke. They also mention that they will profile you based on your data. (I hate this bull$*** reason that we profile you to give you richer ads and improve our software)

Collecting data while under public preview is OK. But collecting it forever from unsuspecting gullible users is EVIL.

Now I put Microsoft under same category as Google and Apple. Just private info greedy corporations who will collect all the data they want. They will tell you that it would be used to improve customer experence. But in the end they will design their OS in such a way that every tap every click would be designed to extract money from you. The whole OS would transition itself into one giant pile of IAP.

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?

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?

The thing is in Group Policy Microsoft clearly states that telemetry can't be disabled even if set to 0 on Home and Pro versions. We are using a reg hack and batch file to disable it on those two editions. So whether reg hack overrides Microsoft's rules is to be seen.

Not being an Android user or iOS user it makes me wonder if they have similar things going on for Siri, Google Now and autocorrect dictionaries.

If the problem that its not easy to turn off - or is it that its there in the first place?

Problem is it's not easy to turn off.

This topic is now closed to further replies.
  • Posts

    • I think it depends on what you're looking for to do, and the time you have to spare. With my Dwarf 3, I easily spend 3-4 hour sessions; half an hour driving to an un-light polluted place, unpacking and setting up the smart scope + tripod for equatorial tracking, mucking around with settings, maybe shoot some calibration frames, spending a few hours shooting, merging with past photo sessions, etc. It's crazy how time flies and I often get home later than I expected. It's something I still need to set aside a good part of an evening to do, all in all. For one session, where you often need like four for best results when it comes to deep space objects. With practice, I can probably begin cutting time here but I think where smart scopes find their home is among people who love to shoot the night sky but don't have the spare time to go deep with the "navigator level" attunement to the night sky itself. Having said this, _if_ you have even more time to spend on this hobby, it will probably be even more rewarding to do it more by hand and learn the skies and the details of how it all works.
    • I misread the title and thought Teams itself would be redesigned. Imagine having this one as a native WinUI app.
    • Dell, HP PCs ran into endless reboot, BitLocker recovery loops but Windows 11 isn't to blame by Sayan Sen Last month Neowin reported on a major issue on Dell systems wherein a bug in its official support tool was leading to endless blue screen of death (BSOD) and restarts. Following our report, Dell officially acknowledged its SupportAssist-related crash issue, confirming that the culprit is not Microsoft's operating system but rather a faulty version of its own remediation software. In a newly published support advisory, Dell stated that version 5.5.16.0 of Dell SupportAssist Remediation and Alienware SupportAssist Remediation can trigger blue screen errors and unexpected system restarts. The company notes that the problematic component operates independently of the main SupportAssist application, meaning users should not remove the primary SupportAssist software when troubleshooting the issue. According to Dell, the crashes are linked specifically to the SupportAssist Remediation service, which is bundled with SupportAssist OS Recovery Tools, and as such it has since released an updated version, 5.5.16.1, which is said to resolve the problem. Affected users are advised to first verify whether version 5.5.16.0 is installed by checking the Installed Apps section in Windows Settings. If so, Dell recommends updating SupportAssist OS Recovery Tools through either SupportAssist's "Update Software" feature or Dell Command Update. Dell also advises users to back up important data before performing the update and to ensure systems remain connected to power throughout the installation process. If you are still having issues though make sure to report to the Dell support forum. As it turns out though Dell is not the only PC maker currently dealing with update-related headaches as HP is also facing a separate but probably equally frustrating issue involving recent Windows Secure Boot updates that were released with recent Windows 11 Patch Tuesdays. Similar to Dell, HP also put up its own support article where it explains the issue. The company says that affected devices could hit a brick wall when booting as they run into a BitLocker recovery loop after the April 2026 updates. The problem appears to affect systems wherein the new UEFI Secure Boot CA 2023 certificates fail to apply properly. As such affected users will find themselves entering their recovery key over and over again despite the system otherwise functioning normally. HP says such PCs should be updated to the latest available BIOS version and configured with the necessary Secure Boot certificates before installing Microsoft's Windows 11 Patch Tuesday updates. Systems that are already experiencing the problem may require BIOS configuration changes to restore normal boot behavior. Admins can find information regarding that in the support article here on HP's official website.
    • Getting further away from the artistic study of mental disease that was the first game... (which never needed any sequels to begin with) But I get it, a company has to make money. And the second was at least visually impressive, if not in any other way.
    • If its the devs fault you would think Unreal would help M$ take full advantage of Unreal and work with them to fix the performance issues. Otherwise they are catching unwarranted bad press.
  • Recent Achievements

    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
    • Dedicated
      Conjor earned a badge
      Dedicated
    • Week One Done
      Windows Guy earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      493
    2. 2
      PsYcHoKiLLa
      246
    3. 3
      Steven P.
      72
    4. 4
      +Edouard
      69
    5. 5
      neufuse
      68
  • Tell a friend

    Love Neowin? Tell a friend!