Project log file location: C:\Project.log You have a choice with query tool save location. Select Y to save file and then choose where to save it to.
Project log isnt saved by query tool. Like I wrote on previous page you get the option to save query log and project log is saved in C:\ after installation.
I see some confusing statements but it seems you are mistaken the query tool for the actual project and it isnt. Its only a query tool to see if the project will brand correctly and possibly activate it. Since you did not post a Project.log file this tells me either project didnt run because of oobe being disabled in which you would then need to use pid.txt file in sources folder of the iso or you didnt include the project in your install. Query tool says you have win8.1 pro but used a win8 key which are not interchangeable. Like I said some things are confusing without all needed info to investigate.
I used the project tool in 20-30 installs to date and always always the project is working fine. Only PCs it did not install the key automatically or activate are HP 400/600/800 G2 (2016) PCs. I meant I used a win 8.1 key to activate Windows as I was in a rush. Will check next time when I will have a HP G2 PC
I am lost until I get a project.log file. As far as key retrieval and application, they all have mdsm keys in bios thus if it extracted, it should be applied. I know Hp has issues with using same keys too many times and M$ blacklists them. My friend has a Hp and neither Hp nor M$ would resolve it. He had to purchase a retail key from M$. Most think their key is only used for their machine but that isnt the case with Hp. Not saying yours is the same but if you tried yourself to input key after install and it still didnt activate then its the key, not the project. Even you said you had to use another key which is probably retail or vl. Guessing here so its hard to say.
Simple google search revealed that some models of hp if upgraded to win10 can never go back and use win8.x keys for windows 8.x again. Either windows 7 or windows 10 after trying windows 10. Your model is one mentioned in the list. Did any of these try win10? If so then that might be why. Lots of ppl complaining about those models and upgrading and downgrading. This info is on hp costumer support tech site. Note: I am glad mine isnt on that list. I tried win10 but had issues with my lappy so went back to win8.1.
First post updated 9-4-2016. Spoiler Change log 9-4-2016: -Updated additional reg files in oobe.cmd to address f8 function key for win10 anniversary builds. (Thanks EFA11)
no, the last one HP 400 G2 mini was brand new, I just set up win 7 on first power on which activated fine and the license for this model supposed to be valid for win 7, 8.x, 10, I did not do a win 10 upgrade the project does not even inject the serial during installation for win8.1, it asks for serial during installation... as I said I used the project on 20-30 other PCs older HPs (2015 and older), lots of Dells, Lenovos etc
No log file from project given. Key isnt working even from desktop Didnt say if branding even took place. Only mentions activation failing even if manually input. Not much to go on but I did say earlier your model of HP is on the list with issues with key and activation. If its new then call HP for support and complain about your key. I am not HP. Subject closed because this isnt a project issue but specific HP issue which falls on them. Call them toll free and get support.
If it shipped with Win 10 Pro then it has an OEM-DM key for 10 in the bios & Slic for win7 because of downgrade rights. That 10 key will not work for Win8.1 Pro...
I still say his key whether oem-dm or retail is blacklisted since he said in previous post about using another key for all. Have a feelin that key that worked on all machines was vl not oem and his oem-dm key has been blacklisted by M$. He even tried his oem-dm key manually and it would not activate so this tells me everything I need to know. HP is known for this and is in process of being sued by purchasers. Either way this isnt a project problem but a blacklisted key problem.