New
#1
Will insiders be able to disable the so called keylogger once.....
Will insiders be able to disable the so called keylogger once the current insider build is upgraded to the insider rtm build?
Will insiders be able to disable the so called keylogger once.....
-
-
New #2
It's not much of a key logger even now but I guess it should be gone in final version definitely. I hope they keep feedback though.
-
New #3
Only the Insider releases have collection mechanisms (telemetry)- the RTM will not.
If you decide to continue in the Insider program and install a post-RTM Technical Preview, then only that machine will have the collection mechanisms active. It's how MS gathers good data on system usage and errors.
Those things are tied to the release, not the machine
RTM - no collection
TP - collection
Say you have Win10 Current Branch (CB) as your main OS and you want to test Win10 Technical Preview (TP) after RTM. I'm going to try setting up a dual boot. The main OS install will not have any telemetry, but the TP will have telemetry active. The two machines are isolated so there's no cross boundary telemetry.
It will be interesting to see how Win10 deals with dual booting two Win10s though. My understanding of Win8.1 dual booting Win8.1 is that you have to split cores (on a 4 core CPU, each instance gets 1, 2, or 3 of the cores - that's covered in the EULA). I'd rather not have to either my main system or my test system - it would be great if Win10 let's you use all 4 cores when booting to either install.
-
New #4
I never knew that you have split the cores when dual booting 8.1 with 8.1. I hope we don't have to split cores if we decided to dual boot Win10 RTM and Win10 TP. I enjoy testing and plan to continue.
-
-
New #6
I think he meant 2 instances of 8.1. I understand why in a VM. Don't get why you would have to in a dual boot system.
-
New #7
I have ran two instances of it, still had all 4 of my cores. Im going to install another 8.1 instance now to check this
Yep, here are two 8.1s ran, I still have all cores(4) on my cpu
Last edited by Dude; 13 Jun 2015 at 09:43.
-
New #8
I didn't think that sounded right. I always understood you could run as many as you had license's and space for. After all you can only run one instance at a time. Limits in VM's on memory and core's make sense.
-
-
-
New #10
Yes, that's what I meant. To clarify, it is the activation phase that complains about the license already being used on another machine. I was using one license - there is a clause that allows this.
When I first tried to set up a 2nd 8.1 dual boot with the 1st 8.1 I followed the breadcrumbs and read that a dual boot 8.1 with 8.1 can activate with 8.1 if you only use some of the cores.
You can of course dual boot if you have more than one license or just run a copy that is not activated. I'm not sure if you can use a VM to get around it - the license will still be checked and found to be already in use.
I just tried to find a citation, but only found dual booting with another OS or the cases I mentioned above. I found a few that looked familiar, but nothing I can use as a citation (error messages and reasons Windows would not activate).
The information might have been in a dialog window when it tried to activate or a link that I followed in that window.
I'm sure it's buried in one sentence in paragraph 24 on page 342 in some legalese document
edit: Right - sorry for the distraction - back to the thread topic....... data collection in the Technical Preview release.
Quote
Related Discussions
