4 ms·
Also a Linux user, but back in the Windows days you could use Diskpart to do so: select disk ## clean create partition primary active forma
by RMPR 5y ago
Also a Linux user, but back in the Windows days you could use Diskpart to do so:
select disk ##
clean
create partition primary
active
format fs=ntfs quick
assign
Then just extract the disk image to the USB Drive and voila. I just noticed it's even documented on Dell's support page[0]
0: https://www.dell.com/support/kbdoc/en-us/000136959/create-a-bootable-usb-flash-drive-using-the-diskpart-utility https://www.dell.com/support/kbdoc/en-us/000136959/create-a-...
- mrjin 5y agoI have to say that M$ has screwed up diskpart in some versions of Windows. Sometimes it simply cannot clean the disk correctly after being formatted using some other tools such as Rufus.
- josteink 5y agoThat’s not a feature of Windows, but simply how UEFI works. https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how-does-that-actually-work-then/ https://www.happyassassin.net/posts/2014/01/25/uefi-boot-how...
- josteink 5y agoKey quote because my linked article is quite extensive: > What the firmware will actually do when trying to boot in this way is reasonably simple. The firmware will look through each EFI system partition on the disk in the order they exist on the disk. Within the ESP, it will look for a file with a specific name and location. On an x86-64 PC, it will look for the file \EFI\BOOT\BOOTx64.EFI. What it actually looks for is \EFI\BOOT\BOOT{machine type short-name}.EFI - 'x64' is the "machine type short-name" for x86-64 PCs. The other possibilities are BOOTIA32.EFI (x86-32), BOOTIA64.EFI (Itanium), BOOTARM.EFI (AArch32 - that is, 32-bit ARM) and BOOTAA64.EFI (AArch64 - that is, 64-bit ARM). It will then execute the first qualifying file it finds (obviously, the file needs to be in the executable format defined in the UEFI specification).