Edit 6: a major edit
Now we talk about the github version of woeusb
The github version is at 5.1.3 and works in Ubuntu 20.04.x LTS (and 18.04.x LTS, probably all current versions of Ubuntu, but I have not tested them).
PPA version of woeusb
deprecated
Please be aware that the woeusb
PPA version at ppa:nilarimogard/webupd8
is deprecated (works in Ubuntu 18.04.x LTS but fails in 20.04.x LTS). Today (2021-11-07) it is at version 3.3.1 (dated 2020-02-13).
Test
-
From the WoeUSB github I downloaded and tested
woeusb-5.1.3.bash
as well as the version in the tarball. They differ only in the line specifying the version. So I used the separate version with explicit version number. -
I used the command line
sudo ./woeusb-5.1.3.bash --target-filesystem NTFS --device Windows11.iso /dev/sdx
-
wimlib-imagex
was not found, andwoeusb
quit. It can be installed from the repository universe with the commandsudo apt install wimtools
It is needed, when installing into a FAT32 file system in order to split the huge
install.wim
file, but when selecting NTFS, the installation should continue withoutwimtools
. That way the WoeUSB bash shellscript will work withoutwimtools
(but it wants an internet connection in order to getuefi-ntfs.img
). -
The USB drive with Windows installer
- created in 18.04.6 LTS and 20.04.3 LTS
- boots both
- in UEFI mode (also with secure boot) and
- in BIOS mode (alias CSM alias legacy mode).
end of Edit 6
I tested the current woeusb
from the PPA (running a persistent live Lubuntu 18.04.1 LTS), and the following command lines work for me.
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt update
sudo apt install woeusb
sudo woeusb --target-filesystem NTFS --device path/windows.iso /dev/sdx
In my case the iso file was in /media/lubuntu/usbdata/images/
and the target device was /dev/sdb
, but in your case check carefully that you will write to the intended drive (avoid destroying valuable data in some other drive),
sudo woeusb --target-filesystem NTFS --device /media/lubuntu/usbdata/images/windows.iso /dev/sdb
Notice that all partitions on the target device must be unmounted.
The created USB boot drive has a small FAT partition (for UEFI boot) and a big NTFS partition with the Windows files. It can install Windows both in BIOS and UEFI mode with woeusb 3.2.10.1
(dated 2018-09-19 (Sept 19 2018) in the PPA).
Using NTFS makes it is possible to use file size > 4 GiB. The size of install.wim
is
-
smaller than 4 GiB in some of Microsoft’s own iso files, for example in
-
Win10_1809Oct_Swedish_x64.iso
$ <<<'scale=3;4274234443/2^30' bc 3.980 # < 4 GiB
-
greater than 4 GiB for some iso files for particular computers, OEM, but also in several of Microsoft’s own iso files, for example
-
Win10_1809Oct_English_x64.iso
$ <<<'scale=3;4396229344/2^30' bc 4.094 # > 4 GiB
-
Win10_1809Oct_EnglishInternational_x64.iso
$ <<<'scale=3;4386496792/2^30' bc 4.085
-
Win10_1809Oct_German_x64.iso
$ <<<'scale=3;4401709065/2^30' bc 4.099
-
Win10_1809Oct_Spanish_x64.iso
$ <<<'scale=3;4404104344/2^30' bc 4.101
There is also a GUI version woeusbgui
. I don’t think is has the option to create a target drive with a FAT file system for UEFI plus an NTFS filesystem, so I would recommend using the command line version woeusb
.
Edit 1:
You can do it yourself with detailed help at
help.ubuntu.com/community/Installation/iso2usb/diy/windows-installer-for-big-files
This method works in both BIOS and UEFI mode and also with secure boot. (But in most cases it should be possible to turn off secure boot, use the drive created by woeusb
, and turn on secure boot again.)
Edit 2:
Thanks @John for your comment that there should be no space character in the source file name. If there is you can rename the file, and then woeusb
works.
Thanks @qbit. This did not solve my problem but your idea of a parsing
error helped me to realize that it does not like having a space in the
source filename. That got me to move one step forward.
Edit 3:
There is a problem in Ubuntu 20.04 LTS.
$ LANG=C sudo apt install woeusb
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
woeusb : Depends: libwxgtk3.0-0v5 (>= 3.0.4+dfsg) but it is not installable
E: Unable to correct problems, you have held broken packages.
Until this problem with woeusb
is solved, you can use mkusb-plug according to this link:
help.ubuntu.com/community/mkusb/plug
The tool mkusb-tow
of mkusb-plug is now available also via dus (mkusb version 12.5.6). See this link
mkusb 12.5.6 with new installer for Windows
Edit 4:
A set of workaround commands for woeusb in Ubuntu 20.04 LTS is described in the following link,
NTFS partition service issue with creating Windows 10 bootable USB on Ubuntu
Edit 5:
Today (2021-10-16) I tested that mkusb can create working installer drives from a Windows 11 iso file.
WoeUSB это приложение для создания загрузочного носителя для операционных систем Windows из дистрибутива Linux
Если вы ищете, как установить и использовать WoeUSB, у нас уже есть статья а также видео, демонстрирующее весь процесс в деталях.
Когда «вилка упала»
Я использую WoeUSB в течение долгого времени, и ни разу мне не удавалось создать загрузочную флешку Windows с помощью программного обеспечения. Тем не менее, я постоянно вижу отчеты на нашем форуме, Диолинукс Плюсот людей, у которых был неприятный опыт с программой.
Именно в одном из этих отчетов я увидел, как пользователь объяснил, что он не может использовать программное обеспечение из-за печально известной «Ошибка 256», и именно в этот момент я понял, что уже получал такое же сообщение об ошибке раньше. Однако в моем случае мне всегда удавалось устранить это небольшое неудобство относительно простым способом.
В тот момент я решил воссоздать здесь, в моей системе, ситуацию, в которой возникает ошибка, чтобы задокументировать эффективный способ ее решения! И, наконец, вот руководство, предлагающее решение.
Сначала я расскажу, в какой ситуации возникает «Ошибка 256».
Во всех моих тестах эта ошибка возникала только тогда, когда я пытался использовать флешку, которая уже содержала записанный с нее образ какого-то дистрибутива Linux. Чтобы использовать USB-устройство с WoeUSB, оно должно быть отформатировано в fat32 и желательно пустым.
Это связано с тем, что способ разбиения и форматирования флеш-накопителя при получении загрузочного ISO из системы Linux несовместим с тем, как WoeUSB работает с файлами ISO Windows, и именно здесь «Me # д * »все происходит.
Чтобы использовать такое устройство с образом Windows, необходимо отформатировать его. Однако в этих случаях недостаточно просто щелкнуть «Формат», нам также необходимо создать новую таблицу разделов на устройстве.
Когда отображается «Ошибка 256», также отображается сообщение о том, что «целевое устройство в настоящее время занято, размонтируйте все разделы, установленные на целевом устройстве, и повторите попытку».
Оказывается, это сообщение может немного сбивать с толку, ведь при разборке целевого устройства (которым является флеш-накопитель) оно просто «исчезает» из системы, что делает невозможным его выбор в WoeUSB.
Для решения проблемы вы можете использовать приложение под названием «Gparted». После того, как вы установили его, откройте его и убедитесь, что ваше устройство флэш-памяти выбрано (вверху справа). Нажми на “устройство“А потом”Создать таблицу разделовВ появившемся диалоговом окне выберите «MSDOSИ затем нажмите «Применять».
После этого появится сообщение об ошибке, просто нажмите «игнорировать».
Теперь полностью отключите флэш-накопитель от USB-порта, подождите 5 секунд и замените его. Что сделано, в левом верхнем углу программы нажмите на меню «Gparted“А потом”Обновить устройства».
В верхнем левом углу Gparted нажмите «Создать новый раздел». В открывшемся окне, в поле «Файловая система“Выбрать”fat32“, в “метка«Введите все, что вы хотите (например,« Pen Drive »), а затем нажмите«Добавить».
Дождитесь завершения операции и в поле «Применение отложенных операций“щелкнуть”близко». Также закрой Gparted и иди!
Ваша флешка готова для получения изображения Windows через WoeUSB без проблем.
Вероятно, это одна из единственных причин, по которым у многих людей возникают проблемы с использованием WoeUSB. Исходя из моего опыта, это программа, которая всегда очень хорошо выполняла свою работу.
Я надеюсь, что, следуя этим советам, вы также сможете насладиться лучшим из WoeUSB. И избавьтесь от «головной боли» каждый раз, когда вам нужно создать загрузочный носитель Windows на Linux.
Были ли у вас проблемы при попытке использовать WoeUSB? Вы уже знали это решение? Расскажите в комментариях ниже о своем опыте работы с WoeUSB до и после этого совета. И если у вас есть еще лучший совет, обязательно поделитесь им с нами!
Вот и все, ребята! ?
When I try to create a Windows 10 bootable USB on my Linux Ubuntu 18.04 with WoeUSB it gives me this error:
Installation failed!
Exit code: 256
Log:
WoeUSB v@@WOEUSB_VERSION@@
==============================
Mounting source filesystem...
Error: File "/media/woeusb_source_1548324574_1839/sources/install.wim"
in source image has exceed the FAT32 Filesystem 4GiB Single File Size
Limitation and cannot be installed. You must specify a different --
target-filesystem.
Refer: https://github.com/slacka/WoeUSB/wiki/Limitations#fat32-
filesystem-4gib-single-file-size-limitation for more info.
Unmounting and removing "/media/woeusb_source_1548324574_1839"...
You may now safely detach the target device
My USB has 8GB of storage.
K7AAY
3,5723 gold badges22 silver badges39 bronze badges
asked Jan 24, 2019 at 10:12
1
As per a Microsoft forum and the explanation from WoeUSB shown above, the maximum size of a single file on a FAT32 device is 4 GiB. That file system uses a 32-bit field to store the file size in bytes, and 2^32 bytes = 4 GiB (actually, the real limit is 4 GiB minus one byte, or 4 294 967 295 bytes, because you can have files of zero length). {Thanks to a SuperUser poster a CVn for the explanation why).
Your file ‘install.wim’ is larger than 4 GiB, so it can’t be written to a FAT32 device. Sadly, Microsoft keeps putting more and more into the Windows installer, and it has grown larger than FAT32 will allow.
SOLUTION: Format the USB using NTFS which permits files >4 GiB before you create the LiveUSB. Right-click on the USB once inserted, and choose Format, then choose NTFS in the Type field.
When the USB drive is formatted, then open WoeUSB and it will allow you to create a LiveUSB with the huge Windows .WIM file.
answered Jan 24, 2019 at 18:21
K7AAYK7AAY
3,5723 gold badges22 silver badges39 bronze badges
0
I am using Ubuntu 18.04, woeUsb, 15 GB usb3 Stick, windows 10 64Bit ISO to create bootable device. I found few tutorials how to do it, but I still get error.
- Installation failed!
- Exit code: 256
Log:
WoeUSB v@@WOEUSB_VERSION@@
============================== Mounting source filesystem… Wiping all existing partition table and filesystem signatures in /dev/sda…
wipefs: error: /dev/sda: probing initialization failed: No medium
found The command «wipefs —all «${target_device}»» failed with exit
status «1», program is prematurely aborted Unmounting and removing
«/media/woeusb_source_1532252869_8362″… You may now safely detach
the target device
I tried to format my USB several times but nothing worked. I used FAT32 format. Should I first convert it to NTFS?
John Kens
1,5972 gold badges10 silver badges28 bronze badges
asked Jul 22, 2018 at 9:53
0
I have the same issue and found the solution by unmounting USB drive in this way,
Go to the Disks and select your USB drive from the left side menu, and click on the icon shown in the below image to unmount USB.
answered Apr 10, 2019 at 6:05
mitesh7172mitesh7172
6161 gold badge11 silver badges21 bronze badges
3
The command line version of the tool works better in my experience:
woeusb --device Win10_1909_English_x64.iso /dev/sdX --target-filesystem NTFS
/dev/sdX
might be different on your system such as sda sdb …, make sure to check the device path using gparted
or fdisk
.
Make sure to set the filesystem to NTFS with --target-filesystem NTFS
as FAT32 doesn’t support large files.
answered Feb 23, 2020 at 13:52
1
I found that you have to run the software with sudo because it requires the use of gparted. If you don’t do this it won’t succeed and exit. I suspect this is your problem. I had a similar problem.
answered Aug 17, 2018 at 15:34
Eamonn KennyEamonn Kenny
1,80117 silver badges19 bronze badges
2
I had the same problem but after surfing internet I found something like this: **
sudo woeusb —device image.iso /dev/sdb —tgt-fs NTFS —verbose
**. So in the command image.iso is the OS you downloaded(or the path to it), while the /dev… is the USB device and type of format(NTFS). Just copy the command, change image.iso to the path of your image.iso and change the /dev/sdb to the name of your USB device and make sure you are connected to internet because when I ran the command it seems it communicated with GitHub. Good luck I hope this will help if you haven’t found any answer.
answered Feb 25, 2019 at 15:39
There is no need to use any third party tool in the Windows operating system to create a bootable USB. Follow the below commands:
1. Plug your USB drive
2. Open Command Prompt
3. Type: diskpart .
4. Type list volume (this will show your drives)
5. Type sel vol h (h can be replaced with ur usb volume, can be anything g, h, i)
6. Type active
7. It will make your USB active, copy and paste windows files inside it.
kenlukas
3,4519 gold badges25 silver badges36 bronze badges
answered Aug 29, 2019 at 14:25
1
Добрый вечер, при создании загрузочной флешки Windows 10 в Woeusb под Linux Mint 20.2 Uma выдаёт ошибку. Насколько я понял, ошибка состоит в том, что на носителе недостаточно свободного места в связи с чем преждевременно заканчивает создание загрузочного диска, но при этом флешку использую объёмом 64 Гб. Вот текст ошибки:
Installation failed!
Exit code: 256
Log:
WoeUSB v3.3.1
==============================
Mounting source filesystem…
Wiping all existing partition table and filesystem signatures in /dev/sdc…
/dev/sdc: 2 байта стёрто по смещению 0x000001fe (dos): 55 aa
/dev/sdc: calling ioctl to re-read partition table: Выполнено
Ensure that /dev/sdc is really wiped…
Creating new partition table on /dev/sdc…
Creating target partition…
Making system realize that partition table has changed…
Wait 3 seconds for block device nodes to populate…
Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.
—2021-10-29 22:06:40— https://github.com/pbatard/rufus/raw/master/res/ue…
Распознаётся github.com (github.com)… 140.82.121.4
Подключение к github.com (github.com)|140.82.121.4|:443… pulse
соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… pulse
302 Found
Адрес: https://raw.githubusercontent.com/pbatard/rufus/ma… [переход]
—2021-10-29 22:06:40— https://raw.githubusercontent.com/pbatard/rufus/ma…
Распознаётся raw.githubusercontent.com (raw.githubusercontent.com)… 185.199.110.133, 185.199.111.133, 185.199.108.133, …
Подключение к raw.githubusercontent.com (raw.githubusercontent.com)|185.199.110.133|:443… pulse
соединение установлено.
HTTP-запрос отправлен. Ожидание ответа… pulse
200 OK
Длина: 1048576 (1,0M) [application/octet-stream]
Сохранение в каталог: ««/tmp/WoeUSB.rUdbeU.tempdir/uefi-ntfs.img»».
0K ………. ………. ………. ………pulse
. ………. 4% 727K 1s
50K ………. ………. ………. ………. …..pulse
….. 9% 848K 1s
100K ………. ………. ………. ………. ………. 14% 2,96M 1s
150K ………pulse
. ………. ………. ………. ………. 19% 4,04M 1s
200K ………. ………. ………. ………. ………. 24% 1,36M 1s
250K ………. ………. ………. ………. ……pulse
…. 29% 5,65M 0s
300K ………. ………. ………. ………. ………. 34% 6,05M 0s
350K ………. ………. ………. ………. ………. 39% 6,69M 0s
400K ………. ………. ………. ………. ………. 43% 7,87M 0s
450K ………. ………. ………. ………. ………. 48% 7,82M 0s
500K ………. .pulse
……… ………. ………. ………. 53% 1,91M 0s
550K ………. ………. ………. ………. ………. 58% 10,1M 0s
600K ………. ………. ………. ………. ………. 63% 11,1M 0s
650K ………. ………. ………. ………. ………. 68% 10,0M 0s
700K ………. ………. ………. ………. ………. 73% 11,4M 0s
750K ………. ………. ………. ………. ………. 78% 11,5M 0s
800K ………. ………. ………. ………. ………. 83% 11,6M 0s
850K ………. ………. ………. ………. ………. 87% 10,3M 0s
900K ………. ………. ………. ………. ………. 92% 11,6M 0s
950K ………. ………. ………. ………. ………. 97% 11,9M 0s
1000K ………. ………. …. 100% 13,3M=0,3s
2021-10-29 22:06:41 (3,38 MB/s) — «/tmp/WoeUSB.rUdbeU.tempdir/uefi-ntfs.img» сохранён [1048576/1048576]
dd: запись в ‘/dev/sdc2’: На устройстве не осталось свободного места
1025+0 записей получено
1024+0 записей отправлено
524288 байт (524 kB, 512 KiB) скопирован, 0,0682348 s, 7,7 MB/s
The command «dd if=»${download_directory}/uefi-ntfs.img» of=»${uefi_ntfs_partition}»» failed with exit status «1», program is prematurely aborted
Unmounting and removing «/media/woeusb_source_1635534382_5428″…
You may now safely detach the target device
Пожалуйста помогите решить проблему. Заранее спасибо
Forum rules
Before you post please read how to get help. Topics in this forum are automatically closed 6 months after creation.
-
[Jonathan_C_Linux]
- Level 1
- Posts: 25
- Joined: Fri Dec 28, 2018 9:30 pm
- Location: North Charleston, South Carolina
WoeUSB not working / Exit Code: 256
When I try to add the Windows 10 ISO to my flash drive I get an error of (Exit Code: 256). The USB drive is formatted as NTFS and is unmounted but it won’t install.
Mounting source filesystem…
Error: File «/media/woeusb_source_1546743561_19723/sources/install.wim» in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation and cannot be installed. You must specify a different —target-filesystem.
Refer: https://github.com/slacka/WoeUSB/wiki/L … limitation for more info.
Unmounting and removing «/media/woeusb_source_1546743561_19723″…
You may now safely detach the target device
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
-
trytip
- Level 14
- Posts: 5311
- Joined: Tue Jul 05, 2016 1:20 pm
Re: WoeUSB not working / Exit Code: 256
Post
by trytip » Sun Jan 06, 2019 1:14 am
this means your flash drive is not large enough to hold the win10 iso. i just formatted my really old 8GB flash drive which i have formatted maybe 1000 times to fat32 and i have no issue making windows usb out of it. what is the full name of your win10 iso called? are you trying to make a bootable iso from an .exe update?
did you format your flash drive with the Usb stick Formatter?
Last edited by trytip on Sun Jan 06, 2019 3:39 pm, edited 1 time in total.
-
[Jonathan_C_Linux]
- Level 1
- Posts: 25
- Joined: Fri Dec 28, 2018 9:30 pm
- Location: North Charleston, South Carolina
Re: WoeUSB not working / Exit Code: 256
Post
by [Jonathan_C_Linux] » Sun Jan 06, 2019 3:07 pm
I have formatted the USB drive to NTFS multiple times using USB Stick Formatter, GParted, and Disks. All formatting attempts have been successful but the ISO won’t install. The USB drive has 31 GB of storage space. The ISO file name is : Win10_1809Oct_English_x64.iso
-
trytip
- Level 14
- Posts: 5311
- Joined: Tue Jul 05, 2016 1:20 pm
Re: WoeUSB not working / Exit Code: 256
Post
by trytip » Sun Jan 06, 2019 4:24 pm
rightclick on the .iso and Open With «Disk Image Mounter» but more than likely your copy of install.esd is larger than 4GB which woeusb can’t handle. is this an official microsoft .iso?
try open gparted, select your flash drive and under devices > create new partition table > msdos > EXIT and format with USB FORMATTER NTFS
not sure if woeusb works with ntfs since it does install grub but fat32 will give you a limit at 4GB
you need to get an OFFICIAL copy of windows 10 or create the usb in other windows os with the Windows USB/DVD Download Tool
-
Vilis
- Level 1
- Posts: 11
- Joined: Sat Apr 23, 2016 4:09 pm
Re: WoeUSB not working / Exit Code: 256
Post
by Vilis » Mon May 13, 2019 1:15 pm
I have the same identical problem using Cinnamon 18.3, but I went further in analyzing it. I installed the Ubuntu repository for WoeUSB, and ran WoeUSB. My copy of Windows 7 Pro is the official Microsoft OEM compatible version, because I have an OEM MS Win. 7 Pro license sticker on my computer, which the local Microsoft rep guided me by phone to verify — it verified as good. Then the Microsoft rep guided me to create a bootable USB stick on a Windows 7 Pro machine I have, using 100% Microsoft software, and that procedure produced a bootable USB stick using my official MS .iso file of OEM Windows 7 Pro 64bit.
So I have a working copy of a USB stick with official MS Win 7 Pro .iso installed on it, made entirely using Windows software, not Linux, to compare with my WoeUSB. Both copies, my 100% Microsoft copy, and my WoeUSB copy are IDENTICAL on my computer screen, plugged in side by side into my computer, until the instant that the WoeUSB installation finishes, when suddenly it crashes in the last milllisecond of installation, and after that millisecond the two copies are no longer identical, but radically different!
Conclusion: THIS IS A VALID COMPLAINT, WHICH I HAVE VALIDATED AS CORRECT, needing attention by the gurus on this forum. The previous guru was wrong in his conclusions.
-
Vilis
- Level 1
- Posts: 11
- Joined: Sat Apr 23, 2016 4:09 pm
Re: WoeUSB not working / Exit Code: 256
Post
by Vilis » Mon May 13, 2019 1:26 pm
My Error Exit code was 512
That is the only difference, besides the fact that the original poster was installing Windows 10 and I was installing Windows 7. This confirms that WoeUSB is not working on Linux Mint 18.3
-
Vilis
- Level 1
- Posts: 11
- Joined: Sat Apr 23, 2016 4:09 pm
Re: WoeUSB not working / Exit Code: 256
Post
by Vilis » Mon May 13, 2019 1:40 pm
PS there is no question that WoeUSB correctly formats the USB stick (I used an 8GB USB) to NTFS, because when I pre-formatted my USB stick to NTFS first, WoeUSB would NOT PROCEED to install my Microsoft OEM Win. 7 Pro .iso file into my USB stick. Only when I pre-formatted that stick to FAT 32, would WoeUSB proceed to format it to NTSF, and to complete its attempted creation of a bootable USB installer for Windows 7, where it failed at the bitter end, giving an Error code of 512 (presumably related to the Exit code 256.
Because local Microsoft rep successfully guided me in producing an OEM Microsoft Win 7 Pro bootable USB stick formatted first to NTSF, NOT FAT 32, I can attest that the original complaint in this thread is 100% valid in every neccessary detai, and that WoeUSB does not work on LinuxMint Cinnamon 18.3, and also does not work on Linux Mint Cinnamon 19.xx according to similar complaints on the internet.
-
Vilis
- Level 1
- Posts: 11
- Joined: Sat Apr 23, 2016 4:09 pm
Re: WoeUSB not working / Exit Code: 256
Post
by Vilis » Mon May 13, 2019 1:53 pm
The official freely downloadable from Microsoft OEM Windows 7 Pro 64bit version I am using and also attempting to install on several properly license stickered computers IS 5.9 GIGABYTES because it includes everything uptated to 2019 in a single .iso file. So the USB stick has to be at least 8 Gigabytes, and it must be formatted to NTSF, not to FAT 32, because FAT 32 cannot handle any file bigger than 4 GB.
Because I have one 8GB USB stick formatted to be bootable loaded with this latest OEM Win 7 Pro .iso file MADE 100% BY THE MICROSOFT REP ON MY WORKING WINDOWS 7 PRO COMPUTER GUIDING ME, WHIC WORKS PERFECTLY, I can confirm that WoeUSB works 99.9% perfectly until the bitter end millisecond of installation on the USB stick, when at that bitter end it crashes, and in my case produces an Exit code 512. Internet reports the same problem under Cinnamon 19.xx.
-
MrEen
- Level 23
- Posts: 18353
- Joined: Mon Jun 12, 2017 8:39 pm
Re: WoeUSB not working / Exit Code: 256
Post
by MrEen » Mon May 13, 2019 3:50 pm
Vilis wrote: ↑
Mon May 13, 2019 1:15 pm
Conclusion: needing attention by the gurus on this forum.
Actually, if this is indeed a bug, this should be reported to the WoeUSB developer(s) on their github page here: https://github.com/slacka/WoeUSB/issues
You may want to try following the instructions here to see if that changes anything.
And take note of the last bit on the page with the instructions:
Everything should work as normal — though I’m told the app may spit an error out but that the actual USB will still boot/install fine — but if it doesn’t you can file bugs on the WoeUSB Github page.
P.S. I am not a guru, I have never used WoeUSB, and I’ve never stayed at a Holiday Inn Express.
- Status
- Not open for further replies.
-
- Nov 28, 2018
-
- 3
-
- 0
-
- 10
- 0
-
#1
Exit code: 256
Log:
WoeUSB v@@WOEUSB_VERSION@@
==============================
Mounting source filesystem…
Error: File «/media/woeusb_source_1543574182_9100/sources/install.wim» in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation and cannot be installed. You must specify a different —target-filesystem.
Refer: https
Unmounting and removing «/media/woeusb_source_1543574182_9100″…
You may now safely detach the target device
———————————————
I’ve formatted my usb to NTFS, then EXFAT, then back again. I’ve unmounted the usb. Been doing this for four hours, and it refuses to work. I’m using linux Mint 18.1 cinnamon.
I’ve tried forcing woeUSB to creat the bootable via «$ sudo woeusb —device Win10_1860Oct_English_x64.iso /dev/sdb»
Didn’t Work.
I’ve tried so many things. Why doesn’t windows just distribute the bootable files rather than only the ISO?
-
- May 8, 2014
-
- 59
-
- 0
-
- 4,610
-
- 17
-
- May 8, 2014
-
- 59
-
- 0
-
- 4,610
- 17
-
- Nov 28, 2018
-
- 3
-
- 0
-
- 10
- 0
-
#3
when I go to the media creation tool page I get this:
«You’ve been routed to this page because the operating system you’re using won’t support the Windows 10 media creation tool and we want to make sure you can download Windows 10…You can use this page to download a disc image (ISO file) that can be used to install or reinstall Windows 10. The image can also be used to create installation media using a USB flash drive or DVD.»
Thus I’m stuck creating a bootable on my own. However, windows requires a special process in order to make it bootable, and WoeUSB, to my knowledge at this point, is the only progam capable of doing so on Linux.
-
- May 8, 2014
-
- 59
-
- 0
-
- 4,610
- 17
-
#4
-
#5
Exit code: 256
Log:
WoeUSB v@@WOEUSB_VERSION@@
==============================
Mounting source filesystem…
Error: File «/media/woeusb_source_1543574182_9100/sources/install.wim» in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation and cannot be installed. You must specify a different —target-filesystem.
Refer: https
Unmounting and removing «/media/woeusb_source_1543574182_9100″…
You may now safely detach the target device
———————————————
I’ve formatted my usb to NTFS, then EXFAT, then back again. I’ve unmounted the usb. Been doing this for four hours, and it refuses to work. I’m using linux Mint 18.1 cinnamon.
I’ve tried forcing woeUSB to creat the bootable via «$ sudo woeusb —device Win10_1860Oct_English_x64.iso /dev/sdb»
Didn’t Work.
I’ve tried so many things. Why doesn’t windows just distribute the bootable files rather than only the ISO?
I have the EXACT same problem as you, what i am doing is, Downloading Windows 10 32-bit, because its ISO is 3,3 GiB , and from there, i am going to Win10 64-bit. Through the Media Creation Tool
-
- Nov 28, 2018
-
- 3
-
- 0
-
- 10
- 0
-
#6
Exit code: 256
Log:
WoeUSB v@@WOEUSB_VERSION@@
==============================
Mounting source filesystem…
Error: File «/media/woeusb_source_1543574182_9100/sources/install.wim» in source image has exceed the FAT32 Filesystem 4GiB Single File Size Limitation and cannot be installed. You must specify a different —target-filesystem.
Refer: https
Unmounting and removing «/media/woeusb_source_1543574182_9100″…
You may now safely detach the target device
———————————————
I’ve formatted my usb to NTFS, then EXFAT, then back again. I’ve unmounted the usb. Been doing this for four hours, and it refuses to work. I’m using linux Mint 18.1 cinnamon.
I’ve tried forcing woeUSB to creat the bootable via «$ sudo woeusb —device Win10_1860Oct_English_x64.iso /dev/sdb»
Didn’t Work.
I’ve tried so many things. Why doesn’t windows just distribute the bootable files rather than only the ISO?
I have the EXACT same problem as you, what i am doing is, Downloading Windows 10 32-bit, because its ISO is 3,3 GiB , and from there, i am going to Win10 64-bit. Through the Media Creation Tool
That’s a clever solution. I ended up emulating Windows thru VirtualBox, then running Rufus within that to create the USB bootable. I spent 3 days trying to reinstall windows on my machine. What an adventure in technological mayhem.
- Status
- Not open for further replies.
Thread starter | Similar threads | Forum | Replies | Date |
---|---|---|---|---|
B
|
Solved! Apple Community Reload Error | Apps General Discussion | 4 | Jun 14, 2022 |
K
|
Question cache deleted in error | Apps General Discussion | 1 | Apr 25, 2022 |
|
Question How do I update my computer because I have an error? | Apps General Discussion | 0 | Apr 12, 2022 |
C
|
Question Photoshop Elements 2021 error codes 81 and 501 won’t allow installation? How to fix. | Apps General Discussion | 1 | May 5, 2021 |
|
Question How to fix“ ERROR-invalid argument/option — ‘Live’ ” in this code? | Apps General Discussion | 0 | Jul 21, 2019 |
|
Question PUBG Lite launcher error | Apps General Discussion | 2 | Jul 1, 2019 |
|
Question Win dos shell syntax error | Apps General Discussion | 2 | Apr 11, 2019 |
I
|
Solved! Getting error 502 Bad Gateway, is it proxy or website itself | Apps General Discussion | 5 | Jan 23, 2019 |
B
|
Solved! No OS is able to be installed | Apps General Discussion | 1 | Jan 19, 2019 |
R
|
Solved! how ro get help from webshots | Apps General Discussion | 1 | Jan 16, 2019 |
C
|
Solved! Sony Vegas 14 Black screen error | Apps General Discussion | 1 | Jan 7, 2019 |
J
|
Most games get error message | Apps General Discussion | 4 | Jan 1, 2019 |
J
|
I just publish a video and went to veiw it it was getting ready to play then it said play back error please help me i want to | Apps General Discussion | 1 | Dec 12, 2018 |
F
|
MS Office 2013 bootstrap error after reviewing forum posts no solution | Apps General Discussion | 1 | Nov 18, 2018 |
|
Solved! Strange text error in Chrome | Apps General Discussion | 1 | Oct 27, 2018 |
K
|
Solved! WinRAR error — The instruction at 0x80024785 referenced memory at 0x25c61000. The memory could not be written. | Apps General Discussion | 3 | Oct 21, 2018 |
I
|
Solved! How to fix youtube playback error | Apps General Discussion | 5 | Oct 16, 2018 |
K
|
Solved! install error «Compatibility Assistant» Corel dvd moviefactory 7 | Apps General Discussion | 4 | Oct 7, 2018 |
J
|
Design Garage doesn’t start up. | Apps General Discussion | 1 | Oct 1, 2018 |
J
|
Error Code: M7701-1003 | Apps General Discussion | 1 | Sep 22, 2018 |
- Advertising
- Cookies Policies
- Privacy
- Term & Conditions
- Topics