To let you know, the older Asus laptop which had 7 on it failed to activate after putting OEM folder into iso and burning. I downloaded the project that had the OEMs zipped with the 2 windows commands in it just as is so it went I put it into sources folder $oem$ $$ setup scrips then the folder with the zipped OEM folder Is this correct? Slic was correct since in the end I just used loader to install cert and key.
All you do is add the $oem$ folder to the sources folder of the iso and save iso....then you can burn it. Did you have a PROJECT_FAILURE.txt file at the root of drive c? If so then it is because you didn't setup everything correctly. The new project will output error at root of c drive if it isn't setup correctly. Did you run the query tool on the older win 7 machine? If so then what did it say? If not then I might not have key or cert included and will need someone to get that info for me so I can add it.
It was the laptop with the modded bios for the SLIC table running Windows 7 and yes had a a project_failure text at C root. To be clear I extracted the project folder got the $oem$ folder and went to sources directory(the one that has the install.wim/esd) and moved it there. I will mention I use install.esd for windows 7 if that affects it, and after i decided to test the Windows Loader it just installed Cert and key and not the loader so the slic must of worked. Can't really check anymore as I sold laptop just trying to work out what I did wrong.
What was the error in the PROJECT_FAIILURE.txt file? One of two errors are present for it. More then likely not setup correctly. If not on media like usb or dvd then it will fail and save a PROJECT_FAILURE.txt file at the root of your c:\ drive. Its made this way on purpose.
I didnt check as I was in such a rush as it was like 4am and courier was coming that day to collect laptop, but it is strange that windows loader had the correct cert and key so I assume its more that it was setup wrong.
Speakin of which. I did a new install of W7 on a secondary SSD with the latest project. Error message in that file was similar to: Source not found. Also your latest download doesnt contain "Install.7z" The problem is that OOBE/Windows isnt using Asus branding. No SLIC2.1 is present i believe as I built it myself. I ran your Query Tool: <I HAVE REMOVED THE CERT-TEXT DUE TO TAKING ALOT OF SPACE>
How did you have the windows media with this project setup? Did you just add the $oem$ folder to the sources folder of your windows media? It looks for the windows media before the install of the project begins. If setup correctly it will brand your machine without issues...its not dependent on the slic version for branding...only activation if possible. Without knowing more on how you setup your install media it is hard to say. Note: Everything is included in the decompile.exe so the install.7z is present, its just packed.
I have W7 on a USB, I drag/dropped the OEM-folder. I used 7 Download Tool to copy the ISO to the USB. ISO works fine in Vmware.
The project worked fine also because it ran and seen it wasn't setup correctly thus why you have txt file at root of your c drive. You only gave a partial answer to my question...Is the $oem$ folder in the sources folder of the usb? I would recommend Rufus as well because it does mbr and gpt (uefi) depending on what options you choose. This is what I use to prepare my usb for windows media.
First post updated...member's should like this version better. Change log: Spoiler This project now works with any 3rd party multi os media creations. This project also works with including it in the install.wim if you wish to do that. The reason behind not working from audit mode or desktop is because lockscreen can be a pita from those environments. The reason is because even with Admin acct your rights are still not high enough to do some system changes. This project is only meant to be ran from OOBE Mode, nothing else.
Thanks to BALTAGY for the teamview session we have noticed that when you go to personalize and click on desktop wallpaper link, it shows all images including logos and all....it should only show the wallpaper...this will be corrected in the near future.
Small silent update to 4-26-2015 build...first post updated. Change log 04-26-2015 (Silent Update): -Fixed under Desktop Background windows setting, the windows showed all images instead of just the oem wallpaper. -Changed output of error file to desktop if not ran from oobe.cmd. -Per Suggestions