Just thought I would share... Helped a friend install win 8.1 core x64 with custom recovery partition and tools on his HP machine and image was captured correctly, windows was activated with oem-dm key in bios, project branded correctly, and this was done while in uefi mode. He likes how simple it was but he wasn't fond of M$ login setup process. lol I said "welcome to win 8.1". Note: This was with a untouched M$ iso.
thanks... so where's the "Certificates" folder in this version? Ops.... So diferent from you, I have always used your new 7z versions for only adding newest "Multibrand_OEM's" and "Certificates" to your old script (Keys.ini, oembios.ini, oobe.cmd, setupcomplete.cmd), because oldest versions are more easy to edit these ini and cmd files... I my case, I have disabled WinVista detection, leaving only Win7 detection (Win8+ had not been released yet) Now I can only extract newest "OEM's" but I don't know what strings will I need put inside "oembios.ini" and no access to new certificates Then... By searching google I can download newest certificates, but which are strings for these brands? ACTION, BIOSTAR, CHILI, FOXCONN, INTEL, OLIVETTI, PROLINK, SURFACE, TTL
I cannot answer your question about which certs are for which brands because if you got them from here at mdl then they are already in order and structured thanks to FreeStyler who is mentioned in the credits on first post. What ppl do is get oem'd machines and pull the keys and certs for that specific oem brand. Most popular oems have more then one cert that they use so it can get confusing if not paying attention. lol If you used this before win8.x then you were using searchengine's old project, not this one. There is no support here for that version. It has progressed since then with restructuring, new code introduced, updated keys/certs/brands and overall reduction in size. Not to mention new tools thanks to Alphawaves.
The only thing you must do is get the correct windows version like in your case 8.1 coreconnected with bing. If you don't use the exact version of windows the key in your msdm table in bios will not match. Everything else is done just like the first post says...will extract bios key and apply it plus brand to the oem manufacture. Simple
thanks for the replies guys, i made an 8.1 oem dvd quite a while ago and was shocked when it didnt activate my new machine. thank goodness murphy78 linked a coreconnected .img to DL. when i used the stock coreconnected .img the machine auto activated. adding this info to the OP would be helpful to a lot of people. thank you for the oem project, i have been using it for years. kind regards
Its a very well known fact for win 8.x you must have the correct installed windows version that msdm table key matches up with in order to oem activate correctly.
The project works well on untouched iso with custom recovery partition and full branding, however when i create a slipstreamed iso with a custom recovery partition and latest updates. The login and off wallpapers are default windows theme as opposed to the oem theme. But oem desktop paper is displayed on desktop. Any way to fix this on win 7. I see its only happening after applying updates on a custom iso.
Redo your custom iso because it is corrupt. Read back a few pages. This has NOTHING to do with this project. Like I said in earlier post, think this topic of slipstreaming should have its own thread. Question: Why don't ppl who have had this issue of slipstreaming contact their third party app for a fix? Seriously. I have even done the research for everyone. All you have to do is simply pass it on to them. From first post: If your original untouched iso works with the project and your slipstreamed version does not then it has NOTHING to do with this project but instead points to your method of slipsteaming (the third party app used).
I removed my fix for wallpaper because after re-reading your above post, your issue is the login/logoff background while using slipstreamed iso. There are too many variables to slipstreaming and you really need to contact the third party app used to create the slipstreamed iso. Sorry but this is not within my scope.
Hi, Im redoing the whole thing again, i tested my untouch version and i had a problem. Im pretty sure i used the March OEM Folder version first time, which worked, with full branding and no issues, then i used the updated April Version for both my untouched and slip streamed version isos Im currently doing a bare bones install with fresh untouched iso and May Final OEM folder. I will update soon. If this fails. I will re test with march version. I have had it working first time with no problems and im pretty sure my slipstream version will work fine in the long run. Just installing which is a ball sack. May Final Failed for me, no themes on login screen etc. Im testing February version now
Are you now using a "untouched" iso with the $oem$ folder in the sources folder of the iso? I cant reproduce your issue so it is something on your end. There has been no changes since May because if fully works if setup correctly. Are you adding anything else to the iso that might interfere? If I cant reproduce the issue then I cant fix it...if it actually needs fixing. Think some of this is either slipstreaming or end users not understanding how to setup the "untouched" iso. It has been working perfect for me and others in VMware and on real machines. It comes back to what you are doing to the iso. Are you editing any of the included files in the project? Have you included any registry tweaks? Are just the login/logoff background images failing or are there other images not installing correctly? This is my untouched iso I got from M$ that works perfect with project... en_windows_7_sp1_x64_dvd_u_677332
Update i have used the February OEM project and all is working well on the untouched iso. i have login papers working now on this version. Il forget the march april may versions as the result is a default windows blue paper for me.
That tells me nothing. lol If ppl cant give me detailed info on the issues then I cant reproduce it. I am done with this conversation because no detailed info has been give and ppl tend to not answer my questions. Have a good day. Funny the one some say works where the newer projects don't is before the protection was introduced. There have been no changes to the script between all of those other then protection added. If using the older versions then you will not have the updated certs or keys but that is up to you all. I am going fishing so catch everyone on Monday.
Basically, the later versions are not working for me on an untouched iso. I get a default windows theme on login. I now get branding on login using the February OEM project. Guardian, I appreciate your time. Something has changed since your February project for me any way, but i have branding on login screen so i am happy now. I have downloaded your projects each month since January 2015. I will upload the package i use and send you a link. i am just using your project with the recover creator and it is gold and im grateful for this. Im going fishing too. Spent too much time ball sacking images. etc.
Yep no changes in the install script at all between feb and may so this is just ppl not liking the protection is all seems like. Again there has been NO changes in the script between those times. If one failed the others would fail also. See my point? Sign up: Gone fishing.