Can be done to windows 7 also doesn't matter If u have ISO without setup files and u don't wanna burn it to DVD or use USB or HDD to boot the setup And Just run setup.exe from the current OS This will be helpful Steps Go to This PC click right mouse on the virtual DVD of ISO and click copy Paste to C:\, right click mouse again on and choose paste Go to sources dir choose to open boot.wim with 7zip Like c:\<ISO dir>\sources\boot.wim\2\sources Copy all the constants dirs and files to same dir boot.wim is Run setup.exe from sources or the upper dir Done
i just deploy it with gimagex and add the boot entry with easybcd and reboot to it no argument the other ways are better
Windows already copies the files when running installprep.exe, which is called by the [root]\setup.exe Does this method differ in functionality? I guess what I'm saying is... Why use this over just mounting the iso and running setup?
in this situation where cant start setup.exe but if installprep and winsetup.dll exist it will fix this problem or need more files ?
Oh... Yes, if you remove all the files in the sources folder you'd have to manually copy stuff. Why don't you just make a sfx setup file that extracts all the required files from boot.wim index 1 and runs setup.exe? installprep also does the Keep programs and settings stuff. You can safely delete the sxs folder, but for the rest... it depends what they're upgrading from. If you're going to go around liteing you should just leave it as lang.ini and setup.exe and just tell people to boot install only. The whole point of upgrading is to keep your existing files and settings. without the whole installprep part, you wouldn't be able to do that.
Is that mean that if I don't plan to setup from inside Windows or upgrade from previous version, I just need 3 files in my sources folder ?
4, but yes. Minimum requirements for both uefi and bios boot installs are as follows: [root]\bootmgr [root]\bootmgr.efi boot\bcd boot\boot.sdi efi\boot\bootx64.efi efi\microsoft\boot\bcd sources\lang.ini (matching the lang.ini in bootable index of boot.wim) sources\setup.exe (also needs to match the one inside boot.wim) sources\boot.wim (just need the bootable index, don't need both) sources\install.wim, or install*.swm, install.esd I don't know if the [root]\setup.exe is required, but it's tiny so there's no point removing it.
Thanks for this extensive information. But I think deleting setup.exe from root is good, to prevent users from trying to setup from windows (I will test that).
You are right about the boot.wim Murph and i did say it was relatively useless. Here are a few scenarios. If you sfx setup files for upgrades you can have a dummy (100 kb) boot.wim included so all you need to add is install.wim. You go to upgrade but mainly use a WinPE as a boot.wim that has no flag 9 set (needed for setup to continue with an upgrade). You boot in EFI and need your boot.wims on a Fat32 partition but you want to use install.wim from an NTFS partition where a boot.wim is required for setup but you will never boot from it. You don't use vanilla boot.wims but rather Winpe_se and have them all named like my picture; Win8.1SE_x64.wim, Win8.1SE_x86.wim etc and want them all properly named instead of one of them having to be named boot.wim. Petty, but viable if i needed\thought of by me in my tinkering. The setup.exe is the important part of my last post. It's where i see the majority of peoples problems with all in one ISOs. They always have an x86 DVD:\sources\setup.exe when they run the setup.exe in an x64 boot.wim. And once you change one, you can do every OS since Vista. I have a 128 gig USB with a 60 gig NTFS partition (x86 boot.wims, every mbr bootloaders, install.wim, Apps, visible in windows, active,/nt60), 20 gig Fat32 (efi dir, x64 boot.wims, Ubuntu, Fedora, Pmagic, Kali, not visible in Windows, etc), 20 gig HFS (Mountain Lion and Mac Apps), and 8 gig HFS (Mavericks) that serves me well in every possible scenario for every possible OS. I have run into every possible boot error for every possible OS and have pretty much mastered the art of loading kernels from USB.
In your 'Modified E2B' why you have added above .efi files ? What function these .efi files performed during UEFI booting ? Regards.....