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

alphanumeric · 06 Jul 2017

Was just copying over the files from my mounted Windows 10 (multi edition) MSDN ISO and got that message. It's formatted as Fat32. This is the just newly released last month ISO. Looks like I'll have to use NTFS? This may be an issue for those that need Fat32 for UEFI installs.

The file "install.wim" is too large for the destination file system.-install-media-capture.png

Bree · 06 Jul 2017

alphanumeric said:

... Looks like I'll have to use NTFS?

exFAT can handle files larger than 4GB too....

....This may be an issue for those that need Fat32 for UEFI installs.

Interesting dilemma....
....I wonder what the answer is?

alphanumeric · 06 Jul 2017

Bree said:

exFAT can handle files larger than 4GB too....

Interesting dilemma....
....I wonder what the answer is?

This is my MSDN ISO, I don't know if the MCT download has the same issue? My laptop will do a UEFI install with NTFS. My wife's laptop I'm not sure? All my other PC's are legacy. I guess you'd have to do a split wim?

Bree · 06 Jul 2017

alphanumeric said:

I don't know if the MCT download has the same issue?

The MCT creates media that uses an install.esd rather than an install.wim - esd is a compressed format so it should be smaller. The MCT currently makes media for 15063.0 with a 3.9GB install.esd

alphanumeric · 06 Jul 2017

Bree said:

The MCT creates media that uses an install.esd rather than an install.wim - esd is a compressed format so it should be smaller. The MCT currently makes media for 15063.0 with a 3.9GB install.esd

Ah, OK. I hardly ever use the MCT. Usually just for testing if somebody reports an issue. Otherwise I use my MSDN ISO's.

Bree · 06 Jul 2017

If it helps, you can convert an install.wim to an install.esd using Dism.
Converting the install.wim in install.esd file
in fact, Kyhi's command in the above link just copies across the image for index 1 (which is Pro, I believe). If you want an esd with more/all versions in it apparently you'd need to use a seperate Dism command for each index.
https://social.technet.microsoft.com...w8itproinstall

alphanumeric · 06 Jul 2017

Thanks, ill keep that in mind. Might come in handy at some point.

Superfly · 06 Jul 2017

alphanumeric said:

Was just copying over the files from my mounted Windows 10 (multi edition) MSDN ISO and got that message. It's formatted as Fat32. This is the just newly released last month ISO. Looks like I'll have to use NTFS? This may be an issue for those that need Fat32 for UEFI installs.

Yup .. posted these results a while back...Cumulative Update KB4020102 Windows 10 v1703 Build 15063.332 - Page 10 - Windows 10 Forums

Seems to EFI install use or... .esd, Rufus (our buddy @NavyLCDR 's best mate) or break the .wim into .swm's.

alphanumeric · 06 Jul 2017

Also not a big fan of Rufus. It won't be an issue for me until I have to redo my wife's Acer Laptop. All my other PC's are fine with NTFS install media. I'll cross that bridge when I come to it.

alphanumeric · 09 Jul 2017

MCT ISO is fine with Fat 32 thumb drive. Just made one up as a test. I did it manually via diskpart etc, not with he MCT itself. If you are doing anymore than one thumb drive the MCT is a PITA. You have to keep rerunning it and it wants to download the whole ISO every time. I do one download of the ISO and use that to make multiple install thumb drives. I customize my thumb drives for each PC so they end up all be unique in the end. If your wondering why I make more than one drive.