Seems to be working for me, but the secret seems to be that you must already have a digital key from Windows Pro. Since I upgraded from Windows 8 Pro long ago and got the free upgrade to Windows 10 Pro, after signing into my Microsoft Account, my computer was already activated with Windows 10 Pro (insider 16257.1). I then applied the key for Windows 10 Professional Workstation and it seems to have activated (see screenshot). I am now in the process of upgrading to the latest insider build (16288.1) to see if this holds. Spoiler: screenshot confirmed
No key was used to install Windows Professional and it was automatically activated via hardware detection via the digital license. The only key I used was the one previously mentioned ending with XD863 which is how I converted it from Windows Pro to Windows Pro Workstation (how else would you convert a working install to a different version?). The question now is whether or not will activation still hold once it upgrades to the next build as a digital license and better yet, will that digital license still be good for the RTM?
The activation you show is a KEY activation, that worked on 16257 and one or 2 builds after that, on 16288 it doesn't work.
I'll repeat myself (listen ... errr... READ closely)... Windows 10 Professional was not activated using a key. I have a digital license entitled to me because I originally had Windows 8 Pro and upgraded it to Windows 10 Pro. As a result, whenever I install Windows 10 Pro while connected to the internet, it automatically activates without any key as a digital license. I have NO Windows 10 Pro key as Microsoft never gave me or anyone else with a digital license a key (I wish they had, to be honest). Now, once Windows 10 Pro had already been hardware activated (that is how a digital license works).... I used the key XD863 to convert Windows 10 Pro to Windows 10 Pro Workstation, because that is how you are superposed to convert a working install to another edition (home to pro for example). What you see is that key, being activated for Windows Pro Workstation... The next build is where I will see if it holds as a digital activation or not. The question remains whether or not will Pro Workstation remain a digital key to my hardware? Say for example, if I were to format and install Pro Workstation directly. --- I have not yet tried that, yet.
Please explain to me how you think it is supposed to work? My computer was hardware activated for Windows 10 Pro. Excuse me for not posting a screenshot of that (I did not think I needed to do so after our chat last night ).
I am also interested in this. Please digitally activate the ProWS, then format, reinstall (you have a ProWS ISO correct?,) and let us know how it went.
I am still in the process of updating to the latest preview 1st. I want to 1st confirm that it will remain active and more importantly, will it list as a digital key when I upgrade? If it does, I'll keep upgrading until the RTM, and if it stays active for the RTM, then I'll try to do a full format and fresh install. Spoiler: screenshot In other words, we're not there yet.
HELL NO!!! Please put a Warning before the spoiler; May introduce seizures! Imagine the difference from this: [Attention very dark image ahead!] Spoiler
Cannot tell if joking or serious. (well played) Spoiler: inquiry Seriously, I know blinking photos can give seizures, but I'm pretty sure a solid light background, as I posted, does not. Else, Google.com must be a problem for many the 1st time they visit it.
The only solution seems to be to use KMS via here https://forums.mydigitallife.net/th...pro-and-office-2013.49686/page-76#post-838808 If there is a "will" there is a "way". It is not the one I know everyone was hoping for, but it still works. Same method used to activate Windows Enterprise LTSB
I have just reformatted the VM And have tested a clean installation of Pro WS 16288.1 Converted from coresinglelanguage to ProfessionalWorkstation and still shows HWID Activated.
Test on a new created VM, @Daz just explained in the chat that when you re-use the same VM it probably will work because of the uuid.bios and ethernet0.generatedAddress on the VM that previously worked.