3 ms·

Oh, that's cool! Seems like it's not malicious then (though it may be the case that the media creation tool doesn't allow you to download a higher level of Win1

Oh, that's cool! Seems like it's not malicious then (though it may be the case that the media creation tool doesn't allow you to download a higher level of Win10 - the normal ISO download allows you to install Win10 Home OR Pro during setup, unless your computer has an embedded license key in which case it automatically installs that version). That also explains why I always had to flash the ISO to a USB stick with Rufus (inside VirtualBox) - just `dd` or `cat`ing it onto /dev/sdX never worked.

vetinari 7y ago
If your target is UEFI boot only, you don't need any special tool to make the install media. Just copy all the files to a filesystem supported by UEFI and you are good to go. The FAT32 support is mandatory, and the UEFI bootloader looks into the efi directory in the root to find the boot files. Some UEFI implementations also support NTFS, but that's optional, so it cannot be used on universally usable boot medium. The magic boot sector that all those tools like Rufus create, is needed only for legacy boot. The Windows 10 ISO from the download is using UDF filesystem and is intended for burning. If you dd it to a block device, very few firmwares support that from non-optical drive. Prior to 1809 release, it's install.wim was smaller than 4G, so you could make UEFI installer by just copying all the files to USB drive, but since 1809, the easier way is just to use the Media Creation Tool. The harder way is to recompress install.wim into install.esd, or just use NTFS if your firmware has the support (e.g. Intel NUCs do).