Install Win8/Windows 8.1 UEFI With a Over-sized(over 4GB) install.wim

Could not find kernel image: wsetup

 

I could not read and understand all post here but to install onto UEFI computer with over 4GB install.wim on UFD is very easy and I have done this for a few years ago.

Just split Install.wim to Install.swm file sized 4000MB...that all.

You can use this to make multi-DVD setup as well. Windows setup will automatic ask for 2nd, 3rd, 4th and so on disc when it finish read/copy/apply file(s) from disc 1.

Hope this help

 

Hiya,

I have created a bootable USB pen drive formatted as NTFS with Win 7, 8.1 x64 & 8.1 x86 ISOs on there using the program WinSetupFromUSB, but then I tried it today on a Win 8 UEFI laptop and it refused to recognise it, but worked if I changed it to Legacy no problem. I have since discovered that UEFI cant recognise ntfs and thats how I got directed to this thread....
So my question is, has anyone managed to get this ntfs method to work with the WinSetupFromUSB program? Or is there an easier way to achieve multiple UEFI bootable Win ISO's on one USB stick?

I've read through this post a few times but I'm still confused, I'm not a noobie by any stretch but some of the lingo goes beyond my knowledge

Thanks

 

hmmm this is starting to get complicated.... haha

Looking at it another way,
I've booted from a USB disk formatted as FAT32 and loaded a efi shell using this Linux ISO (regular-rescue)
Loaded the ntfs.efi file succesfully
Then I do a "map -r" and get
FS0 Alias BLK2 USB HD(1, MBR)
BLK0 SATA
BLK1 USB
BLK3 USB HD(2, MBR)

I then connect my ntfs USB memory stick and do another map -r
FS0 Alias BLK4 USB HD(1, MBR)
BLK2 SATA
BLK3 USB
BLK5 USB HD(2, MBR)
BLK0 SATA
BLK1 USB

The numbers seem to have got all jumbled up and there are an extra 2, but no extra file system, what have I done wrong?

I have also tried turning laptop off, connecting both USB memory sticks and then powering on but it has the same result.

Also tried using your startup.nsh script and that returns this
"error. no mapping found
'fs1:' is not a correct mapping"

 

It didnt recognise the mount command, but nevermind I dont think this is worth the effort now anyway.

Thanks for all you help!!

 

This can be fixed by adding a \sources\ei.cfg file to the same folder as \sources\setup.exe and \sources\install.swm.

The ei.cfg file should match your version (OEM, Volume or Retail) and is used to stop the Enter Product Key box and this prevents the error.

e.g.
[EditionID]

[Channel]
_Default


[VL]
0
​

 

I know this is not the case because I have been using ei.cfg for years & I get the split wim issue. I do have an old 4.3GB install.wim split that does work. All my new attempts fail.
The swm files are good because I can use dism to apply them successfully...

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

Or you guys could just use the diskpart/apply script from my sig. It's pretty much the reason I made it.
As for alternatives... the sources\ licensing stuff makes sense... I haven't personally tested it since I mostly deal with AIOs...

You could also try converting to esd if it is less than 4gb, that would fit in the fat32.

 

enterprise version causes this. it took my several days to find it.

 

Just going back to Clover and booting to Windows bootx64.efi - there is no need to use the startup.nsh and wsetup.nsh scripts - it can all be done automatically

1. Copy ntfs.efi to \EFI\CLOVER\Drivers64 folder
2. Edit the \EFI\CLOVER\config.plist to remove the Hide entries - I just put XXX in front of the strings

Code:

    <dict>
        <key>Hide</key>
        <array>
            <string>XXXWindows</string>
            <string>XXXBOOTX64.EFI</string>
        </array>

That's it! The GUI icon for the windows bootx64.efi file will now show up and the 'boot UEFI internal from xxx' Clover icon will work.

 

You need to login to view this posts content.

 

Or

1. Extract the ISO to a folder on your system HDD
2. Use the Windows ToolKit to split the install.wim
3. Run MakePartImage to make a FAT32 partition image from the folder and remove/make EI.cfg file
4. Copy the image file to your Removable NTFS E2B drive

Rinse and Repeat for all other ISOs.

 

Hello Sir,

I am a regualar user of 'E2B'. I am also interested in 'Mac'. As far as I know no one can help me other than 'HALIKUS' and 'Steve'. After lots of search finally I found a expert ( i.e. 'HALIKUS' ) who already did each and everything what I always want to use.

So I want to use both 'Modified E2B' and 'rEIFind' according to your method. So please give me a simple Tutorial for both.

My Email ID is - krishnadevanand92 @ gmail . com


Thanks for such a great 'Modified E2B' ....................

 

Hello Sir,

I like above feature too much. But Emergency never provide sufficient time to create \sources, \boot\ and _ISO dirs within Internal or External HDD.

Is it possible so that 'Modified E2B' scan all HDDs (both internal and external) and FDDs for ISOs, IMGs, Windows ISOs, etc ?
So that I can utilize ISOs, IMGs, Windows ISOs, etc within from Internal or External HDD or FDD without any limitation of creating \sources, \boot\ and _ISO dirs.

Currently 'Modified Stripped version of E2B' does not scan External HDDs for possible \sources, \boot\ and _ISO dirs. Please do something so that I can also boot ISOs, IMGs, Windows ISOs, etc within from an External HDD too.......................

Thanks for your Unique and Great Work..............