I already have tried and seen everything I post about. Unlike you, I only post things that I am sure about. If you look back at my posts, I never once use the phrase "permanently activated", I don't know how that's relevant. Lastly, as I said already, activation and time bomb are two separate things. A build is either time bombed or not. A given installation on a particular machine is either activated or not. Don't mix the two concepts. Look at Evaluation versions, such as Windows 8.1 Enterprise Evaluation. It is timebombed AND it activates online just fine. That's the intended way for it to work. In conclusion: Windows 10 Insider Preview build 10525 is timebombed. Irrespective of that, once you install it, it's either activated or not. Obviously, it's better to have it activated. PS: the activation of an evaluation version (and a timebombed build like 10525) is "permanent" in the sense that, unlike KMS activation, the activation state never expires.
Maybe is build 10525 special last final build for insider(free licence one year) 15 july 2015 - 15 july 2016?
I'm just going by memory about insider builds, but either way it does not matter, you have backup copy, download esd if you like, you done grading people yet, none of what you say matters, if you don't have to click on get insider previews on 10240, fine, one less step, alot easier to do it this way than your way
This is a little off topic, but how does Hardware ID's work with Virtual Machines (specifically VMware). Im thinking of downloading an ESD and installing it on a VM. If I do that, would The VM use the Hardware ID of my host computer (that would mean that my VM will be activated) or would there be different ID for each individual VM I create
Yeah but I'm web developer and I'm used to work with Chrome's developer tool. Will reverting to a previous build damage any data or files? has anyone tried?
"C:\Users\**Username**\AppData\Local\Google\Chrome SxS\Application\chrome.exe" --no-sandbox <------add this