New
#11
Well, if @Bree is like me, the ISO files we get with the media creation tool has an install.esd file that is smaller than 4 gb.
Odd, the 2004 iso I downloaded from Rufus which I believe comes from Window's servers had an install.wim larger than 4gb.
- update -
I see now why it's different.
The Rufus version is no doubt a multi-edition iso where as when you run the MediaCreationTool2004.exe and before the iso gets downloaded it zeros in on your specifications creating the smaller esd.
My confusion - my mistake..
Last edited by Farvatten; 20 Jul 2020 at 22:02.
These are the editions included in the ISO file created by the Media Creation Tool:
Code:F:\sources>dism /get-wiminfo /wimfile:install.esd Deployment Image Servicing and Management tool Version: 10.0.19041.1 Details for image : install.esd Index : 1 Name : Windows 10 Home Description : Windows 10 Home Size : 14,212,376,596 bytes Index : 2 Name : Windows 10 Home N Description : Windows 10 Home N Size : 13,441,677,475 bytes Index : 3 Name : Windows 10 Home Single Language Description : Windows 10 Home Single Language Size : 14,211,972,277 bytes Index : 4 Name : Windows 10 Education Description : Windows 10 Education Size : 14,450,251,000 bytes Index : 5 Name : Windows 10 Education N Description : Windows 10 Education N Size : 13,693,633,242 bytes Index : 6 Name : Windows 10 Pro Description : Windows 10 Pro Size : 14,450,428,963 bytes Index : 7 Name : Windows 10 Pro N Description : Windows 10 Pro N Size : 13,691,468,430 bytes The operation completed successfully.
It's not up to Rufus, you're just getting a link to download the ISO direct from Microsoft. It is Microsoft's decision to put the larger install.wim in all their direct download ISOs.
The one for 2004 is larger than 4GB partly because .esd uses more compression, but mainly because the 2004 install.wim contains more editions than the install.esd.
Windows 10 2004 Media Creation ToolNavyLCDR said:
As for any advantage of a .wim over a .esd, for install purposes they are interchangeable, but for customising an image you need to start with an install.wim.
Apply unattended answer file to Windows 10 install mediaKari said:
The reason you want the USB flash drive to be FAT32 is to maintain compatibility with most UEFI computers that will only boot from FAT partitions in UEFI mode. If you have no need for that specific compatibility, the flash drive can be NTFS using the same manual creation process. One line gets changed to "format fs=NTFS quick".
...and the reason I want Fat32 is that some of my collection of laptops are Legacy BIOS machines
Legacy BIOS will boot from NTFS no problem. In fact, the default System Partition Windows creates on a legacy BIOS install is NTFS.
I recommend the GitHub project Ventoy. It creates a two-partition bootable USB flash drive: P1 is a 32-MB bootable FAT32 partition that works with both MBR and GPT/EFI boots. P2 is as big as the rest of the USB flash drive, is formatted exFAT and can handle files larger than 4 GB. The program is genius: after booting, it provides a menu of all ISOs in P2 (named Ventoy) and then mounts the chosen ISO as the boot environment. Works like a champ, with Windows and non-Windows OSes. Highly recommended.
--Ed--
PS: @Kari and I have written about this tool multiple times for Win10.Guru. See this Site Search for pointers to those specific items.
Last edited by EdTittel; 21 Jul 2020 at 10:15. Reason: Add user link, fix URL