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

It's going to be interesting to see how MS resolves this dilemma... ESD's are fine but do not support servicing...

 

Another option is to load NTFS EFI drivers (See The rEFInd Boot Manager: Using EFI Drivers) or boot from PE and install with DISM.

 

Hi,
@lx07 : Isn't that what Rufus is using ?

In order Rufus to work (i.e. create a second partition) to work you'd need a flash drive that supports it, such as that Sandisk Glide, correct ?

Cheers, *Wink

 

I think that is what Rufus does, yes, makes a FAT partition with EFI NTFS drivers then NTFS partition.

What I meant was you could boot from FAT formatted PE rescue disk (or you could put bootloader like rEFInd instead) and then install Windows from a separate NTFS USB containing the .wim. This method would be a bit redundant now I suppose as I saw this describing setting up on one USB

WinPE: Create USB Bootable drive | Microsoft Docs

You can partition any flash drive with multiple partitions - no need for a special type. At least I've never had any refuse. The only issue AFAIK is Windows prior to 1703 would only recognize the first partition unless it the drive was seen as fixed.

 

Hi,

Thanks for that. I wasn't aware MS fixed that. I had the impression it was hardware dependent.

Cheers, *Wink

 

See, the thing is, the average joe isn't going to want to go through all these hoops just to install Windows. The more tech savvy will just grin and bear it, but the not so tech savvy will just get frustrated and say WTF Microsoft? A lot will likely just turn secure boot off and do a legacy install.

That being said, the ISO I downloaded via the Media Creation Tool was fine, and worked with fat 32. It hasn't been updated like the MSDN ISO though, its an older version. The MSDN ISO is newer and doesn't work with fat 32. Those with MSDN access will more than likely fall into the more tech savvy group.

If the media Creation Tool remains fat32 compatible it won't be a big issue for most.

 

Hi,

Surely MS is aware of that. IP installs keep on having smaller and smaller footprints.
OTOH, MCT created media or ISO are only good for installing the OS. Ideally you'd want a .WIM file as @Superfly has pointed out.

Cheers, *Wink

 

Pros and cons with each ISO. The MCT "Windows 10" ISO is Home, Pro, Education, and I believe Home SL. I can go from Home to Pro or Pro to Education etc with a simple change product key. My MSDN ISO is just Home and Pro. Education is a separate ISO, as is Home SL. I installed Education with my MSDN ISO and can't change to Pro with change key. I had to reinstall to go back to Pro. If I had used the MCT ISO I could have toggled back and forth with a key change. I could in the past anyway. I haven't tried it lately.

 

Hi, Rufus author here.

No. There's no need for a special flash drive (or even one with the fixed attribute). The UEFI:NTFS partition that Rufus installs is copied wholesale, because it's very small, so it does not need to be mounted in Windows. Which means that you could use any El Cheapo USB Flash Drive with the removable attribute in a version of Windows that does not support mounting multiple partitions (such as any version of Windows before 1703), and it will still work.

Note that, if you use UEFI:NTFS, you may have to temporarily disable Secure Boot if it's enabled. But, you shouldn't equate that with a security risk. See the second part of this FAQ entry for details.

 

Hi,

Thank you for provided the information. I'' ll give it a shot.

Cheers, *Wink