same as https://github.com/slacka/WoeUSB/issues/251
this version is 'ng' but still has this bug?

Good Habit Checklist for Issue Reporting

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

Run pip install woeusb-ng under a local environment (pyenv, virtualenv)

Expected Behavior

The package gets installed successfully and creates executables under the appropriate bin/ folder

Current Behavior

error: [Errno 13] Permission denied: '/usr/local/bin/woeusbgui'

Info of My Environment

WoeUSB Version

0.2.0

Information about the Operating System

Manjaro Linux

I am pretty sure that's not what should be happening:

x@ubuntu:~/WoeUSB-ng$ sudo env PYTHONPATH=. WoeUSB/woeusb --device /dev/sr0 /dev/sdd
Error: WoeUSB requires 7z command in the executable search path, but it is not found.
Dependencies are not met
Warning: The following partitions will be unmounted: ['sysfs', '', 'on', '', '/sys', '', 'type', '', 'sysfs', '', '(rw,nosuid,nodev,noexec,relatime)', '', 'proc', '', 'on', '', '/proc', '', 'type', '', 'proc', '', '(rw,nosuid,nodev,noexec,relatime)', '', 'udev', '', 'on', '', '/dev', '', 'type', '', 'devtmpfs', '', '(rw,nosuid,relatime,size=214892k,nr_inodes=53723,mode=755)', '', 'devpts', '', 'on', '', '/dev/pts', '', 'type', '', 'devpts', '', '(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)', '', 'tmpfs', '', 'on', '', '/run', '', 'type', '', 'tmpfs', '', '(rw,nosuid,noexec,relatime,size=49272k,mode=755)', '', '/dev/sda2', '', 'on', '', '/', '', 'type', '', 'ext4', '', '(rw,relatime,data=ordered)', '', 'securityfs', '', 'on', '', '/sys/kernel/security', '', 'type', '', 'securityfs', '', '(rw,nosuid,nodev,noexec,relatime)', '', 'tmpfs', '', 'on', '', '/dev/shm', '', 'type', '', 'tmpfs', '', '(rw,nosuid,nodev)', '', 'tmpfs', '', 'on', '', '/run/lock', '', 'type', '', 'tmpfs', '', '(rw,nosuid,nodev,noexec,relatime,size=5120k)', '', 'tmpfs', '', 'on', '', '/sys/fs/cgroup', '', 'type', '', 'tmpfs', '', '(ro,nosuid,nodev,noexec,mode=755)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/unified', '', 'type', '', 'cgroup2', '', '(rw,nosuid,nodev,noexec,relatime)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/systemd', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)', '', 'pstore', '', 'on', '', '/sys/fs/pstore', '', 'type', '', 'pstore', '', '(rw,nosuid,nodev,noexec,relatime)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/memory', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,memory)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/rdma', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,rdma)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/hugetlb', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,hugetlb)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/net_cls,net_prio', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/perf_event', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,perf_event)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/cpu,cpuacct', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/blkio', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,blkio)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/freezer', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,freezer)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/cpuset', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,cpuset)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/devices', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,devices)', '', 'cgroup', '', 'on', '', '/sys/fs/cgroup/pids', '', 'type', '', 'cgroup', '', '(rw,nosuid,nodev,noexec,relatime,pids)', '', 'systemd-1', '', 'on', '', '/proc/sys/fs/binfmt_misc', '', 'type', '', 'autofs', '', '(rw,relatime,fd=25,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=13566)', '', 'mqueue', '', 'on', '', '/dev/mqueue', '', 'type', '', 'mqueue', '', '(rw,relatime)', '', 'hugetlbfs', '', 'on', '', '/dev/hugepages', '', 'type', '', 'hugetlbfs', '', '(rw,relatime,pagesize=2M)', '', 'debugfs', '', 'on', '', '/sys/kernel/debug', '', 'type', '', 'debugfs', '', '(rw,relatime)', '', 'configfs', '', 'on', '', '/sys/kernel/config', '', 'type', '', 'configfs', '', '(rw,relatime)', '', 'fusectl', '', 'on', '', '/sys/fs/fuse/connections', '', 'type', '', 'fusectl', '', '(rw,relatime)', '', 'shared', '', 'on', '', '/media/vbox', '', 'type', '', 'vboxsf', '', '(rw,nodev,relatime)', '', 'lxcfs', '', 'on', '', '/var/lib/lxcfs', '', 'type', '', 'fuse.lxcfs', '', '(rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other)', '', '/var/lib/snapd/snaps/core_10444.snap', '', 'on', '', '/snap/core/10444', '', 'type', '', 'squashfs', '', '(ro,nodev,relatime,x-gdu.hide)', '', '/var/lib/snapd/snaps/core_10577.snap', '', 'on', '', '/snap/core/10577', '', 'type', '', 'squashfs', '', '(ro,nodev,relatime,x-gdu.hide)', '', 'tmpfs', '', 'on', '', '/run/user/1000', '', 'type', '', 'tmpfs', '', '(rw,nosuid,nodev,relatime,size=49268k,mode=700,uid=1000,gid=1000)', '']
umount: /sys: target is busy.
Target device is busy, please make sure you unmount all filesystems on target device or shutdown the computer before detaching it.

We must check usb capacity and if lower than iso, we must show error message.

As per the title, there is no clear instruction in the README that tells users how to run it, or maybe I am missing something?

I installed woeusb-ng from the AUR, and when i tried to run it on a terminal i get this error message:

Traceback (most recent call last):
  File "/usr/bin/woeusbgui", line 33, in <module>
    import WoeUSB.gui
  File "/usr/lib/python3.9/site-packages/WoeUSB/__init__.py", line 1, in <module>
    from WoeUSB import \
  File "/usr/lib/python3.9/site-packages/WoeUSB/core.py", line 15, in <module>
    import WoeUSB.utils as utils
  File "/usr/lib/python3.9/site-packages/WoeUSB/utils.py", line 9, in <module>
    import WoeUSB.miscellaneous as miscellaneous
  File "/usr/lib/python3.9/site-packages/WoeUSB/miscellaneous.py", line 7, in <module>
    translation = gettext.translation("woeusb", os.path.dirname(__file__) + "/locale", [locale.getlocale()[0]], fallback=True)
  File "/usr/lib/python3.9/gettext.py", line 587, in translation
    mofiles = find(domain, localedir, languages, all=True)
  File "/usr/lib/python3.9/gettext.py", line 558, in find
    for nelang in _expand_lang(lang):
  File "/usr/lib/python3.9/gettext.py", line 213, in _expand_lang
    loc = locale.normalize(loc)
  File "/usr/lib/python3.9/locale.py", line 403, in normalize
    code = localename.lower()
AttributeError: 'NoneType' object has no attribute 'lower'

I've updated my whole system, and also reinstalled the package after doing a full removal of it

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSB by running woeusbgui
2. Do select Windows ISO file
3. Select Install

Current Behavior

WoeUSB errors with message "Installation Failed! Error: grub-install or grub2-install command not found!"

Info of My Environment

WoeUSB Version

Lastest using sudo apt install git p7zip-full python3-pip python3-wxgtk4.0 then sudo pip3 install WoeUSB-ng

WoeUSB Source

https://github.com/WoeUSB/WoeUSB-ng

Information about the Operating System

Description: Pop!_OS 21.04

Information about the Source Media

"Windows 10 X64 20H2 Pro OEM ESD MULTi-7 MARCH 2021 {Gen2}" downloaded from https://1337x.to/torrent/4803921/Windows-10-X64-20H2-Pro-OEM-ESD-MULTi-7-MARCH-2021-Gen2/

Information about the Target Device

USB Kingston DT100G3 16GB

• [ yes] I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• [ yes] I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced

OS : ArchLinux
woeusb-gui installed from AUR, version - 0.2.10

The program is not creating the efi bootloader named efi/boot/bootx64.efi properly. In my case a 0 bytes sized file "bootx64.efi" is created which obviously is useless. The ISOs I tested are Win7-professional, ultimate, and enterprise.

I tried the old version of the program too, it also yielded same results.

How to fix it?

Hello,

following the installation instruction I got some errors for missing command.
I had to add a couple of dependencies that were not present on my system (MX Linux/debian):

python3-setuptools and python3-wheel (or pip3 install wheel)

Maybe they should be added on the instruction set.

Best regards,
Anselmo

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

Right now, creating an IMG or ISO file (in legacy mode) from a provided ISO is no supported via this tool directly. However, there is a workaround via a loopback device.
But that approach is ugly and needs a lot of workarounds

# Create a sparse-file of sufficient size
truncate install.img -s 6G
# Create a loopback device from that sparse-file
sudo losetup -fP install.img
# Create symlinks, so the internal "sanity check" of WoeUSB does not error out.
# The reason is, that WoeUSB recognizes "numbers" at the end of a supplied target as partition. However /dev/loop0 is a device. And if we set the --device option, WoeUSB recognizes the target as a partition and aborts
# Furthermore, WoeUSB assumes the partions following the pattern <the_device><partition_numbe>, while for a device with already a number at its end, the convention is <device>p<partition_number>
# So we create some symlinks to fool WoeUSB
sudo ln -s /dev/loop0 /dev/lb
sudo ln -s /dev/loop0p1 /dev/lb1
sudo ln -s /dev/loop0p2 /dev/lb2
# Now finally run WoeUSB
sudo woeusb --device source.iso /dev/lb

Expected Behavior

A --file option should just create an IMG or even better, an iso file (with --iso option).

Current Behavior

No support for writing raw images or iso-files

Info of My Environment

WoeUSB Version

v0.2.7

WoeUSB Source

WoEUSB-ng from AUR (Arch)

Information about the Operating System

Manjaro

Information about the Source Media

Win10_Edu_21H1_German_x64.iso

Information about the Target Device

Request for file. Right now: Loopback device.

I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSB from Apps list in GNOME
2. Enter Sudo password

Expected Behavior

Program Opens when launched

Current Behavior

WoeUSB will throw up the screen asking for privileges, then nothing happens

Info of My Environment

WoeUSB Source

Installed using pip as the instructions showed for Fedora as well as building from source

Information about the Operating System

Fedora 34 Workstation running GNOME 40

There are no instructions on how to execute, how do you execute this?

Thanks in advance.

The flash drive isn't seen in BIOS to start the boot. I tried ticking the option on to use NTFS and formatting the flash drive to FAT32, but nothing.

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Expected Behavior

Write access 😄

Current Behavior

ERROR: Permission to WoeUSB/WoeUSB-ng.git denied to WaxyMocha.

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSB GUI
   2.install windows 21h2 64bit

Expected Behavior

No error

Current Behavior

It stucks on 1.6 gb

Info of My Environment

gnome 3.38

WoeUSB Version

0.2.9

WoeUSB Source

installed from repo files
with pip

Information about the Operating System

Zorin OS 16.1

Information about the Source Media

windows 10 2021 h2 64 bit

Information about the Target Device

kingston Data Traveler 104 32 gb usb 2.0

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• [x ] I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

Installed dependencies, then attempted the second install step which failed

phil@Desktop-PC:~$ sudo pip3 install WoeUSB-ng
Collecting WoeUSB-ng
  Downloading https://files.pythonhosted.org/packages/a4/7d/2872b53d9d713f0a3eb5952ad3df8e2bf23184baa2e00fe803830852e884/WoeUSB-ng-0.2.5.tar.gz
    Complete output from command python setup.py egg_info:
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "/usr/lib/python3.7/tokenize.py", line 447, in open
        buffer = _builtin_open(filename, 'rb')
    FileNotFoundError: [Errno 2] No such file or directory: '/tmp/pip-install-1len5mx7/WoeUSB-ng/setup.py

----------------------------------------

Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-install-1len5mx7/WoeUSB-ng/
phil@Desktop-PC:~$ `

Expected Behavior

Install succeeds

Current Behavior

Install Fails

Info of My Environment

WoeUSB Version

N/A

WoeUSB Source

Followed the readme

Information about the Operating System

Debian 10

Information about the Source Media

N/A

Information about the Target Device

N/A

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSB by running woeusbgui
2. authenticate with root password
3. receive the error

Expected Behavior

woeusbgui not to give the error

Current Behavior

WoeUSB errors with message:

polkit-agent-helper-1: error response to PolicyKit daemon: GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: 
No session for cookie
==== AUTHENTICATION FAILED ====
Error executing command as another user: Not authorized

Info of My Environment

WoeUSB Version

WoeUSB-ng-0.2.10

WoeUSB Source

Built from source code, commit 69a430d7498cf3b2af4f0b86ebb2d108cbc5989a

Information about the Operating System

Gentoo Base System release 2.7

Information about the Source Media

Didn't get to use any, irrelevant.

Information about the Target Device

irrelevant.

• [✓] I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• [✓] I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch Woeusbgui.
2. Choose iso and disk required.
3. Click Install.

Current Behavior

Proceeds with installation without any warnings.

Expected Behavior

Shows a warning before proceeding (i.e Are you sure? This will delete all the files and wipe out the selected partition.)

Hi, I'm trying to create a Windows 10 USB with WoeUSB using the latest 20H2, the installation "succeeds" but there's nothing on the flash and it doesn't appear on the boot menu, or sometimes you can't even mount the filesystem again, WoeUSB is definitely doing something to the USB since it heats up when WoeUSB is "copying" the files (normal behavior of flash drives to heatup when in use btw) if you need any screenshot/photos or logs I can provide you with them

OS: Xubuntu 20.10
WoeUSB version: Compiled from Github
Windows 10 ISO: Spanish (Mexico) 20H2

Extra Notes:

using gparted to manually format the flash drive to ntfs gives errors, using gnome disk utility also gives errors, It might be something wrong with my OS not being able to correctly handle ntfs filesystems, but I don't know how I can fix that :P

Hi,

I'm not sure if it's useful for others but I fixed some glitches I found in the original core.py:

1. Removed pseudo progress bar feature. WoeUSB-NG uses a timer progress bar which actually does not show actual progress which is just a decoration.
2. Switched buffered write to sync-IO write. WoeUSB-NG uses buffered write to write Windows files to the USB disk. This would cause potential disk loss issues and would take a longer time when OS initiates write-back.
3. Added additional writing progress information to show the actual data writing process. This is useful for users to understand how much data is written already in the USB disk rather than pseudo progress data.

The patched version is here: https://github.com/meow-watermelon/woeusb-ng-patches

If you think it's useful, I will raise a PR for a permanent fix.

Thanks.

Issue Reproduce Instructions

1. Launch WoeUSB by running command

woeusb --verbose  --tgt-fs NTFS --device en_windows_server_2012_vl_x64_dvd_917758.iso /dev/sdb

2. Output with errors
   

Expected Behavior

No error

Current Behavior

WoeUSB errors with message "[Errno 2] No such file or directory: 'grub-install': 'grub-install'"

Info of My Environment

WoeUSB Version

v0.2.6

WoeUSB Source

Built from source code, v0.2.6

Information about the Operating System

Tested in Vmware guest, CentOS Linux release 7.6.1810 (Core)

Information about the Source Media

en_windows_server_2012_vl_x64_dvd_917758.iso

Information about the Target Device

A Vmware scsi disk

Debugging

In the test environment(Centos7.6), there is no command named 'grub-install', 'grub2-install' exists.
I go through the source code and find where it happens. It happened in function 'check_runtime_dependencies' in file WoeUSB/utils.py, where called shutil.which() to judge which command to use.

It's the if clause matter. when a command, say, 'grub-install' does not exists, shutil.which() returns None instead of ''.
I tested shutil.which() in python3 interpreter.

It's a convention to write such kind of if clause as follows

·```
grub = ["grub-install", "grub2-install"]
for command in grub:
    if shutil.which(command):
        grub = command
        break
```

or

·```
grub = ["grub-install", "grub2-install"]
for command in grub:
    if shutil.which(command) is not None:
        grub = command
        break
```

Problem

woeusb command failed with errors "<urlopen error [Errno -2] Name or service not known>"

Test Environment

(1) OS: CentOS Linux release 7.6.1810 (Core), it's a vmware guest, say, centos76-vm.
(2) WoeUSB-ng: 0.2.6

How to reproduce

(1) Add scsi disk (/dev/sdb) to centos76-vm
(2) excute woeusb command as follows

woeusb --tgt-fs NTFS -d en_windows_server_2012_vl_x64_dvd_917758.iso /dev/sdb

Expected

build successfully

Actual

build failed

More infomation

It looks like this has a similar issue to slacka/WoeUSB#206: The USB creation failed, then after I renamed the iso file, it succeeded.

Good Habit Checklist for Issue Reporting

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

0. I installed the latest release (v0.2.10), which I see is also the latest development version.
1. I launched it with /usr/local/bin/woeusbgui
2. I selected my iso: a Windows 10 21H1 named Windows 10 [bits 64] [down 2021-07-14] [name Win10_21H1_English_x64].iso
3. I selected my target device - a 7.4GB Kanguru USB drive
4. I hit "Install"

Then I renamed the iso to its original filename (Win10_21H1_English_x64.iso) and tried again. It succeeded this time.

Expected Behavior

It actually installs the iso onto the USB drive

Current Behavior

It returns instantly with an installation succeeded message. But in the console it gives the traceback I pasted below.

Info of My Environment

WoeUSB Version

v0.2.10

WoeUSB Source

Installed from the release .tar.gz according to the README

• using sudo python3 -m pip install .

Information about the Operating System

Ubuntu 20.04.3 LTS

Information about the Source Media

Windows 10 version 21H1

• Win10_21H1_English_x64.iso
• sha256sum: 6911e839448fa999b07c321fc70e7408fe122214f5c4e80a9ccc64d22d0d85ea

Information about the Target Device

Kanguru Flashblu 30 8GB

Traceback

$ /usr/local/bin/woeusbgui 
Exception in thread Thread-2:
Traceback (most recent call last):
  File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
    self.run()
  File "/usr/local/lib/python3.8/dist-packages/WoeUSB/gui.py", line 403, in run
    core.main(source_fs_mountpoint, target_fs_mountpoint, self.source, self.target, "device", temp_directory,
  File "/usr/local/lib/python3.8/dist-packages/WoeUSB/core.py", line 155, in main
    if utils.check_source_and_target_not_busy(install_mode, source_media, target_device, target_partition):
  File "/usr/local/lib/python3.8/dist-packages/WoeUSB/utils.py", line 151, in check_source_and_target_not_busy
    if check_is_target_device_busy(source_media):
  File "/usr/local/lib/python3.8/dist-packages/WoeUSB/utils.py", line 134, in check_is_target_device_busy
    if re.findall(device, mount) != []:
  File "/usr/lib/python3.8/re.py", line 241, in findall
    return _compile(pattern, flags).findall(string)
  File "/usr/lib/python3.8/re.py", line 304, in _compile
    p = sre_compile.compile(pattern, flags)
  File "/usr/lib/python3.8/sre_compile.py", line 764, in compile
    p = sre_parse.parse(p, flags)
  File "/usr/lib/python3.8/sre_parse.py", line 948, in parse
    p = _parse_sub(source, state, flags & SRE_FLAG_VERBOSE, 0)
  File "/usr/lib/python3.8/sre_parse.py", line 443, in _parse_sub
    itemsappend(_parse(source, state, verbose, nested + 1,
  File "/usr/lib/python3.8/sre_parse.py", line 598, in _parse
    raise source.error(msg, len(this) + 1 + len(that))
re.error: bad character range 1-0 at position 55

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSB with the gnome launcher menu
2. Insert an USB or an external hard drive or an internal hard drive
3. Try to write a windows 10 ISO

Expected Behavior

Having the ISO written on the drive

Current Behavior

WoeUSB errors with message

[Errno 13] Permission denied: '/dev/sdX2'

Info of My Environment

WoeUSB Version

tested on :
v0.2.5
v0.2.5-18-g445789d

Information about the Operating System

NAME=Fedora
VERSION="33 (Workstation Edition)"
ID=fedora
VERSION_ID=33
VERSION_CODENAME=""
PLATFORM_ID="platform:f33"
PRETTY_NAME="Fedora 33 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:33"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=33
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=33
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation

Information about the Source Media

Windows 10 English

Information about the Target Device

Sandisk 16 gb USB Key
Two Hard drives : one seagate and one toshiba.

Issue Reproduce Instructions

Fresh Install Of Ubuntu 20.04.02 LTS Restart Open Terminal Update List And Upgrade Packages Restart Install WoeUSB-ng Format The USB In Disk to Fat32 Make Sure The USB Is not Mounted And Open WoeUSB Copy The 4.9GB Windows ISO To Flash Drive USING Fat32 Not NTFS Since ISO Is ONLY 4.9GB And The Install ESD

Expected Behavior

No error

Current Behavior

Copys files to USB Fasters than USB Speeds and then when i try running the USB from Boot Override IT List it But Stays in BIOS

WoeUSB Source

Downloaded using Python Pip3
Installed from Ubuntu 20.04.02 Archive

Information about the Operating System

Ubuntu 20.04.02 LTS With All Packages Up To Date

Information about the Source Media

Windows 11 ISO Built Using UUPDump

Information about the Target Device

SanDisk Cruzer Spark USB 2.0

With Secure Boot enabled, I was not able to boot a usb key made with woeusbgui

I don't know if it is expected or not.
A mention about Secure Boot in the README.md would be appreaciated, wheter this is expected to work or fail.

I had to make a usb key with the Microsoft Media Creatin Tool to be able to boot a Windows Live usb.

Looking for help! I've been trying basically everything( woeusb, deepinbootmaker, manual paritioning ) nothing works. The farthest I could get is running windows setup with an error (no device drivers detected). Any ideas?
OS: Deepin 20

Hi guys, this is the first issue I open on github so please apologize me if I made any mistake.
I just wanted to share my humble attempt to draw a Gnome HIG compliant icon ("compliant" at best, I'm not a pro designer in any way) for this awesome utility that saved me so much time and hassles.
I don't know if you like it or ever need it, but I'll be pleased if it can be any helpful!
Cheers,
Lorenzo

PS. I'm open to suggestions and critics

• [✓ ] I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• [ ✓] I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Flash the latest Windows 10 ISO 20H2 with WoeUSB on an USB
2. Restart your PC and see that the device doesn't show up for efi boot
3. look at the partition manager for the device and it's on MBR instead GPT

Expected Behavior

It uses GPT for uefi booting

Current Behavior

It uses MBR for uefi booting

System Information

WoeUSB Version

v0.2.5-18-g445789d

WoeUSB Source

Built from source commit: N/A

Information about the Operating System

Xubuntu 20.10/Ubuntu 20.10

Information about the Source Media

Windows 10 Full Edition downloaded from: here

Information about the Target Device

Hitachi HTS542512K9SA00 with an external hard drive case

As it is, the program assumes that the source is a DVD image, mounts it and gets files from it.
Suggestion is to allow a directory as a source (which contains the files that would normally be on a DVD).
This would save the phase of creating a .iso when making a custom Windows install stick (where you edit/add files on the "DVD").

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

EDIT: @brlin-tw : Fix Markdown markup

Issue Reproduce Instructions

1. Launch WoeUSB by running woeusbgui
2. Write windows image

Expected Behavior

Nice file names

Current Behavior

Ugly cyrillic file names like: �оказа�� ��ил� ди�ка

Info of My Environment

WoeUSB Version

0.2.10-2

WoeUSB Source

Installed from PyPi

Information about the Operating System

Pop!_OS 20.04 LTS x64

Information about the Source Media

"Windows 10"

Information about the Target Device

SP SD card 8GB (USB 3.0 cardrider)

Gnome on some distributions appears to not work well with GUI's started as root. I don't have an solution for this outside of redesigning how GUI interfaces with core. For now you can try to use KDE or other DE, or just use terminal, there it should work well.

Hey there to the creatures to WoeUSB-Ng I'm wondering if I can make a windows 10 legacy bootup usb ive tried to look for it or ways on how to do it but cant seem to find anything is legacy bootup in this version of WoeUSB or no

I am currently packaging this repo for nixpkgs, which is used by NixOS.
My current progress can be seen here: NixOS/nixpkgs#149382
Currently I managed to get the cli-tool working. The gui does not work currently, due to the polkit-actions needed, which are a bit tricky on NixOS.

This repo contains binaries woeusb and woeusbgui .
My main question is:
Should both of them be shipped in a single package, or do you prefer them to be split up?

similar to #251 from the old repo, but still not reported here

Issue Reproduce Instructions

Launch woeusbgui, select ISO and USB-Stick, click install

Expected Behavior

installation completed within reasonable time

Current Behavior

stuck on "Installing GRUB bootloader for legacy PC booting support..." for a very long time (>30min), but completes successfully eventually.

Info of My Environment

WoeUSB Version

0.2.10

WoeUSB Source

woeusb-ng from aur

Information about the Operating System

EndeavourOS on 5.16.12-arch1-1

Information about the Source Media

official Win10_21H2_German_x64.iso

Information about the Target Device

Intenso Speedline 32GB

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSBGUI by running woeusbgui
2. Receive the following error immediately:

  File "/usr/local/bin/woeusbgui", line 5
SyntaxError: Non-ASCII character '\xc2' in file /usr/local/bin/woeusbgui on line 6, but no encoding declared; see http://python.org/dev/peps/pep-0263/ for details

Expected Behavior

Expected the GUI to start.

Current Behavior

GUI does not start.

Info of My Environment

WoeUSB Version

tjcarter@chiyo:~$ pip3 show woeusb-ng
Name: WoeUSB-ng
Version: 0.2.0
Summary: WoeUSB-ng is a simple tool that enable you to create your own usb stick windows installer from an iso image or a real DVD. This is a rewrite of original WoeUSB. 
Home-page: http://github.com/WoeUSB/WoeUSB-ng
Author: Jakub Szymański
Author-email: [email protected]
License: GPL-3
Location: /usr/local/lib/python3.8/dist-packages
Requires: termcolor, wxPython
Required-by: 

WoeUSB Source

Installed using pip3 install woeusb-ng

Information about the Operating System

tjcarter@chiyo:~$ lsb_release -d
Description:    Debian GNU/Linux bullseye/sid
tjcarter@chiyo:~$ python3 --version
Python 3.8.2
tjcarter@chiyo:~$ dpkg -l grub-pc-bin grub-efi-amd64-bin ntfs-3g dosfstools git p7zip-full python3-pip python3-wxgtk4.0
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name               Version           Architecture Description
+++-==================-=================-============-==================================================================
ii  dosfstools         4.1-2             amd64        utilities for making and checking MS-DOS FAT filesystems
ii  git                1:2.25.1-1        amd64        fast, scalable, distributed revision control system
ii  grub-efi-amd64-bin 2.04-5            amd64        GRand Unified Bootloader, version 2 (EFI-AMD64 modules)
ii  grub-pc-bin        2.04-5            amd64        GRand Unified Bootloader, version 2 (PC/BIOS modules)
ii  ntfs-3g            1:2017.3.23AR.3-3 amd64        read/write NTFS driver for FUSE
ii  p7zip-full         16.02+dfsg-7      amd64        7z and 7za file archivers with high compression ratio
ii  python3-pip        18.1-5            all          Python package installer
ii  python3-wxgtk4.0   4.0.7+dfsg-2      amd64        Python 3 interface to the wxWidgets Cross-platform C++ GUI toolkit

Different OS distributions provides different characteristics and may influence the result of running WoeUSB. Run lsb_release --description or lsb_release -d in a terminal to acquire this information.

Information about the Source Media

Windows 10 build 1909, downloaded from Microsoft directly

Information about the Target Device

SanDisk 16GB

When linux_make_writeback_buffering_not_suck() tries to close /proc/sys/vm/dirty_background_bytes after writing "0", python throws exception:

OSError: [Errno 22] Invalid argument

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
OSError: [Errno 22] Invalid argument

This exception is not thrown when saving different numbers.

the french translation contains a string with a typo:

#: ../../../gui.py:58
msgid "&File"
msgstr "$Fichier"

One needs to replace the $ with a &

Hello,

no, no issue. It´s just a question :-)
Today I created a bootable Windows 10 image using WoeUSB-ng to repair my sisters notebook.
I am really happy that I found this tool to help me.
After that I noticed there is no german translation.
So I toke that pot file and did some work on it.
I will upload it here to this project, alright?

Kind regards from Germany

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSB by running <command>
2. Do blablabla...

Expected Behavior

No error

Current Behavior

WoeUSB errors with message "blablabla"

Info of My Environment

WoeUSB Version

For source code build, run git describe --tags --always --dirty under the source tree, for prebuilt releases refer the source that provides WoeUSB

WoeUSB Source

Built from source code, commit abcdefg
Installed from Ubuntu 16.04 software archive

Information about the Operating System

Different OS distributions provides different characteristics and may influence the result of running WoeUSB. Run lsb_release --description or lsb_release -d in a terminal to acquire this information.

Information about the Source Media

"Windows 9 Professional Edition" downloaded from https://microsoft.com/download/windows-9

Information about the Target Device

Transcend JetFlash® 790K 64GB (USB 3.1 variant)

• [*] I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed

Issue Reproduce Instructions

1. Install WoeUSB-ng on
2. No shortcut created in Applications menu

Expected Behavior

WoeUSB-ng shortcut in applications menu

Current Behavior

WoeUSB-ng has no shortcut
Note: /usr/share/applications/WoeUSB-ng.desktop seems to not exist

Info of My Environment

WoeUSB Version:0.2.10

Information about the Operating System

Fedora Linux 35 (KDE Plasma spin)
Debian Bookworm (testing) (KDE Plasma)

I think is the same issue than https://github.com/WoeUSB/WoeUSB/issues/81

(checked on different systems and pen-drives)

$ woeusbgui
/dev/sde: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sde: calling ioctl to re-read partition table: Èxit
Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.
Exception in thread Thread-2:

Traceback (most recent call last):
File "/usr/lib/python3.8/threading.py", line 932, in _bootstrap_inner
self.run()
File "/usr/local/lib/python3.8/dist-packages/WoeUSB/gui.py", line 403, in run
core.main(source_fs_mountpoint, target_fs_mountpoint, self.source, self.target, "device", temp_directory,
File "/usr/local/lib/python3.8/dist-packages/WoeUSB/core.py", line 177, in main
install_uefi_ntfs_support_partition(target_device + "2", temp_directory)
File "/usr/local/lib/python3.8/dist-packages/WoeUSB/core.py", line 381, in install_uefi_ntfs_support_partition
shutil.copy2(download_directory + "/uefi-ntfs.img", uefi_ntfs_partition)
File "/usr/lib/python3.8/shutil.py", line 435, in copy2
copyfile(src, dst, follow_symlinks=follow_symlinks)
File "/usr/lib/python3.8/shutil.py", line 275, in copyfile
_fastcopy_sendfile(fsrc, fdst)
File "/usr/lib/python3.8/shutil.py", line 166, in _fastcopy_sendfile
raise err from None
File "/usr/lib/python3.8/shutil.py", line 152, in _fastcopy_sendfile
sent = os.sendfile(outfd, infd, offset, blocksize)
OSError: [Errno 28] No space left on device: '/tmp/WoeUSB.t03_1bwr/uefi-ntfs.img' -> '/dev/sde2'

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed
• I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

Issue Reproduce Instructions

1. Launch WoeUSB by running <command>
2. Do blablabla...

Expected Behavior

No error

Current Behavior

WoeUSB errors with message "blablabla"

Info of My Environment

WoeUSB Version

For source code build, run git describe --tags --always --dirty under the source tree, for prebuilt releases refer the source that provides WoeUSB

WoeUSB Source

Built from source code, commit abcdefg
Installed from Ubuntu 16.04 software archive

Information about the Operating System

Different OS distributions provides different characteristics and may influence the result of running WoeUSB. Run lsb_release --description or lsb_release -d in a terminal to acquire this information.

Information about the Source Media

"Windows 9 Professional Edition" downloaded from https://microsoft.com/download/windows-9

Information about the Target Device

Transcend JetFlash® 790K 64GB (USB 3.1 variant)

Use this bootable USB drive on Linux to rescue Windows users | Opensource.com

Cheers!

Please consider adding Mac support, it seems to be a real headache preparing bootable ISOs from Mac.

I'm sorry to ask this but can WoeUSB flash Linux iso also if woeusb can't do that right now can we implement it ?

Good Habit Checklist for Issue Reporting

Checkout Mastering Markdown · GitHub Guides if you needs help on the GitHub-flavored Markdown syntax. You may remove sections and contents that don't apply.

• [ x] I've searched the issue tracker and is pretty sure that there's no duplicate issue already filed

• [x ] I've built the latest development snapshot using the instructions in README and verified that the issue can still be reproduced (for bug reports)

• Used the AUR package: https://aur.archlinux.org/packages/woeusb-ng

Issue Reproduce Instructions

I am unable to write a Windows USB via the gui due to this bug

I tried using NTFS and a Windows 10 image but still does it.

here is a log of what it shows via gist:
https://gist.github.com/coreybruce/7054bfff64046334b7b91a8449e26e65

Expected Behavior

Write usb without issue

Current Behavior

WoeUSB errors with message "blablabla"

Info of My Environment

WoeUSB Version

Version 0.2.10-1

For source code build, run git describe --tags --always --dirty under the source tree, for prebuilt releases refer the source that provides WoeUSB

WoeUSB Source

Built from source code, commit abcdefg
Installed from Ubuntu 16.04 software archive

Information about the Operating System

Different OS distributions provides different characteristics and may influence the result of running WoeUSB. Run lsb_release --description or lsb_release -d in a terminal to acquire this information.

Information about the Source Media

"Windows 9 Professional Edition" downloaded from https://microsoft.com/download/windows-9

Information about the Target Device

Transcend JetFlash® 790K 64GB (USB 3.1 variant)

WoeUSB v3.3.1

Mounting source filesystem...
Wiping all existing partition table and filesystem signatures in /dev/sdb...
/dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/sdb: 8 bytes were erased at offset 0xef0420400 (gpt): 45 46 49 20 50 41 52 54
/dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aa
/dev/sdb: calling ioctl to re-read partition table: Success
Ensure that /dev/sdb is really wiped...
Creating new partition table on /dev/sdb...
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 00:00:36-- https://github.com/pbatard/rufus/raw/master/res/uefi/uefi-ntfs.img
SSL_INIT
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving github.com (github.com)... 13.234.210.38
Connecting to github.com (github.com)|13.234.210.38|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://raw.githubusercontent.com/pbatard/rufus/master/res/uefi/uefi-ntfs.img [following]
--2021-10-29 00:00:42-- https://raw.githubusercontent.com/pbatard/rufus/master/res/uefi/uefi-ntfs.img
SSL_INIT
Resolving raw.githubusercontent.com (raw.githubusercontent.com)... 185.199.108.133, 185.199.109.133, 185.199.110.133, ...
Connecting to raw.githubusercontent.com (raw.githubusercontent.com)|185.199.108.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1048576 (1.0M) [application/octet-stream]
Saving to: ‘/tmp/WoeUSB.TKeoTw.tempdir/uefi-ntfs.img’

uefi-ntfs.img 100%[=========================================>] 1.00M 1.89MB/s in 0.5s

2021-10-29 00:00:43 (1.89 MB/s) - ‘/tmp/WoeUSB.TKeoTw.tempdir/uefi-ntfs.img’ saved [1048576/1048576]

dd: writing to '/dev/sdb2': No space left on device
1025+0 records in
1024+0 records out
524288 bytes (524 kB, 512 KiB) copied, 0.0926324 s, 5.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_1635445831_25094"...
You may now safely detach the target device

It hangs for me and many people, yes it's due to bad performance but I have UEFI, I don't need this!

A flag to disable this, or a checkbox in the GUI would be super appreciated.