@Tseng, Please post log files so I can look at them in order to address your issue, thank you. I have a strange feeling the project didnt even run for you. Did you setup the multi oem project correctly by inserting $oem$ folder into the sources folder of the iso? Very odd it did not brand at all.
Edited link out to be included in updated project soon to come. Should output like this now on real machines (not vmware or vbox, its different query for those)... [GPT-Secured Boot Enabled] or [GPT-Secured Boot Disabled]
Sorry, mate! Yesterday I installed Windows 10 Home x64 on my Lenovo Thinkpad X230. So I can't test your v7.3 Build 4 on Windows 7 Home Premium x64 SP1. Results for Windows 10 Home (both version define correct HDD Partition Type): v7.3 Build 3 v7.3 Build 4
I wanted to THANK all the people who created this project! I had a Dell Venue 8 5830 which came with Win8.1 Core Single Language - Bing.... All the recovery media from Dell did not work as it did not apply MSDM key properly but this script DID! Saved me hours of frustration! After install, booted, connected to internet and activated automatically.
Run the query tool and post txt file and if the project did run post the project.txt file located at the root of your hdd (make sure to remove your key from both log files) so I can look at everything. I dont know if you are not properly setting up the project correctly or if it is failing on your machine. The "dont work" isnt much to go on.
I tried using the new version of this today on one of my customers Dell computers. When I installed Windows 8.1 it seemed to be fine. All dell logo's copied and dell activated. But then I reinstalled the computer with Windows 10 Home and for some reason it copied HP logo's and tried activating it with HP certs. Even though the query tool looks like it successfully lables this as a Dell computer with no cert available. It should have just copied the dell logo's over correct? Could there be some sort of bug that when it finds no cert available that it copies over the HP files? I'm gonna attach my Results.txt with product keys edited.
The branding failed because your bios id is the same as a hp one a member here complained about so I add that bios id to address his issue but was concerned about conflicts which you now brought up to me so I see this is a problem. I can remove it so you dell is seen instead of bios id. If the other member has issues he will have to use forced theme txt file to address it. As far as the activation, it doesnt use certs for this OS. It dumps your key from bios and applies it which is the win8.x key. The only way this would activate your machine is if you had a legit win10 oem machine (brand new models just released) or did the upgrade process first which is probably what you did. Correct me if I am wrong. If you didnt upgrade form win8.x first then M$ hasnt gotten your hardware id's in order to active win10. I have used this on my lappy and wife which we did clean installs after the upgrade process and both are actived and branded correctly but you must be online in order to activate (no more offline activation's with win 10 home and pro). I would also have liked to seen the project.txt file from the project running on your machine to see if the same as I have explained. I will remove that bios id this weekend.
No I will not add anymore tools to the project. It is meant mainly for oem installs. If you have a legit key in bios for win10 (new machine with win10 oem) it will auto activate but if you did a type of upgrade like you actually did above then it wont activate until online which is perfectly normal because its then retail not oem. I dont know about that tool you used to do the install but it sound like it grabs info needed to do a fresh install as upgrade with all needed info regarding your hardware id's. I have not ever used that nor do I recommend that way personally. What WORKS for sure is do the upgrade as normal then after the upgrade is fully activated you can then do fresh install. These shortcuts that I read about might cause issues and then might not, I dont know nor do I care. I have done my lappy, wife lappy and my neighbors computer with this exact method with NO issues so I know it works correctly. They all have had legit win8.1 on them which tries to activate but fails of course but when online it activates win10 perfectly. If not original way M$ does upgrade then activates oem to retail then you might want to take it up with them. As far as the HP and Dell conflict I will correct that in the ini file and if ppl have issues with this with HP then they have to use the force theme txt file to force the correct theme. That is why it is included in the project anyways. If you wish to correct yours you can always do the same with the force theme txt file after reading instructions first to force Dell instead of HP until I get time to update the project with correction.
I need all oem images, the reg files and certs (not bin files) in order to add those to the project. Plus would need the query tool results.txt file showing all needed query info so I can add that to ini file. If you have access to those then I can add them quickly.
Got the logo's but need query info in order to add branding. Without need cert I cant add activation part but will see if I can find it online, no promises though. Those might use the normal AT certs included but no way for me to test even in vmware unfortunately. Update: I have been looking all over for needed cert, oem shared key and motherboard query info and nothing is posted anywhere so this is another manufacture that isnt quite popular yet so there isnt much I can do seems like. Without need info we are out of luck.