it'll remain activated 10525 uses same activation status/key as 10240 (RTM), so if you upgraded from activated 10240, you'll remain activated no matter what in 10525, but obviously if you upgrade from non activated 10240, you'll remain not activated. Joining/leaving Insider program doesn't have anything to do with it.
i did clean install from build 10130 upgrade to build 10240. is permanent activated on licence to retail channel. so it should be safe to stop insider build without losing activation. ok thankz
Microsoft's official stance is that you have to remain in the Insider Program to remain activated. However, nobody's been deactivated by leaving it. If you do get de activated, just check the thread regarding upgrading from Daz activated 7
Hi is new build being sent to uk i am not getting any update, i have windows updates on and other stuff off on telemetry with a no of these programs. i have the insider builds greyed out but showing as automatic. any ideas?
If you cant click the button it is because you disable some telemetry stuff. You need to reactivate it for get insider builds
which bits of telemetry i need to revet, i am getting windows updates but not the insider builds, i have used 5 - 6 diffent telemetry programs and done various tweaks so how do i change to normal?
i have on updates screen some settings are managed by your organisation, i am trying to revert settings to enable update of insider 10525 update, but its not doing it !!
I notice that also, Fresh install and 2 upgrades seem to run much better. No lag at all on a cheap gateway that took 2-3 seconds opening the start menu now opens right away
Not totally true. I've got a tablet here running W10 Pro, that was activated the same way. If I 'Reset' it or do a 'Clean' install it fails to activate, 'key blocked' The only way the get it activated again is to go through 10130 first
1 thing definitely changed, Hyper-V Windows 10 now has near same capabilities as server Hyper-V. RemoteFX has been added for vms you can now toggle secure boot certificates in vm settings without having to hassle with powershell