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.

13
  • 4
    Some firmwares doesn't check for boot files in a NTFS partition, someone correct me if m i wrong. Commented Jan 24, 2019 at 16:35
  • 5
    You can compress install.wim to be smaller than 4GB using "wimtools" and "solid" compression level. This way you can simply use FAT32, see tqdev.com/2019-cannot-copy-windows-10-install-wim
    – mevdschee
    Commented Mar 20, 2019 at 18:13
  • 3
    You can significantly speed up the formatting of the stick when you skip filling it with zeros first: sudo mkfs.ntfs -Q /dev/sdc1
    – Rob
    Commented Nov 23, 2019 at 16:26
  • 3
    I came here to say that I too was experiencing the issue described by @VictorAurélio - my laptop would not boot an NTFS partition correctly formatted and flagged with gdisk. I resolved the issue by using FAT32 and the command ` wimlib-imagex optimize install.wim --solid` described in the article linked by @mevdschee
    – testUser12
    Commented Jan 3, 2020 at 2:38
  • 1
    @mevdschee I would warmly encourage you to promote your remark to an answer. It is a sensible option, and it can hardly be spotted tucked under one of several other answers. That could solve the bottleneck of using a fat32 file system and deal with recent installation files that are too big for it. Commented Mar 24, 2020 at 11:35