I tried this project before when the oem folder was not zipped and it worked on windows 7 and 8.1 some previous version but now with the new version of the multi-oem and new versions of windows it didn't work with me unfortunately I don't know why but I tested it with win8.1 update 3 and win10_1511_2 and both failed, only oem branding that occurs (themes) I checked the project txt file in drive c, it says: error: no oem-dm key present Licence status: error, not licenced I used a usb flash drive to setup windows I tried with 2 desktop pc's one lenovo and the other is HP does it need internet connection after installing windows to get the oem activation, or maybe entering a key product in the begining of the process of installing windows instead of choosing skip (which I usually do) ps: I'm using Multi_OEM_05.10.2016 version
Windows 8.X and windows 10 require the net for online activation check on M$ servers. Obviously the extraction within the project worked but you werent connected to the net so activation check could not occur. Has nothing to do with the project being compressed. lol You need to use kms activation since no oem-dm key present.
I am installing the new build in vmware with bios set to HP for testing. I am doing research on your specific machine for windows 10 install. I have a feeling your hardware isnt compatible which can cause oobe.cmd not to run. This is a known issue for some machines and I have a feeling your machine fits in this category. Will report back when done reading and testing new build. Have you done a hardware compatibility check for windows 10 installs on your machine? Really fell this is your issue and is known to M$. Update: After reading your specs on your machine it should work with the project. Is there any way we can do a remote teamview session so I can see if any files are present (after the extraction is done)? I am curious if extraction even took place. An easy way to test if oobe.cmd is running is to add MD "%SystemDrive%\Log" >nul above the call command for decompile.exe. If then the oobe.cmd doesnt create the folder then oobe.cmd isnt running at all and this would be the issue. Need to do a test to see if oobe.cmd is running or not. Right now we dont know...
I agree, definitely there is something incompatible between my EliteBook 1030 G1 and Win10. But there are a few facts which makes the issue a mystery (for now). 1. Windows 8.1 is okay to have OOBE run and do OEM branding 2. EliteBook 1030 G1 is a very new machine, just came out in May, and pre-installed with Win10 Also tried 14376, no luck either. Everything else installed just fine, including activation. Only OEM branding not working.
With windows 10 activation will auto happen if present in bios so even if project didnt run, it should auto activate, its built in windows 10 installation. Yes, I seen your machine is very new and I must say its a nice machine but seems to have issues with custom installs of windows 10 for some odd reason. Really would like to test the oobe.cmd with it creating a folder before the call for the decompile.exe to see if it is running or not. If it does create a folder then its running and then points to the extraction process. Right now we are guessing until this theory can be tested on your machine. I am having install issues in vmware with this new build. Trying install again...
Would you like to send me a customized OOBE.cmd to test whether it creates a folder? At least it will help to clarify the running or not vs. extraction. The laptop has a SSD, installation only takes minutes.
There is no need to upload a customized oobe.cmd file. You can add it yourself from past posts I have made above which has the command to create a folder for testing. Just put it above the call for decompile.exe in order to run first before the decomile.exe. I am uploading a new version which has updated instructions for PID.txt creation with an example as well included. This is the simplest way to bypass the oem-dm key and allow oobe.cmd to run correctly for oem machines with oem OS installations. Unfortunately I cant do everything for user's but with this included and install keys easily found on the net with simple google search, this solves this issue. I believe this is your issue which makes since. You can try the addition to oobe.cmd yourself to create a folder for testing and if it doesnt create the folder then this should solve your issue since yours came with windows 10 by default unless you bought a downgrade option which I dont believe you did. I am uploading the new project version date 6-29-2016 now.
can you please explain the meaning of "no oem-dm key present" I don't understand this part so what I get from you is that in order to get the project successed in activating windows the computer should be connected to internet while installing ? if not it will not be activated even after connecting later ?? please correct me if I'm wrong
Windows 8.x and windows 10 requires online activation check on M$ servers for oem-dm embedded key in bios (win8.x or newer OS's) thus you will need to be connected to the net in order to finish activation process. Its a requirement, not a choice for oem activation or even retail activation's. Vista and win 7 uses slic and key which can be auto activated without online connectivity but any newer OS will be required in order to finish the activation process after the install (win8.x or newer OS's).
Windows 7 OEM not activated I have copied the OEM folder into sources folder and changed the installation files; during installation the prompt came up with the different versions of Windows and no product key was requested however in the Windows system properties it is still showing 3 days until activation - activate windows now. I have attached the query results before the installation.
Get rid of the emulation and project should activate correctly "if" you have a legit slic in bios. If no legit slic in bios then you will need to use a emulation that works or bios mod. If you have legit slic and no emulator in use, then send me results.txt file from query tool again without any emulation running. Note: Key and Cert is already included in this project. Points back to no legit slic in bios seems like you used a emulation that isnt working. Also what do you mean by "changed installation files"?
Thanks Guardian I have used the Phoenix Tool but I will try to flash it again and reinstall; I had used the Windows executable to flash the BIOS and I am not sure why it is referring to the emulation; :Changed installation files" - referring to the OEM folder replacement. I have attached the SLIC 2.1 results. I will try again and post results.
Always use untouched M$ ISO's so you know for sure no emulation has been added. I dont know where you got your ISO from but I would look closely at it or just download untouched ISO from M$ to ensure this isnt the case. If you modded the bios the query tool wont see a possible emulation if the ISO is untouched. Let me know your progress. Note: If emulation was used without your knowledge it will show slic when there is no true slic in the bios with that tool. Its emulated so will always show slic in bios but really it isnt there thus the name "emulation". By the way, I want to thank you for providing needed info and files for troubleshooting. Most say it doesnt work but will not provide the info and files needed to investigate the issue.
Hi The_Guardian, Would like to feedback that the PID file did the trick. OEM branding is working now.
Hi Guardian Based on your feedback I managed to reflash the BIOS using another file and rechecked the SLIC tool to confirm 2.1 was valid. After that I just ran the certificate installation and reentered the key. Following a restart, it came up as activated!. The ISO seems to be fine, I had used a genuine Win7 DVD. I appreciate all your feedback and in such short time. Many thanks for the assistance Guardian!