Now on 29th or 28th at midnight I'll have to check and make sure my upgraded ISO will accept Clean install and stay activated, plese, please
You do have a point. Insiders may have started with a retail qualifying OS so it may be difficult for MS to exclude people from qualify for a POSSIBLE (as in speculation) retail PK exchange process just because they have already upgraded. I think when the GWX process kicks in then we may have a better idea how they will handle retail VS OEM-SLP/OEM-DM
Complication is the normal. With windows 10 normal has been thrown out the window. It's so difficult to believe it's simple.
It's been no different in the past, and the OEM version is already released to them which is basically what we're all running, they can't change much other than integrating the existing updates into the 29th release to save people downloading it then getting 10 updates straight away, that wouldn't be a good look
I don't get where this 29th de-activation paranoia comes from. They're not going to kick anyone off their free upgrade offer. If they wanted to stop the pirate upgrades, they would have done it by now.
They don't want to things goes like with win 8/8.1 when nobody wants to use this crap. So they give it for free and offer stuff from M$ store
I think people a misreading: At this point I am more concerned about Retail licence and the fact that I lose some rights by upgrading and my activation being associated with specific hardware. I have noticed a previously OEM-DM key gets upgraded to retail 3V66T. (OEM-DM was licenced to specific device). Upgrade a VL-MAK and you get VL-MAK *****. You can then change the PK to 3V66T and activate online as retail. (Loophole may be closed soon) All seems a bit of a mess. Anyway for those of you that have updated to the latest sub-build somebody check: CMD (Admin)-> slmgr -dlv and check if they have updated the Software Licencing Service from 10.0.10240.16384
[/QUOTE]CMD (Admin)-> slmgr -dlv and check if they have updated the Software Licencing Service from 10.0.10240.16384[/QUOTE] Thats what mine says.
I have everything MS has pushed by my sub-build hasn't changed, there must be manual updates that people are doing to get the higher sub? BuildLabEx REG_SZ 10240.16393.amd64fre.th1_st1.150717-1719 and yeah, SLS is still 16384
Code: Microsoft Windows [Version 10.0.10240] (c) 2015 Microsoft Corporation. All rights reserved. C:\Windows\system32>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v "BuildLabEx" HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion BuildLabEx REG_SZ 10240.16393.amd64fre.th1_st1.150717-1719 C:\Windows\system32>
It shows a different key because it's a different OS. If you revert back to your old OS it will show your old key.