Skip to main content
The 2024 Developer Survey results are live! See the results
23 events
when toggle format what by license comment
S Jul 1 at 11:22 history suggested CommunityBot CC BY-SA 4.0
command was buggy (the ISO is readonly, the folder needs to be created on the target for the boot.wim to be copied into that directory)
Jul 1 at 8:51 review Suggested edits
S Jul 1 at 11:22
Dec 24, 2023 at 9:11 comment added Adrian Maire I think that the following lines sudo mkdir ~/tmp-win10-iso-mnt/sources ~/tmp-win10-fat-usb-drive/ and sudo cp ~/tmp-win10-iso-mnt/sources/boot.wim ~/tmp-win10-fat-usb-drive/sources are not 100% correct: Should it be: sudo mkdir ~/tmp-win10-fat-usb-drive/sources and sudo cp ~/tmp-win10-iso-mnt/sources/boot.wim ~/tmp-win10-fat-usb-drive/sources/ ?
Jan 9, 2022 at 15:00 review Suggested edits
Jan 9, 2022 at 19:58
Jan 9, 2022 at 14:59 comment added Hugh Perkins variant B worked for me :) (tried soooo many other methods first... :O )
Jul 29, 2021 at 14:12 history edited Lirt CC BY-SA 4.0
Added variant B that works for mainboards that cannot boot from NTFS plus some cosmetic changes.
Apr 4, 2020 at 6:28 comment added mevdschee @Lirt, you may add that if this method does not work (many EFI firmwares do not support NTFS), then you may create two partitions (one FAT32 and one NTFS) as described here: tqdev.com/2019-cannot-copy-windows-10-install-wim (no external tools needed)
Apr 3, 2020 at 16:21 comment added Lirt Agree @mevdschee, you should add new answer. I want to keep this answer to be doable without any external utilities on any linux distribution. Thanks for idea with -Q @Alex, I included it in answer.
Apr 3, 2020 at 16:17 history edited Lirt CC BY-SA 4.0
Added `-Q` argument to mkfs.ntfs to skip filling disk with 0.
Apr 2, 2020 at 16:32 comment added XavierStuvw @mevdschee Sorry, I had overlooked this. I encourage you to keep this improvement in mind for when you reach the necessary credentials. Happy hacking on SE!
Apr 2, 2020 at 16:27 comment added mevdschee @XavierStuvw yes there is.. as this is a "Highly active question" and is protected.. you need 10 rep points.
Apr 2, 2020 at 15:55 comment added XavierStuvw @mevdschee Please do create a new answer of your own. There is no reputation threshold for that.
Apr 2, 2020 at 15:26 comment added mevdschee @XavierStuvw thank you for your kind words, but I don't have enough reputation on this site to do that. I hope somebody else will answer it with that content.
Mar 24, 2020 at 11:35 comment added XavierStuvw @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.
Jan 3, 2020 at 2:38 comment added testUser12 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
Nov 23, 2019 at 16:26 comment added Rob You can significantly speed up the formatting of the stick when you skip filling it with zeros first: sudo mkfs.ntfs -Q /dev/sdc1
Mar 20, 2019 at 18:13 comment added mevdschee 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
S Mar 14, 2019 at 23:07 history suggested CommunityBot CC BY-SA 4.0
code misprint
Mar 14, 2019 at 22:55 review Suggested edits
S Mar 14, 2019 at 23:07
Jan 24, 2019 at 16:35 comment added Victor Aurélio Some firmwares doesn't check for boot files in a NTFS partition, someone correct me if m i wrong.
Jan 20, 2019 at 14:25 review Late answers
Jan 20, 2019 at 14:45
Jan 20, 2019 at 14:10 review First posts
Jan 20, 2019 at 14:14
Jan 20, 2019 at 14:06 history answered Lirt CC BY-SA 4.0