Well I guess since no one else has suggestions for the EI.cfg being broken we can officially pronounce that method dead when doing upgrades. R.I.P. EI.cfg, you will be missed!
Agreed. I'm going to start removing mine next month and require ppl to enter the default keys or gvlk
I've been playing around with multiple sources using different sources files and folders for my SuperAIO v2. I'm getting stuck at a couple things. 1) I'm trying to enable booting to both UEFI boot mode and BIOS mode by editing the corresponding BCD files. On an ISO it boots ok, but on my real system it errors and fails. 2) I'm having errors once inside different sources directories from boot. It's giving me drivers not found errors. Do you have any ideas on that? or should I make some sort of partitioning/apply/bcdboot script?
Its much easier Just put a folder "Langpacks" in the source Root. You can put there your language (de-de\lp.cab), but you dont have to. Then Setup will start as in Windows 8, and you can choose your edition if you also put ei.cfg to the Sources folder. If you put your languages into the "langpacks" folder (just copy content from languagepack iso), and change the lang.ini in the sources folder, you also are able to choose setup and installation language Setup is still english. Have to test if installation installs languagepack after Windows installation.
^^please post SS AS of now All the header and value is mandatory Example Code: [EditionID] Professional;core;Enterprise [Channel] oem/retail [VL] 1/0 if we leave the value field blank then, we would receive "setup could not validate the product key error" if the edition id feild value is given either "Professional or core or Enterprise", no matter what the first listed index of that particular edition is chosen even if we have installed 64 bit window,the 32 bit version will be selected by default if it is the first indexed image in wim for example i have installed win 8 pro X64 and i am running setup as a in place upgrade [ within windows ] then setup checks the EI.cfg file and in Ei.cfg file the following is present Code: [EditionID] Enterprise [Channel] Volume [VL] 1 and in the wim the following index are present Code: 1. Windows 8.1 Core X86 2. Windows 8.1 Pro X86 3. Windows 8.1 Enterprise X86 4. Windows 8.1 Core X64 5. Windows 8.1 Pro X64 6. Windows 8.1 Enterprise X64 no matter what "3. Windows 8.1 Enterprise X86" is being automatically selected by setup now if i put a pid.text with key and the value feild of edition id left blank then also the below result appears 1. Genuine Retail full pro key - can not validate key 2. genuine retail upgrade pro key - can not validate key 3. Oemm pro key - can not validate key 4. System builder oem pro key - can not validate key 5. Oem m core key - can not validate key so with current status the Ei.cfg could be used only to bypass key prompt and not to choose edition.
yes you are correct if we put a empty folder with name "Langpacks" in root and add a ei.cfg file to source folder the the setup works just like any previous versions. will test further and report here
I'm pretty familiar with autounattend.xml, but is there a switch for setting an upgrade? Because running setup for upgrades\install will look for autounattend.xml in the DVD:\sources*whereYourSetupexeWasRun*\autounattend.xml and use it by default. If you set the key, it will only find that edition, but you can use an autounattend thats not in the root specific to the OS. The problem is it wants to start a fresh install, so if there is an upgrade switch you can "kind" do something similar to the efi.cfg trick. I tried an upgrade of a Win8 pro x64 kms activated from my win8x64 (not 8.1) and upgraded to Win8.1 pro without asking for a key. It ran the compatability report, said i needed to uninstall itunes and avisynth, but i clicked next and its on the collecting files and such portion of upgrade at 20%.
By hex edit, do you mean patches to the runtime in setup.exe? I'm wondering if the 8.1 setup.exe could be patched to skip the prod key input much like the ei.cfg method worked w/8.0 , or how it still works with 8.1 boot-mode install?? Has anyone traced 8.1 setup.exe? I find 8.1 "installation unfriendly". Even aside from activation issues. Maybe upgrades will be smoother for 8.0>8.1 with whatever they post to the store at GA time.