Hey guys, here's a weird one I can't figure out. As you know with Windows 7 and Windows 8.1, you can switch between versions pretty easily. In Windows 7 this was called "anytime upgrade" and in Windows 8.1, it was called "add features to Windows". I've searched far and wide for the equivalent for this in Windows 10 Home, but I can't seem to find it. I tried switching the key to the Windows 10 Pro KMS key and it didn't say it was valid for this edition of Windows (which is accurate... I want to upgrade). Reason for all this is that I have setup Windows 10 Home with everything I want, but I want to be able to use the same setup on another machine which will end up with Windows 10 Pro. Any suggestions? The "Optional Features" section doesn't contain anything about upgrading to Pro.
You have to click on the settings menu in the right bottem corner all settings and then update and security there you find activation
I already tried that, like I said in my OP. I'm not trying to activate Windows anyway, I'm trying to upgrade it. I tried the KMS and the retail key, both do not work... because it's for Windows 10 Pro, not Windows 10 Home. I need to be on Windows 10 Pro before the key can be used. They do throw different errors though, I'll throw up some screencaps if I get a moment.
Its unified now; launch changepk.exe & enter your upgrade key. If the upgrade path is supported (like Core to Education), then it will be upgraded.
Okay, so I had a fiddle around. The KMS key doesn't work of course. However, I was still having issues with the retail key. Screenshot here: drive.google.com/file/d/0B2OZr4CkbOsINlROd09zRFNpNjQ As a workaround, I tried upgrading to pro via the ISO and that worked. I wasn't content with that though - so I created a new virtual machine and restored my exact same setup into there and tried again. Result? It worked fine via the "change product key" system, first go. Beats me.
Actually, after a bit of thought, I think I know why it may have been having a fit. I was using VirtualBox, with a default NAT-based network. As a result, it was in a different subnet to the DNS... maybe it didn't like this. The other VM I tested with had a bridged adapter. Anyway, it seems to work, and I use bridged 95% of the time anyway.