You can’t even see the Rufus FAT partition here it shows as 0 bytes in Disk Management. Rather than start from scratch (*), I used a little trick to convert the Rufus USB drive to a secure-bootable USB drive: I ran Disk Management, shrank the NTFS partition by 2GB (although 400MB would have been enough), created a FAT32 partition in the free space, then copied over the files listed above. This article is the real gem: it lists the files and folders that must be copied to the FAT32 partition: Option #2 of this TechNet article presents the main principle: your USB drive needs a FAT32 partition with the boot files and an NTFS partition with the rest of the installation media (which may include files that exceed the FAT32 4GB size limit).
In a brief test, I can confirm UEFI boot worked without the procedure below. You should no longer have to disable Secure Boot if you use Rufus 3.17 or later, as the UEFI:NTFS bootloaders being used by these versions are Secure Boot signed. With Rufus 3.17, this workaround is no longer necessary. However, it felt like a challenge to see if it really must be disabled. I wasn’t really worried about disabling Secure Boot for installation-as he says, if you trust the media, it should be okay. Incompatible with SecureBoot”:Īfter some hunting around, I found the Rufus author explaining here and here that his custom UEFI loader (which loads from a small FAT32 partition) isn’t signed by Microsoft and therefore you must temporarily disable Secure Boot until your OS is installed. Unfortunately when booting from this drive, I got the message, “Operating System Loader has no signature. I created the initial USB thumb drive using Rufus and the default GPT/UEFI/NTFS options: I needed to create a USB drive that would boot with the BIOS in UEFI mode.
#Rufus os loader iso
The installation ISO for Server 2016 is about 5.8GB, so it won’t fit on a a standard DVD.