-
Notifications
You must be signed in to change notification settings - Fork 134
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Woeusb-gui is creating an empty file for bootx64.efi, windows 7. #72
Comments
This was added in #70, I just haven't pushed new release yet. You can install the woeusb-ng from source to get that functionality. |
oh, wrong issue |
No, I was writing for #71 and sent it here |
I see, so any idea how to fix my issue? |
I'm creating a bootable drive in virtual machine to confirm the issue, I'll get back to you when I'm done. |
Just FYI, this is where I obtained the untouched ISOs https://[redacted] |
Firstly, I'm not clicking this link. Secondly, So, if this is an issue that breaks the functionally for you, I don't think I can help you, maybe you can hack the code to change download link. |
No offense, but it's an archive, what are you browsing the web on, windows XP? |
The woeusb-ng creates fat partition for uefi, and then downloads image of that partition form the link I given you. All files that are in uefi partition come from this image, if you get empty files that means that the image was corrupted in some way. |
If I'm not mistaken that image file is only downloaded when the ISO install image is larger than 4GB in which case an NTFS partition is created and the image file is downloaded form the web. Here it says that, Line 362 in 4d4910b
Those are said to be uefi-ntfs bootloader, also looking at the file size the bootx64.efi present in the image, it is only 27KB while the actual windows bootloader bootx64.efi is over 500KB. In workaround.py, it can be seen that the program is trying to open the install.wim file and extract a certain efi file which is then renamed as bootx64.efi. WoeUSB-ng/WoeUSB/workaround.py Line 100 in 4d4910b
My skills are not perfect but please look into it. I'm guessing some bug is preventing the proper extraction of that file. Could you please check? |
By the way, I can open the comment history and find the link. I would advise you to delete the comment if you truly wish to remove it. |
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?
The text was updated successfully, but these errors were encountered: