This isn't that difficult.
There will be, but are not yet, two branches
1) Insider Program
2) Released product
Regardless of the terminology RTM (MS will never call it that - opting for their preferred obscure Current Branch) - 10.0.240 is NOT a Released product. We've already received one rollup and a few other updates - this is the way it's going to be moving forward.
If you have 10.0.240 installed - it is a Preview release downloaded though the TH1 branch. I don't know what the production branch will be called, but it won't be TH1. MS has entries in the registry that differentiate between a production system and a Preview system.
You're either running production code (free upgrade) or development code (Insider Preview). What's the difference?
- Development code is not fully tested and has a high probability of containing bugs - perhaps destructive and catastrophic bugs.
Insider branches will expire and eventually stop booting.
This expiration built into the branch code and might not be visible to the end user, but it is documented.
- Production code has been tested and while there will always be bugs, they probably won't trash your system - worse case is what we've all experienced in all Windows releases. I don't recall catastrophic bugs in past Windows releases - poor design or implementation, yes, but nothing earth shattering.
Production branches will never expire once activated.
I see no reason that users will NOT be able to run both branches in a multi-boot or VM environment. They will be distinct with EULA and licenses.
10.0.240 has been sent to manufactures according to press sites. I would say 10.0.240 is a released product. Manufactures wouldn't put a build on computers that would expire. As I said before Rocky didn't get expiration date. slmgr /dlv didn't show Rocky having an expiration date. Where is the documentation that 10.0.240 expires? I am not talking about a website. I am talking on the computer itself. It suppose to give a date if it expires. It doesn't.
The next lot of changes (or perhaps any changes from now on) will essentially be just "delta" changes -- nothing significant so the chances of your computer not working on the next upgrade if you are on the insider builds will be very small indeed - and if you aren't running a lot of complex software or oodles of unusual hardware the chances are you won't notice any difference.
It seems to me that with care (and TAKE backups) you could legitimately run Windows 10 for FREE on the Insider loop until such times as Ms ends the program.
I'm still an insider. When updating to 10240 from 10166 something screwed up big-time and messed up the OS so I found the 10240 iso and did a clean install. Then found out all the keys were shut down so I used the process that was posted and is now removed. This is what I get:
Whether slmgr is a valid way to check anything any more is anyone's guess. The whole licensing structure has changed - see what you get when you run MGAdiag - I can't make sense of it anymore.
At this stage, I'm not willing to dig any deeper - you can sort though the registry, comparing a previous Insider release to the 240 release if it's that important to you.
Where is it supposed to give you an expiry date?
If I were to venture a guess, 10.0.240 looked at the hard drive for a qualifying OS and used the key it found to anchor 240. Yes it can see drives even if they're not given a drive letter.
You keep pointing to what Rocky did and now ask me to provide proof of an expiry - how 'bout you do the digging? You do seem capable enough.
A production release is available directly from the OEM, in Stores, or on a retail website.
Can you find Windows 10 anywhere other than the Insider program, not from a converted ESD and available today 23 July 2015?
No, then it's not a product yet.
Microsoft could issue one patch/update and give you your expiry date. If it isn't already coded in. One easy way to do it is to blacklist all the insider 10240 keys from activation. Some people just see what they want to see.