Skip to main content
The 2024 Developer Survey results are live! See the results

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Commenting just to remind myself to upvote if it works. Commented Jul 11, 2019 at 19:44
  • It does work. The target-filesystem option --tgt-fs NTFS is necessary because the files in the new Windows installations are larger than 4GB and cannot be supported by a fat32 file systems. fat32 file systems are essential for UEFI boot loading. However, woeusb works around this under hood and produces a USB immediately recognized with Secure Boot disabled (and provided the device's boot loader has the USB drive suitably high of its priority list). I did not need to add the boot flag to any partition. Commented Mar 24, 2020 at 15:48
  • for anyone that lands on this in the future, be aware you need to unmont the partitions but not the disk, e.g /dev/sdb1 , /dev/sdb2 once thats done the application will work, /dev/sdb doesn't need to be umounted. If one uses the gnome file manager it will unmount the entire disk and woeusb won't find it. also you need an active internet connection as the uefi-ntfs.img file is downloaded from github, it depends on the Rufus project for that.
    – Darragh
    Commented Mar 28, 2020 at 10:26