@Akeo When I let Macrium Reflect create the bootable USB drive, it creates a GPT / FAT32 partition. When I try creating that USB using Rufus using the ISO from Macrium, file system is locked on NTFS and I can't change it to FAT32 unless I change from GTP to MBR, why is that? How is Macrium Reflect able to do that ?
@Super Spartan, Without seeing the full log of how you created the drive in Rufus, or, better, access to a Macrium ISO, I have no insight into what you report, and I simply cannot answer your question. Is there any ISO you might be able to share with me? You can e-mail me a link to pete@akeo.ie.
Thanks again for providing the data. As I explained privately, what you are seeing is the normal behaviour of Rufus for Windows-based ISOs, and Macrium happens to be Windows-based. The reason why FAT32 is disabled by default when selecting MBR, and only NTFS is enabled, is to try to ensure BIOS-boot only, since most UEFI platforms do not include an NTFS UEFI driver that allows them to boot from NTFS partitions (though I have to say this is starting to change on modern UEFI systems, that are starting to include an NTFS driver alongside the FAT32 one). So this means that, on most systems, if you plug such a media, Windows can only be installed in BIOS/Legacy mode, which is what you should expect from what you got in the Rufus UI when you created the media, as it notified you that the _Target system_ type would be for BIOS/Legacy. It should also be noted that, as you also have seen, Rufus defaults to selecting GPT as the partition scheme when picking a Windows-based ISO, so as to default to UEFI-only boot (since GPT is not compatible with BIOS boot). We are doing this because we have seen way too many people using the Microsoft Media Creation Tool ending up installing Windows in BIOS/Legacy mode on UEFI systems, which, besides not being able to use modern platform features (or modern security features such as Secure Boot), can lead to major issues in the long run, such as being unable to upgrade to Windows 11... So Rufus does make sure that if you do want to install your OS in BIOS/Legacy mode, you have to take explicit action to change default options, and that, in doing so, you are made aware that the media you create will be for BIOS/Legacy installation and not UEFI installation. Again, this is different from the MCT behaviour, that creates media that can be dual BIOS+Legacy booted, but that, again, lets too many inexperienced users end up with a version of Windows that was installed in BIOS/Legacy mode on UEFI compatible systems. Now, if you really do want a dual BIOS+UEFI bootable media (in which case you will be offered to option to use FAT32 with MBR for Windows-based ISO), you can use Alt-E in Rufus to enable this feature.
@Akeo I remember you mentioned before that for an ISO with a size larger than 4GB, one must disable Secure Boot to boot to the USB because of some driver limitation. I just used this tool to make a 6GB ISO into a 4GB ISO, perhaps this gan be implemented in Rufus and done within the app itself? Windows ISO With Install.esd/Install.swm Creation Tool
Hi everyone, I wanted to know why when I go to make a USB with RUFUS 4.3/4.4 at the end of the process it gives me an error (but in reality the USB works). With RUFUS 3.00 this problem does not exist... are there any fixes?
Why is this warning an error from Black Lotus Secure Boot vulnerability using rufus latest releases? And how to solve this issue? @Akeo