Stories
Slash Boxes
Comments

SoylentNews is people

posted by CoolHand on Thursday August 13 2015, @06:22PM   Printer-friendly
from the oh-that-microsoft dept.

Peter Bright at ArsTechnica reports:

Windows 10 uses the Internet a lot to support many of its features. The operating system also sports numerous knobs to twiddle that are supposed to disable most of these features, and the potentially privacy-compromising connections that go with them.

Unfortunately for privacy advocates, these controls don't appear to be sufficient to completely prevent the operating system from going online and communicating with Microsoft's servers.

For example, even with Cortana and searching the Web from the Start menu disabled, opening Start and typing will send a request to www.bing.com to request a file called threshold.appcache which appears to contain some Cortana information, even though Cortana is disabled. The request for this file appears to contain a random machine ID that persists across reboots.

Hairyfeet's contribution adds the following:

A Czech site went one further and did a traffic analysis on a default Windows 10 install, what did he find? Well it looks like the Win 10 Keylogger in the beta is still running with pretty much every keystroke, voice, and webcam data being sent to Microsoft even with Cortana disabled.

[Ed's Comment: The report about the Czech traffic analysis originally came from a newspaper and some comments doubt the veracity of this source.]


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by MrNemesis on Friday August 14 2015, @08:13AM

    by MrNemesis (1582) on Friday August 14 2015, @08:13AM (#222728)

    Thanks to the pointer for KB3050265 - looks like this'll fix WU gobbling ~2GB of RAM doing its scans.

    Apparently the reg key HKLM\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\[DWORD]DisableOSUpgrade=1 is enough to stop the GWX gubbins doing its stuff alone without the new WU client but I've not tested that yet. Similarly it appears I dodged a bullet by having domain-joined windows clients at home (thanks Samba 4 domain controller!) since that stops the GWX stuff from running as well.

    Sadly most users who have the "home premium" or equivalents won't have access to the group policy editor, and it seems that those of you with windows 7 home premium won't be able to upgrade to a pro or ultra license via "anytime upgrade" any more either; that now appears to be shut down.

    --
    "To paraphrase Nietzsche, I have looked into the abyss and been sick in it."
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2