Stuck on "Installing GRUB bootloader for legacy PC booting support..." about woeusb-ng HOT 45 CLOSED

The same problem there. Waited for 20 minutes already on "Installing Grub for legancy..."

from woeusb-ng.

Use Ventoy it just saved my day!

from woeusb-ng.

For those coming here, canceling the "Installing GRUB boot-loader for legacy PC booting support..." step will still finish with a successful message.

Before un-mounting, make sure to kill the "grub-install" process. After that, I could install windows 10 on a different PC without any problems

from woeusb-ng.

And I confirm process ends up successfully after a few hours.

from woeusb-ng.

The issue still presists. Why isn't there any option for user to disable legacy bios option? Make a tick-box for the GUI until you get it this sorted out.

from woeusb-ng.

Info: Installing GRUB bootloader for legacy PC booting support...
Installing for i386-pc platform.
Installation finished. No error reported.
Info: Installing custom GRUB config for legacy PC booting...
Info: Done :)

It worked, eventually. However it's a UX sin to have something take 1hour without any message whatsoever.

Make sure you use command line, otherwise the KDE window froze for me after a while and had to terminate it.

sudo woeusb --target-filesystem NTFS --device win11.iso /dev/sdb

from woeusb-ng.

I don't believe that installing grub on a flash drive should take multiple hours. Its a few mb that have to be written. When the 6G windows image takes only a few minutes to be written. I bet there is a faster way to do this.

The whole of this has to be solved by the people who maintain grub-install. But you could only install minimal grub modules, maybe the compress option does something as well?

Also why is there no option like --skip-legacy-boot?

from woeusb-ng.

Also an issue on Arch linux. Currently waiting 3 hours... At this moment it makes the software entirely unusable.

from woeusb-ng.

Confirmed, next day the process was finished and everything works

from woeusb-ng.

I saw that someone said it took 2 hours and almost lost is. It finished after about 20 mins for me

from woeusb-ng.

why is this issue closed? i'm experiencing it as are other people

from woeusb-ng.

reporting back since it still seems to be a problem for a lot of users. since the issue stems from grub-install taking long on cheap pen-drives due to a lot of i/o (and getting it fixed upstream would involve lots of headaches), wouldn't a solution be to first generate the complete image for the stick on the main os disk (or even in ram) and then write that over? the install process itself is device-agnostic, so should work on non-device files as well

from woeusb-ng.

After sometime (less then an hour), it finished without any error. Everything worked fine.
[Just a bit of patience is needed. I can live with it and am happy ]

from woeusb-ng.

UPD:
i was needed to wait more.. and all went fine. about 10 mins

from woeusb-ng.

For me and all other people that still needs BIOS support, skipping GRUB2 Legacy step is not an option. What is exactly causing this bug?

from woeusb-ng.

I just installed woeusb on ubuntu using the installation method recommended by woeusb (pip3) and the same thing happened,the gui is stuck for about 10 minutes.

from woeusb-ng.

Currently having this issue still after several hours. Was the flag to disable the legacy grub option ever introduced?

from woeusb-ng.

@recalderon I'm curious, is there a reason to use woe over something like balena etcher?

I tried to use balena before woeusb, but it gave me a warning about some boot config that windows image needs and they doesnt support right now....

from woeusb-ng.

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.

from woeusb-ng.

We are still experiencing this issue with the latest release of woeusb-ng. The latest woeusb-ng is v0.2.10.

Could you release a new version soon, please?

from woeusb-ng.

also facing this issue on arch linux.
Here are the logs when running as root using windows 10 21H2 iso
It seems to get stuck after the installing for i386 pc platform line. I am using x86_64 if that makes a difference.

umount: /media/woeusb_target_1666247380_886682: target is busy.
umount: /media/woeusb_target_1666247380_886682: target is busy.
/dev/sdb: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
/dev/sdb: calling ioctl to re-read partition table: Success
Cluster size has been automatically set to 4096 bytes.
Creating NTFS volume structures.
mkntfs completed successfully. Have a nice day.
Installing for i386-pc platform.

Note, I checked the options and enabled
use NTFS and set boot flag and it still hung as before but it creates a bootable media that I can use, since I will be using UEFI anyways.
Although, im not entirely sure if enabling these options are what solved the issue. ymmv

from woeusb-ng.

I've been also encountering the problem of getting stuck at "Installing GRUB bootloader for legacy PC booting support..." with ubuntu 22.04 to burn win10 installer on an usb.

In the first place, is this process of installing GRUB bootloader is necessary for a computer which was bought in 2022?

from woeusb-ng.

@g-cyan that would depend. For the most part, most BIOS have switched to UEFI instead of tradtitional BIOS. So yeah, unless you explicitly set 'legacy only' in your BIOS, then legacy boot is not required. Especially since secure boot is now being adopted as a default on newer motherboards, UEFI should be supported.

Another caveat I can think of, is if you wanted your windows install to be legacy for whatever reason, you would only be able to perform a UEFI windows install.

from woeusb-ng.

same problem

from woeusb-ng.

Same problem

from woeusb-ng.

For those coming here, canceling the "Installing GRUB boot-loader for legacy PC booting support..." step will still finish with a successful message.

Before un-mounting, make sure to kill the "grub-install" process. After that, I could install windows 10 on a different PC without any problems

What about I want to install in same PC? I need it right? because I want go back to Wins again.

from woeusb-ng.

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.

I tried to install from source, still blocking.
I can see it is blocking on installing for i386-pc platform

from woeusb-ng.

The same problem there. Waited for 20 minutes already on "Installing Grub for legancy..."

It says Could not open Boot Directory: [10] Volume Corrupt

from woeusb-ng.

Had the same issue. Noticed it is referenced in the FAQ : https://github.com/WoeUSB/WoeUSB/wiki/F.A.Q., where they are talking of up to 2 jours of waiting. Launching experiment now..

from woeusb-ng.

same problem, in my case i need legacy support so just waiting and waiting...

from woeusb-ng.

Add a note so not every one has to Google. For me it's not a big case cause how often do we create an stick...

from woeusb-ng.

sooo.. nothing yet? anyone?

from woeusb-ng.

@invictus2010 I agree, this shouldn't be closed. There are some of us that had to wait over 1 hour without any UI indicator of what's happening.

from woeusb-ng.

https://github.com/WoeUSB/WoeUSB/wiki/F.A.Q.#why-does-the-drive-preparation-took-so-long-when-the---target-filesystem-is-set-to-ntfs

Going to sleep now. I'll have a look when i wake up if it finished :)

from woeusb-ng.

It happens to still getting stuck after 12 hours... No way this is normal.

from woeusb-ng.

Also an issue on ubuntu 22... woeusb's last edition available.

from woeusb-ng.

@recalderon I'm curious, is there a reason to use woe over something like balena etcher?

from woeusb-ng.

Also having the issue with ubuntu 22.04 and 0.2.12

from woeusb-ng.

@sebnapi does it supports windows images?

from woeusb-ng.

from woeusb-ng.

Use Ventoy it just saved my day!

Thankyouuuuu!!!

from woeusb-ng.

Still getting this issue and it take me 2.5 Hours and still not Finished.
Not just it take too long, it making my system so slow as well. CPU and Memory usage are seems normal though.
After Canceling the process my system is running fast as normal again, not sure why.

Copied 5.2GiB from a total of 5.2GiB
/support/logging/en-us/actionqueueetw.dll.mui
Copied 5.2GiB from a total of 5.2GiBased with EFI support, applying workaround to make it support UEFI booting
99%
INFO: Detected existing EFI bootloader, workaround skipped.
Installing GRUB bootloader for legacy PC booting support...
Installing for i386-pc platform. <-- stuck on here

Tried Ventoy as sugested above and it worked like a charm for my Windows instalation. Thank You!

from woeusb-ng.

Use Ventoy it just saved my day!

Shiny new bootable creator on the block

from woeusb-ng.

Still getting this issue! using arch btw

from woeusb-ng.

So, this has been fixed in the WoeUSB-ng package -- you will have to manually install that and also use command line
Extremely annoying, but it works
https://github.com/WoeUSB/WoeUSB-ng
Command will look like
sudo woeusb --target-filesystem NTFS --device ~/Downloads/Win11_23H2_English_x64v2.iso /dev/sda --workaround-skip-grub

from woeusb-ng.