Did you setup the ISO correctly by adding the $oem$ folder to the sources folder of the ISO? Are you using a slipstreamed version of windows ISO?
You did not answer both questions (unless you meant yes to both)...Are you using a slipstreamed iso or is this a original untouched M$ iso? Since oobe isn't running at all then I bet this is a slipstream corruption which has been talked about throughout this thread.
This is original ISO but I put Project files directly in WIM in every edition, not in OEM folder on setup files
What location did you put the project files into the wim file? I need to know exactly every step in detail you did in order to help you with this issue. Simply put this is something you did that broke the oobe.cmd file from running, its not the project fault because I know other members here that do the same with the wim file and theirs work.
What all is listed in the scripts folder of the wim file (should have oobe.cmd, decompile.exe and the OEM's.7z files)? By the way, this is not the recommended method to use this project.
Then to determine if it is your method breaking oobe process, use the project as it is recommended by adding the $oem$ folder to the sources folder of the ISO. I think why it isn't working for you is because windows looks for the $oem$ folder during the copying files process and if it doesn't see it then it assumes there are no oobe processes to run thus why the oobe.cmd file fails to run auto.
Then it has to be something your are doing or not doing. Try using it with the windows single language by adding the $oem$ folder to the sources folder of the ISO...if it works then it isn't the project or the single language iso but your method breaking the oobe process. The project in no way can break the oobe process, it needs it to run so if you test the project with recommended method then that tells you it has nothing to do with the project or M$ for that matter but instead points to your method used to integrate the wim file. Testing is the only way to know for sure. If it is your method breaking the oobe process then create a new thread in the forum and ask for some help because there will be nothing I can do to help you further. Just a suggestion.
Oh, I almost forgot, I'm from Russia. And this is Russian iso. Maybe your pack depends on the language???
The project isn't language specific. No matter the language, the oobe.cmd file is named the same and should be recognized if using the recommended method. We have other members here that use other languages also but in turned out it wasn't nothing to do with the project but their customizing that breaks it (especially third party apps for slipstreaming).
Got three more keys to add to the project in the near future (HEDY, INTELBRAS and MEGAWARE for Win7).