Splitting images into 4GB chunks is quite useful if doing UEFI-based offline media deployments.
Note: There are hacks around the 4 GB limits, by using a third party NTFS EFI drivers (but that's not supported by Microsoft). Anyway, see the post below:
UEFI and NTFS – Friends to MDT 2013 at last
https://deploymentresearch.com/471/UEFI-and-NTFS-Friends-to-MDT-2013-at-last
Split image (WIM) support in MDT
In MDT 2013 Update 2 (and Update 1), the split image support is off by default. You enable it by doing the following:
1. In your deployment share, in the file system, navigate to the Control folder.
2. In the Settings.xml file, enable split image support by changing the SkipWimSplit value to False. Like this:
False
What if it doesn't work anyway?
Something I learned, the hard way I might add, is that the above setting may not work. It also requires that the Name (not filename) of your imported operating system actually contains the word .WIM (or .wim).
Note: This is a confirmed bug in MDT 2013. Fixed in the latest release.
The imported image with a ".wim" in the name.
The images in the offline media after splitting, now having the SWM extension.
Thank you for this – continues to be helpful in 2026 and beyond. Split wim! (But only if you call it a wim). Dang it Microsoft.
gracias =)
Johan,
I just had the same issue with WDT not splitting the files because I renamed the OS and removed .wim.
Thanks for you post, and for leaving it up.
One thing, though. It works for me regarding the image, but litetouchPE boot image remains bigger then 4GB, so I'm still unable to use FAT32 formatted USB media.
I have never seen a boot image that is 4GB in size. Something must be up in your deployment share. Make sure that your media folder is outside of your deployment share folder.
It's actually HP's new policy. Their touchpad laptops are now classified as system-class so had to add them to PE.
IF you have a dedicated selection profile for the boot image drivers, you can add the few system-class drivers that are needed (only).
Hmm, your comment made me thinking and I figured out, it wasn't the system-class drivers making it so big. I messed up the selection profiles… After fixing, it's ~3.3GB now. Additionally, I discovered a problem with USB media not booting because of 'insufficient memory to create RAM-disk', so I'm about to check it changing boot image size fixes this one too. So far, thanks for your remark. I'll keep working.
I can now confirm, that newly generated media content works fine. Boot image stays way below 4GB (3.3GB mentioned) and PE booting problem gone. Also, I can now have USB-stick FAT32 formatted.
Big, big thank you again for bringing attention to fact that boot image huge as my previous one, is something that is not supposed to take place.
Hi Johan, thanks for the useful information. Could you be a bit more specific in how to change the "label" of the operating system? Do you mean the "Name" of the indexed OS in the WIM image? I don't seem to find any more info about this
Yes, Label = Name. I have updated the post. Thank you.
Where is the label of the imported operating system defined?
It comes from the WIM meta information (which can be changed). I usually just rename the label after import.