Build 10240 - Any expiry on ACTIVATED versions??

alphanumeric said:

No, if your on the Public release and not running an Insider build, you get the updates and upgrades after they have been tested by insiders. Insider build, beta, public release, non beta.

I thought is was going to be something like this
Insider Branch-Fast Ring
Insider Branch-Slow Ring
Current Branch-Forced updates but you delay the restarting for a few hours
Business Branch-Windows 10 pro You can choose forced update or business branch and can delay updates up to 4 or 8 months
Enterprise Branch-(Not eligible for free upgrade) can delay updates indefinitely.

However, some security will always get installed. Also, you can technically delay updates if you use only wi-fi to connect to the internet. It won't delay security updates though. You need to change your computer/device to metered connection.

@alphanumeric and others

I completed my test and it is a success

Here is what I did.
Upgraded from windows 7 sp1 to previous build, then upgrade to windows 10240 build.
Choose stop receiving the insiders build, it did one reboot
Got the key from showkey
Then I left insider program via insider website
Remove all device except the 10240 build from my account
Created an ISO from ESD build 10240 using Kari instructions
Created a bootable usb disk using windows 7 usb boot creator.
Did some partitioning

Installed Windows 10 and it took the key without issue but it was a little slow checking it. It took about 30 minutes to install. It activated with no expiration date at all. I also logged into my Microsoft account. I also opted out of most privacy setting except for location for the apps.

groze said:

Rocky got me curious. This feels like the official release not saying it is. I was surprised as well that it activated and had no expiration date. I am still holding off on till I find other find out more info on or after the 29th before doing something else. I know this may not be the final build.

I was originally planning to delete all devices and remove computers associated with one drive.

Get the windows 10 app
Let windows update, update to windows 10 when it is ready
Then make an usb install
Then restore image to windows 7
Then do a clean install of windows 10
Then change my windows 7 oem to retail version

I still may need to do this if 10240 build isn't the release version. Right now I am going to mess around with 10 and do some testing to see if my software will install.

Soooo, I decided to dig a little bit and found a few interesting things.

Run: [ winver ]

Shows that Win10 is licensed to Bill - > that's a local account only on my Win8.1 install, so my supposition that Win10 looked for a qualifying install might be correct.

---

Elevated Command prompt:
slmgr -dli

Shows RETAIL channel, but also partially shows the Preview key. You might expect it to show your qualifying OS key if it were a true retail release.

---

Elevated Command prompt:
slmgr -dlv

This is interesting ... I have Win8.1 Pro and the Win10 edition is also Pro.

When I ran the command given in the dialog window, it returned:

Elevated Command prompt:
slui 0x2a 0x8007054B

My install was activated by normal means - auto activation after install. I did not enter any key, it figured it out.
I did not phone activate - I wasn't that curious.

Adding the all parameter to the following slimgr commands gives some interesting results too - all report that the license is unused and UNLICENSED.

Elevated Command prompt:
slmgr -dli all

Elevated Command prompt:
slmgr -dlv all (no pic - just more detail for the above image)

---

At any rate, the channel is Retail but the license is Insider Preview.

MS had to test real world scenarios in some fashion and the license is the controlling factor. This mish-mash of Retail, Activated, Unlicensed, Licensed to, etc is just further evidence that 10.0.240 is NOT production code. It is very close, but there have been 4 security WU and a few iterations of the Store app (as well as the built-in apps, but they're secondary as far as I'm concerned.)

That's as far as I'm going with this - I did find some interesting, albeit not very useful, information.

---

In your test scenario, you said that you were going to restore the Win7 image - want to try a clean install without a base OS? If the upgrade registered your device, then you probably don't need to put Win7 back on the machine - but that's just a guess - it shouldn't take long to test that ... either a clean Win10 install after upgrade will punt, or the license information has been written to the firmware and Win10 will install and activate.

I asking you about this since you'll probably do this way before I do and it might benefit others to know if they have to go through the process you described or if they can skip the restore image step and just do the Win10 clean install after WU upgrade.

Thanks,

Bill

@Slartybart


If I understanding what you are asking me is if I did a clean install of 10 10240 the answers is yes but the image of 10240 was built from an image that was originally upgrade from windows 7 sp1. I originally upgraded from windows 7 sp 1 to build 10xxx then to build 10240, then created an iso image from an esd image using Kari instructions.

Here is an image of what I posted in another thread.