-
Notifications
You must be signed in to change notification settings - Fork 107
problem with W10 ISO + agfm (UEFI) + USB to SATA bridges - system will halt or reboot #271
Comments
Can you try renaming \boot\grubfm\config file so it is not used by Easy2Boot please? |
did, nothing changed here's a video: https://youtu.be/NWAN-WU8TnU if it can be of any help |
@zme-ul AIO Boot uses a1ive grub2, hope you will try it |
You told me grubfm MBR boot also fails in similar way? Is that correct? So it is not just a UEFI issue? |
no, MBR boot works without issues - the issues it's only exhibiting in UEFI mode yes, latest BIOS in both mobos |
Could you please try booting with this menu entry ("Boot ISO (map)") and see if you can boot to the Windows installation screen? |
yes, with ISO (map) booted trough ps: just last few days GigaByte released a new BIOS (F10h) for this mobo but it did not fix the current issue - the rev 1.1 board didn't received this update yet |
found a laptop that won't boot the W10 iso agfm UEFI, gets stuck at the text screen HP 250 G7 model 175R5EA managed to get it installed switching to Ventoy UEFI |
updated agfm to 1.69d I get a new piece of information that might be helpful: zx file corrupted or unsupported block options |
1.69f is today's build. |
same behavior and output |
I think it's possible that the uefi firmware has a problem with the sata driver. |
I noticed this particular problem only on two systems, both with Z390 chipsets, both GigaByte mobos
my system, GigaByte Z390 Gaming X rev 1.0 - system will reboot when trying to boot any of the W10 ISOs with afgm
a client's PC, GigaByte Z390 Gaming X rev 1.1 - system will hang at a black screen with white text with the same ISOs
the problems occur only when using (m.2) SATA to USB enclosures (tested with AsMedia chip and JMicron), IT DOES NOT occur when using regular flash drives - I do not have access to NVMe to USB enclosures to test with
it does not matter if it's plugged into the USB 3 or USB 2 ports on the mobo
Steve Si (Easy2Boot author) recommended I test with Ventoy, so I did - I can confirm the W10 ISOs will boot properly with Ventoy (1.0.22 release tested)
The text was updated successfully, but these errors were encountered: