Windows 10: Will insiders be able to disable the so called keylogger once.....

<sigh> I, too, thought we had put this "keylogger" debate to rest -- and apparently, we have not.

What everyone appears to be missing is what is at the very core of this debate -- your working definition of "keylogger"!

One definition I've found is from TechTerms.com and it says:

There are three parts to this definition:
1) recording keystrokes
2) Keeping a log of all keys pressed
3) Sending the information over a network

There's no question about 1) and 3) -- The EULA grants permission to record keystrokes and permission to upload that information to Microsoft. The debate is really centered around the "all" in 2) -- and this is where feelings run high.

Let's say that you upgraded your Internet service from your ISP and a condition of that was to allow them to install a webcam in your living room -- pointed at your TV -- to record what shows you watch -- to gather "telemetry data to help improve their programming". And, let's say they disabled the red light on the camera, so you don't know when it is recording. Most folks I know, upon seeing that camera, would say "I'm not doing anything in here I don't wanted recorded!".

We have given MS permission to put a "camera" (of sorts) inside Win10TP. Is it recording ALL our keystrokes? We don't KNOW. Is it recording ALL the time the PC is on? We don't KNOW. Do these recording include passwords, or logins, or banking transactions? We don't KNOW. We can only guess -- and that is what we are ALL doing -- guessing.

As to the "keystroke capturing" continuing after RTM, that depends on whether or not you continue your involvement in the Insider program. Unless MS then comes out with a new EULA, one that specifically excludes "keystroke capturing", then the presumption is that it will continue.

 

Unfortunately this issue will never be put to rest. Someone will always bring it up and get worried that MS is going to hack them. Like I say each time. Worry about real hackers and not MS.

 

Bill, when setting up my dual Boot system, I had an option to name the second partition. Could you name it something like Windows 10 the Second or something like that? And would it work?

 

I'm dual booting two Windows 10 TPs without any problems.

 

How many of us actually read the full license for everything on our computers? How many of us know exactly what we grant the manufacturer of that whiz-bang program we absolutely gotta have? And finally, how many of us actually read the Microsoft license?

If I don't want to abide by the license agreement, I don't install the software. It's as simple as that. And, I'm with you; I need to worry about the hackers instead of Microsoft.

 

Sure, I can name the volume, but that isn't the issue I experienced.

I wanted to set up a 2nd Win8.1 as a test bed - I only have one license. After failing a number of times I followed a trail of links through the muck and mire of MS licensing where I found a one clause statement saying you can do this but you have to share the cores. The number 3 is part of that memory - 3 multi-boots? I don't recall.

I tried to find the clause to use in a citation, but I failed to find it again .... *cry *Tongue

I'll image my Win8.1 system before upgrading to Win10, go though the upgrade process, then create Win10 install media using the ISO. Reconfigure the disk and clean install all of the OSes I use or test as a multi-boot system.

The question really relates to the previous OS license - is it still valid? I think it would have to be, otherwise a lot of happy MS customers won't be so happy any more - even taking into account that it is a FREE upgrade to Win10

If I have to sacrifice the previous OS license to get the free upgrade, I'll pass and purchase retail Win10. That solves the key issue for me.

Thanks

 

The insider EULA is different from the Windows EULA which is different from the Office EULA ... MS is trying to simplify all EULAs and write them in plain language, but the lawyers ....

Mr E bought up a good point about capturing typing (I think it was in reference to Office) - it is done to improve spell checking.

Mark Phelps nailed it when he said We have given MS permission... - that's the legal end of it.

Words such as may and might have two different meanings
may - allow You may leave the table
might - possibly I might go to the game tomorrow

When the clause says "Microsoft may collect ..." and you accept the agreement, you are allowing MS to collect ... it doesn't necessarily mean they do collect or might collect. You are only authorizing MS to collect if there is a need. In the TP case, we know they are collecting data - and that's a good thing. In the case of a production release - WER is a good example.

All of the wording is more of a legal CYA than a threat to our privacy. That doesn't mean we should be complacent about privacy though.

Bill's 2¢s