Windows 10: Build 10240 - Any expiry on ACTIVATED versions??

@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.

 

No expiration date that you know of? Kudos for going to all that bother but I still don't see the point, or what it proves? Others have reinstalled with keys obtained via upgrade installs, on that same hardware. That's nothing new. I'm not trying to be a smart ass etc, just don't see the point with the official release only days away.

 

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 *Party 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.

This is not a step by step instruction-just what I was planning to do because of the way I have my partitions setup.

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.

 

slmgr -dlv runs for me. I'm also seeing that same partial key. 10240 10 Pro here, upgraded from Windows 7 OEM. The other two commands you posted got me the same screen shots you posted, so I'm not going to bother reposting them.

 

Running winver shows is licensed to Kerry. It was an upgrade from Windows 7 so maybe that is why. If I run winver on my Windows 8.1 desktop PC it shows my Microsoft Account email address.

 

When I run winver I get my MSA. And I upgraded 10240 over 8.1. OH and I'm still in the insider program.

 

I'm still in the insider too. Windows 7 uses a local account only, and the first time I logged into 10074 it was with a local account. I wasn't prompted to switch, but did eventually switch to my Microsoft Account. On all my PC's it's C:\Users\Kerry.

 

Ok, thanks - I was commenting on your steps you listed in post# 76

Suggesting that you might be able to skip the step highlighted above. I don't know if this will work or not, but suspect that it might. Curiosity is all - if you feel like testing that (skipping the restore image to Win7 step), great - otherwise I'll try it when I get around to upgrading in 2016.

 

Thanks Kerry,

Hmmmm, maybe your Win7 OEM upgraded to Win10 versus my clean Win8.1 install mutli-booting with Win10 (two releases).

I think we're on the same page - this isn't anything to be resolved or researched - interesting academically considering the timeframe, but ....

I also think most of the folks participating in the discussion already plan to create a system image before upgrading. Any anomalies presented by the upgrade can easily be ironed out by restoring the image of the previous qualifying OS.

Groze posted that users aren't certain when they'll actually get Win10 - that's a good point. I'm going to put August 20th out there, just because that's when the MS stores have an event (per the facebook page). There will be launch day events with special appearances to get the ball rolling and keep the excitement high. But when I built the table listing the events I almost missed two dates 6 August and 20 August, thinking all events were on launch day - really need to pay attention)

This was fun!

 

Read this:
Insiders will get WIn10 on the 29th.. not Aug 20th. *Wink
Windows 10: What to expect on July 29 | PCWorld

 

I was going to do that for my benefit because of the way I have my partitions setup and to be legal with the EULA that isn't a step by step instruction. Right now I am waiting to see if build 10240 is actually the release build and yes I know at lot of people don't believe 10240 is the release version. I still may need to do that if build 10240 is not the release version.

 

It all becomes mute in a couple of days anyway. RTM or not RTM, it won't matter after the 29th anyway. IMHO, there is absolutely nothing to be gained by opting out of the insider program before that date. I will *Haha if those that did end up with Watermarks in the lower left after the 29th. *Wink

 

Really.. just stay calm. There is zero reason to opt out of the insider program now. Stay in it for a while and if anyone wants,, then opt out. Insiders will get the update on the 29th. *Smile Windows 10: What to expect on July 29 | PCWorld

**And read new sig..