Checked versions supported in this version (Win Next Pre-Release as it's SKU's are named within)
Windows 8 and 8.1 are supported (including OEM) - this means those keys may well be accepted for installation (of the same edition ) - but not necessarily for activation, however, as Windows 8 keys were in Windows 8.1 specifically for activation, the latter could well a possibility.
In fact the generic key being used is a Windows 8.0 RC key:
NKJFK-GPHP7-G8C3J-P6JXR-HQRJR
Key Status : Valid
PID : 00137-10010-52743-AA144
Extended PID : 00000-01371-001-052743-00-7177-9600.0000-2742014
Activation ID : 507660dd-3fc4-4df2-81f5-b559467ad56b
Product Description : Win 8 RC Professional Retail
Edition ID : Professional
Part Number : [TH]X18-05552
Key Type : Retail
Eula Type : Retail
Group ID : 1371
All could change with the final release of course...
I have the same product key in the UK, it certainly works.
I was never asked for a key on 10 TP
If you have a Microsoft account you are sent a code via email, after IE failed and I reloaded afresh I had to use the product key.
Hi there
With the ENTERPRISE version some time after using it I did see an "Activate Windows" notification where the hall mark is a little time after I'd installed it. Running the command SLUI 3 and entering the Enterprise product preview key activated it OK. Note leave the space between SLUI and 3
Cheers
jimbo
You may have not been asked for a key, because the one referenced by Superfly is embedded in the .iso.I was never asked for a key on 10 TP
I also did not enter a Product Key, came up as Activated after the install finished 3 hours ago.
Mine only asked for a key the 1st time I installed it. After that, a code. Build 9841 or 9860, But once you change to a local account, you don`t have to verify anymore.
Just to clear up any confusion:
Setup uses the PID.txt file during the Windows PEconfiguration pass as soon as it is launched.
When installing Windows, setup.exe uses the following priority logic for product keys:
1. Answer file (Unattended file, EI.cfg, or PID.txt)
2. OA 3.0 product key in the BIOS/Firmware
3. Product key entry screen
Thus when running from WinREor within Windows, it will not access the PID.txt key in the /Sources folder.
FYI: Using EI.cfg and PID.txt
I'm guessing that's why my Enterprise install failed activation "after" upgrading to a newer build. I had to do a change product key. No such issues on a clean install, no code asked for and activated OK.
