Okay, I think I found out the what might be the issue. Insider Preview 14367 is okay, but 14371 won't generate Project.txt at C:\.
Hi The Guardian, I found the OEM branding does not work after Insiders Preview 14371, 14372 does not work too. Could you take a look and see maybe you can help? TIA
Back again, looks like I was wrong. It is the decompile.exe being detected by Windows Defender as virus and deleted.
I will add disabled windows defender in oobe.cmd file and then when decompile.exe is done re-enable windows defender again to ensure this doesnt happen in the future. I need to find the time to add it. Been busy lately so hang in there.
Got a new laptop, HP EliteBook 1030 G1, it has WIn10 pre-installed. The activation part works fine, but not the OEM branding. I assume if OOBE.cmd has the Windows Defender disabled, then the OEM branding would work too? My friend's EliteBook 1040 G3 does not have this issue. Any idea why the Windows Defender would disable decompile in some, but not the others? TIA
Hello, it is me again. Same HP EliteBook 1030 G1, the OEM branding works perfectly when installing Windows 8.1. Looks like Windows 10 Defender is trickier to handle for decompile
It isnt the decompile.exe. Run query tool and post results.txt file so I can look at it. This project has worked on every win10 I install whether it is real machine or vmware. Need info from query tool since code is similar. We are only guessing doing it this way. There has been NO change in win8.x or win10 sections of code. The only thing I did recently was remove all the conflict resolutions to only have one that handles all conflicts. Unless the newer versions of win10 has changed but still using th2 here on all win10 installs. Personally I feel it is some sort of conflict but need the results.txt file in order to see if it is or not. Waiting...
Below is my result.txt. Additional info., this particular laptop - 1030 G1, both Windows 10 TH2 and RS1 are activation working, OEM branding not working Win8.1 OEM branding working ------------------------------------------------------------------------------------------------------------------------ OEM Query Tool v8.0 Build 7 Advanced 07:15 AM Tue 06/28/2016 OEM INFORMATION FOR THIS MACHINE -------------------------------- OS Name: Windows 10 Pro Insider Preview [x64] OS Version: 6.3.14372.0.amd64fre.rs1_release.160620-2342 Processor: Intel(R) Core(TM) m7-6Y75 CPU @ 1.20GHz Processor Cores: [2] Logical Processors: [4] Processor Architecture: [AMD64] HDD Partition Type: [GPT-Secured Boot Enabled] Bios Version: [HP N86 Ver. 01.02, 5/6/2016] Total Physical Memory: [15,751 MB] Available Memory: [13,730 MB] SCANNED ------- #1 CSPRODUCT NAME - HP EliteBook 1030 G1 #2 COMPUTERSYSTEM MODEL - HP EliteBook 1030 G1 #3 BASEBOARD PRODUCT - 80FB #4 CSPRODUCT VENDOR - HP #5 COMPUTERSYSTEM MFR - HP #6 BASEBOARD MFR - HP #7 SERIAL/SERV TAG - XXXXXXXXXXXXXX #8 BIOS ID - HPQOEM #9 SLIC OA - 2.1 #10 INSTALLED KEY - XXXXXXXXXXXXXXXXXXXXXXXXXXXXX #11 MSDM TABLE [OEMM] - XXXXXXXXXXXXXXXXXXXXXXXXXXXXX #12 BIOS MODE - UEFI #13 CERTIFICATE - Un-Listed #14 LICENSE STATUS - Licensed SUMMARY ------- THEME - HP [id:-`#1'] ACTIVATION - HP [id:-`#8'] VALID [OEM OS] - Vista/Win7/Win8.x/Win10 Only
No conflict is found which is good but branding is done by %MAN%=HP. Try th2 and see results. Maybe the preview isnt completed yet which is a possibility. I only use official releases not the previews. Just curious if it works on your machine with th2 version.
Both TH2 (1511_2) and RS1 (insider preview 14372) don's work. So far only Windows 8.1 Pro works. Any more additional info. I could provide to help?
Are you using a slip streamed iso of windows 10? Also is everything deleted under scripts folder of windows 10 OS installation or is the OEM's.7z file still remaining? The reason I ask this question is because the cleanup routine will not run if decompile.exe is deleted so there should be the OEM's.7z file in the scripts folder of the windows 10 installed OS. If its not there then nothing copied over during the installation thus why I asked the first question above about slip streaming.
For 2nd question, no. All files are still there after installation. But there is no oobe folder under Windows\System32, which is evidence decompile does not get to run itself For 1st question, I am not sure. I download TH2 (1511_2) ISO from Microsoft, RS1 insider preview (14372) from wzor's ESD and covert to ISO.
There is no oobe folder but oobe.cmd file that should be with the other files under windows/setup/scripts folder tree. You are looking in the wrong area. Either way I am downloading the new 14376 build to see for myself. I should have something to report tomorrow so check back then. The TH2 release, I tested today even though it has always worked with the project (and still does). Since you said it didnt work for you I thought I would test TH2 for sh*ts and giggles today.
Yes, all 3 files are there under \windows\setup\scripts (decompile.exe, OEM's.7z, OOBE.cmd) I have the 14376 as well, will try it later in my evening. Appreciate any help you can provide to solve this misery. PS. For 14372, this issue only occurs on HP EliteBook 1030 G1, my friend's 1040 G3 are working okay. Both are Skylake, 1040 G3 is Core i5, 1030 G1 is Core m7, which I don't think should be relevant. But want to provide as much info. as possible. TIA
Interesting...if it works on one it should work on another but in your case it isnt a bios reading issue, instead seems as if the files never run period. I will still try with new build and see if I can reproduce. I have a feeling it will work on my computer but its yours that has this issue. None of the files are running for you. I dont mean crashing but instead dont run at all. This is strange. I would love to do a remote teamview session so I can see these files myself. I know what extracts where so this would make our lives easier if you wish to try a remote teamview session let me know in a pm. I know our time zones will be a issue but seems we are both online near the same time everyday so maybe this would be a good idea to try.
Can you please check to see if log file is still under %SystemDrive%\Log\Project.log instead of at the root of the drive. The reason I ask is because you cant write to root of hdd by default so I create a log directory to put it in temp then move it later. The script might have crashed in your case for what ever reason the log file was never moved to the root of the drive. If you do have it in the log directory then please upload for me to see please and thank you.
I did not find the Project.log under %SystemDrive%\Log. Later I will install 14376 and see what is going on. It really puzzles me that Win8.1 okay, but Win10 does not. It is just too strange.