Microsoft’s telemetry U-turn?

I'll believe it when I see it
Which you probably won't, since it's a LTSB-only concession^Hfeature.

What I am saying is that if Microsoft puts in a switch that says "Off" and yet there's still some data being sent to Microsoft because of the time service or Windows Update, some people will freak the fuck out and say that Microsoft is "lying and/or spying". Indeed that's already happen with the Enterprise version that had an "Off" setting but that really doesn't disable able all telemetry because some of it is built into tools that have it baked in and it can't be turned off with turning off those tools. And BTW, those tools did the same thing in Windows 7.
You know, a whole lot of the whinging about telemetry etc could be easily mitigated if Microsoft took three simple steps:
1) Publish (and update) exactly what information is collected by each service, when it is collected, and what is done with that information. What IPs/domains are used for what, etc. For example "Telemetry Service X communicates with IP addresses A, B, and C. Each month, it sends a list of the hardware in your computer, along with driver information (version, vendor). We use this information to make sure Windows is stable on the most common hardware." or something along those lines.
2) Provide controls to allow users to actually turn it off, again with proper instructions so that those who want to, can.
3) Provide useful information with Windows Updates. No more "this KB resolves issues with Windows 7" with zero specifics.

None of these things are affected by the complexity of the software. You have toggles that set values in the registry, the software checks those values and sends/doesn't send data. Simple.

People will be a lot less upset if given the opportunity to understand the why, and the issue goes away almost entirely if you allow people to opt out. Refusing to provide that information, and forcing it upon people, is going to have a negative effect, regardless of your intentions.
Cortana got an update about a month ago that allows for category views. To disable that you HAVE to disable Cortana at the firewall. And that's well documented.
And why can't we simply have a setting to prevent Cortana from updating itself? If you block it at the firewall, and it doesn't mess up the rest of Windows, then why make people jump through those extra hoops? You're right--this may indeed be a non-issue*, but it's yet another example of MS turning a deaf ear to its users.

* --this assumes that there are no buggy updates, that it doesn't suck up some poor user's mobile data, etc. None of these assumptions are reliable at this point.
 
You know, a whole lot of the whinging about telemetry etc could be easily mitigated if Microsoft took three simple steps:
1) Publish (and update) exactly what information is collected by each service, when it is collected, and what is done with that information. What IPs/domains are used for what, etc. For example "Telemetry Service X communicates with IP addresses A, B, and C. Each month, it sends a list of the hardware in your computer, along with driver information (version, vendor). We use this information to make sure Windows is stable on the most common hardware." or something along those lines.
2) Provide controls to allow users to actually turn it off, again with proper instructions so that those who want to, can.
3) Provide useful information with Windows Updates. No more "this KB resolves issues with Windows 7" with zero specifics.

Do you honestly think this is simple? Something that could be digested by anyone that uses a PC? It obviously isn't. Again, I think the only way to do it is to log it and show people what's going on. That's not that simple either, but I don't think that Internet experts are of much help here. The closer that it can be explained without help, the better.


And why can't we simply have a setting to prevent Cortana from updating itself? If you block it at the firewall, and it doesn't mess up the rest of Windows, then why make people jump through those extra hoops? You're right--this may indeed be a non-issue*, but it's yet another example of MS turning a deaf ear to its users.

* --this assumes that there are no buggy updates, that it doesn't suck up some poor user's mobile data, etc. None of these assumptions are reliable at this point.

I'm not saying there can't be a UI interface to do this. Indeed UI's and group policies do a lot of things. But at the same time, there's a LOT of extremely cool things Cortana can do if you actually use it. Part of the problem for Microsoft and indeed Windows is if you provide a switch to turn everything off, you then end up in a situation where you'll have people thinking "I can talk to my phone, my Echo and my car. Fuck Windows sucks because it's so far behind the latest stuff." And oh by the way it can but you some nut bag on the Internet tell you to turn it off. Cortana even tracks packages, just put in the tracking number, works across all Windows 10 devices and I think even iOS and Android with Cortana installed.

I'm really not trying to defend Microsoft here. But everyday I see people do stuff like this on their phones and they don't bat an eyelash. But here were are talking about adding the complex documentation about concepts most won't understand, turning off features that millions are taking for granted on other platforms. But Aero Glass and Windows Media Center with a CableCard, now that's the future! Yeah, there's some serious generational issues here that will push Windows into consumer irrelevancy. More and more switches and complex documents and features for cable TV? No, no, no.

It's one thing for Microsoft not to listen to customers. It's another for it not to listen to customers that are so far out of sync with mainstream computing that they actively avoid using any and all social media.
 
Do you honestly think this is simple? Something that could be digested by anyone that uses a PC? It obviously isn't. Again, I think the only way to do it is to log it and show people what's going on. That's not that simple either, but I don't think that Internet experts are of much help here. The closer that it can be explained without help, the better.
Nice strawman--I didn't say that it has to be useful for "anyone that uses a PC." Again, for most users, the defaults are fine.

And yes, publishing the information is simple. Providing useful descriptions of updates is simple. Adding a bunch of toggles is simple. It's a matter of priorities. And microsoft's priorities appear to be fairly straightforward: save development costs by forcing updates, improve feedback via telemetry, increase value to some customers via additional functionality (like Cortana), and increase revenue via selling user information. Giving users granular control over their computers is obviously not a priority.

Microsoft have specifically and intentionally added various functionality that sends data to them. It didn't happen by accident. They just need to add a step to patch and feature development, to properly document for power users and administrators what the software is doing.


... Part of the problem for Microsoft and indeed Windows is if you provide a switch to turn everything off, you then end up in a situation where you'll have people thinking "I can talk to my phone, my Echo and my car. Fuck Windows sucks because it's so far behind the latest stuff."
Ah, so forcing it in users' faces is the right approach then! /s

I'm really not trying to defend Microsoft here.
....
so far out of sync with mainstream computing that they actively avoid using any and all social media.

1) BWAHAHAHAHAHAHAHA! I don't think I've ever seen a post from you where you were NOT defending Microsoft.
2) This is called equivocation, and is a well-documented logical fallacy. It's also a fine example of reductio ad absurdum, another well-understood logical fallacy. Which means your statement about "so far out of sync...." doesn't even merit a response.

You know what? Logical fallacies are fun! Let's go the other direction, shall we? "It's one thing to give users the ability to search the web from their desktop. It's another to be so worried about your long-term profitability that you force users to install whatever software you want them to, and remove any software that you don't think should be on their computer!" Oh, wait, that's not reductio ad absurdum, that's actually what Microsoft are doing.
 
Hmm my install must be broken. It isn't forcing me to install software and hasn't removed anything from my system.

I better email Gordon Kelly and ask him what's the matter.
 
I was surprised by that sentence, because I was under the impression that Enterprise users could already do that.

The ability to disable the telemetry and other bullshit is only for Enterprise LTSB (Long-Term Servicing Branch), a very specific and rather expensive version of Enterprise only available under some pretty specific licensing by comparison to the typical and more common basic Enterprise that most people are aware of.
 
Nice strawman--I didn't say that it has to be useful for "anyone that uses a PC." Again, for most users, the defaults are fine.

Many people have argue that the defaults are NOT fine.

And yes, publishing the information is simple. Providing useful descriptions of updates is simple. Adding a bunch of toggles is simple.

Describing the high level aspects of an update is simple. Adding a bunch of toggles? To control every possible piece of data that may be between a Windows PC and Microsoft? And why it's sent? That's not anything near simple. "Flip this toggle if you don't want to sync time." "Flip this toggle if you don't want NetBIOS services." "Flip this toggle if you don't want Windows to share malware infections." "Flip this toggle if you don't want the Network icon to display yellow if Windows can't connect to the Internet." "Flip this toggle is you don't want Windows Update to send anything back to Microsoft about how an update worked." "Flip this toggle if you don't want Cortana to know anything about contacts that you have stored years ago in Gmail or Hotmail or any other service." "Flip this toggle if you'd like to use voice control on your PC but don't want any information shared with Microsoft to possibly improve the experience."

It will go on and on and on and on and on. Again, so called experts don't even know what's in the documentation today. The Microsoft Privacy agreement for it's cross platform services is CONSTANTLY being linked as the Windows 10 privacy agreement. If you don't understand just how egregiously bad that mistake is then sure. Adding a bunch of toggles is simple.


Do you have any idea what kind of havoc that can cause?

Again, to fully shut off Windows clients from Microsoft means 1990's computing. Updates and malware defense, that's totally up to a user. Warnings of possible malware, again, that's totally up to the user. It means adding a lot of burden to the user to manage stuff. And remember, that's a lot of the argument here. "Microsoft is hiding stuff from me." That's a true statement. Because in a world full of smartphones and smart TV and smartwatches and everything smart, the thing that many people are arguing for is control of tons and tons of detail.

It's a matter of priorities. And microsoft's priorities appear to be fairly straightforward: save development costs by forcing updates, improve feedback via telemetry, increase value to some customers via additional functionality (like Cortana), and increase revenue via selling user information. Giving users granular control over their computers is obviously not a priority.

This is a complete lack of understanding of how code works. You can not and must not make functional changes to code that introduce new dependencies out of order because it doesn't work. It's just that simple. It's like many never heard of code branching and why Windows 10 has two code branches, like many Linux distros.

Microsoft have specifically and intentionally added various functionality that sends data to them. It didn't happen by accident. They just need to add a step to patch and feature development, to properly document for power users and administrators what the software is doing.

Of course all of this didn't happen by accident. It was intentional to allow Windows on the desktop share and leverage data like phones. To allow one to do things as easily as track a package on a Windows laptop, tablet, desktop and phone as an iOS or Android device.

1) BWAHAHAHAHAHAHAHA! I don't think I've ever seen a post from you where you were NOT defending Microsoft.
2) This is called equivocation, and is a well-documented logical fallacy. It's also a fine example of reductio ad absurdum, another well-understood logical fallacy. Which means your statement about "so far out of sync...." doesn't even merit a response.

You know what? Logical fallacies are fun! Let's go the other direction, shall we? "It's one thing to give users the ability to search the web from their desktop. It's another to be so worried about your long-term profitability that you force users to install whatever software you want them to, and remove any software that you don't think should be on their computer!" Oh, wait, that's not reductio ad absurdum, that's actually what Microsoft are doing.

So it's a fallacy to think that people that are using devices that do things easily will wonder why they are so much more difficult using Windows?
 
There is one logic bomb in here that people do not seem to grasp. Prior to 10, Microsoft did not know how long you had been using the operating system. Frankly, it is none of their business, yet somehow the people will let 10 get away with redrum.
 
Well, let's see how much you can turn off in Win 10 Enterprise. For now sticking with 8.1 Enterprise.
 
Hmm my install must be broken. It isn't forcing me to install software and hasn't removed anything from my system.

I better email Gordon Kelly and ask him what's the matter.

Couple of months ago a big Windows update did remove CPU-Z from my computer, and did so with a clear message. Of course you could reinstall it (which I did) and it does not scan and actively remove stuff 24/7 but whenever a big update comes it obviously does scan the computer for programs it deems... unsafe? Not welcome? CCleaner (another program that got removed from computers) I can somewhat understand because it can cause severe damage on wrong hands but I dont know what MS was thinking when it blacklisted CPU-Z on that update.

And for people who had removed Onedrive, Cortana and such the update also restored them, as well as restored the privacy settings we had altered back to their loose-ass defaults. Just because you never had this happen dont think the issue does not exist. This was a well documented issue when it happened.
 
You know in the real 'normal' world, not one customer who wants to upgrade to 10 (and there have been many) has bothered to mention the whole telemetry thing.
 
I have very limited time in windows 10 and all from working on clients laptops trying to find thier lost crap. I just dug out an older laptop and will get Win10 installed this weekend so that I have something new to argue about or at least to learn it better.

I almost do not care any more if they spy on me, I am just about ready to put ps3 eye cams in every room of my house so they can watch all the stuff I do. There is no excitement to watch, no money to grab. The most exciting thing going on is the goat got out again and texting the daughter telling her to get her butt home before 11pm. The government is more concerned with sending our cash to lybia than protecting the personal accounts of its consumer citizens with hundreds of thousands get stolen every week.
 
Couple of months ago a big Windows update did remove CPU-Z from my computer, and did so with a clear message. Of course you could reinstall it (which I did) and it does not scan and actively remove stuff 24/7 but whenever a big update comes it obviously does scan the computer for programs it deems... unsafe? Not welcome? CCleaner (another program that got removed from computers) I can somewhat understand because it can cause severe damage on wrong hands but I dont know what MS was thinking when it blacklisted CPU-Z on that update.

And for people who had removed Onedrive, Cortana and such the update also restored them, as well as restored the privacy settings we had altered back to their loose-ass defaults. Just because you never had this happen dont think the issue does not exist. This was a well documented issue when it happened.

CPU-Z accesses hardware and has been known to cause a BSOD. (Coretemp also did the same and really screwed things up.) To directly quote you: "Just because you never had this happen dont think the issue does not exist. This was a well documented issue when it happened."
 
I normally ignore Gordon's tin-foil hat inspired articles, but I can agree with him on one point. If you include privacy controls that really do absolutely nothing, I can't trust you. That's what Microsoft did with Windows 10.
 
If you include privacy controls that really do absolutely nothing, I can't trust you. That's what Microsoft did with Windows 10.

Could you please clarify which privacy controls do absolutely nothing and how that's been confirmed?
 
I was surprised by that sentence, because I was under the impression that Enterprise users could already do that.


Enterprise users/companies large enough will block all out going traffic anyways and do updates via systems management center or the like.

Smaller companies will want a version of W10 that is HIPPA/whatever compliant which means no data going out that isn't well documented and can be turned off.
 
I doubt MS will deliver on that. The ability to track users has many benefits inside and "outside" Microsoft.

Yep, as expected MS doesn't appear to have any plans of changing privacy settings (which basically don't even work anyways): Microsoft has no plans to change Windows 10 consumer privacy settings

Rebutting the unsourced Forbes article:

article said:
My sources tell me there are no such plans and that there is no such statement. Executives believe that existing privacy controls are reasonable for consumers and there's no need for a drastic change. A change in telemetry options for enterprise customers was announced last fall and is already included in Windows 10 version 1511.
 
CPU-Z accesses hardware and has been known to cause a BSOD. (Coretemp also did the same and really screwed things up.) To directly quote you: "Just because you never had this happen dont think the issue does not exist. This was a well documented issue when it happened."

Been using CPU-Z for years and it has *never* caused a BSOD. Oh no, the sky is falling!!!
 
Been using CPU-Z for years and it has *never* caused a BSOD. Oh no, the sky is falling!!!

Reread the part of that post of yours that I quoted, perhaps you will then get it? Nah, does not fit what you are trying to say. Do as you say, not as you do or type, eh? :rolleyes:
 
There is one logic bomb in here that people do not seem to grasp. Prior to 10, Microsoft did not know how long you had been using the operating system. Frankly, it is none of their business, yet somehow the people will let 10 get away with redrum.

They didn't? Assuming you weren't pirating the OS/using a volume license, I always assumed they knew exactly when your OS was installed/activated.
 
Reread the part of that post of yours that I quoted, perhaps you will then get it? Nah, does not fit what you are trying to say. Do as you say, not as you do or type, eh? :rolleyes:

Anyone can use portable versions of CPU-Z or CCleaner and Microsoft won't uninstall it because there is no uninstaller registered so they are not saving anyone from the bogey man even if they think they are. But of course Microsoft allowed crapware like Starforce DRM to infect our machines for years and never said squat about it. And now all of a sudden I am supposed to believe they are looking out for me by uninstalling safe programs I've been using happily forever with no issues? LOL

The only reason I can see why they would uninstall CCleaner is because they can't snoop our history of we delete it with CCleaner.
 
Anyone can use portable versions of CPU-Z or CCleaner and Microsoft won't uninstall it because there is no uninstaller registered so they are not saving anyone from the bogey man even if they think they are.

10 updates by keeping a copy of the existing OS and then attempts to move all the apps that it can over to a clean install. It never uninstalled anything, it may have not moved everything over however.
 
10 updates by keeping a copy of the existing OS and then attempts to move all the apps that it can over to a clean install. It never uninstalled anything, it may have not moved everything over however.

Maza was the one who brought it up, and he implies it's a patch tuesday patch, not updating 7/8.x to 10
 
CPU-Z accesses hardware and has been known to cause a BSOD. (Coretemp also did the same and really screwed things up.) To directly quote you: "Just because you never had this happen dont think the issue does not exist. This was a well documented issue when it happened."

Well of course it accesses hardware, thats why it exist. To read whats in there basically. BSOD is not exactly a good reason to delete the program because 1. its not something you automatically run at the start of the computer so there is no risk of putting computer illiterates into a BSOD loop they cant get out of and 2. MS would have to delete helluva lot more programs if a rare BSOD bug that can be patched marks the program for deletion.

And then there is the fact that what programs I install into my computer is bloody my business. If they break my system then its fricking my problem, not theirs. Whats next? Delete overclocking programs because a dumb person can fry their rig with one? I think I got my point across here.
 
Maza was the one who brought it up, and he implies it's a patch tuesday patch, not updating 7/8.x to 10

Yes, it was the latest big Release Build update that did this, not update from 7/8 to 10.
 
Well of course it accesses hardware, thats why it exist. To read whats in there basically. BSOD is not exactly a good reason to delete the program because 1. its not something you automatically run at the start of the computer so there is no risk of putting computer illiterates into a BSOD loop they cant get out of and 2. MS would have to delete helluva lot more programs if a rare BSOD bug that can be patched marks the program for deletion.

And then there is the fact that what programs I install into my computer is bloody my business. If they break my system then its fricking my problem, not theirs. Whats next? Delete overclocking programs because a dumb person can fry their rig with one? I think I got my point across here.

You cannot honestly believe what you just wrote. They removed a version of the program that was found to cause serious issues. The fact is, rare does not begin to describe it but then again, I am not sure whether I should laugh when something goes wrong on your machine or be sad because you were warned and let it happen anyways.

Oh well, if you do not like it, use something else. Tough luck dude, people have been asking for years for the OS to become more stable. Now that they are doing just that, you whine about that. :rolleyes:
 
You cannot honestly believe what you just wrote. They removed a version of the program that was found to cause serious issues. The fact is, rare does not begin to describe it but then again, I am not sure whether I should laugh when something goes wrong on your machine or be sad because you were warned and let it happen anyways.

Oh well, if you do not like it, use something else. Tough luck dude, people have been asking for years for the OS to become more stable. Now that they are doing just that, you whine about that. :rolleyes:


Yes I do believe what I wrote and I do not really understand your thought process. Was it just a single specific version of CPU-Z that was removed that caused problems or all? Honest question because I do not know. Anyway, again if it caused BSOD it can only do so if you start the program yourself. If that happens then its CPU-Z developers problem to fix the bug. MS removing the program is a nuclear solution to a problem that is not even their business! It has nothing to do with the stability of the OS, the program you ran just had a shitty code and messed things up so MS hands should be clean from all blame.

Laugh all you want, it makes no difference to me. If I break my machine I have only myself to blame. I do not want nor need "Big Brothers" help to cover things in soft pillows and round sharp edges so I wont hurt myself. Actually now that you mentioned warning, thats actually all they really should have done! Show a message that "Program X version yadayada is known to cause problems and its recommended to not use it until fixed etc etc...". Them removing the programs without users permission only helped to fuel the hatred towards Windows 10 which is already constantly under fire as you can see.
 
There was indeed a period when CoreTemp would cause a hard reboot on some of my Athlon II computers.
I stopped launching it. I observed that when I doubleclick the icon, everything becomes smurf blue. I didn't need forensic specialists for figuring that out.

Now, forced push installations will leave me having to run diagnostics to determine if my hardware is failing.

We already have stable operating systems. The only bluescreens I saw with Windows 7 were related to Windows Update.
Now, obviously to get this across I need to add: the bluescreens were related to incompatibilities between my hardware, their drivers and the Windows updates.

Remember the Windows Genuine Advantage tech that was pushed to XP systems?
Yeah, it caused a lot of people to actually care about getting genuine software.
But that does not justify the collateral damage caused by false positives and actual positives which were indirectly caused by shady salespeople selling counterfeit systems to win contracts. Not to mention flooded support phone lines.

I work with medical documentation, including some very sensitive data about therapy, history of domestic violence, disabilities.
If an audit comes by and starts oberving my network traffic, how will I explain myself?

At least with systems like XP you were given a choice to send data about an error to MS or not. Following the data protection act's recommendations (here in PL), I always declined.

If our accounting software fucks up, and I have to send the database over to the software company, I have to first establish a contract with that software vendor.
Something in the lines of 'I delegate the right to process data kept in the database for the purpose of correcting errors introduced by a fault in the software. The software vendor shall ensure all legal data protection recommendations are met during the repair process'.

So, yeah, I do need to know about what's actually in these little packets... it's sadly my job.
 
Could you please clarify which privacy controls do absolutely nothing and how that's been confirmed?
The built in controls that allow you you turn things off under Privacy. So maybe the phrase "absolutely nothing" was a little harsh but the point is Microsoft is trying to create an illusion you have choice over telemetry/privacy data. It was proven that you do not.
 
Back
Top