Article Number: 000127789
Microsoft ISO files for Windows 10 Volume License and maybe others as well are bigger than 4GB in total but also contain an install.wim with a size of more than 4 GB. This does not allow creating for example an USB stick with FAT32 file system and would require use of NTFS instead.
If you want to boot under UEFI you might fail, as not all systems are able to boot from external boot media using NTFS.
Option 1 can be done as follows (DISM commands as available under Windows 10 RS4 – might be adapted to other OS versions):
Extract the required install.wim out of the ISO file or mount the ISO file
Open an elevated command prompt to use Microsoft Windows Deployment Image Servicing and Management (DISM) commands
Run the following DISM command with the correct path to the install.wim to get the index that represents your needed Windows edition:
dism /Get-WimInfo /WimFile:"c:\temp\install.wim"
The output might look like the following:
(Figure 01)
Now extract the right index (3 in this case as I want to install Enterprise edition) into a new WIM file via DISM command:
dism /Export-Image /SourceImageFile:"c:\temp\install.wim" /SourceIndex:3 /DestinationImageFile: "c:\temp\install_3.wim"
This will then look like the following:
(Figure 02)
It reduced the file size from 4.11 GB to only 3.68 GB what now fits within the file size limitation of FAT32. You now have to rename the created file to install.wim
Insert the newly created install.wim into the original ISO file or just copy it onto an already prepared USB stick with all the other needed files from the original ISO
Option 2 can be easily done as follows:
Extract the required install.wim out of the ISO file or mount the ISO file
Open an elevated command prompt to use DISM commands
Run the following DISM command with the correct path to the install.wim and the desired file size in MB:
dism /Split-Image /ImageFile:"c:\temp\install.wim /SWMFile:"c:\temp\install.swm" /FileSize:4000
Now just replace the original install.wim with the created SWM files (install.swm, install2.swm, …)
21 Feb 2021
3
Solution