Windows 8.1 EI.cfg Broken?

pilot uses a hybrid setup with x64 files in a folder such as sourc64 instead of sources. If you're really good with hex editing, you could even fix the files so that they not only point at the new directory, but also are modified well enough that the file thinks it's still legit signed. It saves room putting both x86 and x64 versions on the same disc because about 50% of the x64 indexes are x86 files, which are already saved to the install.wim or install.esd

It does cause some problems with UEFI booting, which is why I stopped doing it, but for normal bios booting, it's not bad...

 

Thanks for responding. I guess my question is whether the upgrades discs have the ei.cfg file added or not?

 

You can upgrade with an ei.cfg but it has to be set to a specific [EditionId] such as:

Code:

[EditionID]
Enterprise
[Channel]
Volume
[VL]
1

If you omit the ei.cfg you can enter the key. If you have an ei.cfg and it's not set to any specific EditionID, you cannot keep programs and settings.

 

You need to login to view this posts content.

 

maybe we need an underlaying ACTIVATION ("Data.dat")!??!!?

 

The file was deleted from the MEGA! Its leveling up another server? Thank you!

 

Hi,

Maybe this thread is not the most adequate, but here it goes.
I'm trying to create a ISO with Windows 8.1 x64 ENT EN and PT, i know you can install Lang packs with ENT... I have a legit KMS server, since its not announcing through DNS i need to execute slmgr /skms server, i manage to do this with an autounattend.xml, and in settings pass OOBE i use the Microsoft-Windows-Shell-Setup component that allows to execute first logon commands. And everything works flawlessly, the problem is when i try to upgrade, i cannot upgrade, never....the setup doesn’t even asks. The problem is the autounnattend.xml, if i remove the file its possible to upgrade otherwise is no go. I tried to figure out what in the file was creating the issue, and its the settings pass "WindowsPE", if i remove the settings pass "WindowsPE" i'm able to upgrade the rest of the autounattend.xml its not executed.... no kms server neither my logo and company name....

Does anyone has any idea, how i can solve this problem?

Thanks in advance

 

You need to login to view this posts content.

 

Hi and thank you for the response,

I'm using the EI.cfg file like this :

Code:

[EditionID]
Enterprise
[Channel]
Volume
[VL]
1

I tried upgrading from:

Windows 7 enterprise x64 EN -> Windows 8.1 Enterprise x64 EN
Windows 8 enterprise x64 EN -> Windows 8.1 Enterprise x64 EN

With no luck, i can only upgrade if i remove the autounattend.xml, or the section which contains the Settings pass "WndowsPe"

 

You can always leave it in and just reformat the partition using boot setup

 

Yes i know, and if i remove the autounattend.xml it also allows to upgrade. But i need to set the kms server, and without the autounattend.xml i dont know how to do that...

Thank you for the help anyway

 

Make folder structure $oem$\$$\Setup\Scripts\

Inside scripts\ make setupcomplete.cmd
Edit setupcomplete.cmd to look like:

Code:

cscript %windir%\system32\slmgr.vbs /skms 666.666.666.666:6666
cscript %windir%\system32\slmgr.vbs /ato

Toss the $oem$ folder into the sources\ directory in your iso

 

Thank you i will try that out.

Another thing its not very important, but if i could set the logo and company name without using autounattended.xml would be perfect.

Thanks

 

Hmm... I believe you can do that with an OOBE.cmd OEM folder, but I'm afraid I don't know that much about it

 

In the old days it worked like this.

 

Removed the Autounatend.xml.

Created the structured you said $oem$\$$\Setup\Scripts\ and inside there a setupcomplete.cmd with :

Code:

cscript %windir%\system32\slmgr.vbs /skms kms.server.address
cscript %windir%\system32\slmgr.vbs /ato

And now i'm able to upgrade my windows 8 instalation, the problem is the setupcomplete.cmd doesnt run on the upgrade, only works with clean install....

I'm again stuck.....

After upgrade i only have this inside c:\windows\setup\state\state.ini

Maybe and since its not clean installing he doesnt execute the setupcomplete.cmd, i'm trying to find if there is a $oem$\$$\upgrade\ or even a upgradecomplete.cmd but i dont think so....

 

You might be doing something to prevent things. It should run the script regardless of the setup method.
Are you running setup.exe from the root of the iso?

 

Yes i am running from the root of the iso

If i boot from the ISO and clean installing the scripts are executed... I copied the scripts DIR inside the install.wim, to /windows/setup/, maybe it will force it to run

It's upgrading now, i will be back with news eheh