Win 8.x • Win 7 • Vista - 'Multi-OEM' ISO Project

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Hello there maties,
Last these few days i've been customizing and slipstreaming my win8.1 dvd.

I can't seem to get this to auto apply the branding and theming. I'm using windows 8.1 update 1 Core/Pro

Cheers

 

Try it without your customizations.

 

Basicly it's slipstreamed and copy pasting this folder. It seems that the key to activate windows 8.1 (win 8 oem key) disables oobe.cmd.
Any workaround?

 

You need to login to view this posts content.

 

ok, but does this need any cracking or activation besides the embedded key?

I just added the ei.cfg, better delete it and add one of these keys then.

Isn't it better to have a firstlogon.cmd in this case?

 

No other method is needed.
For win 8.1 add PID.txt file in sources folder of iso with either a gvlk key or install key (anything other then a oem key). oobe.cmd will then work.
Setupcomplete.cmd = non oem (no oem-dm key in bios for win 8.x)
Firstlogon.cmd = for oem (oem-dm key in bios) only

So in your case add the pid.txt file with any key other then oem (a non oem key for the version you are installing of course). Use Firstlogon.cmd in your case also and it should work.
Hope this helps.

 

theres an issue evey time i try to download the $OEM$ project on both mirrors it comes as a 315KB .exe file
and is flagged as a virus

its supposed to be 143 MB and ISN'T dose someone have the origanial and want to upload it to a more reliable host like MEGA

 

All links are working properly. Just untick "use our download manager...." before downloading on datafilehost.

 

I didn't have any problems , but here is a MEGA link.

 

How to restore default theme and logon-off screen

After installing Windows how to restore, using a registry hack or even better, a script file:
1. Default logon-off screen.


2. Default wallpaper.


In other words, undo OEM Branding but OEM activation.
Sometimes after installing Windows with this $oem$ project, for any reason, it's needed to restore or revert to defaults.

 

@ Mr.X
I am confused on what you are asking...can you rephrase so that I might understand better?

 

Oh sorry...been one of those days for me. Just replace the oem branding with the original ones on the root of your drive. Might have to look at the script to find exact locations...I am not at home right now so I don't have my ext. hdd with the oem project with me. Then navigate to this reg setting and delete the info...

Hope this is what you are asking...if you need more help pm me and when I get back tomorrow I can give more detailed info.

 

To those who still talk with "searchengine" tell him Thanks! Very much appreciate the work that went into this.

Also to all who contributed Thanks also!

Really useful to be able to re-install Windows 7 on peoples Laptops removing all the usual bloat ware.

I couldn't believe the amount of times you had to reply where people couldn't be bothered reading or searching for same things over & over again. I read through all 214 pages & all my questions were answered.

 

Hello all,

There is an issue I discovered when using this OEM activation project. I hope my work-around will help others.

I am using this for a Windows 7 unattended install. The issue occurs when I use FolderLocations in the autounattend.xml:

Code:

            <FolderLocations>
                <ProfilesDirectory>D:\Users</ProfilesDirectory>
                <ProgramData>D:\ProgramData</ProgramData>
            </FolderLocations>

This is for moving \Users and \ProgramData to a 2'nd hard drive when the system drive is a SSD.

What happens during install is the OOBE.CMD is run and the folder locations are moved. Then setup reboots and OOBE.CMD is run a second time. Since the OOBE.CMD supplied deletes itself at the end of the script, setup hangs when trying to run it on the second pass.

My work-around is to rename the OOBE.CMD script to something else, such as OEMACT.CMD, then create a new OOBE.CMD like this:

Code:

@ECHO OFF
IF EXIST "%~dp0OEMACT.CMD" CALL "%~dp0OEMACT.CMD"

I've tested this in a VMWare Player VM with BIOS modified to be HP and with 2 30GB hard drives.

 

This isn't a bug or issue for you are trying to use this project for something else and it wasn't meant for that. Good you found your own workaround though.

 

tnkz por the App !

 

Hello, i can't download oem Query Tool with your link, you have an other?

 

You need to login to view this posts content.