Woeusb ошибка 256

asked Jun 26, 2018 at 13:20

Below steps worked for me for windows 7 bootable pendrive in ubuntu-18.04

Step 1: Download the latest bash file from the release of the WoeUSB page https://github.com/WoeUSB/WoeUSB/releases

Step 2: Fix the missing executable file permission chmod +x path/to/woeusb-N.N.N.bash

Step 3: Install GParted sudo apt-get install gparted

Step 4: Start gparted ui interface

Step 5: Select your drive by top-right dropdown
delete your whole partition using GParted ( Don’t create a new partition after that )

Step 6: Make bootable Pendrive ( sudo ./woeusb-N.N.N.bash —target-filesystem NTFS —device path/to/windows.iso /dev/sdX )

 wget https://github.com/WoeUSB/WoeUSB/releases
 
 sudo apt install gparted
 cp /home/devops/Downloads/woeusb-5.2.4.bash .
 
 
 chmod 777 woeusb-5.2.4.bash 
 sudo ./woeusb-5.2.4.bash  --target-filesystem NTFS --device /home/devops/Downloads/test/en_windows_7_ultimate_x64_dvd.iso  /dev/sdb
  
   sudo apt install wimtools

 # Install above package if you get below error and then rerun woeusb command  below it again
 
 # "error woeusb requires wimlib-imagex command in the executable search path, but it is not found"

   sudo ./woeusb-5.2.4.bash  --target-filesystem NTFS --device /home/devops/Downloads/test/en_windows_7_ultimate_x64_dvd.iso  /dev/sdb

answered Dec 31, 2021 at 19:24

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

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?

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

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.

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.

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.

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.