Technical Anshu
Tutorials Blog
💾 USB Copy Error Fix

install.wim Is Too Large to Copy to Your FAT32 USB Stick - How Do You Fix It

The copy stops with "file is too large for the destination file system". Nothing is corrupt — FAT32 simply cannot hold a single file over 4 GB. Three proper fixes below, in the order a technician would use them.

✍️ Technical Anshu🪟 Windows 10 / 11⏱️ 6 minute read
🎥 Building the custom ISO that produced this WIM — watch the full process on video

This problem appears at the very end of building a custom ISO: you add drivers and updates, export the image, and now install.wim is 4.5 or 5 GB — but your bootable USB is FAT32, and FAT32 has a hard limit of 4 GB per single file. Windows refuses the copy with "The file is too large for the destination file system." The strict UEFI-with-Secure-Boot setup wants FAT32, so simply reformatting is not always an option. You have three clean solutions: split the WIM, convert it to the smaller ESD format, or change how the USB is written.

File Too Large

The file 'install.wim' is too large for the destination file system.

install.wim4.72 GB
FAT32 single-file limit4.00 GB max
The exact Windows message when a custom install.wim meets a FAT32 USB stick — the file is fine, the file system is the limit.
1

Split the WIM into .swm Parts with DISM ⭐

Windows Setup natively understands split WIM files — this is Microsoft's own intended solution. Open Command Prompt as Administrator, and adjust the drive letters to yours (D: below is the USB stick):

  1. Copy everything from your ISO to the USB except sources\install.wim
  2. Run the split command (file size is in MB, so 3800 stays safely under the 4 GB limit):
  3. dism /Split-Image /ImageFile:"C:\ISO\sources\install.wim" /SWMFile:"D:\sources\install.swm" /FileSize:3800 /CheckIntegrity
  4. DISM creates install.swm, install2.swm, and so on, directly inside the USB's sources folder — keep all parts together there
  5. Boot from the USB as normal; Setup joins the parts by itself during installation
File Explorer — D:\sources after the split
install.swm3.71 GB
install2.swm1.01 GB
boot.wimunchanged
The result of Fix 1: one impossible file becomes two legal ones — every part under the 4 GB FAT32 limit.
2

Convert install.wim to install.esd (Smaller File)

The ESD format uses stronger ("recovery") compression and is often 25–30% smaller — many images drop under 4 GB and copy as one file. The trade-off: an ESD cannot be mounted and edited again as easily, so convert only when your editing is finished.

  1. Open Command Prompt as Administrator
  2. Check the index of your edition first: dism /Get-WimInfo /WimFile:"C:\ISO\sources\install.wim"
  3. Export it (replace 1 with your edition's index):
  4. dism /Export-Image /SourceImageFile:"C:\ISO\sources\install.wim" /SourceIndex:1 /DestinationImageFile:"C:\ISO\sources\install.esd" /Compress:recovery /CheckIntegrity
  5. Replace the old install.wim in the sources folder with the new install.esd — Setup accepts either one, but never keep both
3

Or Change the USB: Rufus NTFS Mode or Ventoy

If you would rather not touch the image at all, change the media instead:

  1. Rufus: when you write the ISO, Rufus offers its UEFI:NTFS bootloader — the stick boots on UEFI systems while the big partition uses NTFS, so a 5 GB install.wim copies happily
  2. Ventoy: install Ventoy on the stick once, then simply copy the finished ISO file onto it — Ventoy boots ISO files directly, and its data partition is normally exFAT/NTFS, so the 4 GB limit never appears
  3. Note: a plain NTFS-only stick made by hand will not boot on many Secure Boot systems — that is exactly the problem the Rufus and Ventoy methods work around
⚠️ Do not do this: do not chop the file with a random file-splitter or copy a half-written WIM hoping Setup will manage — a truncated install.wim fails mid-install, after your old Windows is already gone. Use the DISM split, the ESD conversion, or the proper USB writers above.

🎥 Building the Custom ISO, Start to Finish

The complete custom Windows ISO process — extraction, DISM conversion, NTLite editing and the final build — on video.

▶️ Watch Full Video
❓ Frequently Asked Questions (FAQ)

Why is there a 4 GB limit at all?

FAT32 was designed in the 1990s and stores a file's size in 32 bits, which caps a single file at 4 GB minus one byte. The limit is per file, not per drive — a 64 GB FAT32 stick can hold many files, just none bigger than 4 GB each.

Does Windows Setup really install from split .swm files?

Yes. Split WIM (.swm) is an official DISM/Windows Setup feature. As long as every part sits in the sources folder with the correct naming (install.swm, install2.swm, ...), Setup reads them as one image with no extra steps.

WIM or ESD — which should my final ISO use?

Use WIM while you are still editing and testing, because it can be mounted and serviced. Produce the ESD at the very end if you need the smaller size for FAT32 media, knowing you would convert back to WIM before any further editing.

This guide is based on the Technical Anshu video on creating your own custom Windows ISO • Stuck on a step? Ask in the video comments — you will get help 🙏