I've used slui / changepk + the key in this thread a few times successfully, but on this new install it is telling me it couldn't upgrade and didn't give a reason. I've tried it with internet on and without. https://forums.mydigitallife.net/threads/windows-10-pro-activated-itself-with-generic-key.69692/
error code is 0x80042306 which is apparently VSS related. It was set on manual and not running, so enabled it and trying again.
To be clear, you were on a MTK2.6.x kms activated 16299.xxx Home install and want to upgrade to Pro now?
Yes. And the only reason is to enable group policies, so if you know of another way to do that on Home I'm open to learning something new here.
I probably made an error, for upgrading to Pro you should use the GUI combined with the generic pro key, you could test it. At the moment i am fighting my Home install from being HWID activated to test KMS and upgrade.
Yeah that doesn't work, either using cmd prompt 'changepk' or in settings. Worked before with this same install iso. Only difference is that I did an inplace upgrade from same iso recently to fix some settings issues. Gives the error I pasted earlier that google says is VSS related.
The error code in my background shown cmd's is when you enter the key in an elevated command, not when you enter it in the GUI, the command lines only work for license switches. When it doesn't work by using the GUI try it again when offline (@s1ave77 once showed he needed to be offline to get it to work). I now notice my test VM was offline too
I'm pretty sure both changepk and gui gave same code but I'll double check. Slui has no echo or any apparent activity or error shown.
Hi Enth I have one issue very strange when I try use Dism for some reason OS warn me that with OS of 64 bit is not possible use Dism of 32 bit what happen? thanks You cannot service a running 64-bit operating system with a 32-bit version of DISM. Please use the version of DISM that corresponds to your computer's architecture. When executing the DISM command, you may encounter the message: "You cannot service a running 64-bit operating system with a 32-bit version of DISM. Please use the version of DISM that corresponds to your computer's architecture." This message typically means you are attempgint to execute DISM while using the 32-bit version of CMD rather than the 64-bit version of CMD on a 64-bit version of Microsoft Windows. On a 64-bit version of Microsoft Windows, the 64-bit version of CMD is located here: C:\WINDOWS\SYSTEM32\CMD.EXE On a 64-bit version of Microsoft Windows, the 32-bit version of CMD is located here: C:\WINDOWS\SYSWOW64\CMD.EXE Using the 64-bit version of CMD, you can also explicitly execute the 64-bit version of DISM using: C:\WINDOWS\SYSNATIVE\DISM.EXE
yep I think you are right... err I have the best solution dude: Dispart\listdisk\select disk 0\clean\convert to gpt\install....