The purpose of that thread is to get HWID on machines that never had (Home (+N) and Pro (+N)) installed before, it had worked well few weeks back until MCST realized this flaw and corrected it.
You still can generate HWID's by all methods, real upgrade from 7/8.1 or by gatherosstate (use the one from 10586 iso for 8.1 KMS activated systems). Weird thing is: Last 20+ installs of home an pro got hwid's again out of the blue, next i set up VMWare on my test system and after the first test all home and pro installs get hwid's too now. Yesterday i started up a friend's laptop, never got pro on it, only has a HWID for home and after entering the generich Pro HWID key it was activated as Pro by Digital License.
My pc only have OEMM of 10 Home on it and I can't install win 7 on it because of drivers not working. I thought I can get a valid 10 Pro with this
Are you willing to try something? I have a genuineticket.xml that seems to work for other hardware, i can share it by convo and you could try to clipup it and use @mkuba50 info to get the hwid for pro.
I also have an AiO similar to your laptop: never saw 10 Pro, it has a MSDM for 8 then upgraded to HWID 10 Home. Will test to see if it gets HWID activated after 10 pro clean install and insertion of the generic Pro key (-3V66T)
If i'm correct inserting the key (-3V66T) will allow to upgrade to pro from home edition and will allow to get HWID at the same time and only then you will be able to clean install and get your win10 pro activated automatically.
So you mean the correct method is to insert (-3V66T) to the existing HWID activated 10 home edition first, then do a clean install 10 pro to get HWID activated?
how did you exactly proceed ? when you have win10 home installed, entering this key VK7JG-NPHTM-C97JM-9MPGT-3V66T allows to do the upgrade to win10 pro but usually doing that does not allow to get win10 pro automatically activated with HWID after the upgrade but someone has recently found out that this procedure was leading to automatic activation of win10 pro with HWID so either you did something wrong or MCFT figured out this flaw and stopped it.