New
#970
Really, instead of a "pretend" real license agreement on build 10240, It should have a EULA that explicitly shows the rights of Insider and non-insider users of the OS build, down to the expiry clause, and even the date, that the build will reach notification and will finally expire.
Well just to clarify something: When you do a clean install then you automatically are "logged out" of the insider programm. Doing this you will end up with a generic key.... So it does not make any sense, that you would get a new key after singing off of the insider program. But maybe something is going to change after the 29.07., who knows.
Exactly - normally EULA is determined by the key (OEM, Upgrade or whatever) it will be interesting to see how things will be handled going forward
I think the point is that as a non-MSA activated (Insider) install one would expect a key to tie up with the underlying activation, or so we would hope.
BTW: per my and groze's discussion... here's my Win10 OEM activation (obviously w/ fake key) - just a 'proof of concept...'
@Superfly
Is there anyway Rocky could get the updates EULAs/licenses agreement he agreed to. It would be interesting to read it here.
Rocky if you do find what you agreed to put in a code bracket, it will make it easier to read if the EULAs/licenses agreement is very long. That is if you want to do it. :)
Oems manufactures can use slmgr to update and erase keys, so they could still even use build 10240 as RTM when insider may not be able to do that
I am also concerned about another issue a dell liaison/mod brought up on his/her blog. That upgrading from an Oem slp will be fine and will activate. The issue will be getting an windows 10 iso and doing a clean install after the upgrade. It may not activate. I guess time will tell.
Could I upgrade my Windows 7 now with The DVD of 10240?