That's normal, it has to jump to the other install.swm and continue exactly where it left off. In the meantime, there are enough programmes like Rufus that can handle an install.wim/esd that is larger than 4GB.
Yeah, I just found it strange that he had to create each file (.SWM) with the full size of the image, instead of "incrementing" it with the partial size specified in the /Filesize parameter of Dism /Split-Image. And with this, exponentially increasing the time during the copying files process. I did a test here by splitting the WIM file into 4 parts of 1 GB. Thanks!
4 parts a 1GB, I would divide them differently, I think the more parts you have, the longer it takes to find the next file. I don't know exactly how this works, whether every install.swm is looking for a hash, but jumping and finding the end of the file takes a lot of time. Code: Split Install.wim Dism /Split-Image /ImageFile:C:\images\install.wim /SWMFile:C:\images\swm\install.swm /FileSize:3000
It looks good, as long as the split fits into the norm. You also have to consider that the hardware used also plays a role in how long it takes.
The size of the swm files shouldn't really influence the install speed, the fact that they are swm does, setup needs to copy them first to be able to apply them, wim and esd can be applied directly.
Exactly! With a single Install.wim file, this step runs much faster compared when using split files. This is just an experience report of someone who has nothing to do at home.
Quick stupid question: If I wanna add an app to windows image, for using it in windows setup in command prompt(when you press shift-f10), in which .wim and which index I should put it in?