Run query tool and post results.txt file. The project includes certs and oem shared keys so you should not need to install the key. It will be auto installed with matching cert if your machine is supported by this project. The results.txt file will let me know.
Dont use the key you got and skip the key entry when it pops up during the install. The project should activate automatically. The key is included and I have included 3 different certs for the ASUS brand. Try it without the key you used and it should work. FYI, make sure to put $oem$ folder in the sources folder of the iso. Any other location and the project will not run.
I have first tried installing without the key. It didn't activate by default. The $oem$ folder is in sources in my iso. You mentioned in original post that this will only work in the OOBE mode. Do I need to do anything special to put the VM ware in OOBE mode?
The slic included in that vmware bios mod isnt matching the included cert in the project. I use this one, VMware_Man&Auto_Selector_v361H_vmware which works in vmware 11. I recommend you use the same as me for testing in vmware. I have some things to do today so wont be back until this evening. Try the above tool I use and see what your results are.
Where can I find this VMware_Man&Auto_Selector_v361H_vmware? Is it the same tool I used except different version? Thank you for your patience.
I dont think some understand how win10 activates. It doesnt use the normal activation key but goes online to check hardware id's for upgrade. If you did not do the upgrade to win10 feature then that is why it didnt activate nor are all the images activated. Once it is activated the images will be available. In other words, install win8 and then do upgrade to win10. Once win10 goes online and shows activated, you can THEN do a fresh clean install. Once win10 is done with fresh install it will contact M$ activation servers and compare hardware id's and activate properly. The images will then show.
FYI, win 10 th2 x64 iso will not load properly in vmware 11. In my case vmware says that VT-x isnt enabled, I enabled it in vmware bios and it makes no difference. Looks as if we have to wait for vmware to be updated to address this issue. Win10 th2 x86 installs perfect but x64 has major issues with vmware 11. Downloading vmware 12.0.1 now to try and see if this issue has been addressed yet...
Tried vmware workstation 12.0.1 registered and it does the same with win10 th2 x64. No choice but to wait until vmware updates their software.
Update on above issues with vmware 12.0.1... Seems installing the win10 th2 x64 on my lappy turned off visualization in my bios. I havent touched my bios in a year so I know I havent turned it off. The only conclusion is that win10 th2 update turned it off to install. I am installing win 10 th2 x64 now in vmware but did notice it show from vmware dropdown menu it said server 2012 data center for some odd reason. Still think vmware needs a update. I will see what my results are BALTAGY and will let you know if I run into the same problem as you.
BALTAGY, I reproduced the exact same issue as you with the info folder. It doenst get created. I need to add permissions for win10 x64 seems like to address this. I will work on testing it tonight and come up with a solution. Win10 has become worse then ME days. lol
I reproduced it so I know exacty where the problem is. I will work on it tonight when I have more time to address the issue. I have to install win8.1 in vmware in order to update the project since some of my tools dont work on win10 on my lappy. This will take time but I will have a solution for you tonight.